After upgrading from beta6 to rc1, features is unable to determine the status of some of my previous features. The column labeled "state" turns blank when the "Checking..." label disappears.

Sometimes the features overview page lists one feature as being "Overridden" but when I click on the overriden link, the next page shows me that the whole feature is "Default"

CommentFileSizeAuthor
#2 features-false.png26.03 KBjenlampton
#1 features-overridden.png20.27 KBjenlampton
#1 features-default.png98.2 KBjenlampton
features-wtf-1.png19.15 KBjenlampton

Comments

jenlampton’s picture

jenlampton
she / her
commented
StatusFileSize
new features-default.png98.2 KB
new features-overridden.png20.27 KB

Sometimes the features overview page lists one feature as being "Overridden" but when I click on the overriden link, the next page shows me that the whole feature is "Default"

screenshots of overridden vs default


jenlampton’s picture

jenlampton
she / her
commented
StatusFileSize
new features-false.png26.03 KB

On the "review overrides" tab, the difference is apparently FALSE

univate’s picture

univate commented

Not sure if this is related but I have also noticed problems upgrading from beta6 to rc1.

When using with context 3, all my contexts defined in features don't appear in the UI?

hefox’s picture

hefox commented

univate: unrelated, see issue linked to on frontpage of features.

Anyhow, was there ever a menu link with path usa_pr_menu (wtf a path with) as part of that feature? The feature's page shows no menu links in that feature, but the diff is thinking there is one defined.

mpotter’s picture

mpotter commented
Status: Active » Closed (won't fix)

Closing this for lack of activity. Please re-open this issue if you can reproduce it in the latest version.

mpotter’s picture

mpotter commented
Issue summary: View changes

add more conflict