Forum Replies Created
-
Posts
-
There are pieces of code that you can add to whatever plugin or solution you are using to track leads or sales. It may not seem very obvious from these API documentations but if you explain your scenario I will be able to give you more help:
– http://www.tipsandtricks-hq.com/wordpress-affiliate/api-awarding-commission-via-wordpress-hook-501
– http://www.tipsandtricks-hq.com/wordpress-affiliate/awarding-commission-via-http-get-or-post-189
When you use the multiple membership feature, the last purchased membership is set as the primary level. eMember’s expiry mechanism works based on the details of the primary level. So what you observed is correct. Adding the multiple membership feature has been very chaotic due to the complexity it adds to the normal flow of the plugin. We had to make some assumptions in order to keep the simplicity of the plugin. This behavior you observed is the result of one such assumption. For most of our users who use multiple membership, use a setup that kind of goes around this problem (for example: if you sell a 30 day access to your levels or you use subscriptions where the access is valid until cancelled then it has no issue). Anyway, this is something we like to address in the plugin as the multiple membership feature becomes more mature.
I just added the capability to use the email tags in the email subject field. If you download a new build of eStore from here you should be able to use it:
I have seen this max limit issue before. I am yet to determine exactly what condition makes that happen but the easiest workaround for you is to use a large number in that field rather than keeping it empty. For example use 9999 as your max number if you want to have no limit. Remember, you can change these numbers any time you want. So temporarily change the max limit of that coupon and test it then change it back to whatever you feel comfortable.
It should fetch the download within a few seconds unless your server is taking some time for the script to process (can happen on an overpopulated shared hosting account). What kind of hosting plan do you have?
Looks like IPN is still not hitting the eStore. Those lines in the debug was generated from you directly accessing the script. When a true PayPal ipn hits your server it will have data in the “Post string:” area.
I just send a PayPal sandbox IPN to your site to make sure that nothing is blocking it. Looks like the sandbox IPN got to it fine so nothing is blocking the IPN for sure. That leaves only one option… IPN is not enabled in your PayPal account profile correctly.
When you say “entered just my mail URL” what do you mean by that? What is your mail URL?
Can you also post a link to the page where you have the “Buy” button that you are testing with so I can check the code for that button?
I always prefer to use the double opt-in option. This way you are always communicating to a customer who truly wants to hear from you. You might get more numbers on your list without the double opt-in but a lot of those will be very low quality leads. A list of double opt-in users is way more powerful (even though the number may be low).
The word manual refers to a manual process of checkout (meaning there is no automatic/instant payment option). This is useful for people who want to accept payment via a manual process such as Bank Cheque or cash payment.
Go to the Payment gateway settings tab in eStore and uncheck the “Use Manual Payment Option” checkbox if you don’t want to use this option.
It’s not coming from that plugin. Its coming from some code you added in your theme. Its really easy to prove this point. Do the theme testing mentioned here which will make you see that the error only shows up when using this theme (which means some javascript code in the theme is messing things up):
https://support.tipsandtricks-hq.com/forums/topic/test-to-identy-a-conflicting-theme-or-plugin
Now, given the fact that Thesis is a good theme and all of our plugins work with that theme, it is safe to assume the following:
You added code to this theme for customization purpose and some of that code is incorrect which is having a snowball effect and making other JavaScript code to not work also. So focus on removing javascript codes that YOU added from the theme and try to identify which code is causing this. Once you isolate then you can investigate that piece of code to see what exactly is wrong with it.
I have added a new action for this event so you can use the following in your plugin to get notified when someone logs into eMember:
do_action('eMember_login_complete','your_custom_function_name_to_handle_this_event');Please get a new build of the plugin from here to get this new action hook:
I agree with wzp, so first make sure that the encrypted download is working fine.
Aside from that, there is one other thing that you can do to help the PDF Stamper with the stamping process which is to turn on caching for the PDF stamper. Open the “wp_pdf_stamp.php” file and search for the following line of code:
define('WP_PDF_STAMP_USE_CACHE', "0");Once you find it change it to the following:
define('WP_PDF_STAMP_USE_CACHE', "1");Just make sure to clean the cache out every now and them from the “Manage Stamped Files” menu if you end up using this option.
What you can do is specify 100% commission for this subscription product then in eStore’s addon settings check the following checkbox:
One Time Commission for Subscription PaymentThis will make it to where it won’t give any commission for the recurring payments so only the first payment will be used for affiliate commission.
What you can do is specify 100% commission for this subscription product then in eStore’s addon settings check the following checkbox:
One Time Commission for Subscription PaymentThis will make it to where it won’t give any commission for the recurring payments so only the first payment will be used for affiliate commission.
