Last gasp … is
(assuming you tried deactivating your other plugins first; some people having issues with YOAST latest edition and conflict with Visual Composer 4.5 on some servers; issue with those plugins not theme — see the support threads on wordpress.org for yoast, for more info)
1) increase default php memory for WordPress in your wp-config.php file to 256MB. I’ve found, oddly, that for some reason, on some setups, changing the amount of memory via theme panel and php.ini does *not* actually increase amount of memory WordPress will actually use … adding the setting ALSO in config file makes difference.
https://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP
or
2) fully delete the js_composer folder, reinstall either the latest version from theme, or install version from prior theme version.
Hi,
@sjlabar Replied via email.
@bsullivan The issue with saving settings usually appears because the server security module blocks the access to admin-ajax.php file or the file it’s not found. Try to verify if this happens when you save settings in other cases in theme panel and also verify the console for error while saving the settings on the Theme Panel, usually it displays a 403 or 404 error.
Contact your server administrator and explain the situation, as it’s requested many times during the a save the file it’s treated as threat so it’s banned. You can report false positives to your server administrator to remove it from the banned list.
Hope this helps! Please let me know how it goes!
Thanks
Hello folks.
I’m also having issues with trying to save theme settings. I’m using the latest version of both WordPress and Newsmag themes. I’ve disabled all plug-ins except for Wordfence, WPBakery Visual Composer,Ultimate Addons for Visual Composer, tagDiv Visual Composer Shim and tagDiv Speed Booster.
When in the theme settings page in the admin panel, I’m able to modify most of the settings without any issue. However, when I try to click on the Block predefined style section links to modify them, the ajax spinning icon just hangs and doesn’t pop open the menu. When I pull open the dev console in Chrome, I noticed this:
Uncaught SyntaxError: Unexpected token < admin.php:1
Things that I’ve tried:
Cleared both the server cache and the browser cache.
I’ve spoken with my host, HostGator and asked them to check the admin-ajax.php and confirm that it wasn’t being blocked, which they said it wasn’t. They also stated that the maximum memory limit is already set to 256, and cannot be changed by the end-user on a shared hosting account.
Reference: http://support.hostgator.com/articles/cpanel/php-settings-that-cannot-be-changed
memory_limit = 256M (MAXIMUM)
Per Chris’s link above, I also went into the wp-config.php file and added the following line of code:
/** Increased memory allotment to prevent Ajax Errors. https://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP */
define( 'WP_MAX_MEMORY_LIMIT', '256M' );
(The official WordPress.org article Chris showed said you had to add it in prior to settings.)
Please note, this has to be put before wp-settings.php inclusion.
You can see it in-line where I included it right after the absolute path section, and before the wp-settings.php section, here:
/** Absolute path to the WordPress directory. */
if ( !defined('ABSPATH') )
define('ABSPATH', dirname(__FILE__) . '/');
/** Increased memory allotment to prevent Ajax Errors. https://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP */
define( 'WP_MAX_MEMORY_LIMIT', '256M' );
/** Sets up WordPress vars and included files. */
require_once(ABSPATH . 'wp-settings.php');
Perhaps this is related, but when I’m on the front end, and try to use the left and right arrows to scroll through content in the various section blocks, the ajax loading icon just spins, and the console spits out the following error:
SyntaxError: Unexpected token < madlymanly.com/:1
Any thoughts as to what is causing the syntax error message in the console? Thank you in advance for the help!
Hi,
I’ve checked your site and found that the syntax error that appears in your site’s console is because this div which appears in your page source and which shouldn’t have to be there: http://screencast.com/t/lrNX1IJ0pn1
You should try to disable all plugins first, empty all caches, purge files if you use CDN host then check again. If it’s still there then you should try a fresh theme and WordPress install and see how it goers.
I’ve haven’t dealed with an similar situation before but as I’ve made some research on this I’ve found that this could mean that your site could be hacked, according to this tread form WordPress support and other statements I’ve found related to this: https://wordpress.org/support/topic/hidden-links-please-help-with-removal
You can try the resources offered there and the suggestions and introductions provided there.
You need to start working your way through these resources:
http://codex.wordpress.org/FAQ_My_site_was_hacked
http://wordpress.org/support/topic/268083#post-1065779
http://smackdown.blogsblogsblogs.com/2008/06/24/how-to-completely-clean-your-hacked-wordpress-installation/
http://ottopress.com/2009/hacked-wordpress-backdoors/Additional Resources:
http://sitecheck.sucuri.net/scanner/
http://www.unmaskparasites.com/
http://blog.sucuri.net/2012/03/wordpress-understanding-its-true-vulnerability.html
http://codex.wordpress.org/Hardening_WordPress
http://www.studiopress.com/tips/wordpress-site-security.htm
You can also contact your host providers and let theme know about this.
Thanks
Lucian,
Thank you very much for all the reading material. I spent the better portion of today deleting all old databases, wordpress and other CMS system directories, etc. just to tighten down the security of my server. There was a lot of house cleaning that needed to be done.
Once I cleaned everything up, I re-installed WP and the theme, and the ajax issues just went away.
I’ve also installed some extra security plug-ins, check the directory permissions, added stronger passwords to the accounts and am finishing up some other security audits. Thanks once again!