I think the subject says it all. I was installing a few modules to try them out (tinycontent and the like) and somewhere along the line I lost all of the items in my main menu. You can see what I mean at jonwatson.ca
I have a user whose activation email is getting eaten by his spam software (we suspect).
Is there some way for me to either activate hsi account myself, or to edit his account details so when I resend the email it will go to a different account? All I can see to do in the inactive users page is to send an email to him.
Wolfpack link good. XOOPS link bad. I've looked in the FAQ. Is there an actual tutorial on the three points I mentioned in there? If so, I missed it entirely...
I'm attempting to trouble-shoot a module's layout. One of the things that is complicating this for me is that I don't have a full understanding of how XOOPS caches and updates module's html pages.
Is there a nice tutorial somewhere that explains how the following all work together:
1. the templaces_c directory 2. the 'Update module template .html files from themes/your theme/templates directory? ' setting in Preferences -> System -> General Settings 3. the 'update module' function in the Modules administration
In short: if I make a change to a module's php file, what do I have to do to make it show up on a browser refresh?
That seems odd to me because all my other modules center and I did that by adding a div centre tag (as you say) to the bottom of my header file. Therefore, anything below the header gets centered.
I'm willing to try, though, but the Dokuwiki code is the most complex I've run across yet. Any clues what file to plunk my div tag into?
My theme consists of two major parts - the header and the body. In all (except Dokuwiki) modules and pages, the body and header are both centered. However, on the Dokuwiki page, the body part is not centered.
Does any know why only one module would fail to center? It's the most recent module installed, if that makes a difference, and I'll be the first to admit that I don't understand the cache thing that XOOPS does at all...could it be that?