Forum Replies Created
-
Posts
-
WP eStore -> Add/Edit Products -> Some Product -> Buy Now Or Subscription Type Button Specific Settings -> PayPal E-mail
You can set the PayPal address for that specific product. Also, that product can have it’s own return page, ***AND*** you can specify a product specific currency code, in case the co-seller wants to be paid in RMB or some other currency!
Unfortunately, as the title of the setting suggests, you can only do this on Buy Now buttons or individual subscriptions, because otherwise it would totally confuse the shopping cart.
It’s a bug. The “You must agree…” message is being displayed at the same time the CSS is being generated. That screws up the output. You also get the same result if you close the Ajax generated popup, before it finishes transferring to PayPal.
Some of my work is in the Unix System V code… yeah, *nix runs through my blood.
“Hooks” refers to the ability to integrate your code into somebody else’s code. WordPress allows eStore and other plugins to hook into it (WordPress). eStore has the ability to hook into other “selected” plugins, and allows other “selected” plugins to hook into it (eStore). That’s what it means when you see Amin and Ivy talk about eStore integration.
The only way you are going to hook into eStore is to get down and dirty with the code, unless Amin reveals the presence of an eStore API.
On the subject of Google Checkout, please see:
https://support.tipsandtricks-hq.com/forums/topic/google-checkout-revisted#post-7904
As a “safety precaution,” it’s a good idea; but not a requirement. The reason it’s a good idea, is to prevent accidental IPN callbacks to the old notification URL.
@arts — Here is some pseudo code that may answer your question…
IF server allows fopen() for URLs {
SWITCH $DownloadMethod
CASE(2):
// Method 2.
CASE(3):
// Method 3.
CASE(4):
// Method 4.
CASE(5):
// Method 5.
CASE(6): {
IF Apache Gzip installed, disable it;
IF Resumable downloading supported, enable it;
Send file contents in 1 MB chunks;
}
DEFAULT:
Send file contents in 8 KB chunks;
END SWITCH;
} ELSE {
IF cURL library installed {
Download using cURL;
} ELSE {
Fatal error;
}
}
=======================================
Since the smaller server is your production system, and it seems to be working for now; is it fair to say the situation is not as “hot” as it was 2 days ago? I’d like to study the code a bit, and maybe try a few things. I will pass any suggestions on to Amin.
Or, if you are feeling really brave and adventurous, since you appear to be technically advanced, would you like to be able “test drive” any of my code suggestions? If so, please visit my site and leave me your e-mail address on a contact form:
h-t-t-p colon slash slash TheAssurer dot com slash contact
You don’t need to set it for eStore. The reason is because eStore tells PayPal what the Notification URL is, when it invokes PayPal. Some plugins will deliberately not embed the URL in their PayPal calls, to lock you into one product; because you can only have one Notification URL at a time in your PayPal profile!
I was thinking of asking Amin if he’d be interested in my writing a tutorial on how to use the PayPal sandbox with eStore… Is that something that would help? At least it would save you 32 cents whenever you wanted to see if it works
If you have access to a Unix/Linux/*nix command line, change to the plugin directory and issue the following shell command:
grep add_shortcode *.php
Essentially, you are looking for all occurrences of when/where a new short code is added to WordPress.
The first argument to add_shortcodes is the shortcode string itself. The second argument is the name of the function that WordPress should call, when that shortcode is parsed.
Yes I can tell you in about 2 hours. Am mobile now.
@Amin007 — Thanks for the promotion, boss!
Okay, so let’s try to confirm something… is the actual amount of monies in your PayPal account, for each transaction correct? Not from the PayPal e-mails, but from logging into PayPal and looking at your transaction history. If so, Amin can focus on any eStore bugs; instead of possible fraud exploits.
The permissions for the plugin directory and all subdirectories should be 755. The permissions for all files in the plugin directory and all subdirectories should be 644.
