Support Forum
Support Forum
Add Reply
Add Topic
Offline
QuoteWP4.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?
Offline
not much to go on...
could be a caching plugin or wp theme or other wp plugin replacing wp jquery or jquery ui script...
Visit Cruise Talk Central and Mr Papa's World
OfflineHave you had any difficulties with Thesis theme?
We use currently version 1.8.2.
OfflineAll 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
 |
YELLOW
SWORDFISH
|
OfflineOk, we'll try to sort this out soon, since this is now preventing us from moving (back) to SPF.
Offline
let us know what you find... could just be disabling plugins affecting wp js...
Visit Cruise Talk Central and Mr Papa's World
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.
OfflineWhat? 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
|
Offline
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.
All RSS1 Guest(s)