3012
Are you absolutely sure the db settings are entered correctly? See the Troubleshooting Guide in the XOOPS wiki (see to the left here) for turning error reporting on the hard way. Without error report we can't tell much about the issue...
Herko
Herko
3013
That last instruction dates back to XOOPS 1, where there was a config option where you could set what HTML tags were allowed for users, and which were not allowed. This probably means that the module is made for XOOPS 1 as well. This may not be completely compatible with XOOPS 2, since the core has many many changes.
In other words, it could be just a small issue and then be solved quickly, but it also can be a big problem because of incompatibility issues...
Herko
In other words, it could be just a small issue and then be solved quickly, but it also can be a big problem because of incompatibility issues...
Herko
3014
Log into your site as administrator, then go to system admin -> Blocks. You'll see a list of all available blocks there. You can configure the place, order and settings there.
Herko
Herko
3015
XOOPS comes installed with no sample content, blocks or modules installed or activated. This is what a clean install looks like. If you have installed any additional modules and aded content, I'd check the anonymous user group access to that module, if I were you. To do that, log in as admin, go to system admin -> groups and check every module you want your site's visitors and members to have access to.
Herko
Herko
3016
Quote:
You could try the cache settings for the blocks that don't need to be queried from the DB every time a user visites the page. This can reduce the number of queries a lot, thus saving you on the load time.
Herko
brash wrote:
I ran the MySQL/Blocks dubugging mode, and I found that upon entry to my site the server runs 77 queries, 23 blocks in about 1.3 seconds. Short of removing content, or upgrading my hardware I have no idea if there are any other methods to reduce this time.
You could try the cache settings for the blocks that don't need to be queried from the DB every time a user visites the page. This can reduce the number of queries a lot, thus saving you on the load time.
Herko
3017
Yes, it's built in to the XOOPS core. You can refer to backend.php, which generates such a feed. Just try www.xoops.org/backend.php
Herko
Herko
3020
Normally not being one to dig up old grudges, but the fact of the matter is that eXoops is a XOOPS1 fork by Half-Dead, who didn't agree on the devs descision to go with Smarty. His disagreement led him to take the CVS code (which is ok), and started his own fork (which is also ok, albeit he didn't do it in a friendly fashion). The grudge the devs hold over e-Xoops is that Half-Dead removed the credits and copyrights of the CVS code, and with little to no adjustments released it as his own... That, by any standard, is plain rude and illegal as well, since the code was released under the GNU-GPL licence.
This was a looong time ago, and XOOPS has moved on, since. The fact remains that a lot of confusion is created by the name eXoops, and the main differences. Personally, I support XOOPS and think that eXOOPS has been left behind when we moved to smarty. But please jedge yourself
Herko
This was a looong time ago, and XOOPS has moved on, since. The fact remains that a lot of confusion is created by the name eXoops, and the main differences. Personally, I support XOOPS and think that eXOOPS has been left behind when we moved to smarty. But please jedge yourself
Herko
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | May 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|