RNYA Fails To Work

Theme Guru Joined: Nov 01, 2003 Posts: 1006

I upgraded a website from RN 2.02 to the latest. Everything seems to be working very well except for the new user sign up.

I can go to the RNYA admin and put a new user in without any issue. However, people cannot go through the entire registration process themselves.

When they register they can agree to being 18.
They can agree to the terms.

But on the page where you fill in your information, name, password, etc, once they finish filling in those fields, the "continue" button does not allow itself to be pressed. Everything looks right, but it does not function.

So, the registration cannot complete for them to receive an email.

Additionally, it does not make a difference with using the default Ravenice theme or any other. Also, it fails the same way in both IE and FF.

Any help would be greatly appreciated. I would like to get this working right away. The website url is www.hauntingtales.net if you would like to try to register and test it yourself.

Thank you in advance. Smile

registered · Posted: Thu Mar 12, 2009 10:00 pm

I got to creating the user, but actually activating, I get this upon "Saving Changes"

http://www.hauntingtales.net/modules.php?name=ErrorDocuments&file=404&rs=/account.html

My guess is something wrong with your Short Links

Posted: Thu Mar 12, 2009 10:08 pm

I see that you got a bit further than the other five who tried.

Here are the entries for the shortlinks in my htaccess file for this website.

Code:

#Your Account


RewriteRule ^userinfo-([a-zA-Z0-9_-]*).html userinfo-.html$1 [L]


RewriteRule ^account-avatarsave-([a-z]*)-([\.0-9a-z]*).html modules.php?name=Your_Account&op=avatarsave&category=$1&avatar=$2 [L]


RewriteRule ^account-showcookiesredirect.html modules.php?name=Your_Account&op=ShowCookiesRedirect [L]


RewriteRule ^account-deletecookies.html modules.php?name=Your_Account&op=DeleteCookies [L]


RewriteRule ^account-showcookies.html modules.php?name=Your_Account&op=ShowCookies [L]


RewriteRule ^account-bypass-([a-z_]*).html modules.php?name=Your_Account&op=userinfo&bypass=1&username=$1 [L]


RewriteRule ^account-([a-z_]*).html modules.php?name=Your_Account&op=$1 [L]


RewriteRule ^account-gfx-([0-9]*).html index.php?gfx=gfx&random_num=$1 [L]


RewriteRule ^account.html account.html [L]

I took these from the shortlinks.htaccess file included in the RN 2.30.01 download package.

Do you, or anyone, have any suggestions? Everything else seems to be working correctly.

BTW, Evaders, I approved your waiting membership. It gave me the message that an email was sent to you.

I turned the shortlinks off and the same problem happens in the same stage of the registration. Once we reach that final page, clicking the "continue" button does nothing at all. You can see the url in the status of the webpage, but nothing happens.

registered · Posted: Fri Mar 13, 2009 5:24 pm

If the same thing happens with shortlinks off, then it cannot be shortlinks causing the issue...

Do you by chance have "force nuke URL" turned on in NukeSentinel? If so, turn that off. Grasping at straws here. Maybe something else within your .htaccess is rewriting the URL somehow?

Posted: Fri Mar 13, 2009 5:29 pm

I removed the entire htaccess file and still have this issue. I also do not have the force nuke url on. I am at a total loss. Sad

Posted: Fri Mar 13, 2009 8:21 pm

Alright, I have done this a few times.

The site functions perfectly at RN 2.02.

The site functions perfectly at RN 2.20

The RNYA fails at 2.30 and 2.30.1

Is it possible to use 2.31 and not use RNYA? I would like to run the current RN package, but for some reason the RNYA will NOT funtion on this website.

If anyone has any ideas what could cause it to fail, I would appreciate the assistance. I have run the upgrades two time now going by each distro in order and checking after each upgrade. It works fine until RNYA is installed.

Thank you in advance.

Posted: Fri Mar 13, 2009 10:20 pm

After a few hours of work these are my findings.

RNYA fails no matter what.
RNYA does not work even on a totally clean install.

It fails at either RN 2.30 or 2.31.

I thought that it was just the upgrade, but after trying several ways, it is the same result even with only the core files and core db.

I have successfully used RN 2.30 on other websites on this same server. There are no issues and if I visit those websites, I can use the RNYA there.

The only difference between those websites and this one is the following.

This website is an addon domain that sits inside of another domain.

Is it at all possible for this to be the problem? If yes, then what are my options? If there is no way to make using RNYA optional where I can still use the normal your account module, how will I ever be able to use a RN distribution past RN 2.20?

I am truly at a loss and need some ideas. If anyone can assist, please do let me know. I need to get registration functional with this website.

Thank you!

registered · Site Admin Joined: Jun 04, 2004 Posts: 6437

Some questions:
What do you mean by "fails?"
Is there an error message, white page, etc.?
Are the user tables created?

Posted: Fri Mar 13, 2009 10:40 pm

Hello Kguske,

I described the failure in my first posts.

The person can go through the agree to age page. They can agree to the terms page. Then they get to where you fill in your name, password, email. When you click continue, nothing happens. It does not actually "click" to allow you to finish the registration.

There are no errors, no errors in the logs, no white pages.

I can create a new user manually in the admin section using RNYA. That works perfectly.

Yes, the database tables are all there.

This same issue happens on the upgrade files. It happens with "virgin" files. It happens with the upgrade database. It happens with a "virgin" database.

The registration works perfectly in RN 2.20 and all earlier versions. The RNYA simply fails.

I have checked the db tables over and over. Everything appears correct and as I said, I can manually add a new user using the RNYA admin.

Do you or anyone else have any ideas?

Posted: Fri Mar 13, 2009 10:58 pm

I didn't see those because I came from your private message. I have an idea - could you send me a PM with FTP info?

Posted: Fri Mar 13, 2009 11:00 pm

Yes, I certainly will. It will just be a moment.

Posted: Fri Mar 13, 2009 11:01 pm

evaders99, how did you get to creating the user?

Posted: Fri Mar 13, 2009 11:04 pm

I was wondering that as well. Smile

PM is now sent.

Posted: Fri Mar 13, 2009 11:22 pm

I just "did" - I cannot reproduce the issue. Sorry that doesn't really help you

Posted: Fri Mar 13, 2009 11:36 pm

You can switch back to your preferred theme. There is a conflict with the horoscope block. If you move that to the right hand side (i.e. it won't be displayed during registration) and everything should work correctly.

I downloaded the block, and I'll investigate, but the solution above should work for now.

Posted: Fri Mar 13, 2009 11:37 pm

I am certain that website can live without the block unless you are able to find a solution to the issue within the block. Thank you so much. I cannot thank you enough!

Posted: Fri Mar 13, 2009 11:42 pm

The form in the block uses a get method, but I'm not sure why it can't use a post method. Also, since it's generated by PHP, it should probably calculate the hidden day input value, instead of using JS to do that in the block. Finally, it probably shouldn't name the submit button - there is no point in that, as far as I can tell.

Posted: Fri Mar 13, 2009 11:48 pm

Yeah...the block doesn't work anyway. It just resolves to a site - the form is meaningless.

Posted: Fri Mar 13, 2009 11:55 pm

Thank you so very much for your help. I appreciate it greatly. I will toss that block in the trash. I am certain that they can live without it. It seems odd to me that the block was causing the issue when the same issue was happening with a "virgin" install and database since the block would not have been on there, but who knows!

It seems to be working now. Razz

Posted: Sat Mar 14, 2009 7:20 am

I tested the block on a test server, and could not reproduce the problem. On the other hand, it's odd that it worked when the block was removed...

Posted: Sat Mar 14, 2009 8:47 am

kguske, thank you for the detailed discussion though too, because I would not have thought of a conflict there because it was already passed the AJAX part. I didn't even consider a potential code conflict. interesting.