Support Forum

SP 5.5.3 upgrade said it completed but it did not. the plugins and themes that require 5.5.3 did update.

SO SooLi
SooLi
Member

upgraded to WP 4.1 and SP 5.5.3 and the theme was not working on an individual post level. it didn’t display the content of the posts or any more of the page under the topic tree and clicking the watchlist and subscribed icons created a window in the lower left with only the top of the window visible.  after trying everything i could think of i happened to go back to the plugins page it was showing 5.5.2 as installed and 5.5.3 was still showing as available for update but the themes and plugins are showing as updated and they required 5.5.3.  so i tried updating to 5.5.3 again. it said it completed and provided a link to update the database.  i clicked the link, the browser url shows http://www.madeupname.com/wp-admin/admin.php?page=simple-press/sp-startup/sp-load-install.php, and it returned “You do not have sufficient permissions to access this page” and an blank page.  i believe it did the same thing the first time around as well.  the forum admin is fully functioning and it says 5.5.2 at the bottom of the page.  the current theme is default 1.2.12.  please tell me how to resolve this.

thanks

24 Answers

New Answer

MP Mr Papa
Mr Papa
Member

sorry, having a hard time following you…

are you trying to update wp, sp or sp themes/plugins?  or all?

yes, sometimes after an upgrade, the wp admin loses the nonce and the loading of the sp admin page gives you a permission error…  reloading the page makes all well…

what is in the forum admin now?

and if still getting permissions, are you sure this account has the wp capability for install_plugins?

SO SooLi
SooLi
Member

SP 5.5.3 required WP 4.1 so i first upgraded to 4.1.  it appeared that 5.5.3 went through so i updated the plugins and themes as well.

i just reloaded the page 4 times, the same message very time.

the forum admin shows everything.  at the bottom it still says 5.5.2.

there are two admin accounts.  i have been logged in on one, and i just tried the other.  same result on both.  under Manage Admins both have “Manage Plugins” which they must have since the SP plugins updated just not 5.5.3.  i have never had any problems installing or updating a plugin before, including SP.

here are the messages received when i click automatic update:

The update process is starting. This process may take a while on some hosts, so please be patient.

Updating Plugin Simple:Press (1/1)
The plugin is at the latest version.
Simple:Press updated successfully. .

All updates have been completed.

Upgrade the Simple:Press Database | Return to WordPress Updates | Return to Plugins page

SO SooLi
SooLi
Member

does the database upgrade function call “/wp-admin/upgrade.php?step=upgrade_db

we run sucuri cloudproxy and I saw this call getting blocked by our firewall because it is being internally generated by a server as an un-whitelisted ip.

MP Mr Papa
Mr Papa
Member

we use scurri too, so its not a general issue with them..

and yes, wp does all the updating, not us…  we just supply wp with the location of the zip archive to use in the update and they do the rest…  no, we would not cause a db upgrade function call.. thats wp…

getting late here for me…  but couple things to try…

on the server, check your version of sp…

in the wp-content/plugins/simple-press/sp-control.php, please verify the version number at top…

and try the upgrade with the browser console open…  see what the ajax responses are during the upgrade… see if anything hijacking the ajax responses or if any errors visible in the html response… again, you would see this in the browser console, not on the page display itself…

SO SooLi
SooLi
Member
Version: 5.5.2

i am using firefox and opened the browesr console and saw a lot of these messages before and after i launched the SP 5.5.3 upgrade so they do not seem to be associated with the upgrade.  
that's all that was in the console.

"[AGENT] Exception caught when connecting to helper:  - " global.min.js:325
"[AGENT] Could not connect on port 6258; trying again on next port." global.min.js:325
"[AGENT] Exception caught when connecting to helper:  - " global.min.js:325
"[AGENT] Could not connect on port 10191; trying again on next port." global.min.js:325
"[AGENT] Exception caught when connecting to helper:  - " global.min.js:325
"[AGENT] Could not connect on port 14821; trying again on next port." global.min.js:325
"[AGENT] Exception caught when connecting to helper:  - " global.min.js:325
YS Yellow Swordfish
Yellow Swordfish
Member

As this looks to be fundamentally a WordPress update issue let’s just check a few things before we go any further.

Firstly – can you look in your WP plugins folder – commonly /wp-content/plugins/ – and make sure that there is only one plugin folder for simple:press. You are looking for the folder /simple-press. If there are any others – like /simple-press-1 for example – then they need to be deleted.

Secondly – take a look in your uploads folder – again – most commonly /wp-content/uploads/. If there are ANY folders in this location to do with ‘simple-press’ then they need to also be deleted.

It has been known that WordPress, while updating a plugin, has not managed to delete the old version which means you end up with multiple folders. This may be the problem here.

XD xDave
xDave
Member

Same here :/

Checked all your hints and advices..no success->insufficient rights.

How to fix it?

SO SooLi
SooLi
Member

1) only one simple-press plugins folder

2) no SP folders

MP Mr Papa
Mr Papa
Member

none of those from post 8 are related to simple press…  sounds like a theme js file…  was the theme updated with wp 4.1?

any caching?

were you able to look at the ajax responses?  to see if some other js was interfering?

is the admin via ssl?

SO SooLi
SooLi
Member

1) the theme was not updated with 4.1

2) no caching

3) nothing showed in the browser console

4) admin is not ssl

 

how is it that the plugins: File Uploader with Plupload v4.0.2, Subscriptions 1.4.7, and Watches 1.5.6, all updated when they “required” SP 5.5.3?

MP Mr Papa
Mr Papa
Member

wp doesnt support dependency for plugins…  so they can freely be updated regardless of version compatibility…  this is true of any wp plugin or in this case, plugins for plugins… try grabbing any wp plugin from wordpress.org…   you can use it regardless of compatibility… likely to break things, but you can do it…

the version required is for information purposes…

the wp dev cores keep talking about doing dependencies for plugins (others and versions), but not ETA…

so can you summarize where we are at?

you are still on version 5.5.2?  and the upgrades fail?  WP is at version 4.1, right?

there must be an ajax response in the console or wp just isnt running… guess that could be, but that would be bigger issue than sp install…  when the ajax runs, and you are in the console tab, you should see text printed… its the ajax going… expanding that text (will be plus sign) will show you the response…

I guess if you wanted to send us (yellow swordfish, Ike and Mr Papa) some temp credentials via pm, we could look ourselves and see what we see…  if that works, send to all three and link back to this topic so we know what its about…

MP Mr Papa
Mr Papa
Member

@apokh afraid that you did not make that temp account an sp admin… please go to forum – admins – manage admins and give the account all the sp admin capabilities… cannot try to upgrade the forum without it…

SO SooLi
SooLi
Member

still on 5.5.2, WP 4.1, and all upgrades have failed.

I installed the site on my PC using ServerPress and when I click on a post I get the following message.  Does that help answer what is going on?

Fatal error: Call to undefined function sp_get_activity_exists() in C:UserscdDocumentsWebsiteswww.madeupname.devwp-contentsp-resourcesforum-pluginssubscriptionssp-subscriptions-plugin.php on line 306

MP Mr Papa
Mr Papa
Member

No, not really… Says you have the latest, updated version of the subscriptions plugin which requires simple Press 5.5.3… So those are incompatible versions….

Never heard back if you were willing to provide access to your wp admin….