Forum Replies Created
-
Posts
-
Please create a test affiliate account then post a link to your affiliate login page and the login details so I can check out how it reacts.
@malcolmmind, Your theme would be the first thing to test (I wouldn’t worry too much about the plugins). Can you switch to the default WordPress’s twenty ten or twentey eleven theme and give me a link to your gallery page?
@vmseven, you have one inline CSS that defined to take 50% of each NextGen gallery element (this is making it to where you can only have two images side by side). You have another CSS (most likely from your theme) that is specifying the line-height to be 20px!
body {
font-size: 12px;
letter-spacing: 0.4px;
line-height: 20px;
word-spacing: 1px;
}A 20 pixel line height is making it to have the lines too much space between them. You also have an extra “
” there which is introducing an extra empty line (you can take that out).You can’t mix percentage based commission and fixed commission in the same setup. It gets very confusing so we do not support this setup. You have to either stick with a % based commission or a fixed commission for your site. In most cases you can tweak the commission % value to achieve close to how much you were going to give out as a fixed amount anyway.
The shortcode you used on that page has a typo (pay attention to the letter “S”). The shortcodes are case sensitive. Use an uppercase “S” for eStore.
[wp_eStore_transaction_result:end]If the member makes the payment while logged into the site, the plugin will know that an account already exists for this user and it will simply reactivate that account. If he/she makes the payment as an anonymous user then the plugin won’t be able to mysteriously determine that an account exists and it will assume that this is a payment for a new account:
The bottom line is this… you only get the “Rendering of template…. failed” message if NextGen gallery cannot find the template file that you are asking it to use in the “view” directory.
With that said, when you use the following shortcode, the NextGen gallery plugin will look for “gallery-wp-eStore-auto-addtocart.php” file in it’s “view” directory (it adds the “gallery-” keyword to the file name shortcode you specify) and if it can’t find that file it will show that error.
[nggallery id=1 template=wp-eStore-auto-addtocart]So the simplest thing you can do is browse to the “view” folder of the NextGen gallery plugin and make sure the “gallery-wp-eStore-auto-addtocart.php” file exists there.
Check the “common mistakes” part from this post and see if you have done any of those:
You simply place a gallery on a page then protect that page so that only members from particular membership level can view that page.
There are video tutorials here that shows you how to protect a page:
When a user changes password in eMember the corresponding WordPress user’s password is also changed automatically.
With that said, WordPress requires you to relog after a password change so you could be experiencing the effect from that. We can maybe force the user to log in again after a password change in eMember which might be a better option?
1. Changes to the stylesheet – You should always add your custom CSS in the “wp_eStore_custom_style.css” file. That file is never modified by us. This way during the upgrade you just keep a backup of that file and then after the upgrade you replace that file.
2. Custom integration that are not officially supported by eStore will need to be reapplied. You can tell us what you did and we can look into adding this integration as an option in eStore (we will add it, if it is reasonably easy and benefits a lot of customers).
3. If we told you that we added conditions in the plugin then this change also made to the core. So there is nothing to worry.
You can take a backup and keep a backup copy of your current eStore somewhere on your PC. If things do not turn out good you can roll back.
That would be the issue.
This means you didn’t specify the membership level in the PayPal button. Please check this documentation on how to make a PayPal button for a particular membership (there is also a video on that page):
How to Use a Simple PayPal Payment Button to Accept Membership Payment
To be more specific, it is missing the following line from the advanced variable section (X is the membership level ID):
custom=subsc_ref=X
