Funny that your existing members aren’t getting the same menu the new ones get. I wonder if it’s related to caching? Do you have a caching plugin installed?
By the way, most of your conditions are repeating the same thing. You could try a shorter code like this:
I tried the link and saw the blank page. It is not the page you linked to the one shown white, but the Membership Options Page, where I got redirected to when trying to view the protected page. This is the URL in my address bar:
Those are the Membership Options Page Variables:
[hilite path]Dashboard -› s2Member® -› API / Scripting -› Membership Options Page Variables (MOP Vars)[/hilite]
Now, if I go to that URL directly, it loads fine, the problem seems to be in the redirection. The redirection results in a 414, which means that the URL is too large. This is most probably the same problem with the one you get after checkout.
We may not officially integrate it soon. There are very many gateway requests, including that one. For now we’re concentrating on improving the API that’ll make it possible to create new integrations, so that they’ll be easier.
You could export your users and in the CSV search for those that have the custom capability you want, and create the list of users for that custom capability.
Could you please post the related log entries, x’ing out private info (e.g. email addresses)?
[hilite path]Dashboard -› s2Member® -› Authorize.Net® Options -› Account Details -› Logging[/hilite]
Are these new subscriptions you’re selling, or is the user already logged in and with a subscription which he’s trying to modify? Could you give more details about the situation that’s giving you that error?
I honestly don’t know how that’d go before I tried it and checked that everything works fine. You can try it, but I suggest it with a test installation and see how it goes.
You can Google migrating WordPress user tables from one site to another, see what you find. Maybe you find some pages that confirm it can be done without repercussions.
The way I’d probably do it, knowing the limitations of PayPal, would be to create a regular subscription and when the 13th month gets charged, I’d refund it and email the member about it, thanking him for having stuck with the membership that far and that I look forward to have him another year as a member.
int|str $item_number – An s2Member-generated [hilite mono]item_number[/hilite] ( i.e. [hilite mono]1[/hilite] for Level 1, or [hilite mono]level|ccaps|fixed-term[/hilite], or [hilite mono]sp|ids|expiration[/hilite] ).
Could you try that and see if it works right?
I hope it helps.
This reply was modified 4 years, 10 months ago by Cristián Lávaque.
Well, you have two options. Either move all the new theme and posts to the existing installation, which would leave the userbase untouched, or move the userbase to the new installation.
I’m not sure which one is best, though. I’ve never needed to do either one.
Since you’ll probably have to move the new site to its final location, you could probably just copy every table from the new installation to the old one, except for the user related tables. I have never tried this, though, you should test it in a clone of the existing one first.
Also remember you’ll have to double check that all your content access restrictions match what your users have bought.
I’ll let others share their thoughts on your question.
Then, in order to add them, you’d have to create a form that lets the user choose and submit it to the page with the pro-form or button to check out, which will be updated with what the user chose in the previous step. http://www.primothemes.com/forums/viewtopic.php?f=36&t=1604
Well, you can bypass the BuddyPress registration using a free registration pro-form.
[hilite path]Dashboard -› s2Member® -› PayPal® Pro Forms -› Free Registration Forms[/hilite]
But this would be usable by anyone, not just those who purchased through ClickBank, and doesn’t even recognize if you purchased or not, so it’s not very useful unless you hide it in a URL that only those getting the email see.
Now, here’s an idea: you could put the free registratino pro-form in a page protected with Specific Page restriction and then what you sell is the access to that page.
[hilite path]Dashboard -› s2Member® -› ClickBank® Buttons -› Specific Post/Page (Buy Now) Buttons[/hilite]
Viewing 25 replies - 7,051 through 7,075 (of 7,376 total)
Pre-Sale FAQs
Video Tutorials
Community Forum
Knowledge Base
News/Updates
s2 Codex / Docs
GPL v2 License
Contact A Human
About Us
Our Customers
Support Policy
Privacy Policy
Old Forums (READ-ONLY): The 
