everade

Hi there @anastas10s
So your alternate solution for keeping the data private is by sharing the “secret link” in a public forum?! How’s that supposed to be helpful?

Precautions for card testing attacks were already in place, as well as further basic security measurements. Thanks for the links but it would have been helpful to first indicate that you are suspicious of an attack documentation about card testing attacks.

As far as i’m aware, the useragent: Amazonbot is a simple web-crawler from Amazon, similar to Google and Bing.

It would have been helpful if you guys could explain what exactly could trigger these logs. From my understanding the Amazonbot crawls the website and triggers a purchase with a value of 0. And WooPayments reacts by simply deactivating the purchase button.

But why is a web crawler able to do that in the first place?

As far as i’m concerned, there’s nothing bad happening here. I also run a test and purchases still go through just fine. I disabled logs for now so i’m no longer bothered with my logs being overfilled by this crawler.

Feel free to close this topic. As i don’t expect to get any valuable information from here.

Thank you.

Lovely, thank you

Well not just that line, the entire logs i’ve posted. It’s all over the place every single day. So it’s not just the Info that the order price was 0, but the entire back trace of whatever is going on there. Not sure if it’s an actual attack or if just crawlers are causing it.
All of these logs seem to be only Informational, so i wouldn’t declare them as errors. Note: I’ve enabled error logs within WooPayments.

I would have expected that enabling error logs would enable error logs, not info logs. Will disable this feature for sure, but would be great to hear if these logs are normal.

I haven’t tested an order recently, so i’ve no idea if it still works. I would assume they started showing up as soon as i’ve enabled the debug mode. Start date of logs was: 2023.10.30

And yes i can share the system report for sure, but not here in public due to security reasons.

That’s the case indeed.
Thank you very much.

• This reply was modified 12 months ago by everade.

@geraltrivia @simplysaru @kellymetal
I contacted you guys via the pre-sales question website 2 weeks and 3 days ago as i’ve been told. Unfortunately I haven’t received a single reply.

On top of that, this support “ticket” is more than 3 months old!

Honestly doesn’t look like a serious service from what I’ve witnessed so far. I would have expected that the “official” mail service would offer the best integrated experience unlike 3rd party competitors. But i’m starting to get the feeling that i’ve made an utterly bad choice with this one. Neither the mail service is able to mail, nor the support is able to support.

Does anyone care?

These are 3 different logins with 3 different random usernames and pws.

[23-Nov-2023 13:11:46 UTC] PHP Fatal error: Allowed memory size of 1610612736 bytes exhausted (tried to allocate 1340084224 bytes) in /public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/classes/wp-security-user-login.php on line 336

[23-Nov-2023 13:11:47 UTC] PHP Fatal error: Allowed memory size of 1610612736 bytes exhausted (tried to allocate 803213312 bytes) in /public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/classes/wp-security-user-login.php on line 336

[23-Nov-2023 13:26:50 UTC] PHP Fatal error: Allowed memory size of 1610612736 bytes exhausted (tried to allocate 937431040 bytes) in /public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/classes/wp-security-user-login.php on line 336

@kellymetal
I believe i recreated all mails at least once by now, but i can’t remember. But i can guarantee you that even if it has been recreated, this new version has been sent out >20 times by now, but sent count stays at 0.

There are no errors to be found in WooCommerce > Status > Logs

However i found errors in WooCommerce > Status > Scheduled Actions
These are related to hook: mailpoet/cron/daemon-trigger

1. 2023-10-25 14:01:30 +0000
   action created
2. 2023-10-25 14:04:22 +0000
   action started via Async Request
3. 2023-10-25 14:10:00 +0000
   action marked as failed after 300 seconds. Unknown error occurred. Check server, PHP and database error logs to diagnose cause.

There are no additional PHP errors logged on the host and SQL database seems to be fine too. No idea where else to look. An unknown error isn’t really helpful.

name: redacted
email: redacted
PHP version: 7.4.33
MailPoet Free version: 4.34.0
MailPoet Premium version: N/A
MailPoet Premium/MSS key: redacted
WordPress version: 6.3.2
Database version: 10.6.14-MariaDB-cll-lve
Web server: LiteSpeed
Server OS: Linux redacted 4.18.0-425.3.1.lve.el8.x86_64 #1 SMP Tue Nov 22 22:59:23 EST 2022 x86_64
WP info: WP_MEMORY_LIMIT: 256M - WP_MAX_MEMORY_LIMIT: 1536M - WP_DEBUG:  - WordPress language: en_US
PHP info: PHP max_execution_time: 600 - PHP memory_limit: 1536M - PHP upload_max_filesize: 1536M - PHP post_max_size: 1536M
Multisite environment?: No
Current Theme: Minimog Child
Active Plugin names: polylang-pro/polylang.php, redux-framework/redux-framework.php, all-in-one-wp-security-and-firewall/wp-security.php, complianz-gdpr/complianz-gpdr.php, connect-polylang-elementor/connect-polylang-elementor.php, elementor/elementor.php, google-site-kit/google-site-kit.php, host-webfonts-local/host-webfonts-local.php, insert-headers-and-footers/ihaf.php, insight-core/insight-core.php, insight-swatches/index.php, litespeed-cache/litespeed-cache.php, loco-translate/loco.php, mailpoet/mailpoet.php, metronet-profile-picture/metronet-profile-picture.php, pll-merge-comments-0.2/pll-merge-comments.php, polylang-wc/polylang-wc.php, pymntpl-paypal-woocommerce/pymntpl-paypal-woocommerce.php, tm-addons-for-elementor/tm-addons-for-elementor.php, uncanny-automator/uncanny-automator.php, updraftplus/updraftplus.php, woo-smart-wishlist-premium/wpc-smart-wishlist.php, woocommerce-payments/woocommerce-payments.php, woocommerce-product-tab-manager/woocommerce-tab-manager.php, woocommerce/woocommerce.php, wordpress-seo-premium/wp-seo-premium.php, wordpress-seo/wp-seo.php, wp-mail-smtp/wp_mail_smtp.php, wp-sweep/wp-sweep.php, wpforms-lite/wpforms.php
Sending Method: MailPoet
Sending Frequency: 5 emails every 10 minutes
MailPoet sending info: Send all site's emails with: default WordPress sending method - Task Scheduler method: Action Scheduler - Cron ping URL: redacted?mailpoet_router&endpoint=cron_daemon&action=ping - Default FROM address: redacted - Default Reply-To address: redacted - Bounce Email Address: redacted
Total number of subscribers: redacted
Plugin installed at: 2023-03-24 04:23:26
Installed via WooCommerce onboarding wizard: false

Hey @simplysaru,
I noticed, that the 2 pending tasks just keep getting postponed by another day. As soon as the scheduled time has past, it just sets the scheduled time +1 day, and the mails are never sent. So they’re just stuck there in an never ending loop. Hope my recently provided data and screenshots help.

• This reply was modified 1 year, 1 month ago by everade.

No separate Cron (not that i’m aware of):

System Status:

Here you can see that the 2 mails are scheduled properly this time, but they’re still never sent out. Only the first out of the 3 mails is being sent, the other 2 will just vanish out of the scheduler.

Here’s my basic setup of 3 mails, scheduled one after each other.
The only one being sent is the initial one “Did you get distracted?”. The other 2 just get deleted out of the scheduler. Test-sending them works fine, the only difference of these are the timers.

Problem still persists

Plugin still doesn’t support Polylang/WPML by using multiple Wishlist pages in different languages. Links generated are always in the main language, and links leading to the wishlist page do not link properly.

• This reply was modified 1 year, 1 month ago by everade.

Is this now supported?
I saw in your changelog that you added WPML support, so i’m not sure what’s meant with that.

Well i guess the optimal outcome would be a collaboration with Automattic so you can natively load custom folders and remove some overhead from helper hooks.

This particular plugin I’ve had issues with was even developed by Automattic themselves. I’m not sure if a basic user like me can achieve anything by telling them they’re doing it wrong, but i will try. However it doesn’t affect just this plugin.

I’m really not here to tell you what to do, i’m certain you’re way smarter than me. I’m just looking for a better solution since without custom folders i run into new issues when it comes to updating translations.

And thanks for the FAQ pages, i wasn’t able to find these when navigating your website. Those are helpful indeed.

I’m not really expecting further help or answers from you on this one, just leaving this here. I’m happy with Loco as it is, but i wouldn’t say no to further improvements.

Thanks Tim

Oh wow, you just told me what’s the problem, and i was able to fix it!

before Loco Translate has been allowed to start

System files work absolutely fine but as soon as you try to read customs it just fails.

That tells me custom files are initiated long after the system files were read, which would mean some plugins aren’t particularly”to fast” but instead Loco custom files are just initiated/read to late.

Since you’re referring to this as a “common problem”:
I think it would be really helpful to all users if you would just add a Notice about this in the “Relocate” tab when selecting “Custom”. That it’s possible that some plugins are faster than Loco and some strings might fail because of it, so in some cases using System or Author may fix it.

You can’t expect end-users to know this, and i think this would reduce support requests.

Please note that I never asked you to debug my website, i haven’t even shared it with you. I understand that you’ve been repeating yourself for the past 7 years and it’s super frustrating. But not every user is a programmer or has insights into the depths of your plugin. I personally did not realize that Loco must initiate anything for the custom folder mo files to be read. I believed Loco compiles them and sets a definition in WordPress so it reads the additional loco folder just like the system folder at the same time.

Either way. I’m happy that i found the root cause for this one.
And i hope that adding that simple notice would help you to get a few less frustrating support requests in the future.

Again, thank you for your time.

Yes for issue 2, that would be correct. I found it better on different languages which aren’t scrambled, so the translated string is definitely inside the .mo, however it just doesn’t work when the entire file was generated, translated and compiled 100% by Loco.
I just confirmed this by deleting the entire language, then recreate it using Loco, and only translate this particular string with Loco.

I also confirmed its not a caching issue.

When editing and compiling the working system translation using Loco, the string works perfectly fine.

The system translations which were installed automatically work for this particular string. And the .po entries when comparing the po files from the System to my Custom Loco files are identical for this one, so there’s no issue with the string itself.

I assume there’s a bug in the compilation process so that wordpress can’t read it properly. Unfortunately i’ve no idea how the .mo reading process works, but i would assume that if there’s a tiny error in the .mo file, it will stop reading the rest of the file thus failing?!

Here’s the comparison:
https://i.ibb.co/kB67rSs/2023-09-02-12-03-44-Source-of-woocommerce-payments-zh-CN-po-Woo-Commerce-Payments-Plugin-translat.png

Here are some more custom and working system files.
Note: custom folder fail, system folder work on this string:
https://filetransfer.io/data-package/idT4GNqC#link

Again, thank you for your time, appreciate it.
Looking forward to a fix on issue 3. And fingers crossed on issue 2.

• This reply was modified 1 year, 2 months ago by everade.

Thanks for the swift reply and the insight.
One string that specifically doesn’t work starts with “We noticed “, and which can be found in both the po and mo file. However i can’t find the translated string in the mo file, so i’m not certain if that’s the issue or if i just can’t find it because it’s binary. This is the case for all languages i created custom files for. The string works properly with the Author files though. That’s why i even started comparing the custom files to the author ones and started to notice the multiple line differences.

Here are the 100% completed files:
https://filetransfer.io/data-package/sJoXqsDi#link

• This reply was modified 1 year, 2 months ago by everade.