I use one of the backup modules for Xoops. I can save locally or send to an email address which is a nice option since GMail has a 2 gig limit now. If you save locally, it lets you determine how many copies to backup. Not all of the backup modules do restores as well.

The module I use has instructions on setting up a chron job to automate the backups if the OS the site is on supports chron.

I found mine here by doing a seach on backup modules.

If I delete inactive users from a site, what will happen to their posts? Does it orphan them and cause problems? What would be the suggested method to clean up the userbase to get rid of dead wood?

I seem to recall a topic on this in the past but search wasn't coming up with any hits. Thanks for your help!

Very encouraging. After the joys of getting Apache, PHP and MySQL to work in the past, a one button install that functions well will be a godsend.

I did consider XSAS but I would rather have a more generic base install for my web server infrastructure. XAMPP seems to be the more flexible choice for my needs.

I need to setup a new server and rather than wrestle with Apache, PHP and MySQL I thought I'd give XAMPP a try. It looks like a much simpler way to set up a server quickly.

Have any of you had any experience using XAMPP? Good? Bad?

Do you have any helpful hints for using it?

How do you feel about its security?

Thanks in advance!

I love Xoops. :)

You guys take a pissy tirade and turn it into a productive new direction for Xoops. And I can't even remember what the original poster was whining about anymore because the moderators polishing the forums, FAQs, etc is so exciting!

The more I use the following file repository, the more I really wish I had something like it available for Xoops.

http://www.curse-gaming.com/mod.php

Categories are listed clearly and simply.

Files are listed with a brief description within each category.

Files are detailed when selected with a full history of revisions. This is very important for situations like we currently have with 2.0.x and 2.2.x to determine which file works with which version. It also lists languages each file is currently translated for. And of course, the file upload date so you have an idea of how current the file is. The revision history is the main feature I'd like to see imported.

File descriptions are editable by submitter. At the above site, they require all submissions to be approved by admins I think.

File descriptions include revision notes and feature sets.

We've already got a comment system in XOOPS which I think is great for a download module.

-----

So if I want to install CBB on my site, I can click on ONE link for ALL versions of CBB. I can then see what versions of XOOPS are supported. I can see when the files were uploaded. I can see whether my language is supported. I can see whether the bugs I experienced last iteration have been fixed. In short, I can make an informed decision quickly and easily.

-----

Thanks in advance for considering creating something along these lines!

Thank you for the frequent updates, upgrades and fixes. I'd rather see the project always moving forward than sit stagnant for months between monolithic changes. The changes for 2.2.x are significant. We all knew that some modules may not work as intended. The only way to get them working 100% is to use them and report the issues.

If working through bugs doesn't appeal to you, then don't be an early adopter. The XOOPS devs definitely maintain support for earlier known stable version. This posting is a great example -- security fixes are coming for both 2.0.13 and 2.2.1 with next update.

Why isn't the XOOPS site updated to 2.2.x yet? I'd reckon the devs are just a tad bit busy working. Sure it's nice to know the chef eats his own food. But not if it gets in the way of cooking dinner for the rest of the customers.

Keep up the great work! I'm looking forward to the module "packs" and the 2.4 release!

Ok, so I'm not the only one....

I have an updated 1.7 using XOOPS 2.2 and I can't find the add link option either. I've used MultiMenu in the past and it's super simple. But that button just isn't appearing for me....

I like DokuWiki. There's a thread about it here in the forums and a walkthrough on integrating available. It's a little different from most in that it's a plain text rather than database-driven wiki.

@Forgiven: The short answer is yes, this multisite hack can probably do what you'd like. Bear in mind though that this thread was started to explore a hack that adds functionality that is not in the base XOOPS install. The title asks us to test it out if it sounds like something we might find useful.

I think the impetus behind it originally was to allow a single userbase to access several dissimiliar sites. An example would be a gaming network. The common thread for the userbase is they all play games. Several sites could be created for different games -- HL2, Doom, WoW, Ravenshield. They each have a different theme and can have different module placements. You choose what databases and modules should be shared across them. Perhaps you want a common userbase and a common set of forums. Perhaps you also want downloads for all games to be accessible from all sites. Maybe each site needs a different news module and links modules. Whatever.

The long answer is you won't really know unless you install it and see if it meets your needs. Set up a site with subsites. Does it work as you envisioned? Why or why not? Were the instructions clear enough? What would help to make it work better for you? What problems did you run into? How did you work around them?