yes, what I was thinking of is a few strategic ‘print’ and ‘die’ statements…   see what the data tells us…

might be easier on live server only cause we know its happening…  we can limit the debug display only to your user account…  check our our sp-load-debug.php file… in particular ashow() and vshow()…

Let me know when you might be around tomorrow (I am in Arizona) to do some stuff and can try to walk you through some stuff to look at…   or you could shoot us (via pm) a temp account with wp and sp admin caps, and ftp access and can do some troubleshooting myself… either way is fine…

have opened a bottle wine now, so tonight probably not the best time!

Things got a little hectic, but I am ready to look at some ideas, if you have advice?  I will be around this evening (Eastern time) or tomorrow (thursday)

gonna have to be a weekend for me…  how did you want to do it?  you or me?  if you, can try to post a view things to get you started…   work just limits my time during the week…

I think for now it’s best if I try, because my security guy is very tight-fisted with ftp accounts.  But if you can post a few obvious things to start with I can work with those to get started and then see if we can do some teamwork on the weekend.  If it looks like we will need to get you an ftp account to troubleshoot, I can try to wrangle that as a step two.

Thanks!

understand… no worries…

first thing is to make sure you can read our update file…  since you see it on the plugin, assume you can, but lets check…

edit file simple-press/sp-startup/admin/spa-admin-updater.php…  around line 19 after

    $body = wp_remote_retrieve_body($response);

lets add

ashow($body);
die();

load up an admin page and see if we get a good response on the server… if so, can remove again…

now to go further you need to have a plugin that needs updating…  you can just edit one of them and drop the version by a .1…  verify that you see update needed on the sp plugins page…

then edit same file, routine sp_update_check_sp_plugins(), around line 105… after

        $plugins = sp_get_plugins();

add in

ashow($plugins);
die();

and go to the wp udpates page…  does it show some plugins?

so you can see what I am doing here… just following the path on down to see why you dont see plugin updates…  in that same routine, just keep stepping your way down until you see why you dont get to the part with all the table output listing the plugins…

sound easy?

oh….  ashow() is one of our debug stuff for pretty display of debug info…

Mr Papa said
edit file simple-press/sp-startup/admin/spa-admin-updater.php…  around line 19 after

    $body = wp_remote_retrieve_body($response);

lets add

ashow($body);
die();

load up an admin page and see if we get a good response on the server… if so, can remove again…

 So I tried this, and then the “available plugins” admin page gives me a long text block, like this:

5.0.58289(link)simple-press.com/download-manager.php?id=607Simple:Press Version 5.0.5 Release Build 8289 is now available for download. This is a largely a bug fix release but does include a few new features (see the changelog). Please note, this version of Simple:Press requires WP 3.3+.Simple:Press is a feature rich forum plugin for WordPress. It fully integrates into your WP based site utilizing the same user records and database and displaying on a single WP page.

 

]]> It is fully customizable and comes with a number of themes to get your started. Current users have shown it to be fully scalable whether your site membership numbers the tens or the thousands.

 

]]> Through it's powerful and flexible permissions system it is suitable for those who wish to run private, specialist forums with invited members but is equally able to accommodate open, public forums that allow guest posting.

 

]]>*** CHANGE LOG Simple:Press Version 5.0.5

 

]]> *** Build 8289

 

]]> *** 7th April 2012

 

]]>

 

]]> 2496 [Spam Registrations Plugin] add option to spam registration plugin to only remove users who have never visited

 

]]> 2733 [Private Messaging Plugin] add a thread delete link to each pm thread in thread list (css update needed)

 

]]> 2752 [Simple:Press] add option to set stats frequency update interval

 

]]> 2818 [Plupload Plugin] add file attachment UI when editing posts

 

]]> 2857 [Simple:Press] properly santize filenames with spaces for getimagesize()

 

]]> 2888 [Simple:Press] New template function to dislay pin icon in pinned posts

 

]]> 2891 [Plupload Plugin] add a tooltip to the image enlarger thumbnail to indicate how it works

 

]]> 2903 [Simple:Press] move theme api stuff from admin code to api code

 

]]> 2904 [Simple:Press] correct IE idiocy for forum tools handling

 

]]> 2905 [Template Tags Plugin] create shortcode for each template tag in template tags plugin

 

]]> 2906 [Simple:Press] consolidate profile tab/menu building into one routine

 

]]> 2907 [Simple:Press] Retire the old mouse icon on images in favour of something new and simpler

 

]]> 2909 [Simple:Press] add poster id for current post to forum tools view properties

 

]]> 2910 [Spam Registrations Plugin] correvct spam user removal mis-selecting candidates

 

]]> 2911 [Simple:Press] update profile menus to work from windows network share

 

]]> 2912 [Simple:Press] reate default unread group/forum index icons

 

]]> 2913 [Simple:Press] only show rss buttons if user can actually view the rss feed

 

]]> 2914 [Spam Registrations Plugin] add option to spam registration plugin to move users to user group instead of delete

 

]]> 2915 [Simple:Press] add badges to usergroups with template tag for displaying

 

]]> 2917 [Blog Linking Plugin] Rewrite forum post edit/save to blog after filter change

 

]]> 2918 [Simple:Press] Add support for custom forum icon with unread posts

 

]]> 2920 [Template Tags Plugin] fix validation error in hot topics template tag

 

]]> 2921 [Simple:Press] add version number function was added to api functions

 

]]> 2922 [Simple:Press] add filters to allow removal of upgrade notices

 

]]> 2924 [Simple:Press] add proper permission checking on displaying signature form and signature uploads in profile

 

]]> 2925 [Simple:Press] Ensure the correct permissions are being applied to sub-forum access

 

]]> 2926 [Simple:Press] New option to set the user tracking timeout value

 

]]> 2927 [Simple:Press] add admin popup help to custom icons admin form

 

]]> 2929 [Simple:Press] Correct timezone conflicts in ajax and remote calls

 

]]> 2930 [Simple:Press] Add an optional remove link to each user notice

 

]]> 2931 [Simple:Press] See if we can keep popup images central on the display

 

]]> 2932 [Simple:Press] rename sp_forum_ahah_support() to sp_forum_api_support() to better reflect what its for

 

]]> 2933 [Simple:Press] Add truncate argument for user display names (truncateUser)

 

]]> 2934 [Plupload Plugin] add in height and width to uploaded images if we know it

 

]]> 2936 [Private Messaging Plugin] css change - p tags in pm should look lik p tag in message

 

]]> 2937 [Simple:Press] Correct missing permission tooltips in admin panels

 

]]> 2938 [Spam Registrations Plugin] Remove errant debug statement

 

]]> 2942 [Simple:Press] Don't show quote button if forum or topic is locked

 

]]> 2943 [Simple:Press] Correct occassional missing item in List Topic View

 

]]> 2944 [Plupload Plugin] add uploader admin help panel that was missing

 

]]> 2945 [Custom Profile Fields Plugin] update custom profile help on using radio and select types

 

]]> 2946 [Plupload Plugin] add new permission for download other file type attachments

 

]]> 2947 [Admin Bar Plugin] correct some admin bar CSS issues in IE

 

]]> 2948 [Simple:Press] Correct last post used in Group View when multiple sub-forums

 

]]> 2949 [Simple:Press] switch updated plugisn to use sp_forum-api_support()

 

]]> 2950 [Simple:Press] New admin panel with codex links and information

 

]]> 2951 [Plupload Plugin] update plupload to latest 1.5.3 version

 

]]> 2952 [Simple:Press] save topic id and post id right after post created to keep other actions from overwriting

 

]]> 2953 [Plupload Plugin] support file uploader (plupload) translations

 

]]> 2954 [Simple:Press] Added user id as second parameter to ashow() and vshow() functions

 

]]> 2955 [Simple:Press] general cleanup of the profile photo functionality

 

]]> 2956 [Simple:Press] Adapt the Categorizr script for mobile device detection

 

]]> 2965 [Simple:Press] correct profile photos ignoring the max size setting

 

]]> Admin Bar 1.0.12 https://simple-press.com/download-manager.php?id=539 A newer version of Simple:Press Admin Bar plugin is avaialble Blog Post Linking 1.0.13 https://simple-press.com/download-manager.php?id=601 A newer version of Simple:Press Blog Post Linking plugin is avaialble Captcha 1.1 ...(SNIPPED)... Default theme is available iForum 1.0.16 https://simple-press.com/download-manager.php?id=598 A newer version of Simple:Press iForum theme is available css-only 1.0.16 https://simple-press.com/download-manager.php?id=597 A newer version of Simple:Press css-only theme is available Stacked 1.0.15 https://simple-press.com/download-manager.php?id=599 A newer version of Simple:Press Stacked theme is available

The other admin pages all look the same as normal, no changes.

Then trying this:

now to go further you need to have a plugin that needs updating…  you can just edit one of them and drop the version by a .1…  verify that you see update needed on the sp plugins page…

then edit same file, routine sp_update_check_sp_plugins(), around line 105… after

        $plugins = sp_get_plugins();

add in

ashow($plugins);
die();

and go to the wp udpates page…  does it show some plugins?

The wp updates page does not show any plugins in need of update (although three of them are old versions, in fact).

So I guess the problem is occurring early in the process?

please use the code button for pasting stuff like that… its the button that looks like ${}… paste, highlight then use button and select a language… comes out looking better with less wasted real estate… probably should update our theme to remove all that space and old style code formatting.

okay, remove the first part as I mentioned I suspected it worked since you see the updates on the plugins panel…

but lets talk about the second… you didnt really give feedback there… did you add the ashow()??  if so, when you visited the wp updates page, what was displayed??  should have been something else besides just wp stuff, even if just empty blue box…

Sorry about the gigantic paste! Wasn’t really sure how to do that. 

I did add the ashow() for the second part, and when I went to the wp updates page, there was just the wp stuff.  No empty blue box, nothing at all about SP.

no worries!

no plugins listed???  that says you have no simple press plugins?  what do you get on forum – plugins – plugins list in the sp admin?  you are putting sp plugins in the sp plugin dir and not the wp plugin dir?

might also check forum – integration – storage locations and see if the sp plugins dir is readable and writable…

just to be sure, the code is

        $plugins = sp_get_plugins();
        ashow($plugins)”
        if (empty($plugins)) return;

Hmm, let me try again.  

in spa-admin-updater.php

I have

$plugins = sp_get_plugins();
 ashow($plugins);
die();
 if (empty($plugins)) return;

(I also tried it without the die();)

Even with that ashow($plugins), when I go to the wp updates page (/wp-admin/network/update-core.php), there are no SP plugins listed (nothing related to SP) just the regular WordPress stuff.  (see the screenshot).

On the SP plugins page, the plugins are listed and it says there are updates available. (screenshot of that, too).

SP plugins directory is readable and writeable, according to forum-integration-storage locations.

so what I am struggling with is why you are not getting any output on the wp updates page…  not plugins, but anything from the ashow() you added?  that should at least show something (ie empty blue box) on that panel…

can you try moving those two lines to be the first things in the sp_update_check_sp_plugins() routine… its only moving up 4 or 5 lines of code…  that will make sure its not bailing earlier…

also, I noticed that all your sp plugins are deactivated…  shouldnt matter, but for grins, can you enable the File Uploader plugin and see if it then shows?  and continues to show on the plugins page?

I wish I had an explanation!

Nothing at all from the ashow(), as you see.

I moved those two lines up to right underneath function sp_update_check_sp_plugins() {

and still the same.  nothing on the wordpress updates page

I activated file uploader, and in the SP plugins page it shows as activated (and in need of an update), but still nothing on the WP update page.

One thought–this is multisite with subdirectories, not subdomains, if that matters?

well, perhaps there ya go…  didnt know it was multisite…  are  you on the main site?  that is the only place that can update the sp plugins and themes… network sites cannot as you dont want them affecting stuff that affects the entire network…

worth noting that I can duplicate all this now that I know its multisite (sorry if you mentioned that before)… but its still proper behaviour since a network site does not have permission to update at the main site level… if you were logged in as the super admin, you would see the updates too when you clicked on the link on the sp plugins panel because it redirects you to the network site update…

in actuality we should not show the update available on our plugins/themes panels unless its the main site too… have opened a ticket for that…

but would like confirmation on this from you…

Sorry, this seems to keep getting more confusing! It is multisite, I am the super admin, and I am looking at the place (the only place in multisite) where wordpress updates appear. (That is, /wp-admin/network/update-core.php ).

There is no more “main site” with updates page in multisite.  There is now the network admin (maybe that’s what you mean?).  

So…it’s sounding like this is something that is changed when MU went to multi-site.  There isn’t any way to do the network-wide SP plugin updates? (other than FTP, I mean).

Back in post 12 in this thread you said “This has been working. We have multiple folks doing admin upgrades in multisite.”  But how? Individual sites can’t do WordPress updates in multi-site.  Only super admins, and only on the network update page (in /wp-admin/network/update-core.php ).

It’s OK if it’s just not possible, but if others are doing it, and I can’t, it would be good to figure out why!

No it is definitely possible… I did a bunch last night…

and there most definitely still a definition of main site in multisite…  its determined by wp api function is_main_site()…  it wa added in 3.0 when wpmu became multisite…  and yes you will get it true when logged in to blog id 0 or on the network update page…

And back in post 12, what I meant is that we have multiple users (dozens and dozens actually) of simple press on multisite and they can upgrade their stuff just fine…  actually, we did have one user  back in the beta who was having an issue doing a network upgrade of simple press (ie the db stuff) but not with updating core, plugins or themes…

the only thing that remotely comes to mind is that all my current multisite test sites are running wp 3.4 (currently in beta)…  so I dont know if wp made a change between 3.3 an 3.4 which might be affecting this…

but yes, as site admin, on http://lyoursite.com/wp-admin/network/update-core.php, is where you should see any sp core, plugin or themes updates… I do on my testsites…  and would definitely like to figure out why you are not seeing it…

I should add that what I was seeing and thus thinking on your stuff, was that is_main_site() was not being true which would explain why nothing would show…  might be worth seeing what it is for you… 

so file sp-startup/sp-load-core-admin.php and around line 68 find

# check sp version for upgrades
if (is_main_site()) {

and put a die(‘here’); inside the if and see if it gets there…  if not, should see what the function and evaluates to and why…