WAIT! HOLD ON A SECOND...

I am looking at a demo for cPanel, though I don't use it. It might or might not work for you.

It looks like after you log into cPanel there is a screen that reminds me of the Control Panel in Windows (icons for Mail, Webmail, Change Password, etc.). Down in that list I see an icon called MySQL Databases. Click on that.

Next you come to a screen called MySQL Account Mainenance. If you scroll to the bottom you'll see a link to phpmyadmin. Click that.

That should take you to a phpmyadmin screen.

There, on the left, you should see a list or a dropdown list of databases. Hopefully you know the name of you XOOPS database, but let's pretend it's myXoops. You should see something like myXoops(89) which shows that the database called myXoops has 89 tables.

You should see tabs across the top of the phpmyadmin screen. Click the Export tab. Here you have several options and I'm not sure which is the best. Do some homework here and consider making mulitiple copies with different options settings.

After you have your mySQLbackup, do a Google search about restoring databases. I'm not sure how you do that through an ISP since I have my server here at home.

I hope this will help you.

Is the server at your home or business or is it hosted?

I have experienced your symptoms. I restored my database from a backup and that took care of the problem. In my case, it seems that the database got corrupted when I accidentally unplugged my server while I was logged into the site (yeah, yeah, I know). Hopefully that's not what happened to you.

I/we need more information:

Do you have physical access to the server?

Did the power to the server cut out unexpectedly?

Is this a new installation?

Did you recently install (or activate) a new module? Try to remember the last thing you did as administrator.

Do you have backups of your database? In the worst case scenario you can resore your database and it should work.

If you haven't been backing up your database, you might have just learned a valuable lesson the hard way. I have been using AutoMySQLBackup for a long time and I love it. There are others. Anyway, if you haven't been backing up you should install this and back up your database. There's also a module called Backpack to help you do this in the future.

Read the instructions for either or both of these carefully before you do anything!

The worst thing I can imagine is you'll have to make a new database and a new site, then copy everything from the modules, themes, etc. folders to the new site. Then you'll have to use phpmyadmin to copy the tables you want from the old database to the new one.

When this happened to me for some reason the only damage was that I couldn't log in. All of the other data was intact.

I hope this helps.

I had this problem in the past also. I think it had something to do with PHP. As I recall, I had problems with PHP5 but not 4. Also I ended up using XHLD and I gave up on the packaged one for whatever reason. At any rate, I'm using 2.0.13.2, PHP4, and XHLD. This is working well for me.

XHLD is more configurable that the standard headlines module. I know it isn't the only one. Try others, too. I was never satisfied with the original headlines module and come to think of it I don't think I ever got it to work.

Good luck.

Assuming there's no module, shouldn't you be able to add it as a virtual domain in apache? You'd route the request for http://www.blahblah.com/user1 to http://www.myxoopssite.com/modules/popnupblog/user1.php where the php page is the beginning of user1's blog. In such a case you'd have to make sure that anonymous users have access to the module page you're referring to.

-EDIT-
The more I think about it, the more I think this is the only way to do it. It's your web server that would be "listening" for something like this, right? Otherwise your XOOPS site will be looking for a folder called user1 which would need its own index.php and God knows what else. I'd sure like to be wrong, here. Somebody correct me.

I suppose somebody could create a module that added a folder for users who created sub-sites, then copied needed files into each folder as they were created. It sounds pretty cool, actually. I need to learn PHP.

I don't know if this will help you, but read the upgrade text file in the docs folder of the upgrade package.

I don't think you need to do anything in the install folder. You should be running the file xoopsupdate.php.

Make sure you read the directions in the doc folder. By your post it seems like you haven't.

How about letting people vote?

Perhaps by default a compatability table could be added to each module listing. Hopefully, as new versions are added it would be easy to display yet another row for the new version.

Registered users could "vote" with yes, yes with bugs, no. The votes could be displayed using the modules that already exist or scores could be given and averaged to produce a "compatability score" for each release.

Sure a few people would be jerks, and a few others would screwed up their implementation of the module 'cause they don't know what they're doing yet, but overall it should average out and be useful.

Just a thought. Thanks for all of your hard work.

I had the same problem.

I copied the one line of code provided earlier in the thread, i.e. <{$xoops_module_header}>

Of course you must save the file.

Then you must go to PREFERENCES--> SYSTEM--> GENERAL SETTINGS and check "yes" where it says "Update module template .html files from themes/your theme/templates directory?"

Now return to your home page and log out. It should work. Log back in, go back to GENERAL SETTINGS, and change Update modeule template etc. back to "no."

Rock on.

Yes, it looks like PHP5 is the culprit.

I run my XOOPS site on top of Xampp, which by default uses PHP5 but also comes with PHP4. I switched to PHP4 and all of a sudden everything works like it's supposed to.

I've been struggling with this for a while, so I'm releaved to finally figure it out.

Thanks to all who posted here, I wouldn't have figured it out alone. In fact, I don't think I can take credit for figuring anything out.

If you use Xampp (lampp), it's very easy to switch to PHP 4.

See http://www.apachefriends.org/en/xampp-linux.html and scroll down to:

Note to XAMPP since version 1.4.7
Because such very new versions like PHP 5 always should be handled with care we decided to include both current versions of PHP into XAMPP: PHP 5.0.x and PHP 4.3.x. If you find out your PHP application doesn't work with PHP 5 you will be able to switch back easily to PHP 4.

By the following command you can switch "back" to PHP 4.3.x:

/opt/lampp/lampp php4

And with the following command you can switch back to PHP 5.0.x:

/opt/lampp/lampp php5

If you forgot which version of PHP is in use simply use phpinfo() or call this command:

/opt/lampp/lampp phpstatus