-
Notifications
You must be signed in to change notification settings - Fork 300
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Force settings in config.js on all users #214
Comments
Why don't you change it in SQL? |
At the risk of sounding naïve, I've never done any SQL editing. Would anyone be able to offer some guidance in this endeavor? |
Don't worry everyone has to learn, normally on your server you have PHPMyAdmin in there you just run a query to change the value of the one table or column, have a look here http://stackoverflow.com/questions/23442039/i-have-a-list-of-records-in-a-phpmyadmin-table-i-want-to-change-the-value-of-on |
It will change all the values in that one column for you |
One more tip, download MySql Workbench from here https://dev.mysql.com/downloads/workbench/ |
The settings in config.js that users can change in their own options are only meant to be defaults. If users clear their cookies and log into chat, those are they settings they get. There's no way to force them over to users other than ask them to clear cookies. I don't see a good reason to change this, really. Once someone is in your chat, they can change their own settings. The config.js file is also cached by user browsers, so they won't know about those changes unless they clear their cache (or unless you modify chat to force it not to cache that file). To do what you want would require a bit of work. |
I've always been a big fan of Blue Imp's AJAX Chat. Recently I set it up on a forum, and I've been tweaking the settings to my liking. However, I noticed that when I update things in config.js, everyone still has to manually change their personal setting to match the default I've set. Is there a way I can force certain settings defined in config.js on all users (but then continue to let them edit the settings after it has been set to the new default)?
The text was updated successfully, but these errors were encountered: