If you want to go that route, which refreshed my memory a bit, duplicate your 2.0.13 in a new sudirectory with a differently named database. Experiement with that, while your live 2.0.13 site is still running on the front end.

Once you are satisified it work in the subdirectory test area, then you can migrate over to the main site directory. Thats what I did, and it worked just fine.

Please keep in mind, that the profiles module in the newer version may or may not work and this module is integral for new user registrations. If you have a follwing and expect people to register, I would not upgrade at this point.

Quote:

My upgrade was quite some time ago and I can't remember how it went. I do remember it being a little different then from the past and I didn't run into any troubles.

I really don't have nything of value to add here unfortunately because there have been some rather sticky issues with the recent upgrade path, many of which are just plain baffling, even to the veteran users.

If you can, whioch I hate to reccomend, could you hold off on the upgrade, or revert back to your 2.0.13 instalation?

For right now, your best solution may be to hold off for a little while longer until some of the issues have been sorted out.

I'm assuming you didn't over-write your mainfile.php file. If that is the case, then you will have to edit the file again to reflect your instalation environment, if you follow what I mean.

Let us know how it goes.

Hi Everyone.

I have done a little investigation into the matter and I have possibly hit on some early results that I would like to share with you all here for further investigation by developers and users alike.

As you can imagine, I too have been afflicted with this little issue and met little to no success in finding a resolution. So I will give you all a little background information and then share what I just recently discovered.

Some weeks ago, I upgraded from 2.0.13 to version 2.2.3/4. The upgrade of course went without fail.

I decided to do some initial testing after making some modifications. I logged out of the site so I could register a new testing account to see my changes. I was hit with the same problems as mentioned here in this and other posts.

I went searching for a solution here on the forums as I always do and set out with the proper permission changes to the anonymous group to no avail.

I was rather stumped.

2 weeks ago, I made the permanent switch to Linux (I can hear the applause from the community already). In so doing, I was, for the first time, setting up linux to my liking and while exploring around I decided to create a local XOOPS environment for testing purposes.

I installed Apache2, php4 and mysql4 with no problems at all. (I rightfuly patted myself on the back for my mad newbie terminal command line skills - a week and a half without so much as thinking about booting back into windows, what can I say, I'm proud!).

So anyway, I installed XOOPS localy without a hitch, in fact it was running better then my hosted solution.

What did I find? I was able to register new users with a fresh instalation of XOOPS 2.2.3/4! Wow this is great! So I went back to my shared host online, moved all my old files and proceeded to upload/install a brand spanking new version of XOOPS with all the updates included with a new database, new tables and everything else you can salivate over.

WHAM! I was slapped with the same error that I could not reproduce on my local machine. The answer was staring me right in the face!




Apache 1.3? Ok, we're onto something here. Listed below are the shared hosts specs and my local machines specs.

Shared Host Environment

My localhost.localdomain Environment


So what do you all make of the difference in Apache versions? Obviously, I'm not an expert on the user side of things when it comes to all things linux, but it seems to me that some of the new updates to Apache 2.x.x may have affected something in the profiles module. In which case, we may need a minor code revision. We can't expect all of our host providers to update to the latest Apache. This would also explain why some users have not been affected while others have.

I hope this little bit info has shed a bit of light on the issue.

Sorry for the delayed response, this post got list in my list of posts to regularly check.

I couldn't find a user administration area in phpmyadmin unfortunately, so I will leave that to others to verify for me. I would like to know if this is avail via the same section.

You should be able to modify, create or delete users in the control panel area of your website. The most commone element for this is in cpanel, but your host configuration may differ so check your local support area on where and how to modify your mysql.

Once there, the simplest thingt o do is edit the user you have configured for your xoops_DB. If not, then delete the current user, create a new one with the same name and assign it to your xoops_DB.


Hope this helps or clarifies things a little more clearly for you.

Herko and the Development team are working together to find a suitable solution and will be addressing the community on this issue shortly.

Uhm yeah sure, thanks!

You are correct, it is a problem with your host because of the backup. The username for the db has been reset or altered because of the backup.

Your DB account is allowing you to edit tables, but not drop or add them.

You will have to go into your cpanel (if that's what you use) and add your username and password back into the sql authorized users.

You may be able to edit existing users, if that's the case, give FULL permissions to the username you have associated with your _xoops database. It will be the same as you have in your mainfile.php

I must transparent, this thing had me down to a science.

The Keys to Your Heart



You are attracted to those who are unbridled, untrammeled, and free.

In love, you feel the most alive when everything is uncertain, one moment heaven... the next moment hell.

You'd like to your lover to think you are stylish and alluring.

You would be forced to break up with someone who was emotional, moody, and difficult to please.

Your ideal relationship is lasting. You want a relationship that looks to the future... one you can grow with.

Your risk of cheating is low. Even if you're tempted, you'd try hard not to do it.

You think of marriage as something precious. You'll treasure marriage and treat it as sacred.

In this moment, you think of love as commitment. Love only works when both people are totally devoted.

What Are The Keys To Your Heart?

http://www.blogthings.com/keystoyourheartquiz/

Shouldn't have to check perms on the file, it should work out of the box.

I havn't said anything for some weeks, but this niggling little problem has effectively shut me down.