Bug #198
Webpanel Settings checkboxes aren't saved - Bug Still Present
| Status: | Closed | Start: | 08/03/2008 | |
| Priority: | Normal | Due date: | ||
| Assigned to: | Brad Smith | % Done: | 0% |
|
| Category: | Web Panel | |||
| Target version: | 1.2.1 | |||
Description
In SVN rev 108, the below bug is still present.
When you check the Disable Log Popup, Enable Protest Ban or Enable Submit Ban checkbox and click Save Changes, the checkboxes are unchecked again after reloading the page.
Related issues
| related to SourceBans - Bug #196 | Webpanel Settings checkboxes aren't saved | Closed | 08/03/2008 |
History
Updated by Recon _ 154 days ago
Shouldn't the checkbox.checked assignment be done in the template?
I didn't mean to set done to 100% (I did an issue copy).
Updated by Brad Smith 154 days ago
I could not duplicate this problem with R108. As for putting it in the template, possibly. But using javascript in the smarty template is not fun and probably why it was separated originally. Can you do a view source on that page and check to see if the .checked is being set to 0 and 1 respectively. Are you using any custom templates other than default or sourcebans_dark?
Updated by Recon _ 153 days ago
Brad,
Of course I already did that... The value is being properly retrieved, but it never makes it to the checkbox. I am using the default template.
How about assigning a smarty var with the checkbox value in the page code then assigning the smarty var to the checkbox in the template? Wouldn't that fix the problem?
FYI: The enabled checkbox on the mod edit page seems to be working fine for me.
Could it have anything to do with the fact that I use FF3?
Updated by Recon _ 152 days ago
Yes. Maybe it has something to do with the location of the script block? For some reason, the mod edit page works perfectly...
Updated by Erik Minekus 150 days ago
- Status changed from New to Closed
- % Done changed from 100 to 0
Alright, the problem is that you're missing config.enablekickit and config.exportpublic in your settings table, causing a JavaScript error. You can just insert them like this:
INSERT INTO sb_settings (setting, value) VALUES ('config.enablekickit', '0');
INSERT INTO sb_settings (setting, value) VALUES ('config.exportpublic', '0');