Closed (fixed)
Project:
Metatag
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
11 Dec 2012 at 23:58 UTC
Updated:
28 Jan 2014 at 05:30 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
pbz1912 commentedI consider this a bug. It breaks the usefulness of being able to put this into features.
I want to disable the global:frontpage in code and keep it that way.
However if it is changed on the site it is impossible to revert the feature to disable that setting.
This is also a problem with an enterprise workflow where we are trying to deploy changes to the live site with code and to version control our settings. There is no way to push that change with code.
Comment #2
hefox commentedDoesn't sound like a bug to me -- it doesn't break the feature support, just makes it less useful. People can integrate with features however they want =). Views d6 also had a similar issue.
Comment #4
damienmckennaCommitted. Thanks. (and properly attributed this time too)
Comment #5
chriz001 commentedIm having a few problems with this change. Whenever i visit the module page i get this error:
In my exported module disabled is set to NULL. Ive tried re-exporting and enabling/disabling the module but it didn't help
Comment #6
chriz001 commentedComment #7
damienmckennaGah.
Comment #8
chriz001 commentedcool! Thats fixed the error for me :)
Comment #9
damienmckennaCommitted, thanks for reporting the bug.