42
By the way, if you literally want to have something similar to the site (not just the way the blocks are displayed), the site uses the Blue Lagoon theme available here in the Themes Library.
43
A few modules are kind enough to give you the option of excluding the module link from the Main Menu listing. If you have things like "Home" and "Contact Me" as buttons in your template header, it is a waste of space to repeat this in the Main Menu block.
Is there any easy way to exclude a module link from the Main Menu? The only way I can think of is to edit the Main Menu block and have an exclude statement in the linking loop for each module you don't want listed.
Is there any easy way to exclude a module link from the Main Menu? The only way I can think of is to edit the Main Menu block and have an exclude statement in the linking loop for each module you don't want listed.
44
Almost any theme is easily modified (width, for example) by editing either the theme.html or style.css (or both) files. You can use an editor as simple as Notepad to open either file and change the width paramaters.
45
David: I'll always remember FGTH as the first CD that made buying an expensive (at the time) CD player a must. Still a great CD to play. 
46
As Rudix said, you could also have XOOPS in a different directory. I have my own misgivings about not having XOOPS in the root directory, however.
Either way, your index.html or index.htm file with the Flash code would either have a link (click to enter our site) or a timeout that goes to the index.php --which is always the XOOPS main entry point.
So, the simple thing is to have a very short index.htm that starts with the flash code and ends with a graphic or text link, "ENTER" or whatever, that is a simple link to "http://www.yoursite/index.php" or "http://www.yoursite/xoops/" if you want to put XOOPS in a different directory.
If you want a timeout that automatically loads XOOPS after a few seconds, then it would be best to edit the Flash code to go to your XOOPS main page after the Flash plays.
Either way, your index.html or index.htm file with the Flash code would either have a link (click to enter our site) or a timeout that goes to the index.php --which is always the XOOPS main entry point.
So, the simple thing is to have a very short index.htm that starts with the flash code and ends with a graphic or text link, "ENTER" or whatever, that is a simple link to "http://www.yoursite/index.php" or "http://www.yoursite/xoops/" if you want to put XOOPS in a different directory.
If you want a timeout that automatically loads XOOPS after a few seconds, then it would be best to edit the Flash code to go to your XOOPS main page after the Flash plays.
47
It should just be a matter of having an index.htm file with the Flash intro that then goes to your XOOPS index.php. Since index.htm "outweighs" an index.php file, the htm will load first. However, there are disadvatages, like the Flash intro popping up again if the user goes "home" without using your specific home link that would be back to the php file.
To my mind, however, Flash intros suck.
One major use of a good CMS like XOOPS is to encourage frequent visits and to present a good bit of information on a central page.
Nothing is more annoying to a frequent visitor than to have to see the same boring Flash intro on every visit.
I think you should first reconsider whether you want to annoy your users for the sake of something pretty.
Flash intros are better suited to a corporate information site that is not updated much and has mostly once-only visitors.
To my mind, however, Flash intros suck.
One major use of a good CMS like XOOPS is to encourage frequent visits and to present a good bit of information on a central page.
Nothing is more annoying to a frequent visitor than to have to see the same boring Flash intro on every visit.
I think you should first reconsider whether you want to annoy your users for the sake of something pretty.
Flash intros are better suited to a corporate information site that is not updated much and has mostly once-only visitors.
48
I applied the hack. Works with no problem.
Interesting, though. The autologin check box is already in the login block in the template but is commented out. It also doesn't have the text "remember me" or whatever you might want.
So, I uploaded the two new files as instructed. Then I edited the entry in mainfile.php. And finally, I edited the block template from within the administration template editing area to un-comment out the remember check box. I then saved the new template.
Remember that you will need to clone your template since you can't edit the default template, then you will have to make the new template your default template from the system admin area.
Interesting, though. The autologin check box is already in the login block in the template but is commented out. It also doesn't have the text "remember me" or whatever you might want.
So, I uploaded the two new files as instructed. Then I edited the entry in mainfile.php. And finally, I edited the block template from within the administration template editing area to un-comment out the remember check box. I then saved the new template.
Remember that you will need to clone your template since you can't edit the default template, then you will have to make the new template your default template from the system admin area.
49
I'll try the 2.2 hack on an experimental site I have running to see if it works for me.
I will let you know how it went.
I will let you know how it went.
50
Mainfile.php is set to 444 to prevent changes --either malicious or accidental.
You will need to CHMOD it to 777 before you can edit it.
You will need to CHMOD it to 777 before you can edit it.
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | Apr 30 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|