Fatal database update error w/ 7.x-2.3 and dev update

The reason is that picture has support for file entity, but since a lot has changed between version 1 and 2 of file entity, we didn't check version 1. Since it is a soft dependency we cannot check the version in the info file. I added an extra check in the picture.install file, to make sure the function exists, if it doesn't an exception is thrown urging people to update.

For those having similar problems, the solution in #1 is spot on.

I have now tried rolling back the module from a backed-up older version, and have truncated the watchdog table in the database. I then added the code that checks the file entity version that you mentioned to the picture.install.php, and then ran update again. It now gave the warning as expected, but allowed me to continue form there.

I'll have to check if that broke anything.. *crosses fingers*.

Now everytime that I run update it asks that I update the file entity.

Media module and picture module are now incompatible?
Unfortunately, updating to version 2 of the file entity module is not as easy as you think. If you want to use a stable version of the media module, the recommendation is using version 1.0, which in turn uses a special 1.0 version of the file entity module (if I understand correctly).

From the media module page: "The File entity project is not compatible with Media 7.x-1.x. You must use the File entity module bundled with Media 7.x-1.x."

Updating to the 2.0 version of media module from 1.0 is not only terribly complex, but the 2.0 version still has all kinds of bugs (just had a look at the issue cue), cementing the claim that it's not production ready.

It's all incredibly interconnected.. the short of it: you can't use the media and picture module together in a production system.

And that's a serious issue in my opinion.

I hope I'm being a n00b, if so, please explain.

Also, please don't assume everyone has access to Drush. The killer feature of Drupal is its WYSIWYG sitebuilding nature after all.

My bad, I'm using media 2 since a long time and I assumed - wrongly - that most people are. The problem is that file entity has matured a lot in version 2, so for now I guess the are kind of incompatible.

If you ignore the error, is everything still working, because we removed some code in version 2 specific to file entity?

I'm afraid it has caused some serious trouble, from what I can tell from a short analysis. Images are all rendered in one resolution. No more responsiveness.

I also couldn't update any other modules, as the picture module kept wanting to update every time I started update.php. In the end I had to manually modify the database to fake that the picture module had updated successfully (changed schema version in system-table, if anyone else is wondering).

Would it theoretically be possible to still use the old version of file entity with the latest picture code? Your claim that you deleted a lot of code makes me fear the worst..

Another option would be to roll back to the old version, and just not update the module anymore (horrible thought obviously). In this scenario, how would I go about it? Did this latest Picture update make any changes to the database structure?

This should be fixed in latest dev. Picture should now work with both File Entity 1.x and 2.x.
Can you confirm?

Hurray!

The flexslider is still acting wonky, but the other parts of the pages seem to output the correct sizes of images again. I'll see what's wrong there later, but so far things are looking good. The update.php ran without a hitch too.

Thanks so much for the quick response!

Ok, I installed in on production, and some strange things still going on there:

http://setup.nl/

The scaling/cropping seems to be going wrong. The Flexslider on top is supposed to be more narrow, and the images below it are all supposed to be equal height. Hmm.

UPDATE
There are 4 breakpoints in the site, but the image stays the same at all sizes, across all different imagesets: it outputs the mobile version. It's as-if it thinks the site is being watched in a mobile phone.

I've hacked it by upgrading the mobile image to 960x480px instead of the 320x240 it used to be. This means that mobile users are now downloading a very heavy site, but at least desktop users don't get very grainy images.

I guess the order of your breakpoints are reversed, it uses the first match, so it always uses (min-width: 0px)

The order was indeed from mobile tot desktop.

But then why did it work ok before? And now, having changed that order around, the problem isn't fixed either.

Now the right image is used based on the media query, so what other problem do you have? If it's the height, check your image styles to make sure they are high enough

If you updated Picture recently, I believe they just made changes for the 2.x release that caused a reverse in order, so now standard (large) is on top of the list whereas mobile (small) was the top of the order before. Try reversing the order of your breakpoints in your picture groups. See the Picture project page for more info.