OK, if you’ve tried every plugin could you next try the WP theme? Try enabling one of the default themes to see if you can then post.

Not sure how old your theme is, but you’ve said it hasn’t been updated or changed since you started. Does it need updating?

While we’re on the subject, is everything else up to date i.e WP and WP plugins?

Ike- Yes, WP and WP plugins are updated every 2 weeks, so those are fine.  The theme is a custom theme and we have never gotten an update from the developer. 

It really is frightening to try a default theme, as I am not sure it won’t break the whole site. This is a membership site and folks rely on it 24/7.

Is that my ONLY option at this point?

I don’t think that enabling a default theme will do anything but display the site under the default theme. Your custom theme should be sitting there waiting to be re-activated but of course I can’t guarantee it wont break anything! Your best bet here would be to talk to the theme developer.

As to the error, it seems to me that this is theme based having done a bit of digging. It looks like the conflict you’re having is with the ‘jQuery Cycle Plugin’ – This by the look of things is to do with some kind of slideshow. It’s loading it’s own version of the jquery library and not only does WordPress have it’s own that your theme should be using, but the one it’s loading is about 6 years old by the look of it.

We will need to wait for @mr-papa or @yellow-swordfish to take a look for further help with this as jQuery problems are a bit out of my depth, but from memory it might be possible to remove some lines of code from the theme that call it’s own library forcing it to use the provided WordPress library, but if the theme is geared towards using it’s own that may have some really bad knock on effects elsewhere.

Please could you PM login details to myself, Mr Papa and Yellow Swordfish – Include a link to this topic and a reminder of the problem (for the other two admins) so they have the info, then let’s wait to see what Steve or Andy think, and in the meantime as I’ve said I would talk to the theme developer to ask them what they think.

I think the issue is in the Theme functions.php file here – using Enqueue – pulling from Google: 

/*
* Enqueue scripts and styles
* – taking care not to force site scripts on WP Admin sections
*************************************************/
if ( ! is_admin() ) {
function init_wfts_scripts () {
wp_enqueue_style( ‘style’, get_stylesheet_directory_uri() . ‘/style.css’ );
/* css for overlays */
//wp_enqueue_style( ‘shadowboxcss’, get_stylesheet_directory_uri() . ‘/inc/js/shadowbox-3.0.3/shadowbox.css’ );
/* using wp_deregister_script() to disable the versions that comes packaged with WordPress */
wp_deregister_script(‘jquery’);
wp_deregister_script(‘jquery-ui’);
/* using wp_register_script() to register updated libraries */
wp_register_script(‘jquery’, ‘https://ajax.googleapis.com/ajax/libs/jquery/1.5.2/jquery.min.js’, false, ‘1.5.2’, true );
wp_register_script(‘jquery-ui’, ‘https://ajax.googleapis.com/ajax/libs/jqueryui/1.8.11/jquery-ui.min.js’, false, ‘1.8.11’, true );
/* using wp_enqueue_script() to load the updated libraries */
wp_enqueue_script(‘jquery’);
wp_enqueue_script(‘jquery-ui’);
/* used for home page cycling (stage) images */
//wp_enqueue_script( ‘jquery-cycle’, get_template_directory_uri() . ‘/inc/js/jquery.cycle.all.min.js’, array( ‘jquery’ ), ‘2.88’, true );
/* used for overlays */
//wp_enqueue_script( ‘shadowbox’, get_template_directory_uri() . ‘/inc/js/shadowbox-3.0.3/shadowbox.js’, array( ‘jquery’ ), ‘2.88’, true );
/* document.ready() */
wp_enqueue_script( ‘wfts-plugins’, get_stylesheet_directory_uri() . ‘/inc/js/plugins.js’, array( ‘jquery’ ), ‘1.1’, true );
wp_enqueue_script( ‘wfts-javascript’, get_stylesheet_directory_uri() . ‘/inc/js/wfts.js’, array( ‘jquery’, ‘jquery-ui’ ), ‘1.1’, true );
}

// k, now add the scripts in the init
add_action(‘init’, ‘init_wfts_scripts’);

Is this something you can help with?  Is there an easy fix? Yesterday I tried disabling this section of this functions.php file and broke the whole site.

Thank you!

Thank you, Ike. I sent separate PM’s with the login info to @mr-papa and @yellow-swordfish as you asked. I put a link to this thread in there, too. Thank you for any help you can give. Best, Michelle for Lisa Cherney

If you comment out the 2 ‘wp_deregister_script’ calls and also comment out the 2 ‘wp_register_script’ calls then you are back to things they way that WordPress expects them to be. Does doing that solve the problem?

You would almost certainly need to completely clear your browser cache after making the code changes and before testing them…

Thank you Yellow Swordfish…I commented out the portion in red: 

* Enqueue scripts and styles
* – taking care not to force site scripts on WP Admin sections
*************************************************/
if ( ! is_admin() ) {
function init_wfts_scripts () {
wp_enqueue_style( ‘style’, get_stylesheet_directory_uri() . ‘/style.css’ );
/* css for overlays */
//wp_enqueue_style( ‘shadowboxcss’, get_stylesheet_directory_uri() . ‘/inc/js/shadowbox-3.0.3/shadowbox.css’ );
/* using wp_deregister_script() to disable the versions that comes packaged with WordPress */
/* wp_deregister_script(‘jquery’);
wp_deregister_script(‘jquery-ui’); */
/* using wp_register_script() to register updated libraries */
/* wp_register_script(‘jquery’, ‘https://ajax.googleapis.com/ajax/libs/jquery/1.5.2/jquery.min.js’, false, ‘1.5.2’, true );
wp_register_script(‘jquery-ui’, ‘https://ajax.googleapis.com/ajax/libs/jqueryui/1.8.11/jquery-ui.min.js’, false, ‘1.8.11’, true ); */
/* using wp_enqueue_script() to load the updated libraries */
wp_enqueue_script(‘jquery’);
wp_enqueue_script(‘jquery-ui’);
/* used for home page cycling (stage) images */
//wp_enqueue_script( ‘jquery-cycle’, get_template_directory_uri() . ‘/inc/js/jquery.cycle.all.min.js’, array( ‘jquery’ ), ‘2.88’, true );
/* used for overlays */
//wp_enqueue_script( ‘shadowbox’, get_template_directory_uri() . ‘/inc/js/shadowbox-3.0.3/shadowbox.js’, array( ‘jquery’ ), ‘2.88’, true );
/* document.ready() */
wp_enqueue_script( ‘wfts-plugins’, get_stylesheet_directory_uri() . ‘/inc/js/plugins.js’, array( ‘jquery’ ), ‘1.1’, true );
wp_enqueue_script( ‘wfts-javascript’, get_stylesheet_directory_uri() . ‘/inc/js/wfts.js’, array( ‘jquery’, ‘jquery-ui’ ), ‘1.1’, true );
}

// k, now add the scripts in the init
add_action(‘init’, ‘init_wfts_scripts’);

With no luck… I cleared my cache for a full week on both Firefox and Chrome and asked someone else to do the same and test. 

Could this line be an issue: 

rel=’stylesheet‘ id=’jqcss-css‘ href=’https://ajax.googleapis.com/ajax/libs/jqueryui/1.8/themes/smoothness/jquery-ui.css?ver=4.4.2‘ type=’text/css‘ media=’all‘ />

I get that when I View Code on the main forum page.  I know it is a stylesheet, so it doesn’t seem that it should be an issue?  I am stumped…

Thank you for any help you can give.

OK… where to start!

Let’s kick off with jQuery. The site is till not loading the WordPress ‘standard and supplied’ jQuery which is version 1.12 with a small alteration to the code specifically for WP. You are running a plugin called jQuery-Updater which aims to load the latest version. It is running version 2.2. There are two problems with this. Firstly it will not have the WP ‘no-conflict’ code (which may or may not be a problem) but it will not run on any Internet Explorer version below V9. There are still a lot of IE7 and IE8 users out there…

Then there is the WordPress theme. I know you have said it has not changed bit I am afraid it must have. Ot is not running the standard wp_footer() function at the end which is 100% required for things to run correctly – especially for footer loaded scripts, and that alone wil lstop all of the Simple:Press scripts and ajax from running.

I reckon these two things need dealing with and then we need to see where we are at. But neither of these have anything to do with the last SP update

Ok… I have deactivated the plugin called: jQuery-Updater now. I just added that yesterday.

And, no, we have NOT changed the WordPress theme a bit since the latest update of SimplePress.

Can you clarify WHERE we are not running the standard wp_footer() function, please? Because this has NOT changed in several months. And things have been running fine is Simple:Press since these updates. We needed custom footers for different types of pages…

Thank you.

WordPress requires tow functions to be called in themes. 

wp_head() needs to be called at the end of the header code – so would usually be found in the header.php file of a theme just before the ‘head’ tag is closed.

wp_footer() needs to be called – as it suggests – in the footer of the theme and is usually called just before the closing ‘body’ tag.

If in doubt look at the header and footer template files of any WordPress default/supplied theme.

Both calls are vital for plugins and are used extensively. Simple:Press will never work if one of these standard functions is not being called.

In the case of your site, either wp_footer() is not being called at all – or – it is being called but something is causing an error and stopping code from completing. If this is the case then you will find the cause in the php error log.

Thank you! You were correct, both custom footers were missing that call. I appreciate you finding the culprit for us. 🙂  Best, Michelle

Fantastic! Glad you are all up and running.