noplanman

I’m still running into this issue, even with PHP 8.1.

When test mode is activated, the PayPal connections works perfectly, even with PHP 8.2.

Is there anything I can try or logs to check?

Thanks so much!

Thanks @smakazmi15, here you go. I doubt it’s a plugin conflict, but just to point out, the domain of the site is different to the email sending domain, in case that matters.

Mailer: phpmailer
HostName: example.org
cURL Version: 7.81.0
OpenSSL Version: OpenSSL/3.0.2
OS: Linux localhost 5.15.0-76-generic #83-Ubuntu SMP Thu Jun 15 19:16:32 UTC 2023 x86_64
PHP: Linux 8.1.23 C.UTF-8
PHP Dependencies: iconv=Yes, spl_autoload=Yes, openssl=Yes, sockets=Yes, allow_url_fopen=Yes, mcrypt=No, zlib_encode=Yes
WordPress: 6.3.1 en_GB UTF-8
WordPress Theme: SMN
WordPress Plugins: PDF Embedder Premium, Admin Menu Editor, Amazon Link Engine, AWeber for WordPress, BuddyBoss Platform Pro, BuddyBoss Platform, Category Editor, Classic Editor, Vimeotheque, Complianz Privacy Suite (GDPR/CCPA) premium, Complianz - Terms and Conditions, Disable Comments, Divi Builder, Enable Media Replace, Enhanced Media Library, OMGF, LH Add Media from URL, MEC Advanced Speaker, MemberPress AWeber, MemberPress + BuddyPress Integration, MemberPress Divi Content Protection, MemberPress Downloads, MemberPress PDF Invoice, MemberPress Plus 10 (Legacy), Members, Modern Events Calendar, NinjaFirewall (WP Edition), Pages with category and tag, Popups for Divi, Post SMTP, Post Type Switcher, Fixed Widget, Recencio Book Reviews, Rank Math SEO PRO, Rank Math SEO, SMN Book Review Importer, SMN, SupportCandy, Vimeotheque PRO, WebP Express, WPForms AWeber, WPForms Conversational Forms, WPForms Form Locker, WPForms Geolocation, WPForms Google Sheets, WPForms PayPal Standard, WPForms Stripe Pro, WPForms, SupportCandy - Agentgroup, SupportCandy - Assign Agent Rules, SupportCandy - Canned Reply, SupportCandy - Email Piping, SupportCandy - Export Ticket, SupportCandy - Print Tickets, WPvivid Backup Plugin, YouTube Showcase Professional
WordPress wp_mail Owner: /var/www/example.org/wp-includes/pluggable.php
WordPress wp_mail Filter(s): wp_staticize_emoji_for_email, PostsmtpMailer->get_mail_args
Postman: 2.5.9.4
Postman Sender Domain (Envelope|Message): example.net | example.net
Postman Prevent Message Sender Override (Email|Name): No | No
Postman Active Transport: Gmail API (https:oauth2://www.googleapis.com:443)
Postman Active Transport Status (Ready|Connected): Yes | Yes
Postman Deliveries (Success|Fail): 113511 | 572
Postman Email Log (Enabled|Limit|Transcript Size): Yes | 10000 | 128
Postman PHP LogLevel: 30000
Postman Stealth Mode: Yes

Hi @postsmtp, I’m good, hope you are too! =)

I’m on 2.5.9.4 now and the error is still popping up in the logs.

Let me know how I can do to help debug this.

I get the same error, using the latest version 3.0.3

Changing the add_page method at lib/controller/class-premium.php:57 to static fixes it.

Sounds good!

Hi Tom,

Thank you for the clear response.

Since this plugin is developed by AWeber itself, I wrongly assumed it was the safest way to do this.

It is very clear now that I need to develop our own integration, which I’ll go ahead and do.

Armando

Hello again,

I’m flabbergasted with the latest update to the plugin, version 7.3.3.

Instead of fixing a single line of code, the decision has been made to remove parts of the API…

Very sad to see how actively AWeber doesn’t want to create a developer-friendly experience here.

Uninstalling now…

Hi Steve,

Thanks for your reply.

To be quite frank, I can’t understand how an official plugin from AWeber doesn’t fix a bug in their code, even if it’s not used internally.

I’d expect the API provided by this plugin to be the truest reflection of the AWeber API, so that any developers who would like to create simple extensions, can use this plugin as a base. Forking for my own needs is always the last option for me, as a fix would benefit everyone!

If the code were open source I’d be more than happy to make a fix.

P.S. I’ve seen other plugins that use the AWeber API code that’s in this plugin, and they have the bug too…

https://en.wikipedia.org/wiki/Amazon_Standard_Identification_Number

For books with a 10-digit International Standard Book Number (ISBN), the ASIN and the ISBN are the same

Confirming that 4.9.1 fixes the problem, thanks!

Brilliant, thanks!

Hi @w33zy, I don’t mean to be impatient, but is there a plan for the next release that contains this fix?

Quick update, which is working for me. Not sure how pretty this is though.

$GLOBALS['review_id'] = $post_id;

$_POST['rcno_reviews_gr_cover_url'] = get_post_meta( $post_id, 'rcno_reviews_book_cover_url', true );
$_POST['rcno_book_title']           = get_post_meta( $post_id, 'rcno_book_title', true );
$_POST['rcno_book_isbn']            = get_post_meta( $post_id, 'rcno_book_isbn', true );

( new Rcno_Fetch_Book_Cover() )->save_and_attach_cover_data();

Hi @arsalantariq

I can confirm that 2.0.25-beta.1 is working ok.

Thank you!

• This reply was modified 2 years, 11 months ago by noplanman.

Great, thanks for the update!