WP4.0, SPF 5.5.1.
Installation fails with error on the top of the page:
“PROBLEM – The Install can not be completed”
and then on the bottom of the page:
“There is a problem with the JavaScript being loaded on this page which is stopping the upgrade from being completed.
The error being reported is: undefined is not a function (evaluating ‘jQuery(“#progressbar”).progressbar(‘option’,’value’,currentProgress)’)”
Any hints on what could be the problem?
not much to go on…
could be a caching plugin or wp theme or other wp plugin replacing wp jquery or jquery ui script…
Have you had any difficulties with Thesis theme?
We use currently version 1.8.2.
All I can really say is that I do know for sure we have many users who also run Thesis as their WP theme. This is clearly an item of bad script that has stopped the whole of the jQuery engine from running. Again – as far as I am aware, Thesis sticks to the WP API and standards.
You should be able to use the browser console to check for the script error which may tell you which file and hence which component it is in although it may just tell you it is jQuery. The likelihood is that the problem lies with another WP plugin. You might try deactivating them one at a time and attempting the upgrade between each one.
Whatever is causing the error would be worth getting sorted as such errors can stop other functionality from working and not just within Simple:Press
Ok, we’ll try to sort this out soon, since this is now preventing us from moving (back) to SPF.
Mr Papa said
let us know what you find… could just be disabling plugins affecting wp js…
Hi there, regarding the issue reported by Ari, we looked into it and the problem is the SPF install script loads custom versions of some jquery and jquery-ui scripts, which understandably can conflict with any plugin that happens to be using the built-in versions. So the work-around is to disable other plugins during installation (confirmed), but the fix would be for you to re-engineer the installation to use only core scripts or if that’s not possible, namespace the custom scripts in a way that won’t create a conflict.
What? I would welcome you naming one please…
There are NO jQuery UI or main jQuery scripts supplied with Simple:Press. ALL use of the jQuery UI scripts used are those supplied by WordPress. This has been a policy for many years now and has been faithfully adhered to.
Yellow Swordfish said
What? I would welcome you naming one please…There are NO jQuery UI or main jQuery scripts supplied with Simple:Press. ALL use of the jQuery UI scripts used are those supplied by WordPress. This has been a policy for many years now and has been faithfully adhered to.
not sure if the poster means jquery and jquery ui itself… or add on scripts that use jquery and jquery ui… hoping for the latter would be kind of silly… and as Andy says, we use jquery and jquery ui (and any available ui js addons) that core supplies…
OK it seems I might have been a bit hasty in this assessment:
On the comment on line 72 of spa-admin-framework.php it says “# Install and Upgrade – use our own jQuery and ui.core” but looking at the code that follows it seems this is not the case. Sorry about the misinformation.
A new look at this problem – maybe with better luck this time.
Failure might be a conflict between SPF and Shopp plugin. Installation of SPF seems to fail only when Shopp plugin is active.
We see an error in Javascript console like “Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user’s experience.”
I’ve filed a support ticket to Shopp (too), but wondering if you could take a look at this potential conflict as well.
Any help appreciated.
Well, I suppose the first thing to ask would be – is this actually an error? or a warning.. It definitely looks more like a warning, and if so it shouldn’t really have any bearing on whether having the plugin active causes problems, as it would then not be a conflict.
Can you follow the error (normally on the right it will have a link) to the Debugger to see where it’s originating from?
Of course I could be wrong.. Just a guess!
