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

jbrauer’s picture

A 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.

  • Commit 324426a on 7.x-2.x by e0ipso:
    Issue #2284655 by e0ipso: Avoid caching for overridden environments.
    
e0ipso’s picture

Status: Active » Fixed

After 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!

hessam61’s picture

Awesome! thank you.

e0ipso’s picture

@hessam61 I would love to hear back if that commit fixed your issue.

hessam61’s picture

I 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.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.