Drush "missed" 6.x-2.0-alpha3 and carried out the update from patched
alpha2 directly to alpha4. During the update the following error was issued
for some content types: 

Couldn't recognize variable: <em>comment_subject_field:default_value_story</em>

Following that, my CS configuration for story was gone (no big deal...), being replaced by 

COMMENT_SUBJECT__DEFAULT_SUBJECT_PREFIX
COMMENT_SUBJECT__DEFAULT_SUBJECT_BETWEEN
COMMENT_SUBJECT__DEFAULT_SUBJECT_SUFFIX

Comments

arhak’s picture

arhak commented
Priority: Normal » Critical

please, stay with alpha2, until we fix that
commit wasn't clean, right now maintainers copy works fine, but packaged tarball went wrong
hold until alpha5

more details:
alpha3 was a bug fix, while alpha4 got new features, that was why we released two at the same time
haven't checked if alpha3 is working, by now alpha4 is BROKEN
please, some patient, we are working on it

arhak’s picture

arhak commented
Title: Update error » BROKEN Update (working on it)
arhak’s picture

arhak commented
Title: BROKEN Update (working on it) » BROKEN alpha4 Update (working on it)

alpha3 is fine

arhak’s picture

arhak commented

attempting an alpha5, please wait until confirmed

arhak’s picture

arhak commented
Title: BROKEN alpha4 Update (working on it) » BROKEN 6.x-2.0-alpha4 update (commit flaw fixed on alpha5)
Status: Active » Fixed

6.x-2.0-alpha5 is fine

(a well as 6.x-2.0-alpha3, just 6.x-2.0-alpha4 got broken)

arhak’s picture

arhak commented
Title: BROKEN 6.x-2.0-alpha4 update (commit flaw fixed on alpha5) » BROKEN 6.x-2.0-alpha4 (commit flaw fixed on alpha5)
arhak’s picture

arhak commented

BTW the message "Couldn't recognize variable" is another issue #689884: Couldn't recognize variable: comment_subject_field:default_value_[type]

arhak’s picture

arhak commented

@skizzo

my CS configuration for story was gone

no, it is actually there and successfully migrated (update_6002)

once you replace the files with 6.x-2.0-alpha5 you'll find everything is ok and you're already updated

if your update only showed THAT "Couldn't recognize variable: ..." (from the unofficial version 0.4, see #689884) then everything was fine

just don't know how the heck .module file got corrupted that way (it got partially patched)

skizzo’s picture

skizzo commented

Yesterday I ended up doing a drush disable and drush uninstall (although I now see there is no real uninstall).
Today I enabled 6.x-1.5 (datestamp = "1258616711") but oddly the three comment subject fields do not show up
anymore in the Content Type administration form. I guess my system is not in a clean state. Is there any variable
that I should clear?

arhak’s picture

arhak commented

@#9 I reproduced your situation and nothing got broken, it got ugly for a while (as described in the orignal post), but downloading 6.x-2.0-alpha5 fixes the problem and the variables are already migrated

the only dirty variable you have is explained at #689884: Couldn't recognize variable: comment_subject_field:default_value_[type]
but that has nothing to do with the broken 6.x-2.0-alpha4

I enabled 6.x-1.5 [...] but oddly the three comment subject fields do not show up
anymore in the Content Type administration

of course, 1.x branch does NOT support tokens, it has no settings page and it is not configurable per content type, it just enables the "Re:" behavior for every content type there is (that was the original feature of this module)

WHAT TO DO
-------------
- your variables got migrated (via comment_subject_update_6002), that's a fact
- now you can use 6.x-2.0-alpha5 (I recommend you this)
- also, nothing keeps you from using 6.x-2.0-alpha3. I also tested your case for that and the only downside is that configuration will be reseted to defaults (since it got migrated to the new names)
- the worst scenario, there is no big deal with 6.x-2.0-alpha2 besides the bug #678024: HTML entities require to be decoded for [comment-parent-title]

EDIT: skizzo, I think you confused 6.x-1.5 with 6.x-2.0-alpha5 (note that 2.x branch is the one with token support, and it is not marked as recommended, just supported, since it is an alpha yet)

arhak’s picture

arhak commented

BTW be aware of UI changes in 6.x-2.0-alpha5 #683706: UI improvements for settings (screenshots available)
- 1.x branch doesn't have any settings anywhere
- 2.x branch up to 6.x-2.0-alpha3 has three textfields (per content type)
- latest 6.x-2.0-alpha5 has one textfield and a checkbox (per content type)

skizzo’s picture

skizzo commented

yes, that was it... I didn't realize that drush dl would pick the latest stable,
i.e.: 1.5. I am now running 6.x-2.0-alpha5, so far without any problem. Thank you.

arhak’s picture

arhak commented
Status: Fixed » Closed (fixed)

clearing the issue queue
(no usage is being reported for that broken release)