<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Stratus - Magento 1 Guides on Webscale Product Documentation</title><link>https://docs.webscale.com/docs/reference/stratus/guides/magento-1/</link><description>Recent content in Stratus - Magento 1 Guides on Webscale Product Documentation</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.webscale.com/docs/reference/stratus/guides/magento-1/index.xml" rel="self" type="application/rss+xml"/><item><title>Stratus Magento 1 Guides - Cache Management</title><link>https://docs.webscale.com/docs/reference/stratus/guides/magento-1/cache-management/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/stratus/guides/magento-1/cache-management/</guid><description>&lt;div class="box" &gt;
 &lt;figure itemprop="associatedMedia" itemscope itemtype="http://schema.org/ImageObject"&gt;
 &lt;div class="img"&gt;
 &lt;img itemprop="thumbnail" src="https://docs.webscale.com/images/stratus/img/articles/cache_management.png" alt="magento-19"/&gt;
 &lt;/div&gt;
 &lt;a href="https://docs.webscale.com/images/stratus/img/articles/cache_management.png" itemprop="contentUrl"&gt;&lt;/a&gt;
 &lt;/figure&gt;
&lt;/div&gt;

&lt;p&gt;After clicking that link, you should see a full list of your caches, similar to below. The types of caches may vary depending on what extensions/FPCs or even Varnish modules you have enabled.&lt;/p&gt;

&lt;div class="box" &gt;
 &lt;figure itemprop="associatedMedia" itemscope itemtype="http://schema.org/ImageObject"&gt;
 &lt;div class="img"&gt;
 &lt;img itemprop="thumbnail" src="https://docs.webscale.com/images/stratus/img/articles/cache-management-2.png" alt="magento-83"/&gt;
 &lt;/div&gt;
 &lt;a href="https://docs.webscale.com/images/stratus/img/articles/cache-management-2.png" itemprop="contentUrl"&gt;&lt;/a&gt;
 &lt;/figure&gt;
&lt;/div&gt;

&lt;p&gt;In the above case, we see this site is using the standard Magento caches alongside Varnish through the Turpentine module. Caches that are invalidated with show up as &lt;strong&gt;Invalidated&lt;/strong&gt; in a red bubble under the &lt;strong&gt;Status&lt;/strong&gt; column. Invalidated is not necessarily bad, it just means the caches are out of date and could be serving older content.&lt;/p&gt;</description></item><item><title>Stratus Magento 1 Guides - Change Index Mode</title><link>https://docs.webscale.com/docs/reference/stratus/guides/magento-1/change-index-mode/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/stratus/guides/magento-1/change-index-mode/</guid><description>&lt;p&gt;The Magento 1.x indexer has two settings &lt;strong&gt;Update on Save&lt;/strong&gt; and &lt;strong&gt;Manual&lt;/strong&gt; update.  There are several ways to adjust this setting, but the easiest is via the Magento Admin.&lt;/p&gt;
&lt;p&gt;You can set it on Stratus by running this command via SSH from within the docroot of your Magento 1 install:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;$ php shell/indexer.php --mode-manual
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;To avoid problems when multiple updates are being performed that trigger automatic reindexing, set all indexers to manual. Otherwise, every time an object is saved, a full reindex will be triggered and any affected objects with dependencies might cause a deadlock. Symptoms of a deadlock include high CPU usage and MySQL errors. As a best practice, schedule indexing as a cron job or run it manually to prevent deadlocks from occurring.
Setting indexers to manual is a requirement under our &lt;a href="https://docs.webscale.com/reference/stratus/about-webscale-stratus/magento-requirements/"&gt;TOS&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Stratus Magento 1 Guides - Invoicing printing blank or 500 error</title><link>https://docs.webscale.com/docs/reference/stratus/guides/magento-1/invoicing-printing-blank-or-500-error/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/stratus/guides/magento-1/invoicing-printing-blank-or-500-error/</guid><description>&lt;p&gt;If you Googled this, you probably found yet another StackOverflow link – &lt;a class="external-link" style="line-height: 1.42857;" href="http://stackoverflow.com/questions/17022829/magento-blank-empty-page-whene-printing-invoice-on-backend" rel="nofollow"&gt;&lt;a href="http://stackoverflow.com/questions/17022829/magento-blank-empty-page-whene-printing-invoice-on-backend" target="_blank"&gt;http://stackoverflow.com/questions/17022829/magento-blank-empty-page-whene-printing-invoice-on-backend&lt;i class="ps-1 fa fa-external-link"&gt;&lt;/i&gt;&lt;/a&gt;
&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;u&gt;From the above link:&lt;/u&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Make a core override:&lt;/p&gt;
&lt;p&gt;Copy – [magento root]/lib/Zend/Pdf/FileParserDataSource.php&lt;/p&gt;
&lt;p&gt;To – [magento root]/app/code/local/Zend/Pdf/FileParserDataSource.php&lt;/p&gt;
&lt;pre&gt;Fixed it by commenting out __construct() and __destruct() methods in lib/Zend/Pdf/FileParserDataSource.php

// abstract public function __construct();

 /**
 * Object destructor. Closes the data source.
 *
 * May also perform cleanup tasks such as deleting temporary files.
 */
// abstract public function __destruct();
&lt;/pre&gt;
&lt;p&gt;Then clear Magento cache and test.&lt;/p&gt;</description></item><item><title>Stratus Magento 1 Guides - Log Cleaning</title><link>https://docs.webscale.com/docs/reference/stratus/guides/magento-1/log-cleaning/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/stratus/guides/magento-1/log-cleaning/</guid><description>&lt;h1 id="log-cleaning"&gt;Log Cleaning&lt;/h1&gt;
&lt;p&gt;A few of these tables are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;log_url&lt;/li&gt;
&lt;li&gt;log_url_info&lt;/li&gt;
&lt;li&gt;log_visitor&lt;/li&gt;
&lt;li&gt;log_visitor_info&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If these tables get very large, they can slow down your frontend and backend considerably (when you hit several hundred thousand rows).  To clean these manually, you can do so via the MYSQL command line with a query like this –&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;delete from log_url;delete from log_url_info;delete from log_visitor;delete from log_visitor_info;
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;With these cleared, you should lower the retention period via &lt;strong&gt;System-&amp;gt;Advanced-&amp;gt;System&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>Stratus Magento 1 Guides - Magento 1.9 Unknown cipher in list</title><link>https://docs.webscale.com/docs/reference/stratus/guides/magento-1/magento-1-9-unknown-cipher-in-list-tlsv1/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/stratus/guides/magento-1/magento-1-9-unknown-cipher-in-list-tlsv1/</guid><description>&lt;p&gt;This is fixed by adjusting one line of code.&lt;/p&gt;
&lt;p&gt;To correct this, in downloader/lib/Mage/HTTP/Client/Curl.php, change:&lt;/p&gt;
&lt;pre class=""&gt;$this\-\&amp;gt;curlOption(CURLOPT_SSL_CIPHER_LIST, 'TLSv1');&lt;/pre&gt;
&lt;p&gt;to&lt;/p&gt;
&lt;pre&gt; $this-&amp;gt;curlOption(CURLOPT_SSLVERSION, CURL_SSLVERSION_TLSv1);&lt;/pre&gt;</description></item><item><title>Stratus Magento 1 Guides - Patching Magento 1</title><link>https://docs.webscale.com/docs/reference/stratus/guides/magento-1/patching-magento-how-to-guide/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/stratus/guides/magento-1/patching-magento-how-to-guide/</guid><description>&lt;p&gt;The community patching tool applies EVERYTHING for you – &lt;a href="https://github.com/magesec/magesecuritypatcher" target="_blank"&gt;https://github.com/magesec/magesecuritypatcher&lt;i class="ps-1 fa fa-external-link"&gt;&lt;/i&gt;&lt;/a&gt;
&lt;/p&gt;</description></item><item><title>Stratus Magento 1 Guides - Product image uploader does not work</title><link>https://docs.webscale.com/docs/reference/stratus/guides/magento-1/product-image-uploader-does-not-work/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/stratus/guides/magento-1/product-image-uploader-does-not-work/</guid><description>&lt;p&gt;To fix this, you must patch your store. There are no exceptions. The malware involved has been compromising store security and leading to credit theft. Security outweighs convenience in this case, unfortunately.&lt;/p&gt;
&lt;p&gt;You may encounter issues such as –&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt; broken forms, getting to patch 8788 requires all previous patches will cause issues with form keys on custom templates, this can break things like the customer login or registrations, which we cannot support fixing, though our patch attempts to add them to all the forms we can detect&lt;/li&gt;
&lt;li&gt;the image uploader may remain broken after patching if there are core overrides, certain modules, or custom admin templates that affect it or rely on the old flash uploader. This is something else we cannot support fixing unfortunately&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Roughly 10% of patched stores run into some issue that we have seen. Let us know if you need assistance applying the latest patches.&lt;/p&gt;</description></item><item><title>Stratus Magento 1 Guides - Recommended Cookie Settings</title><link>https://docs.webscale.com/docs/reference/stratus/guides/magento-1/recommended-cookie-settings/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/stratus/guides/magento-1/recommended-cookie-settings/</guid><description>&lt;p&gt;In Magento 1 under **System-&amp;gt;Configuration-&amp;gt;Web **then &lt;em&gt;Session Cookie Management&lt;/em&gt; you will see a form like this:&lt;/p&gt;
&lt;p&gt;&lt;img src="https://docs.webscale.com/images/stratus/img/articles/cookie-settings.png" alt="cookies"&gt;&lt;/p&gt;
&lt;p&gt;In general, we recommend the following settings –&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Lifetime at least 86400 (1 day)&lt;/li&gt;
&lt;li&gt;Path /&lt;/li&gt;
&lt;li&gt;Cookie domain exactly matches your domain or is .example.com if you are using www in your domain name&lt;/li&gt;
&lt;li&gt;HTTP Only &lt;strong&gt;Yes&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Cookie Restriction Mode &lt;strong&gt;No&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="cookie-domain-issues"&gt;Cookie domain issues&lt;/h2&gt;
&lt;p&gt;The cookie domain can cause problems such as&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Failed customer logins&lt;/li&gt;
&lt;li&gt;Broken carts (products won’t add)&lt;/li&gt;
&lt;li&gt;Cart empties on page load&lt;/li&gt;
&lt;li&gt;Cart empties at checkout&lt;/li&gt;
&lt;li&gt;Cannot log into the Magento backend/admin&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Because of this, you may need to try various cookie domain settings depending on your exact site URL. For example, a sub-domain typically requires the cookie domain to match the sub-domain i.e. mysite.example.com exactly&lt;/p&gt;</description></item><item><title>Stratus Magento 1 Guides - Sales Reports are blank</title><link>https://docs.webscale.com/docs/reference/stratus/guides/magento-1/sales-reports-are-blank/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/stratus/guides/magento-1/sales-reports-are-blank/</guid><description>&lt;p&gt;This section requires generating the lifetime stats.  Do this via Reports → Refresh Statistics.&lt;/p&gt;
&lt;p&gt;Then &lt;strong&gt;Select All&lt;/strong&gt; and in the &lt;strong&gt;Actions&lt;/strong&gt; drop-down refresh lifetime stats.  This may take a while and once complete your reports should work.&lt;/p&gt;</description></item></channel></rss>