Hi,

Quote:

and/or 'visible' also to 0.

Also check the cache folder if you have module / block cache enabled.
Did you have set some of the SEO futures or path rewriting hacks?

Hi everyone!
First of all thanks for all the support! It's great to know that Xoops-support is not just a fancy name!

Quote:
How exactly do I do this Stefan?

Quote:
As far as I know, i did NOT changed any of these settings.

-Just a sideline question:
Will setting the block to
"isactive - 0 and visible - 0"
still have any effect if I already done this for the whole module? (see your previous advise)

Thanks again!

Edwin

Hi,

For the cache - in your XOOPS root you have 'cache' folder - look inside. You will have adminmenu.php and maybe some other files. If you have some files with 'smartsection' in the name - delete them.

Quote:

I would say that deactivating the module is enough, but I don't have experience with 2.0.15 and in your case there is something wrong.

Also some things you can try:

With phpMyAdmin do 'check' 'repair' if needed for some tables. When you select the table, chose 'Operations' from the phpMyAdmin top bar and at the bottom of the screen you will see 'Table maintenance' with check/repair options. You can try this on modules, newblocks and smartsections tables.

Try to rename smartsection folder in your modules dir. Do not delete it, just rename it to something else - delete first or last letter, so you can easy bring it back, and see what the result will be.

Hi,

A member of the Dutch XOOPS forum advised me, before doing anything else, to upgrade to 2.0.16.
What do you guys think of this?
Wouldn't this get the whole thing tangled up even more?
Or would it, as the Dutch members thinks, solve some of the problems...

I hope you guys don't mind me asking for different options and opinions as I feel seriously insecure messing up completely.

Thanks
Edwin

Hi,

I'm using hack of 2.0.13.2, so can't say much about later versions and upgrades.

My advise is, if you go this way, make backups first - database and files!

If you have a test system on a local computer do some tests first. 2.0.16 upgrade require runing upgrade script and that may require loging in as admin ... (maybe someone can give more info here ...)