The footer is probably hard coded at the bottom of your theme.html.

Quest

try a different method of sending by changing the settings in the module preferences. Php Mail, SendMail etc.

Quest

Have you recently installed a new module or made a change to your theme etc?

Try to login as administrator at
hxxp://www.your_xoops/user.php

Go into administration/system/preferences/general-settings and turn on Debug PHP then click okay and try to return to your homepage to see if it reports any errors.

Quest

Yes.

The user logs in to your site. Then clicks on View Account in the User Menu. At the top they click on Avatar and they can select None from the drop down list then submit and it will get rid of their avatar, or they can change it to a different one too, themselves.

Quest

I wouldn't post your mainfile.php, unless you are willing to change it again. It contains db login information which should always remain secure.

A few questions:

Did your database take on a different name and or prefix for your tables when you moved accross domains. If so did it get changed in the mainfile.php too?

What text editor did you use to make the changes to the mainfile.php? It is very important to use a good text editor-wordpad and notepad can cause problems with whitespace in php and java coding.


Quest

@Vargr

Just remember, the template overiding doesn't seem to work if you are using a cloned template set. It does work and works great, as long as your default template in your admin/system/preferences/general-settings is set to Default and not a cloned template set. At least that has been my experience.

Best of Luck! And remember: Never condemn those who try and fail, save that for those who never try.. :)

Quest

Vargr

Quote:

The newer template functionality of around XOOPS version 2.14 allows XOOPS users to place templates inside their theme folder. Relieving the need to clone the default template set. This was and is a great addition to the XOOPS functionality which eleviates (if used) the problems you mention from occuring during module updates or XOOPS upgrades. The XOOPS user's modified templates are within the used theme folder therefore they are not in danger of overide and can easily be downloaded with your theme folder onto your PC for safe keeping.

Here is an excellent Tutorial on Template Overide feature introduced with XOOPS 2.014, posted by alain01

https://xoops.org/modules/news/article.php?storyid=3367

Quest

IMHO:
I do not feel your assertions are all together correct in relation to the fact that XOOPS is an Open Source CMS. It has come to me by experiencing XOOPS for several years now, however cumbersome it may sometimes seem, it is the very thing that seperates it from the other open source CMS(s) offered out there. I have checked out the others and believe me when I say this-although they appear to have things in order, looks can be deceiving.
To be honest with myself first I had to realize I was very excited about XOOPS and when I started it did come with modules but it was my own excitedness and expectations which got me the most frustrated. In hindsight the modules which came with XOOPS I wanted to change anyway for others that were offered. And what I ended up doing anyway was uninstall them all (except the system module) then used the XOOPS Search to find what I wanted making sure I downloaded the most recent version of the module I wanted and asking question pertinent to that specific module. And with the veracity of helpfullness that can only be found at Xoops.org I was and have always been helped.

FIRST what I didn't do, because of my knowledge, excitedness and expectations, I didn't read the F.A.Q.s and I didn't bother reading the documentation. For example-I too had what I thought were problems with the Modules and Installation of the modules, only to find that there wasn't anything wrong at all, I had indeed uploaded it but I hadn't installed it so it just sat there doing nothing that I expected it to do.

SECONDLY: I didn't use the XOOPS Search! As per numerous suggestions written in the F.A.Q.s, Forums, and Documentation. I now realize from being around a little while that sometimes questions don't get answered in a forum because they have already been answered many many many times. Generally even then-someone comes to the rescue. Another great thing only found at Xoops.org.

Thirdly: Module updater and Installer. This would be a wonderful thing to have and an excellent feature in most software that is not Open Source! However, since the XOOPS Core is under great revisions, and no matter how you look at it XOOPS is Open Source-therefore many if not all modules other than the XOOPS core System module, are from 3rd Party community contributors. So by virtue of the very thing that makes XOOPS great-it would be very difficult to create one as you suggest and still remain Open Source! But I know I would be happy to try it out should you develop such a module. :)

Fourth: As far as I know, XOOPS does not write the standard. Other than the XOOPS core, which is constantly being updated to keep up with the standards of the World Wide Web, PHP, Mysql, etc. Whos standards do you suppose XOOPS should adopt? Mine? Yours? W3C? Firefox's? IE's? Operas? Linux? Windows?

Fifth: I would like to say Welcome to the world of XOOPS Whoops and Happy New Year!

Quest

xoops/admin/system/modules

Give a zero 0 for the modules you want to hide. Users will still have access to them, as long as you have it set up correctly in the group access.

Quest

Gotcha. I do see the difference now. I'll do some looking around to see if can come up with a possible solution to the agonizing < b >.

Quest