First of all, I have tested the affiliate scheme on my site and it is working absolutely fine...unique banners and raw/unique hits are working fine as well. Since the affiliate sales are related to the payments in Amember, people can not spam or use fraud in any way. P3P policy was not too hard to implement. I paid $25 to subscribe to a site which had a P3PDeveloper software. Feel free to look at my policy on my site. You also need a Compact policy in your headers (Using Apache here) for higher privacy settings in IE6. I have done this using a .htaccess file. You guys can view the headers of my website via some tool (cant remember which one now) on w3.org website. Alex, can you please look into the following: If I have my affiliate scheme turned on then the first subscriber works ok, however when the second subscriber attempts to pay, a MYSQL error message comes up just after the payment... error message was to the effect of "... Duplicate entry '0' for key 1 INSERT INTO amamber_aff_commission(aff_id, date, ....." Having looked into it i believe this was happening because the primary key (commission_id) in the above table is not AUTO_INCREMENT. I changed it in the database to AUTO_INCREMENT and everything seems to be working fine. Although I am quite sure this is the correct solution, but would be grateful if you can confirm this. Once again thanks for this brilliant addition to AMember. So far so good. By the way what are we expecting in the latest version coming out in a weeks time? Best regards, Zeeshan
Zeeshan, thank you for your report! This bug is known, and will be fixed in 2.3.3 release (tomorrow). Changelog for 2.3.3 here: - IMPORTANT: paypal_r payment plugin fixed, recurring subscriptions were not handling correctly starting from 2.3.0 - IMPORTANT: backup databases list has not been full, so aMember CP Backup function doesn't backup all tables (starting from 2.3.0) File fixed: common.inc.php - IMPORTANT: code added cc_core plugin to pre-validate credit card# before sending it to payment processor for processing - it may help to save on transaction fees; - IMPORTANT: affiliate program may not work correctly in some cases - fixed; - experimental trials handling added to "worldpay" payment plugin; - user cannot login to member.php until his e-mail address is really verified; - it is now possible to configure if address info is optional or required at "aMember CP -> Setup : Use Address Info" - cdg plugin fixed; - Invision2 plugin confugration issue fixed;
Affiliate and P3P smooth process for me too! Our company is too taking advantage of the killer new features. It is amazing the level of support we received in the process. The P3P policy was a needed addition anyway, and like Zeeshan said, is quite an easy process. Thanks again CGI-CENTRAL!
Amember 2.3.3 Hey Alex, Is there any chance that you can release the new version 2.3.3 before 9th of December. My recurring payments with paypal are due to start from that date and I was wondering if I would be able to change the paypal plugin in time. Best Regards, Zeeshan
Hi What did you add to your .htaccess file to insert the P3P header? What's the syntax? Also - I noticed you have a custom affiliate singup page. I was wondering how you created that, since aMember seperates the code from design. Thank you -Arash
It is from my .htaccess (on cgi-central.net) Header append P3P 'CP="CAO DSP COR ADM DEV PSA IVA OUR IND STA"'
Mike, it means that ANY affiliate tracking will not work, why are we talking about aMember only? Anyway, there is a solution. How to add P3P to PHP files (add it to top of amember/config.inc.php by example): http://www.privacycouncil.com/implementation.php http://www.mambers.com/showthread.php?t=6955 How to add P3P to static HTML files: http://www.w3.org/TR/p3pdeployment#Using_Link_Tags
Ok I am completely lost on what needs to be done to make the p3p work with amember. I put header("P3P: CP=\"DSP IDC CUR ADM PSA PSDi OTPi DELi STP NAV COM UNI INT PHY DEM\""); in the top of my config.inc.php and created a policy, human readble file & reference in a directory called \w3c\ the reference is called p3p.xml the policy is called policy.xml I have this on my non amemeber protected pages <POLICY-REFERENCES> <POLICY-REF about="http://www.warriorinsider.com/w3c/policy.xml#global"> <INCLUDE>/*</INCLUDE> <COOKIE-INCLUDE/> </POLICY-REF> and also <link rel="P3Pv1" href="http://www.warriorinsider.com/w3c/p3p.xml"> What else needs to be done? Thanks, Tony