Hello,
I noticed that when I point two environments to the same database in my settings.php, the module caches the indicator for the latest environment in which the cache has been flushed. In version 1, I was able to use the same database for a local copy, and a staging, and change the text and color for my local copy in settings.php. But it doesn't seem to honor that. I added version 2 friendly configuration variables (from documentation) to my setting.php, and when I flush the cache in my local, it shows the settings for my local environment on my staging site as well. This wasn't the case in 1.x branch. Is there a way around this?
Comments
Comment #1
jbrauer CreditAttribution: jbrauer commentedA strong second for this. I'm just looking at upgrading and much of the build and deploy process on my site relies on this ability to share databases but have different settings per site in settings.php.
Comment #3
e0ipsoAfter some thought about this I have decided to skip cache for overridden indicators (meaning that you define them in
settings.php
instead of the new cool way).Now that you can skip cache altogether this is fixed.
Thanks for reporting!
Comment #4
hessam61 CreditAttribution: hessam61 commentedAwesome! thank you.
Comment #5
e0ipso@hessam61 I would love to hear back if that commit fixed your issue.
Comment #6
hessam61 CreditAttribution: hessam61 commentedI did work, but I had to delete all the environments, including the default, one for it to work. Basically I added configurations variables to all the settings.php files (with different settings of course). Thanks for fixing it again, love this module.