I recently reinstalled CentOS on a server for a client and then proceeded to install their WordPress web site on the fresh install of CentOS Linux. After working through various minor issues the WP site was up and functioning without issue but after a week or so they contacted me to let me know that they could no longer view items in their FAQ system via the WordPress administration site. The FAQ system is a WordPress plugin called FAQ Builder and is a great little system for frequently asked questions. Below I describe the error received when attempting to access the FAQ Builder admin and what I did to resolve the issue.32MB, 33554432 bytes, 64MB, allocate, apache, bytes, faq builder, fatal error, HTML/XHTML filter, kses, kses.php, maximum, memory allocation, memory size, memory_limit, PHP, php.ini, plugin, script, WordPress, wp-admin
Posts Tagged “fatal error”
Apr 01 2010
Mar 14 2010
After moving a WordPress site from one server to a brand new server I ran into an issue with one of the WordPress plugins called MM-Forms. The MM-Forms WordPress plugin allows you to easily create contact forms that will either email filled out forms to you, store those forms in the MySQL database, or both email you and store the results in the database. The issue was the fact that the contact form was not displaying on the page it was configured to display on. After digging around a bit I located the issue by looking in the Apache logs. The issue ended up being with the PHP function called imagetypes. Below I describe the actual error noticed in the Apache logs, the CentOS RPM package that will provide the PHP function that was missing, and the yum logs from installing the package.apache, CentOS, error, fatal error, function, gd, httpd, imagetypes, Linux, mm-forms, package manager, PHP, php function, php-gd, plugin, rpm package, undefined function, WordPress, yum
Dec 09 2009
In the process of creating a mirror image of a current WordPress to be used for development purposes I ran into a PHP error that I had not seen before. The current version of WordPress was working without issue but because many of the settings needed to be modified for the installation to work with a different domain pointed to it. Even after modifying the settings that I had modified in previous instances to make WordPress work with an updated domain name I was still getting an error related to the WordPress Theme. I enabled some PHP error logging, started looking for answers on the web, and then implemented some changes described below to resolve the error.error_log, error_logging, fatal error, function, IF, PHP, php.ini, read, template, theme, theme.php, WordPress, wp-include
Jun 04 2009
PHP Fatal error: Allowed memory size of 25165824 bytes exhausted (tried to allocate 491520 bytes) in /path/to/filePosted by alex in Errors
I received the below error during the process of a ZenCart shopping cart upgrade. The error was noticed when navigating through the ZenCart store admin via a web browser. I wanted to post a resolution because I wasn’t able to locate the exact resolution to my answer online and it took me awhile to locate the issue. Most of the resolutions I located on the Internet talked about modifying the post_max_size or other options located in the php.ini file however no matter what I changed these to I ended up receiving the same error.
Error: PHP Fatal error: Allowed memory size of 25165824 bytes exhausted (tried to allocate 491520 bytes) in /path/to/fileallocate, ascii, binary, error, exhausted, fatal error, FileZilla, FTP, PHP, php.ini, post_max_size, ZenCart
Mar 27 2009
This means nmake is not installed on your Windows PC. To install you need to downloading, extract, and place two files into your $PATH. Follow the couple steps below to install nmake on your PC. In my case I installed nmake on Windows XP.