upgrading from 1.x to 2.x support

#2082037: Document Upgrade Path from Media 1.x to Media 2.x/3.x

Please note: some of the older comments about upgrading are likely out of date, so use them not as fact but as background information. Also note that recent improvements to the media module have made the upgrade easier. If you have something new to add, please do.

When in doubt' have a look at the media documentation:

Upgrading Media 7.x-1.x to 7.x-2.x

otherwise if upgrading is giving you fits, try to go back to your db backup, prior to upgrading to 2.x, then upgrade to the latest 1.x.

What were the problems with html formatting? Perhaps we can deal with those.

In a test environment, try restoring db and then media 7.x -2.0-rc8 , recent fixes

Ok, I figured out what might fix your issues.
Note: do not do this unless you actually think you have this problem related to upgrading from an older release.
back up your database before trying;

update to the latest 7.x-2.0-rc11

delete the rows in these two tables: media_view_mode_wysiwyg
and media_restrict_wysiwyg

then write a php script as follows, and save it as script.php :

<?php
media_wysiwyg_update_7205();
%>

then execute this above script using drush
drush scr script.php

Use this issue to track support requests for 1.x to 2.x

Pretty crappy to have to install file_entity which is not covered by the security advisory policy, just to update to media and if I don't install file_entity I can't complete update.php for ANYTHING else on my system. Oh I know I don't have to upgrade but I have a mailbox full of module update messages just because of this one module. So thanks for that, love having insecure beta modules on my sites.

Drew

@pikadroo, If you don't like the notices and emails then disable the update module.

FYI: file_entity is derived from media 1.x , it started in media 1.x , but in 2.x file_entity became it's own module.

FYI; there's a lot of compelling reasons to upgrade to 2.0 or 3.0-alpha4 , notably: reliable bulk upload and plupload support using media_bulk_upload using multiform , bulk image importing, as well as enhanced wysiwyg features and support (align left / right) , full i18n / entity_translation support for multilingual , among other improvements and bug fixes and enhanced security. and many more features

Just made a two successful upgrades from 1.5 > 2.0. Without disabling any modules first. Just removed the old media module and uploaded media and file_entity, then ran updates.

The only issues I came across were:
- file_entity update failed because the file_metadata table already existed #2183267: Updates fail if the file_metadata table already exists
- I had to reassign the 'use file browser' permissions to the right roles

Will update here if I run in to any other issues.

@JKingsnorth, thanks for your feedback. I haven't yet tried upgrading from 7.x-1.5 ,
it appears that upgrading to 7.x-2.0 from 7.x-1.6 works very well
I attempted to reproduce your file_metadata table issue , but haven't been able to do that with 7.x-1.6.

Possibly, it might work better upgrading to 7.x-1.6 first , then to 7.x-2.0.

Here's what I tried:

installed media 7.x-1.6
then added a media widget to an image field on a content type
added some content to make sure there's data

then upgraded to media-7.x-2.0 , got warning saying that file_entity must be upgraded first because I forgot to first download file_entity because it was removed from the media module in 2.x
so downloaded file_entity latest 2.x version (7.x-2.0-beta3)

then ran updb
everything updated correctly, no errors.

see my upgrade console text output from performing these operations.

FYI: By following the instructions in the thread #15 above, I had an error when running "drush updb" after the the "field_entity" was manually downloaded and enabled:

"Unable to create directory public://media-icons/default. [error]"

Any suggestion? Thank you.

@glenchen, error most likely server file system permissions related.

Hello, I've tried to upgrade and doesn't work.
If i disable md slider module works but without sliders that i use.
What happens?

Thank you.

@nmantas84 please see the most recent instructions for upgrading here:
#2082037: Document Upgrade Path from Media 1.x to Media 2.x/3.x

Recent versions of media have resolved most of peoples concerns and is compatible with entity translation, multilingual and various advanced configurations. Due to the high volume of inactive and most often irrelevant issues we are Closing this as (outdated). If for whatever reason this issue is important to you AND you still have issues after checking the media recipe documentation, then let us know and we will review your concerns.

Otherwise, see the recipe documentation for how to configure media and for troubleshooting tips OR refer to the media_dev distribution if you want to see a working media setup.

As mentioned, feel free to make some noise in this issue if you still feel it is important to you or someone else.

Thanks,

Media team