willemb2
Forum Replies Created
-
Forum: Plugins
In reply to: [WooCommerce] WP dashboard inaccessible after 6.50 updateCheered to early. The next day, surprise: even 300 seconds is not enough:
An error type E_ERROR occurred on line 337 of the file /home/lvbhb/public_html/wp-content/plugins/woocommerce/src/Admin/API/Reports/TimeInterval.php. Foutmelding: Maximum execution time of 300 seconds exceeded
It looks like the webshop itself is work. The only problem is the WP dashboard becoming inaccessible. We returned to 6.4.1 again and disabled auto-updates.
Forum: Plugins
In reply to: [WooCommerce] WP dashboard inaccessible after 6.50 updateUpdate: 6.5.1 is avaiable now
with a Maximum execution time of 90 seconds 6.5.1 is causing the same problem, with 6.4.1 it is fine. Nu issues with our heavy theme (Avada) and around 40 other plugins.
With Maximum execution time of 300 seconds 6.5.1 does not cause the problem.
But 90 seconds is already quite long. Something must have been introduced with 6.5.1 that wants to run very long….
- This reply was modified 2 years, 10 months ago by willemb2.
Forum: Plugins
In reply to: [WooCommerce] WP dashboard inaccessible after 6.50 updateKindly follow the steps provided in this guide to increase maximum execution time
IMHO the instructions on wpbeginner.com are not entirely correct. The line
php_value max_execution_time 300
should be entered UNDER the # END WordPress. Otherwise it gets overwritten by WordPress itself.Forum: Plugins
In reply to: [WooCommerce] WP dashboard inaccessible after 6.50 updateThanks. I have set it to 300 in .htaccess. Currently 6.4.1 is the latest, so we’ll have to wait until a new version gets released.
Forum: Plugins
In reply to: [WooCommerce] WP dashboard inaccessible after 6.50 update@margaretwporg You mention Woocommerce Admin. If you mean this plugin: https://www.ads-software.com/plugins/woocommerce-admin/, we do not have that. We did not see the errors reported in that Github thread. But more in general discussions on Github are above my level of knowledge. I’m not a software developer.
Our problem after the 6.5 update was that the general WordPress dashboard (/wp-admin/) was inaccessible.
That’s sad. This means that I cannot use one of those image optimizer plugins that convert everything to webp. But thanks for clarifying, @bruberries
- This reply was modified 3 years, 1 month ago by willemb2.
This blog post suggests that Outlook supports .webp, but I don’t think it does, natively. When you insert a webp image in Outlook itself it is converted to .png
- This reply was modified 3 years, 1 month ago by willemb2.
@stevejburge , @andergmartins ,
Yes! 2.7.1 solves the problem (and so did RC4, but I wasn’t able to test it until seconds before the release).
Thanks a lot!
@stevejburge Sorry for the late reply. I had to fix my staging site first.
2.7.1 RC3 does not solve the issue. When I pick an old post that is listed with ‘Never’ in the column Expires and edit it, Enable Post expiration gets selected.
Hi @stevejburge
I only entered my email address in the ‘Who to notify’ field on the Defaults tab. I also find it in the same field for all active post types on Future > Post. I assume the plugin replicates it.
EDIT: We use Easy WP SMTP for sending, but we don’t get double e-mails with notifications from other plugins or WP itself.
So, at this point, I would really like to ask you to share this here: https://feedback.mailpoet.com
Forum: Plugins
In reply to: [Easy Updates Manager] plugin stopped workingHi @anthoniusalfred,
In the meantime I had learned that theme and plugin auto-update is part of the WP core since 5.5.
But after uninstalling EUM the column “Automtic Updates” does not appear.
Site health is reporting no issues, it even says at Passed-tests > Security: “Plugin and theme auto-updates appear to be configured correctly”
My guess is that our hosting provider is blocking it somehow. We will open a ticket there.
Hello @bruberries,
So as I understand it, the plugin does not only do this by default, there is even no opt-out. And IMHO that is a bad choice.
Even though addresses are added as “Unsubscribed”, this list is for the GDPR an administration of personally identifiable information that does not comply with the purpose for which the information was provided: fulfilling the order. We’re simply not allowed to do this. And apart from the legal side: the list is there and if an inexperienced editor is only a few mouse-clicks away from accidentally sending a newsletter to webshop users and we will have quite a riot. Data harvesting is a very sensitive subject these days. Before you know some people will be calling it a data-leak on Twitter.
Now that MailPoet is part of Woocommerce.com I understand that your management wants to provide added value by offering integration between the products. But why not give your customers the choice whether they want to use that?
We’re approaching the 1000 address limit and were just considering buying a license. But we cannot use MailPoet if you’re not allowing us to switch off this “feature”.
I know that this pushy marketing style is more common and accepted in the US, but in Europe you will bite your own tail with it.
I just took a closer look to compare recent Woocommerce orders with the contents of the ‘Woocommerce customers’ list. Not every Woocommerce address gets added to the ‘Woocommerce customers’ list. Only a part of them appears on the list as “unconfirmed”. Some others appear when I filter all subscribers on ‘Woocommerce customers’ but without anything listed in the LISTS column. And again others do not appear in MailPoet at all.
Something is not working consistently here.
Note: I left ‘Opt-in on checkout’ unchecked on the Woocommerce tab in MailPoet and the option does not appear on the Woocommerce checkout.
Oh, and Merry Christmas / Vrolijk Kerstfeest op Texel ??