Updated to Enfold 4.5.4 and now get admin-ajax 400 error

Hey Vinay,

I looked at the docs and comment below:

1. First of all, make sure that you are running the latest version of the theme – you can find out what the latest version is here
Done

2. Clear your browser cache and restart – Guide to clearing your browser cache
Done

3. Try a different browser to verify if you are getting cached results or not – preferably a browser you have never used to log into the WordPress installation in question with before. If it works as expected in this browser, then you are getting cached results in the first one.
Done

4. Disable all plugins to see if there is a conflict with any of them – if there is a conflict, you can reactivate them one by one to find out which one is causing the problem.
Done

6. Increase the WordPress memory limit.
Done now at 256MB

7. If none of the above should work, then try to overwrite your theme files with a fresh copy from your Themeforest account – Please make sure to properly back your site up prior to attempting this. Refer to this guide for further instruction on updating via FTP.
Done

8. Still not working? Please open a new ticket in the support forum with admin login details for your installation supplied in private, and we’ll have a closer look at it for you.

Its still not working, and I thought this was the support forum? should I just link details in the private content on this topic?

• This reply was modified 5 years, 8 months ago by jeaustin.

Hey Ismael,

mod_sec is not included in our config below are active modules; also if mod_sec were blocking it there should be a trace in the apache log file right?

I have ssh access to the machine so here is the loaded Aapache modules:

root@roadrunner:/var/www/wizard/quad/wp-content# apachectl -M
Loaded Modules:
core_module (static)
so_module (static)
watchdog_module (static)
http_module (static)
log_config_module (static)
logio_module (static)
version_module (static)
unixd_module (static)
access_compat_module (shared)
actions_module (shared)
alias_module (shared)
auth_basic_module (shared)
authn_core_module (shared)
authn_file_module (shared)
authz_core_module (shared)
authz_groupfile_module (shared)
authz_host_module (shared)
authz_user_module (shared)
autoindex_module (shared)
cgi_module (shared)
deflate_module (shared)
dir_module (shared)
env_module (shared)
filter_module (shared)
log_sql_module (shared)
log_sql_mysql_module (shared)
log_sql_ssl_module (shared)
mime_module (shared)
mpm_prefork_module (shared)
negotiation_module (shared)
perl_module (shared)
php5_module (shared)
reqtimeout_module (shared)
rewrite_module (shared)
setenvif_module (shared)
status_module (shared)

Seems odd that Enfold works under Apache2.2 with PHP5.6 but not Apache2.4…

I dont really want to upgrade to PHP7 as some other sites will break as they rely on the PHP5.6 old way of doing things.. and this will cause me a whole lot of work :(

Is there nothing we can try _before_ upgrading to PHP7 as that route will require me to configure Apache with both PHP5.6 and PHP7 and I am yet to get that to reliably work :(

Regards
James

• This reply was modified 5 years, 8 months ago by jeaustin.

Thank you I will enable WP debug and see where that gets me prior to update to PHP7.. 5.6 is very old and really my server should be on 7 by now… :)

Thank you, I will let you know what happens…

Hi Rikard and Ismael,

This ticket maybe closed now as the matter is now finalised.

Everything works fine after a full system upgrade to:

Debian 9
Apache 2.4.25
PHP 7.0.33
Newest Enfold!

Thank you.