Forum Replies Created
-
Posts
-
Most likely you upgraded the plugins without following the upgrade instructions so the database tables are out of sync.
Are you using WP eStore and WP Affiliate plugins together? If you are then please follow the instructions here and then do a test:
https://support.tipsandtricks-hq.com/forums/topic/how-to-upgrade-the-plugins-properly
Have a look at this post which might give you some pointers as to what might be going wrong:
It is also a good idea to upgrade to a fresh build of the plugin that you can download from here:
Please get a fresh build from here then try this feature after the update (this will resolve any issue that may be arising due to the fact that a file got corrupted or something):
https://support.tipsandtricks-hq.com/update-request
You can also export all your member’s data directly from the database using the PHPMyAdmin tool. This tutorial should help:
Everything is working fine when the payment actually goes through. We just need to identify why two different transaction has the same transaction ID when paid via Authorize.net.
I know that auth.net uses the same transaction ID when used in sandbox (testing) mode but the plugin has code to ignore the duplicate transaction ID check when used in sandbox mode. So my question to you are…
– Are you doing live auth.net transaction or test transaction?
– If you are doing test transactions then do you have the “Enable Sandbox” checkbox checked from the eStore’s settings menu?
– You have only one copy of eStore in the plugins directory right? You did delete the old eStore version completely right? Some people like to rename the directory of the older eStore version and keep it in the plugins directory which is the source of many issues.
You simply install a separate copy of WordPress on your sub-directory then use eMember on that install. Your WordPress install in the sub-directory will have all the protected content that you protect using eMember.
We offer a “Plugin installation, configuration and basic testing” service that maybe of some use in some situation:
Option 1 is to follow the ‘How to Use the ‘Buy Now’ or ‘Subscribe’ button on a Standalone HTML page’ section from this documentation:
You can use this technique to post a but now or subscription button on any 3rd party site that lets you use HTML code.
Option 2 would be to use eStore’s buy now button via a text link method. You simply create a link with the following URL:
http://www.your-domain.com/?wp_eStore_buy_now=11 is the product ID of the eStore product. The extra eStore shortcode has more details on how to use this.
Looks like the form code on that page is messed up.
From the HTML code I see that you have a form and then the buy now button is inside that form. Here is the outer form code which is making the “Buy Now” button go to the “http://www.veteransdisabilitybible.com/index.php?rn=429&action=show_detail” URL after you click it:
<form action="http://www.veteransdisabilitybible.com/index.php?rn=429&action=show_detail" method="post">Have you manually placed that form code there? If you did for what purpose? If you use a form then you should use the eStore form outside that form.
We just need to debug it a little and find out what is missing.
Can you please tell me the the output that you get from the lines of code where you added an “echo” statement?
$sale_amt = $this->order_data['price_gesamt'];
echo $sale_amt;
// The Secret key (Get this value from the settings menu of this plugin)
$secretKey = "4e09fc1de376d";
echo $secretKey;
// Retrieve the value from the browser's cookie to find out who the referrer was
$affiliate_id = $_COOKIE['ap_id'];
echo $affiliate_id;Also, pease add the following line immediately after the
$returnValue = curl_exec ($ch);line which should print out some more details:print_r($returnValue);After the above modification please do a test and let me know what output you get from it.
Also, if you enable the debug by checking the “Enable Debug” checkbox from the settings menu of the affiliate plugin it will write a log file (aff_commission_post_debug.log) that will have more info for as to what it did when it received the request from your thank you page.
There is a permission issue on your server. So when the plugin tried to write to the debug log it failed. You can change the permissions of the log files inside the eStore directory to 777. Log files have a “.log” extension.
Alternatively, if you are not troubleshooting anything then you can keep the debug turned off by unchecking the “Enable Debug” checkbox from eStore settings menu.
Remember, if you are planning to place the PHP example code on a WordPress post or page then you need to have a plugin (e.g. PHP Execution plugin – http://wordpress.org/extend/plugins/php-execution-plugin/) that lets you execute PHP code in WordPress page or post. If you have such a plugin installed on your site then you should be able to copy and paste the example code in HTML view
WP eMember does not use the wordpress user’s database (wishlist does). Having a completely separate membership table gives us the flexibility to offer many features that other membership plugins cannot. We also don’t like to modify a core WordPress database table (WP users table). Anyway, without going to much into implementation details… to get the same effect you need to enable the “WordPress User Integration” feature and then import your WP Admin user to a special membership level (you can call it admin level) that has access to all content protected by eMember.
For each of these products have you specified the product specific commission by editing the eStore product and specifying the amount in the “Product Specific Commission” field for that product?
In the affiliate settings you specify the default value but if you want to apply a different commission on a per product basis then you need to override that in the product.
