Paula Talbott

Forum Replies Created

Viewing 9 posts - 26 through 34 (of 34 total)
Oct 11, 2017 at 2:31 pm
#64372
Member
Paula Talbott
OP

I just heard from Stripe, and they said the LogoURL error is coming from the Stripe plugin:

“I have taken a look at your account and I can confirm that there is no problem on our side, however, looking at your error message it does sound like that there is an error with your third-party integration. I hate to redirect you but I believe the best course of action would be if you got in touch with your developers as it is not a typical error message that Stripe would send to the users.”

So now there are 2 issues, the blank page in Safari, and the LogoURL error in the Stripe Add-on plugin.

Oct 11, 2017 at 1:12 pm
#64370
Member
Paula Talbott
OP

One other thing. On all 3 browsers when I click on the pay button and launch Stripe, I get this error “logoUrl (https://cdn3.iconfinder.com/data/icons/10con/512/money_cash_pay-128.png) failed to load.” Is this a Stripe issue, or the Stripe plugin?

Oct 11, 2017 at 12:43 pm
#64369
Member
Paula Talbott
OP

Here is more information… This is working perfectly with Chrome and Firefox. It does not work (produces blank page) in Safari. All browsers are running on my Mac. Mac is running Sierra version 10.12.4. Safari is version 10.1.

Why is it failing in Safari, and not in Chrome or Firefox?

Thanks!

Oct 11, 2017 at 12:25 pm
#64364
Member
Paula Talbott
OP

That is not the case at my end. The source does not show the extra line (see attached), the code is not producing an extra line, and a different theme does not work either (produces a blank page when download link is clicked). I have no doubt that what you have identified is a problem, but don’t know how to reproduce this at my end. Any ideas?

Oct 10, 2017 at 4:03 pm
#64319
Member
Paula Talbott
OP
This reply has been marked as private.
Oct 2, 2017 at 2:15 pm
#63971
Member
Paula Talbott
OP

That took care of the issue. Thank you.

One note: On the plugins page I was not being prompted that there was a newer version of WPDM or the PDF Stamper available. Thought you might want to know that.

Otherwise, I’m all set!

Oct 1, 2017 at 10:43 am
#63939
Member
Paula Talbott
OP
This reply has been marked as private.
Mar 26, 2015 at 8:30 pm
#27517
Member
Paula Talbott
OP

Do I need to uninstall the old one to upgrade? If so, won’t I lose all of my settings and all of the settings I have on all of the PDFs on my site?

Mar 20, 2015 at 12:58 pm
#27334
Member
Paula Talbott
OP

WPDB PDF Stamper Plug In 1.4.0
3/20/2015
Bug: Wasn’t putting watermark on individual file downloads, only on package downloads. To fix this bug I changed the wpdm-pdf-stampers.php file on line 120 from
isset($_GET[‘ind’])?$_GET[‘ind’]:0;
To
$ind = 0; //isset($_GET[‘ind’])?$_GET[‘ind’]:0;

Then at the bottom of the fileProcess method I added stats counting, which it does not do on file download when the change above was made:
//wpdm_download_file($filepath, $filename, $speed, 1, $package);
global $current_user;
get_currentuserinfo();
$log = new Stats();
$oid = isset($_GET[‘oid’]) ? esc_attr($_GET[‘oid’]) : ”;
$indsc = 1;
$indsc = isset($_GET[‘ind’]) && get_option(‘__wpdm_ind_stats’) == 0 ? 0 : 1;
if ($indsc && !isset($_GET[‘nostat’]))
$log->NewStat($package[‘ID’], $current_user->ID, $oid);
//process filepath to create new file
$this->processPDF($filepath,$filename,$package[‘ID’]);

Obviously all of this gets wiped out when I update the stamper plugin. I’ve added this to my change log notes so that I can add this back in if this bug is not fixed in the next release.

Viewing 9 posts - 26 through 34 (of 34 total)