Quote:
ARGGH - another issue - My posts don't get in - I get a message saying Thank you for your post: Already submitted. (Perhaps it's a timeout on login??)
I've never had this on my site, but I do get this occasionally on xoops.org, like you had.
I tend to select all and copy, just in case I have to paste it back in and post again.
Sometimes I get logged out, but this is the lengthy posts, as my session expires.
Quote:
1. The theme was from http://www.omnetwork.net and called OM7, you have to put up with registeriung and lots of pop-ups to get it. It downloads with two folders: om7 and res, both of which had theme.html files with correct permissions at my site (755). I have the files and can email tem to anyone who wants them.
I did find this after my last post and then got distracted with other things and forgot to post the address.
These guys released a fair few themes a short while ago, I tested one of them and had problems myself, because at the time I was too busy to look into it, I never bothered with their themes again. Thats not to say there bad themes, just that I didn't have the time to look further.
The user on XOOPS is called hardyvoje, and his X profile can be found here:
hardyvoje - Click HereIn the admin ---> general settings, etc.
You have default theme, and selectable theme.
In your blocks admin you can choose a block which allows users to change the theme from the back end, now when they do these are not permanent theme changes for the whole system, only for that user.
Quote:
I tried that after the blank screen and got a 'you are not authorised message that redirected me to a blank screen. all other 'back-end attempts yielded either a blank screen or a redirect... UNTIL I changed the [offending theme name] to [dummyname], and the 'default' theme name to [offending theme name], cleared templates_c (except index file) and retried. THEN I got the opening XOOPS page BUT only with Header and footer - no side menu to access Admin etc. And in templates_c two new files with [offending theme name] in the title appeared.
If you've done it this way, and it worked, you can type the url
http://www.yoursite/user.php and then log in from there.
If you still have no side menus, type in
http://www.yoursite/admin.phpChances are the you changed the theme folder name, but the block code in the html files have the default path hard coded:
<{include file="folder-name/theme_blockleft.html"}>
This code will be different if they use the new XOOPS template code, ie $xoBlocks
Quote:
5. My choice of words in the first post may have been a bit emotive, but the other instance I found in support (see my first post) was a longstanding production site that similarly blanked out after a theme change. I was concerned about putting 1000s of hours into building a site which could crash on a theme change. From your comments it seems this is either exceptional, or it is module related (how is anyone's guess) but rarely happens.
I've been running many, many XOOPS sites for years, well since the project practically started, I was one of the first nuke converts, and it's very rare I've had a problem, when I have it's been something I've done, and then I back track and fix what I broke.
I have had problems with modules conflicting, sometimes it's something simply like similar instances, which the developer may not of seen in another module. Sometimes a little more complicated, but then again you get this in all CMS's even the commercial ones.
If I'm totally stumped I ask the good people here in the community and most of the time I'll get a reply that helps and works.
I think you noticed the amount of people trying to help in this thread, and that's one thing I love about the XOOPS community, most people want to help others, as they've been there, and pulled their hair out too. lol
Quote:
Did you choose the new theme as the Administration theme instead of using it for your Default theme?
If you using 2.0.16 then this shouldn't effect you, I believe that option is only in 2.2.3 - 2.2.5 at the moment.
Hope this has been of some help.
