Forum Replies Created
-
Posts
-
A tech confirmed that HTTP POST is allowed on the same server as CURL.
He does ask:
“However, it’s possible that the timeout may not be with our server. Can you ask the plugin developers whether the stamping is done directly by the plugin, or whether it uses an API to the plugin server to do the stamping?”
In any case, do you have an updated example of the HTTP POST integration guide? I’ve discovered that even if the integration code manages to stamp, Acrobat isn’t able to open the file (this is after I upgraded the plugin, was working fine before), so I think there’s an issue with changed code in the updated plugin.
1) “Enable PDF File Encryption” is unchecked.
2) Using method 2 doesn’t seem to make a difference.
WPEngine loads the site much faster than my old host, so I don’t really think it’s a server power issue, though they do have a pretty stringent timeout limit. They’re willing to help work out this issue, but can’t do it if the code is encrypted.
I have noticed that using the Manual Stamping in the Dashboard seems to have a higher success rate than using my custom code to generate the pdfs in the frontend. I’m using the suggested code here: http://www.tipsandtricks-hq.com/wp-pdf-stamper/third-3rd-party-integration-guide-10
Which actually seems to be outdated, and might be part of the problem. Do you have an updated version of this code? I know that for one, this line isn’t applicable anymore:
list ($status, $value) = explode (“n”, $returnValue);
I’ve gone through that common mistakes post, and I believe my setup is right: 1) I have everything checked for global access; 2) I only have my one member page checked for protection for “General Protection”; 3) I have the one member page checked for access for my one member level; 4) everything else is untouched.
I’ve also upgraded WordPress and have updated the eStore and eMembers plugins. No change.
I believe that it’s finding the protected content correctly, since I’m getting the “Please Login to view this Content.(Not a member? Join Today!)” message only on that one member’s page. But from what I can tell from the function code, it sees everything before the more/teaser span tag as teaser information to be displayed. Since I’m not using this tag, it thinks my entire post content is a teaser and displays it before the “Please login” message.
