zsero

Thanks, removing that works!

Yes, I’m also experiencing the “headers already sent by” php bug with 1.2.1.

Came here to add my experience:
1. Disappeared everything silently, this is quite serious.
2. Fixed with clicking on Permalink Settings / Save

Automatic would be the best, but even if not automatic a big global warning would be really handy (like the caching plugins for example), so at least the user can see that there is something wrong. The problem with this button was that there was no feedback that it had to be done, unless coming here and asking it.

The thing is that for keeping 30 WP websites up to date, I believe everyone uses some centralised update management. For example I’m using the excellent and free InfiniteWP. These plugins can only trigger the normal auto upgrade process, not something custom like clicking on a button.
https://infinitewp.com/docs/updates/

Ah, I see I had to manually go to admin and select any single menu and click upgrade. Can you not make this automatic? I’m using InfiniteWP to manage WP upgrades and that just runs the standard upgrade process.

I just did the wordpress built-in upgrade. Do I need to manually go and click on database upgrade somewhere?

Some more information:
downgrading to 1.9.22 did not help
downgrading to 1.9.21 fixed the issue!

Please provide a fix in 24 which works like 21 did.

I do not use any custom admin theme, I will have to look for what causes this bug.

An easy fix is to change:

.ui-widget-overlay { position: absolute; top: 0; left: 0; width: 100%; height: 100%; }
to
.ui-widget-overlay { display: none; }

in admin\css\jquery.ui.css

Fixes bugs for other functions as well.

Nextgen 1.9 was a 100% stable and reliable plugin. You can download it from here:
https://downloads.www.ads-software.com/plugin/nextgen-gallery.1.9.13.zip

Upload latest 1.9 using FTP! Nextgen 2.x is a joke so far…

@photocrati, I tried the new version (2.0.2), but the error is the same!

Downgrading works for now!

I have the exact same problem! The site broke with 2.0, since this function doesn’t exists! Please fix it as soon as possible!

My problem with the current way is that images aren’t called: image.jpg, but called image-625×320.jpg

Let’s say I change my theme (manually of course), and I have a new one having width = 800px. Now I regenerate all images, and get a series of them being: image-800×430.jpg or similar. That’s great.

However in all my posts and pages, I have image-625×320.jpg. So it’s in chaos, because all my existing posts and pages are still looking at the old sizes.