Closed (fixed)
Project:
Accelerated Mobile Pages (AMP)
Version:
8.x-1.0
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
11 Aug 2017 at 15:40 UTC
Updated:
21 Apr 2018 at 18:24 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
mtodor commentedHere is solution with
hook_uninstall().Comment #3
mtodor commentedJust uploading new patch without renaming of the configuration file, since that's addressed in #2860803: Cleanup default configuration.
Comment #4
mtodor commentedComment #5
zalak.addweb commented@mtodor, Thanks for providing steps & patch, both help me to check & Perform RTBC. It works well as I checked it with simplytest.me. PFA
Comment #6
quietcorn commentedSo what is the process by which this can be uninstalled? I'm running into an issue where it wasn't working because I enabled the module before installing the theme, so I tried uninstalling it, and I got caught by this problem.
I found some information about how to remove a configuration. I ran this with the drush php console:
>>> Drupal::configFactory()->getEditable('image.style.amp_metadata_logo_600x60')->delete();resulting in this message:
=> Drupal\Core\Config\Config {#7443}Then I tried re-enabling amp, and got this response:
Not sure where to go now. I do need AMP to work on my site. Any advice you might have would be really appreciated.
Comment #7
karens commentedThis should not be a problem after https://cgit.drupalcode.org/amp/commit/?id=dae5667. That commit is not in a packaged release but only on the development branch. If you originally installed the module from the packaged release or from a development release before that commit you'll have these problems uninstalling and reinstalling. For any installation after that commit things should be fine. Note that this code needed to be in the module when you installed it, so you'll still have problems on older installations and you'd need something like the above to remove the old config.
This problem is fixed in the latest development code.
Comment #8
karens commentedChanging this to needs work just to make it clear that this is probably not needed as a patch to the module, since the module has already been fixed. Just need to confirm that there isn't any need for more than that.
Comment #9
karens commentedThis patch is not needed, there is now a new release with the fix.