Fixed. Thanks to some feedback on reddit (see this thread and this one), I learned that the issue was that the mootools.js script was being loaded far too late. I solved it (rather inelegantly, I’m sure) by adding this line to themes/rt_gantry_wp/index.php, around line 30 or so (before the if blocks): $gantry->addScript(‘/wp-content/plugins/gantry/js/mootools.js’); It’s no longer … Read more
Check your WooCommerce System Status to make sure there are no red entries, especially in the Pages section Test your checkout process with the console active Check your server error logs for any entries that relate to the pay page How to use the Google Chrome console : https://developers.google.com/chrome-developer-tools/docs/console How to use FireBug for FireFox … Read more
Thanks to @Pat J i removed the syntax that was causing me problems. For those who are interested, inside the Search Everything plugin, on line 198 – 221 there is the following function: function se_search_default() { global $wpdb; $n = ( isset( $this->query_instance->query_vars[‘exact’] ) && $this->query_instance->query_vars[‘exact’] ) ? ” : ‘%’; $search=””; $seperator=””; $terms = … Read more
This is an issue when installing mod_security2. The solution is as simple as disabling mod_security or allowing that page to POST that request. The issue is that mod_security thinks someone is trying to hack into your site.
Since you cannot access the WordPress Dashboard with your user account you will need to use FTP or SSH to access the wp-content/plugins directory for your site and rename the plugin folder for wp-customer-reviews. Example: wp-content/plugins/wp-customer-reviews becomes wp-content/plugins/wp-customer-reviews-broken This will disable the plugin and allow you to log into the WP Dashboard again.
Monster Widget is a bit of a trap like that. Despite how it looks it doesn’t actually place “real” widgets into sidebar. It is a single widgets that creates output of other widgets inside of itself. If you are significantly interfering with its expectations then it won’t pick up on changes, since it’s not engineered … Read more
I think that main problem here is that you try to use “fail” to indicate the state where form has errors. This is wrong, because ajax call will “success” even when form will have errors, because from jquery point of view – it made a ajax call and got response. Fail will be called only … Read more
Don’t store serialised PHP data in the database! It can be a major security risk! When the contents of the value are deserialised, any objects get recreated and their constructors and wakeup methods run, this can be used to launch an attack. Additionally, that data can’t be search replaced, because PHP serialised strings contain values … Read more
First thing i see that needs to be changed is your assigining unchecked values to your input fields. Try wrapping isset round the variable before echoing, this will stop errors if they are not assigned or empty. Second thing as you have passed a post id to get_post_custom() you dont need the second array. function … Read more
I’ve successfully tracked this problem by adding error_log(“wp-hook: “. print_r($the_, true)); within apply_filters in wp-includes/wp_hook.php The task is then to look at the function calls (the data inside $the_) surrounding the “PHP Warning: call_user_func_array()”. It will be the one directly ahead of the warning, but you may need to look at calls after or before … Read more