How to fix a WordPress Memory exhausted error on your blog.

WordPress

How to fix a WordPress Memory Exhausted error in the Cache.php

Many times a blogger will insert a plugin thinking that everything will be fine and you will see the results immediately but instead after activating the plugin you are shown after logging back into the admin area.

PHP Fatal error:  Allowed memory size of 33554432 bytes exhausted (tried to allocate 6253909 bytes) in #### on line ### leaving you with no method of getting to the admin area getting only a white screen with this message.

After doing some research the results were 3 simple updates that fixed the problem and brought back the web site.

Step #1 – Make sure you have a FTP account with a username / password to retrieve the necessary files as well as uploading files. If you only have the web hosting control panel you will need to have that username / password and can get the job done by using the file manager.

Step #2 – Open wp-includes/cache.php and enter after

ini_set('memory_limit','32M'); // set memory to prevent fatal error

Save the file and go on to the next step.

Step #3 – Create a .htaccess file for the wp-includes directory and insert the following lines:

# set memory limit for cache.php
php_value memory_limit 32M

Step #4 – The final step is to create a local php.ini file in the same directory (wp-includes) and insert this:

;; set memory limit for cache.php
memory_limit = 32M

That is all you have to do and your blog should be back up working. Always make sure you have backups of your entire WordPress site that includes the Admin – Content – Includes along with the initial set of WordPress files. Finally get a SQL backup from the database that you are using, either MySQL or MS SQL but you need to get a complete backup, download it to a local machine.

Every single time you are doing an update on WordPress the point is to have insurance, a bad plugin or widget can destroy your theme by an out of place tag. Always be on the safe side.

Microsoft will stop extended support in 2016

Microsoft will stop extended support for Products and SQL Server Versions in 2016

extended support ends in 2016

Extended support in 2016 for various Microsoft products will come to an end.  Losing extended support will be some of the older Internet Explorer browsers (IE) as well as some .NET framework 4 versions.  In April of this year, SQL Server 2005 also will lose extended support.

The loss of extended support means that Microsoft will stop issuing security patches for these products, which represents a potential security risk for organizations. The products won’t get any future hot fixes, although there’s an exception for software covered under Microsoft’s “custom support” contracts. That’s a potentially costly option, though, with costs going up after the first year.

As a long practice by Microsoft they have provided support for the older product lines as long as possible until they feel it is time to “retire” the product for good. There are countless Windows 98 machines out there as well as Windows XP regardless what Microsoft gives in their press releases. A product life cycle is valid up to the point where software updates are released, once a company has deemed they no longer will support with a group of QA or developers that product in the simple term is considered dead.

Over the years Microsoft has developed numerous software applications and sometimes they bail on a released product if the sales are low. That makes pure business sense but it is the method that Microsoft performs their announcements.

The various products such as Internet Explorer for the most part is not used by many people but instead Chrome or Firefox is leading in that department. As for SQL Server 2005 that is pretty critical because many companies will have to pay Microsoft for the upgrade and possibly a DBA to handle the migration which is a huge task.

For additional information click here.