Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I have two questions.
Can I uninstall 8.x.1.1 without problems?
If I chose to upgrade how shall I do it?
In the documentation it is written: There is a partial upgrade path from 8.x-1.x; user customization will have to be reset.
Can you explain this? I do not know how to do this.
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | edit_history-form.txt | 2.48 KB | chrotto |
Comments
Comment #2
nickdickinsonwildeHey,
So, yes uninstalling 8.x-1.x will be harmless; it will lose the configuration but that's normal when uninstalling.
For upgrading, the best way is just to do a code update (either with
composer update drupal/hide_revision_fieldor with deleting existing files and putting the new files in place), then run update.php ordrush updb. If you haven't customized the user specific settings (on /user/#/edit) then everything should update fully. If you have then you'll need to adjust those settings on /user/#/edit.Comment #3
chrotto commentedWhen tying update like:
or with deleting existing files and putting the new files in place), then run update.php or drush updb
I get this error when running drush updb:
Do you wish to run all pending updates? (y/n): y
The "hide_revision_field_log_widget" plugin does not exist. [error]
Performing hide_revision_field_update_8201 [ok]
sh: line 1: 3351390 Bus error /usr/bin/drush --backend=2 --user=0 --root=/home/longstay/sites/flex/flextid_proj --uri=http://default updatedb-batch-process 62 2>&1
Cache rebuild complete. [ok]
Finished performing updates.
I noticed that this module was not in composer.json so I run composer require drupal/hide_revision_field
and then drush updb
Then I get this error:
hide_revision_field module :
8201 - Implements hook_install().
Do you wish to run all pending updates? (y/n): y
Performing hide_revision_field_update_8201 [ok]
sh: line 1: 3362027 Bus error /usr/bin/drush --backend=2 --user=0 --root=/home/longstay/sites/flex/flextid_proj --uri=http://default updatedb-batch-process 63 2>&1
Cache rebuild complete. [ok]
Finished performing updates.
in both cases the site crashed.
Comment #4
chrotto commentedUninstalled the module now and run composer update and drush updb and everything is ok.
Perhaps I do an attempt to install the module from this stage tomorrow when my site is backuped.
Comment #5
chrotto commentedThe site was working fine after uninstalling the module.
Tried to reinstall it. First I deleted also the directory for the module.
Run composer require drupal/hide_revision_field
When enabled the module the site crashed again.
Running drush updb result in nothing to update.
Running drush cr result in error: bus error
So, For now, I have to live with the visibility of revision field
Comment #6
chrotto commentedHowever
I installed the module on another site. On this, I have uninstalled the previous version (disabled it in UI) but not deleted the module directory.
Then, I run composer require ...
Enabled the module and run update.php in the browser.
This seemed to be error free.
But I can not make the revision field invisible.
Have disabled it in the form view but it is still there.
How shall I make this to work?
Comment #8
nickdickinsonwildeI believe I've resolved some issues in other tickets and updated the documentation and update hooks here.
Did you save the form view after updating the field?
If so, could you export the config for that entity form display and post it here?
Comment #9
chrotto commentedHere is the actual form.
Comment #10
nickdickinsonwildeGRR! That looks entirely right!
Alrighty... pretty certain it has to be a conflict with something. What's your admin theme? And what modules are active?
Thanks! Nick
Comment #11
chrotto commentedI now noticed that the problem is related to the theme. My admin theme is seven and for admin in this theme the revision field is hidden.
But when changed to my user theme Bootstrap it showed the revision field.
Comment #12
chrotto commentedI have the same theme in the other site so probably the problem I described earlier also was related to the theme.
Comment #13
nickdickinsonwildeI tried using the contrib bootstrap theme and don't see that problem. Is that a custom bootstrap based theme? or what version of the contrib one? If possible, I'd like to fix it since if one theme is conflicting, it probably indicates a problem in my assumptions or code and could happen with other themes.
Thanks!
Comment #14
chrotto commentedI use a custom subtheme to bootstrap but I also tested the standard Bootstrap now (the latest) with the same result.
Also tested Bartik and Stark the latest versions with the same result.
The only theme, that I have installed, that works is Seven.
Comment #15
nickdickinsonwildeDrupal 8.5 or 8.6?
(thanks for your patience btw)
Comment #16
chrotto commentedHave updated to the latest version 8.6.1
Comment #17
chrotto commentedAny progress about this?
I do not understand why this function (hide or view this version thing) not is in core.
Do you know if it is coming?
I am using Drupal to build systems that definitive not is actual to do any versioning in.
It is very annoying, not to be able to hide this.
Comment #18
chrotto commentedHi,
Have now installed latest dev version and it works for me.
Thanks
Comment #19
nickdickinsonwildeThanks for the update Chrotto, not sure which change fixed it.
Nick