Hello,

I'd been using String Overrides on my Open Atrium site with great success, until recently. I attempted to change one of the string replacements using the String Overrides UI, and nothing happened; no matter what I tried, my changes would not take effect.

My first reaction was to check the permissions to make sure my role could administer string overrides. When I did this, I saw that there was a line that said "stringoverrides module," but there were no check boxes next to it for any of the roles. In essence, I was left with the "stringoverrides module" heading but no actual permissions to see/tweak.

I couldn't figure out what was causing this, so I tried disabling, uninstalling and reinstalling the module. No luck.

Even more frustrating, I restored my entire site (both the code and the database) from a backup and I STILL had the same problem (even tried several times from different backups, dating back to a month ago). How could this be?

One added but perhaps unrelated note is that even after disabling/uninstalling the string overrides module, my overrides remain, even after clearing my Drupal cache. The only way to get rid of them appears to be manually editing relevant database tables. I thought this was odd, too.

I really would appreciate anyone's help.

Comments

rbenhase’s picture

rbenhase commented
Category: support » bug

Changing to bug report, as repeated attempts to fix the issue have led me to believe the problem is likely either with the module itself or conflicts with another module. Has anyone else experienced a similar problem, though?

michaelraasch’s picture

michaelraasch commented

I have the same problem. I can only edit the string overrides when I log in as admin.
As admin: I grant the "administer string overrides" to one of my support roles. Then flush the caches (just to make sure) and the permission is removed from that role again. This is very odd.
I agree, it may clash with a different module, because granting permissions works fine with a different Drupal installation of mine.
If you find out what causes this, then pls post it here in this thread.

michaelraasch’s picture

michaelraasch commented

I figured out what the problem in my case was.
I have some Drupal actions. Some of those Actions have tokens (the ones with [ and ]) in their description, so I can change on the fly what is displayed (that was a customer request). However, in the permission-granting screen, the description is used to to create the form. And the tokens throw the form-validation off guard replying with an "illegal choice deteced". I have removed the tokens and everything was fine again.
Hope that helps you as well.