Setting custom theme as default theme locks everyone out of the forum [message #159930] |
Fri, 10 July 2009 10:15 |
ANiko
Messages: 30 Registered: May 2009
Karma: 0
|
Member |
|
|
Fresh install of FUDforum 2.8.1 on Linux, Apache 2.2.11, MySQL 5.0.81 and PHP 5.2.9.
I can lock everyone out of my forum -- including myself -- unintentionally, ie, without using the global settings. I just set the default theme to a custom theme instead of the (named) default theme and we're all stuck.
Steps to reproduce:
1. Log in as admin and navigate to your forum's Admin Control Panel-> Theme Manager.
2. Create a new template set based on Path_info. Name it custom.
3. Create a new theme using the custom template set. Language and location English. Mark the default and enabled check boxes.
Name this new theme and click "Create."
4. Rebuild all themes.
5. Return to the forum and navigate around. Check that everything is working as it should. It appears to be, even after the cache is cleared.
6. Let's check what all other users except the Admin user see. Open a different browser and go to the forum index.php page. The user can't log in, can't visit the forums or members list, can't register or do anything else because a click on any link refreshes the current index.php page instead of showing the user what he expects.
The other user is locked out of the forum.
If the other user had been logged in as a member, he'd be locked out too, because clicks on any link only refreshes the index.php page instead of navigating to the intended page.
(DON'T DO THIS! but if the admin user logs out, he's locked out of the forum too. Every click on a link only refreshes the index.php page. And because some of you will lock yourselves out in testing this even after I told you not to, to save your forum use the browser's back button to return to the admin control panel. You'll be prompted for the admin user and password, but you'll get back in.)
So this is verified as broken.
To fix this:
7. In the logged in admin window, navigate to your forum's Admin Control Panel-> Theme Manager.
8. Edit the default theme by setting it as default with the check box and click on the update button.
9. Rebuild all themes.
10. All users can now navigate around the forum as normal.
[Updated on: Fri, 10 July 2009 10:15] Report message to a moderator
|
|
|
|
|
|
|
Re: Setting custom theme as default theme locks everyone out of the forum [message #159950 is a reply to message #159943] |
Sun, 12 July 2009 09:29 |
ANiko
Messages: 30 Registered: May 2009
Karma: 0
|
Member |
|
|
Thanks. I totally forgot about reading about that when I was studying the documentation 2 months ago. (Can you tell I've only played with the Windows version up until this install on a Linux server?)
I tried your patch. It worked initially -- until the cache was cleared. Then the user was stuck on the index.php page until the admin user went back to the default theme.
Just to make sure I applied the patch correctly, I added the lines with the + in the far left column and deleted the line with the - in the far left column.
I don't know if this is significant, but in case it is: my compiler.inc file was version 1.98 (from the FUDforum 2.8.1 install) when I applied the patch to make it version 1.100. I don't know what version 1.99 is. Any way to find it easily so I can apply it, too?
I tried this every which way I could think of: unlocking the files before creating the new template based on the Path_info template, creating the new theme with that template and setting that theme as the default theme; starting over by uninstalling, reinstalling and applying the patch, then creating the new template based on the Path_info template and the new theme using that template and making that the default (current) theme. Always locks the other users out of the forum until the admin user reverts back to the default theme.
BTW, uninstalling doesn't drop the FUD28_ tables and it doesn't delete the GLOBALS.php link in the forum/adm directory, so that directory can't be deleted during the uninstallation because it isn't empty.
Thanks for your help, but the problem doesn't seem to be resolved yet.
|
|
|
|
|
|
|
|