Quote:
I would suggest looking at http://www.opensourcecms.com (and I think there's another site). It posts some of the more common CMS. Although I think Xaraya and Mambo have some good following.

The Contact Us module uses the Admin email found in Sys Ad -> Preferences -> Gen Settings. Is this where you edited it? This should work.

XOOPS call the templates from the DB and not from HTML files in the web folders. Please do a search on cloning templates for editing. This will be the topic you want to tackle first.

There are old threads discussing about Tinycontent Duplication and even cloning the News module. Do a search for those as they would be helpful in this case.

I'm not sure if there are system-wide effects. As I see it, the uid is the most important identifier.

The main problem you might encounter is the need to check that the new username does not have a duplicate in the database, i.e. other users already have that username.

I wasn't sure what you really wanted to do but these links might help:

Placing Blocks
Custom Block
News Module Help
Block positioning question
Modifying Module Blocks Administration details

Do you have PHP installed?

If you just changed the root password for MySQL in your local setup, you might need to 'FLUSH PRIVILEGES' for it to take effect.

If you have phpMyAdmin installed, you can just click on the link given in the index page. Or you can use the MySQL command line.

Quote:
That would probably be an issue of HTTP_REFERRERS.

Check this thread: NIS Problems

You can also do a search. Several similar threads will come out.

At the risk of over-generalization, we find major 'public' problems with release versions from the actions of those too eager to update but lack enough skills (PHP or XOOPS) to really know what they are doing.

I feel that those who have used XOOPS for some time know enough to test release versions on test sites or local setup. It is not meant for the weak of heart.

I have a local setup that serves as a backup of my site. I also use it to experiment with new modules and upgrades, if I have the time. If I find some errors or bugs, I would definitely report it here. But if I don't have time, I usually wait for some bug reports here. Nobody should immediately upgrade their live site just hours from a new patch release, unless they know what they are doing.

This is not to undermine the devs efforts. I could feel the sense of accomplishment from the devs when they released the new version. But all products have to be tested and, as with most open-source, the community does the testing. XOOPS is actually lucky that a bug was found hours after release. It was easy to pull back without widespread damage.

New XOOPS users should be aware of the community testing phase of open-source, especially for release versions. It is not like proprietary software or an anti-virus software where you can just click a button to update virus defs.

For the other issue of old problems answered but continually re-surface, we are hoping that some good documentation would minimize that--and the Documentation team is hoping to make contributions in that aspect.