Status does not refresh for variables [#1956910]

1. On site A I add a variable and start tracking it
2. On site B I synchronize the variable
3. I change the variable on site A and write it to datastore
4. Refresh the page on site B, and it still shows "In Sync", but when clicked "View Info", it shows "Overridden" and diff works fine
-------
Bernard Szlachta
http://www.nobleprog.co.uk/drupal/training
http://www.nobleprog.us/drupal-training-courses

Comment	File	Size	Author
#6	configuration-status-does-not-refresh-1956910.patch	2.03 KB	bisonbleu
#6	7.x-2.x: PHP 5.3 & MySQL 5.5, D7 66 pass
#2	quickfix.patch	2.02 KB	Chi
#2

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

bnobleman CreditAttribution: bnobleman commented 28 August 2013 at 15:35

Priority:	Major	» Critical
Status:	Needs review	» Active

I tracked it down to problem with hashBuild method for variables
-------
Bernard Szlachta
http://www.nobleprog.co.uk/drupal/training
http://www.nobleprog.us/drupal-training-courses

Comment #2

Chi CreditAttribution: Chi commented 29 May 2013 at 14:01

Priority:	Critical	» Major
Status:	Active	» Needs review

File	Size
quickfix.patch	2.02 KB

Here is my workaround.

Comment #3

sbrattla CreditAttribution: sbrattla commented 20 November 2013 at 09:56

I've tested the patch provided by Chi in #2. This works very well.

I've experiences issues with status not being correctly displayed for most items (e.g. views). The overview list would say "In Sync", but when clicking on an item i know has been changed it says "Overridden".

The overview list now correctly displays "Overridden" after the patch has been applied.

I'm voting for this patch!

Comment #4

dagmar

Spanish

Argentina

CreditAttribution: dagmar commented 20 November 2013 at 13:15

Issue summary:	View changes
Status:	Active	» Needs review

Comment #5

sbrattla CreditAttribution: sbrattla commented 11 December 2013 at 18:17

I've tested this patch a little more, and even though the code is much cleaner than the current implementation (it uses the status codes produced by Configuration#getStatus() I don't think it solved the issues I had after all. In my case, I believe the issues rather were rooted in the various configuration handlers not being quite up to speed.

Anyway, I still think this patch is good as it is cleaner and it uses Configuration#getStatus() which eliminates code duplication.