User selects main registration, he then is presented a screen with 2 options, Paid Subscriptions and Free registration.
User selects free registration, when he reaches the registration screen, user changes his mind and wants a paid membership. So he reselects the register tab.
However now, the screen with the 2 options is no longer presented and the user goes directly to the main registration screen.
Resolution for Chrome : All browser cookies must be cleared.
Resolution for FireFox: All browser cookies must be cleared.
Resolution for IE: not found
User selects main registration, he then is presented a screen with 2 options, Paid Subscriptions and Free registration.
User selects free registration, when he reaches the registration screen, user changes his mind and wants a paid membership. So he reselects the register tab.
However now, the screen with the 2 options is no longer presented and the user goes directly to the main registration screen.
Resolution for Chrome : All browser cookies must be cleared.
Resolution for FireFox: All browser cookies must be cleared.
Resolution for IE: not found
Reproduced on IE, Chrome and FireFox
This was actually a test case before I released the beta. If you click on the free option then go to the forum's home page, then go back to the registration, it removes the cookie (a plugin does this) so you can make a choice again. Maybe I should add a note on the subscription selection screen to visitors know they can make another choice. Thanks for testing this!
Lancerforhire, I need your help please. Right now the paid subscription appears before the free one. I would like to reverse that, present the free first, followed by the paid one. How can I accomplish this?
Lancerforhire, I need your help please. Right now the paid subscription appears before the free one. I would like to reverse that, present the free first, followed by the paid one. How can I accomplish this?
In the LancerForHire - Paid Registration template group, open the lancerforhire_paid_registration_subscription template, and find:
Code:
{vb:raw subscriptionbits}
Cut the code you just found and paste it below/after the </vb:if> block that was below it.
Quote:
Originally Posted by HellRZR
May I make a cosmetic change request.
Right now the payment selection page looks basically like this:
Cost payment/ subscription selection box
description of the subscription
sign up now button
If you have a long description, the user must go back to the top of the page to select the payment/subscription he or she wishes to choose.
I think, it would be more user friendly in this order :
description of the subscription
Cost payment/ subscription selection box
sign up now button
What do you think?
In the Subscription (Paid) template group, open and edit the subscription_availablebit template.
User registers a free account, once termination is completed, the regular screen appears informing them that an activation email was sent.
When the user clicks on the activation email, following screen is presented :
testuser, you do not have permission to access this page. This could be due to one of several reasons:
1.Your user account may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
2.If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.
When you verify the user in admincp, there status is user awaiting activation.
User registers a free account, once termination is completed, the regular screen appears informing them that an activation email was sent.
When the user clicks on the activation email, following screen is presented :
testuser, you do not have permission to access this page. This could be due to one of several reasons:
1.Your user account may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
2.If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.
When you verify the user in admincp, there status is user awaiting activation.
Prefect release 0.7 corrected reported problem. however it did not address the cookie problem previously reported, this will be corrected prior to going out of beta I hope.