Running drupal 8.0.5 with the books module enabled. Initially I installed the alpha 5 version. Prior to install, I had 5 books with about 10 pages each. After installation of MV the books were removed. The content pages remained, but were no longer linked to a book. I tried alpha6 today and saw the same behavior. I was able to create a new book post-installation of MV. Let me know what else I can provide. If books aren't supported yet, is there some way I can prevent the MV installation from affecting existing ones?

Thanks.

Comments

dnebrich created an issue. See original summary.

dixon_’s picture

dixon_
he/him
Primary language English
Location France
commented
Priority: Normal » Major

We really should make this more clear in documentation for Multivetsion; it's highly advised that you enable Multiversion *before* you add any content to your site.

The reason is that Multiversion provides a new entity storage handler and has to migrate existing content when it's enabled. And this is tricky and so far a bit buggy as you can tell.

Your report is however a legitimate bug that we should fix. So I'm leaving this ticket open to get this fixed as soon as possible.

dnebrich’s picture

dnebrich commented

Thanks. I've been able to restore from a site backup, remove content, install multiversion alpha6, and then add the content. Question -

Looking at past alpha release notes, it says an upgrade path between alpha releases isn't supported. Is this still the case? If so, I'm not sure how I can add content now and then later upgrade to alpha7. I don't want to have to recreate content each time (I have a lot). Or do I need to look into something like the migrate module to do something like:
a) Setup dev1 site with content, migrate module, but without multiversion.
b) Setup dev2 site with no content, migrate module, and with multiversion.
c) Use migrate module to transfer content to dev2 site with multiversion.

And have to do above whenever upgrading to new multiversion version.

In case this helps someone else - I was trying to use drupal console database dump/restore to return my site to a clean state to allow installing multiversion with and without content. But this didn't work. When starting from clean site where MV was never installed, it worked that 1st time. But if I then used 'drupal database:restore ...' to revert to the DB before MV was installed, I couldn't then re-install MV. The site would get stuck in maintenance mode and error.log showed entries for table key_value_sorted already existing. And a few others.

I ended up doing a backup with phpmyadmin, then dropping all DB tables, then importing backup using phpmyadmin. I could then reinstall multiversion.

jeqq’s picture

jeqq commented
Status: Active » Closed (outdated)