WordPress 3.7

I have upgraded to 3.7 too and am getting the

Call to undefined function wp_get_current_user() in wp-includes/user.php on line 215 – this is being reported on this forum PROBLEM UPGRADING TO 3.7

I followed their route and isolated the problem to nextgen gallery. I am running 2.0.

Any thoughts, as I now have no images in my site, as each time I re-enable the nextgen plug-in, the error returns.

Have upgraded and everything working as well as it was before update

There is a solution posted here that is working but can this be noted by nextgen to be added to the list of possible fixes? I am certainly not criticising the plugin as this is a very recent update, but protocol suggest the burden will lay with the plugin and a fix and not the other way round.

Solution to Call to undefined function wp_get_current_user() in /home/…/public_html/…/wordpress/wp-includes/user.php on line 215

Many thanks

Also had the “Call to undefined function wp_get_current_user() in wp-includes/user.php on line 21” error after upgrading to wp 3.7

Hi all – just seeing this. I’ll pass this thread and details to the developers. If anyone wants to help make sure we can resolve this quickly, please submit a bug report with login credentials so we can see the error (we’re not seeing it on any of the instances we’ve udpated). Thanks! (Erick)

Hey all – just noticing that the fix provided in the other thread actually relates to a different plugin. Lots of users with this all unrelated to NextGEN Gallery.

@danbailan: can you confirm that you did trace this to NextGEN Gallery and how? Also, can you confirm you are using the latest version of NextGEN Gallery 2.0.33?

Hey all – it’s *possible* this might occur for users with NextGEN 2.0.30 and earlier, but it should be happening with the latest version. Given that, and given that it’s being tied to other plugins, I don’t think this is a current NG issue. If anyone has confirmation otherwise, let us know.

Hi Photocrati I am running 2.0.

I used ftp to rename plugins folder (to_bak) and then having established that was where the problem lay, used the same technique to disable each plugin folder and unfortunately nextgen drew the short straw.

I used the capabilities.php edit as per the link above and this has resolved the issue but I am not happy at editing core wordpress files.

I know you will suggest upgrading to your latest version but given, the previous problems, I am understandbly nervous. I lost the lot when I went to 2.0.

Hope this helps.

@danbalian: You’re right :). I’m going to suggest that you update. Or more precisely, this issue is already resolved as far as NG is concerned it looks like. You’d just need to update to get the solution.

One quick note: The upgrade from 1.9.13 to 2.0.0 was very, very major. Every update since then has been incremental with small fixes and improvements. And the 2.0.33 version is – by far – the most stable version of the 2.x series. In otherwords, you’re very unlikely to encounter the same issues going from 2.0.0 to 2.0.33 than you did from 1.9.13 to 2.0.0.

So it’s definitely worth updating. Since I’m basically convincing you to update: if you do update and have an issue, submit a bug report and include “Erick” in the title and I’ll be sure to get your issue in front of developers. If you think there may be an issue, wait until next week rather than the weekend so our team is on and around.

I will do the update as I really want the ajax pagination for my image browser – I am right in saying this will simply allow the images in the imagebrowser to go forward or back (on navigation), without the need for the whole page to re-load???

…but as you sensibly advise, next week –

Before the update, quick question. Should I replace the edited capabilities.php file with the original or leave it in place??

Many thanks, Erick.

(I am still a big fan of nextgen despite the problem I had and thinking seriously of going pro – to get the responsive galleries for mobile, assuming your reassurance they work across all platforms including windows phone, android and iphone) But maybe do the update first and then the upgrade.

@danbailan. Thanks for the kind words!

Yes the latest version reintroduced the ajax pagination options for imagebrowsers. When selected, your image browser galleries won’t reload the page.

On the edited capabilities.php file, not sure what you are referring to there!

On pro gallery types (and basic ones for that matter), they do work across all platforms, though I have to say there are still some quirks here and there. Unless you’ve tried it, you’d have a hard time imaging how difficult it is to get all our galleries to behave the same way across so many platforms. We now have to test on windows hosting, linux hosting, local dev sites, mac, safari, firefox, chrome, opera, ios (4, 5, 6, and now 7), ipads (different behavior than phones, including different versions), android phones, windows phones, nexus tablets, etc, etc. Plus you can combine different elements above, plus combine them with different WP versions and plugin set ups.

They’re all so different and it’s an ongoing challenge to keep everything performing consistently across all platforms. But for now, everything is functioning fairly well across all platforms, with a few small variations here and there.