Quote:

I don't necessarily want to but the site is useless as of right now with no one being able to register or access anything through the modules.

This is what i found in register.php file (xoops 2.0.13.2):


and _US_REGISTERNG = Could not register new user.

So i think this problem may happen in both 2.0.13.2 and 2.2.3 !!

so meaning a bug at XOOPS ?

That fixed it for me. There are several "Extended Profile" sections in my admin pages. I updated Users->Groups
Selected "Modify Anonymous", then allowed "Module Access Rights" for the "Extended Profile" module.

Quote:


I did but.. nothing happend.. :(

Can any 1 help us with this.. they said need to contact the admin of the hosting.. but.. what i will say to them? i need some good points or specific reasons to tell them.... :(

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.

Stewdio,

Welcome to Linux, I think you will love it.

I have a couple questions for you.

On your hosted site.

1. If you remove the PM module can you add a new user?


On your new Linux site.

1. Can you copy your old site to your new box and see if the problem goes away.


Glad to see this is being looked into.

Thanks,

John

Quote:

Thanks! I've rediscovered computers after a decade of mainstream computing, I'm loving it!
Quote:
Removed the module and I get module doesn't exist for registrations.

Quote:

No problems on my local machine.

Hi all...

I have the same problem..

After submit, and clicking Finish after verify the info.
I get :

"Forbidden
You do not have permission to access this document."

on the file "/modules/profile/register.php"

In apaches errolog_log I can see this :

[Sat Feb 18 18:28:34 2006] [error] [client xxx.xxx.xxx.xxx]
mod_security: Access denied with code 403. Pattern match
"(((URL|SRC|HREF|LOWSRC)[\\s]*=)|(url[\\s]*[\\(]))[\\s]*
[\\'\"]*[\\x09\\x0a\\x0b\\x0c\\x0d]*j[\\x09\\x0a\\x0b\\x0c
\\x0d]*a[\\x09\\x0a\\x0b\\x0c\\x0d]*v[\\x09\\x0a\\x0b\\x0c
\\x0d]*a[\\x09\\x0a\\x0b\\x0c\\x0d]*s[\\x09\\x0a\\x0b\\x0c
\\x0d]*c[\\x09\\x0a\\x0b\\x0c\\x0d]*r[\\x09\\x0a\\x0b\\x0c
\\x0d]*i[\\x09\\x0a\\x0b\\x0c\\x0d]*p[\\x09\\x0a\\x0b\\x0c
\\x0d]*t[\\x09\\x0a\\x0b\\x0c\\x0d]*[\\:]" at POST_PAYLOAD
[hostname "my_nice_domain"] [uri
"/modules/profile/register.php"] [unique_id
"-bIH@38AAAEAAFCUYfcAAAAY"]

Does this info help anyone to identify the problem?

I use the latest XOOPS and patch.
Not sure what version of apache, php and MySQL my webhost uses..

*edit* Did cut the error message into several lines.

Best Regards

Roar