System Required

Many common issues that you may run into such as: white screen, demo content fails when importing, message “Fatal error: Allowed memory size of xxxxxx bytes exhausted” empty page content and other similar issues… are all related to low PHP configuration limits. The solution is to increase the PHP limits. You can do this by your own by following these steps as below:

Change the memory limit in your php.ini

To fix the Allowed memory size exhausted error, we need to increase the memory limit. This memory_limit can be changed in the php.ini in the public_html folder in your hosting account. This error can creep up in your website during the normal development process.

Step 1: Login to your cPanel

Step 2: Go to the File Manager.

Select the Web root (public_html/www) directory and click Go.

Step 3: Find the php.ini file in the public_html.

Note: If you do not have a php.ini in your public_html files, you can have our tech support staff restore the php.ini to your public_html directory.

Open the php.ini with the code editor.

Step 4: Find the following section in the php.ini file, then increase those limits to a minimum as follows:

  • max_input_vars = 3000
  • memory_limit = 128M
  • max_execution_time = 300
  • max_input_time = 300
  • upload_max_filesize = 64M
  • post_max_size = 64M

Save the changes.

Step 5: In order for your memory limit to take effect you will need to make the php.ini recursive.

Making your php.ini file affect all child folders as well is referred to as making the file “recursive“. To make your public_html/php.ini file recursive, edit (or create the file if it doesn’t exist) your public_html/.htaccess file and add the following code:

suPHP_ConfigPath /home/username/public_html

(replace username with your cPanel username) This line you entered is specifying the directory where the php.ini is located that you want to make recursive. This change is immediate, so you should see the update right away.

After saving the changes, be sure to create a phpinfo page in one of your subdirectories and test the results.

Video guide on How to View your PHP Settings with a PHPinfo page

When looking at your phpinfo page, the “Loaded Configuration File” should reflect the php.ini file that you wanted to make recursive.

Now visit the site. You should not see the “Allowed memory size” error anymore. If the error still shows on your website, there may be a setting within the software itself that is overriding the change or the php.ini in the public-html may be overriden by another setting elsewhere. If this is the case, you can contact our our tech support staff to have them look into the error further.

 

The official WordPress guide on this topic can be found here: http://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP

Fatal error “Allowed Memory Size Exhausted” error

The reason for this error is that your server configuration has a very low memory limit. Try adding this to wp-config.php (put it after <?php in this file):

define(‘WP_MEMORY_LIMIT’, ’96M’);

Please note that this limit is OK for the theme and the plugins that come with the theme. If you want to enable other plugins you may need to increase the limit further.

define(‘WP_MEMORY_LIMIT’, ‘256M’);

The official WordPress guide on this topic can be found here: http://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP

Blank screen after installing or when trying to activate the theme

 

If you upload the theme and then activate it but see nothing but a blank white screen, In this instance there will be no error messages, no hint as to what the issue is and no way to tell for certain how to fix it. When attempting to diagnose a white screen condition consider what you did before the condition occurred:

  • Did you install an upgraded version of WordPress, and did you check to see if the white screen occurred before you installed and activated your theme?
  • Did you install any plugins prior to installing the theme?

A blank screen in WordPress can be caused by a myriad of things. It can show up on an admin page while the rest of the website works perfectly. You may even experience a blank screen on one post while the others are flawless. In most instances, the blank white screen is caused by an exhausted memory limit for WordPress. Having too many plugins running simultaneously or a faulty plugin could be taking up the memory.

Here are some of the most common and easy fixes to try before you start delving into some of the more deeper issues.

Fix 1: Clear Your Cache

One of the easiest ways to solve the white screen of death in WordPress is by emptying your cache. If you can access the admin panel but the front end of the site is displaying a blank screen, you may have to empty the cache used by certain tools. This problem is often caused by a caching plugin and can be quickly fixed from the admin panel. You can consult our guide here:   How to Clear Cache

Fix 2: Check the Memory Limit

Exhausting the memory can cause a white screen to appear. Sometimes it may be accompanied by a message that the memory size has been exhausted. In this case, you may need to increase your memory limit in WordPress.  Check with your web hosting service and ask them to increase your PHP memory_limit to at least 96MB. 128MB is recommended. You can consult our guide on how to Increase the Memory Limit in WordPress

If the blank white screen persists, then the memory wasn’t the problem and it’s time to check the plugins.

Fix 3: Disable Plugins

The wrong plugins can cause all kinds of issues on a website. While many developers try to make everything compatible, sometimes these additions break each other or have the slightest error in the code. As a result, the site can break down.

There are a number of ways you can deactivate plugins, and it also depends on whether you have access to the admin panel of WordPress.

If you’re unable to access the admin panel, you can delete plugins by using FTP. Go to the root folder of your website, access wp-content and open the plugins folder, you can delete those files directly.

 Afterward, you should be able to access your website. That is, if it was a plugin causing the issue.

Fix 4: Changing the Theme

The most likely issue associated with a theme being the cause of a white screen condition is when the upload of the theme did not complete the transfer of all files, the transfer resulted in corrupted theme files, or you have PHP configuration memory limits set too low. So please try this solution:

Access your admin area if you can and disable all plugins as described above, change the theme to one of the WordPress default themes. Check to see if this resolves the problem. If it does, try reinstalling the theme by completely removing the old copy in /wp-content/themes/ and installing a fresh copy (I recommend using FTP to do this because you less likely to run into errors than when you use HTTP WordPress theme installer) Activate the replacement theme and see if the white screen condition returns.

If you cannot access your admin area, use an FTP client to access your site. Disable your plugins by following step #3 in the plugins instructions above, and delete the theme entirely.

This will force WordPress to use the default WordPress theme. See if the problem persists. If it does, then the problem is likely in your WordPress installation. If the problem does not occur, then install a fresh copy of the theme via FTP, activate it and see if the problem reappears.

Fix 5: WordPress in Debug Mode

Check your error logs. You can change the blank screen in WordPress to show you errors which may help you fix the problem. This is done by accessing the wp-config.php file in your root folder.

Create a backup of the wp-config.php file. Using an editor, add the following code to the file and save it to the site:

error_reporting(E_ALL); ini_set(‘display_errors’, 1); define( ‘WP_DEBUG’, true);

When you access the website again, this time the blank screen will list the errors in the system. By tracking down these errors, you may find even more solutions to the problem.

Run a PHP validator on the code prior to saving. It will catch a lot of simple mistakes.

Fix 6: Checking Other Site Issues

If you have more than one instance of WordPress running on a server, find out if the other sites are having the same issue. This can help you eliminate many possibilities. For instance, a problem on one WordPress site and not the others can lead to: Faulty plugins Bad themes Custom coding issues Compromised files from hacks or malware If the white screen is displayed on all of your sites, then there is more than likely a problem with the server itself. In which case, you will need to contact your web host provider or network administrator.

Besides, there is a list of possible other causes for the white screen condition here because they too can cause this error:

  • Blank space in functions.php – This is easy to do if you’ve been modifying the file. A good way to check is to replace it with the unchanged version of the file and see if the site works.
  • Blank line in wp-config.php – a blank line at the start of this file can bring on the White Death. Check for extra spaces at the end as well.
  • File Permissions – Make sure all the directories are set with permission of 755 and the other files 644. This should not happen because the server should inherit the permissions of the files that get uploaded to the server. But we have seen occurrences where, for example, unpacking a ZIP archive using CPANEL and other interface tools botched permissions.
  • Multiple Plugins – When you’re reactivating your plugins, the first one you find that causes the problem may not be the only one. Sometimes its a combination of two or more. So you may think you have the problem solved, but it may still exist and come back in the future.

—————————————

500 Internal Server Error

If you just installed WordPress, a WordPress plugin, or a theme for your site and out of nowhere your site returns a 500 Internal Server Error, please read the information below.

There are five major reasons why these errors occur in WordPress:

Incorrect web server configuration

Incorrect folder/file permissions

Corrupt files or files that contain errors in code

PHP memory limits set too low

Conflicting third party plugins

1. Incorrect web server configuration – If your web server (whether it be Apache or IIS) is configured with incorrect directives, they can cause 500 errors to occur. The problem is that web hosting support will often blame the error on software you have installed without even checking to see what is contained in their error logs. Just know that after you have checked the following remaining causes, and they fail to resolve the issue, you will need to (sometimes forcefully) get your web host to help diagnose and fix the problem.

2. Incorrect file permissions – With very few exceptions, file permission for WordPress, plugins, and themes need to be set at 755 for folders, and 644 for files. You may think that setting permissions more loosely, like 777, will relieve the problem, but you would be wrong. Setting permissions either too strict or too loose often cause this and other errors.

3. Corrupt files or files that contain errors in code – Usually improper/errors in file transfers to the web server cause corruption to occur. It may look like the file is sitting there just fine, but something in the process caused the file to be unusable by the server. For example, if you uploaded a text file in binary language instead of ascii it will render the file unreadable by the web server. Coding errors can also create this error, whether that be in WordPress, a plugin, or a theme.

Often, the only way to resolve an error in WordPress core is to reinstall WordPress.

If it is plugin related, deactivating all plugins will relieve the error.

If it is theme related, deleting and reinstalling the theme will often take care of the problem.

By far the most common 500 error produced by a file is related to the WordPress .htaccess file. The .htaccess file is primarily designed to be used with custom permalink structures. But it is also used by some third party plugins, and for overriding certain server configuration directives if allowed. If it contains errors, it can return the dreaded 500 internal server error. The .htaccess file is located in the root folder of your WordPress installation (not the theme).

log into your site via FTP (Filezilla, etc.)

download a copy of your .htaccess file, rename the copy e.g. “.htaccess-backup”

delete the .htaccess file residing on your Web server

create a new blank file called “.htaccess” on your PC/laptop/Mac

upload this new file to your Web server in the same place as the original .htaccess (which you deleted)

navigate to your WordPress admin URL, e.g. http://www.yoursite.com/wordpress/wp-admin, and you should now be able to log in!

finally, once logged in, navigate to the Permalinks settings page in the admin console and do nothing further. Simply going to the settings page should enable WordPress to write the correct .htaccess declarations itself.

You should now be able to nagivate to www.yoursite.com or http://www.yoursite.com/wordpress (depending on whether WordPress is running your entire site or just a blog etc.) and all should be well once more.

4. PHP memory limits set too low.

You can ask your web host to increase your PHP limits. You will find the recommended limits below

5. Conflicting Third Party Plugins Should Be Deactivated

If you can access the admin area of your site, login to your admin section and deactivate all plugins. After doing so, check your front end page again. If it loads without error, you have a plugin conflict. Now, start activating each plugin one by one. When you see the 500 error again on the front end pages, you will know that the last plugin you activated is the likely culprit. Deactivate it and continue checking all remaining plugins one by one to make sure there are no others.

If you are getting the 500 error on the front end and the back end admin area, then you will need to access your site via an FTP client. A little known trick is to change the name of your/wp-content/plugins folder to something else temporarily like “plugins.bak.” This will make WordPress ignore your plugins. Then check to see if this resolves the problem. If it does, log into your admin section and then change your plugin.bak folder back to plugins. Then deactivate all of your plugins via your admin page.

Recommended PHP configuration limits are as follows:

max_execution_time 100

memory_limit 256M

post_max_size 32M

upload_max_filesize 32M

You can verify your PHP configuration limits by installing a simple plugin

(Source : http://theme-fusion.com/knowledgebase/500-internal-server-error/)

Fix Issue Shortcode When Update Visual Composer 4.7 or Higher

Hi,
Visual Composer update to version 4.7 or higher have some significant transforms, so G5Theme shortcode (on Grove) had been affected abit, so we have to fixed it for next update version.
Please follow these steps as below to fix it asap:

1. Download grove-shortcode
2. Deactive plugins grove shortcode, delete all files, then re-install

Done.

————
If you have any troubles configuring your website applications with the above settings you can contact the Support Center by signing up and submit a new topic. G5Theme Support Team will be glad to assist you.
Thank you very much for choosing G5Theme!

Fix Issue Cannot Edit Revolution Slider on Cupid

After updated Revolution Slider, if your slider cannot edit/update, please do follow to fix:

1. Download file filter-cupid.zip on attachment by click here or http://support.g5plus.net/wp-content/uploads/2015/09/filter-cupid.zip

2. Extract and replace file filter.php to path: cupid\lib

———–
If you have any troubles configuring your website applications with the above settings you can contact the Support Center by signing up and submit a new topic. G5Theme Support Team will be glad to assist you.
Thank you very much for choosing G5Theme!

Why “Install Demo Data” completed, but website not load success?

To these theme: CUPID, ZORKA, GROVE, DARNA, WOLVERINE, HANDMADE, MEGATRON, ACADEMIA  when you have “Install Demo Data” completed but website not load success, please follow below instruction to fix this issue.
First, you should check Why “One Click Install Demo Data” not completed? to know more about variables on your server.
If everything done, after installation process finish, go to Theme Options then you click “Save All Changes” and click “Generate Less to CSS” button. Look like below:

generate-less-to-css

Why “One Click Install Demo Data” not completed?

In this case One Click Install Demo Data can’t completed, please check follow:

1. What version php do you using? If lower 5.4, please update to 5.4 or greater.
2. Check your folder theme has permission create/write file? if not, please set permission for it.
3. Did you do as our document?
That is:
PLEASE SET VALUE FOR VARIABLES BELOW IN PHP.INI/.htaccess or some where(ask your hosting provider) BEFORE DO “One Click Install Demo Data” function:

  • max_input_vars = 3000
  • memory_limit = 128M
  • max_execution_time = 300
  • max_input_time = 300
  • upload_max_filesize = 64M
  • post_max_size = 64M

Follow this instruction to increase the memory limit: http://support.g5plus.net/knowledge-base/system-required/

4. Make sure directory: [your_theme]\assets\data-demo\log has permission can create/write file.
In case, you done this way but it doesn’t work well, please open wp-config.php to edit, add line:
define(‘FS_METHOD’, ‘direct’);

5. Make sure can create directory “uploads” on [your_theme]\wp-content\uploads and can create files in it.
If you did all but still error, please create topic and give me your account website and account ftp to check.
Thanks for your time.