Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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 |
|
Comments
Comment #1
bnobleman CreditAttribution: bnobleman commentedI 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 commentedHere is my workaround.
Comment #3
sbrattla CreditAttribution: sbrattla commentedI'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
dagmarComment #5
sbrattla CreditAttribution: sbrattla commentedI'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.
Comment #6
bisonbleu CreditAttribution: bisonbleu commentedThe patch in #2 no longer applies to the current dev (7.x-2.0-alpha3+11-dev). Here's a fresh one that does. Thanks Chi!