bighippo999

Hi @sarkware,
Yes that’s fixed it. Will update the review ??

Hi Sark,

Thanks for checking it, screenshot of the area affected by the logo.

https://pasteboard.co/4ZdccDEoJuFi.png

Thanks,

Interesting. Yeah I think it’ll be going off all ours today. I can’t see a reason why that page needs calling, I could be wrong but it doesn’t appear to add anything to our pages, it just looks like tracking.

I can see a lot of changes to plugins in the next few months given the above ruling.

As a website(s) owner, I can’t see how we could justify a connection being needed to pull any icons for social sharing. There’s a number of functions that we do need to call out for, but sharing icons I’d even place below fonts.

I’m interested in this too.

I’ve turned on Cache AddToAny Locally, but still seeing a call to https://static.addtoany.com/menu/sm.23.html

Following: https://www.theregister.com/2022/01/31/website_fine_google_fonts_gdpr/ we’re going through all the requests to see what we need.
The above page just seems to be a function (maybe cookie related) but interested to know exactly what it’s doing before we decide to remove AddToAny.

@ospiotr Upgraded tonight and turned off the temporary one I created to kill the homepage/breadcrumb bar.
New version fixes it and I’ve bought you a coffee ??

Hi @clubkert thanks for the very quick response. Really glad to hear it’s a bug, not intentional and will be fixed. I’ve seen others do similar (we normally just remove the offending plugin, but we use this one) and may have jumped to the conclusion lol otherwise I’d have put it for support. I’ve update the review and look forward to the next update.

Thanks @supportadtribes for replying quickly.
Sadly I don’t feel like removing 60k shortcodes and without them we have no descriptions to pass to Facebook so we’ll have to try another way ??

Hi @wfadam

??

Report sent.

API? The Database server was previously it’s own server running MariaDB (maybe 10.4 can’t remember) on Ubuntu 18.04. And web servers nginx and php7.4-fpm on Ubuntu 18.04. As part of maintenance we’ve built up a new server on Ubuntu 20.04 and migrate everything to that. MariaDB 10.5 (I think), still nginx and php7.4-fpm. Additional web servers can be brought online and will use this first server for DB and NFS but at present since it’s quiet everything is on one server but it’s got more base resources CPU,RAM etc than ever before (that’s not really important lol).

When we migrate from the old DB server to the new each database was export and import then new users were create with new passwords and finally the wp-config.php DB info was update.
I didn’t expect there to be any issue with the _wfhits table after export/import, but run through the disable/delete tables just in case there had been to let the plugin recreate the tables fixing any issues. Since the problem still exists it’s wasn’t an issue caused by moving the DB or sites (phew lol).

Cheers,

@bobpassaro I think it’s against rules to post other plugin links, and I don’t fancy being in moderator jail for 6 months again. So I’d suggest a search for “woocommerce feed” and see what’s available that may suit your setup. We run with about 800 products but behind those are thousands of variations. Like you we had memory errors and no matter how much we threw at it or how much time we increased to just couldn’t get passed the errors. The previous version we ran at least seemed to push new products straight to facebook, but the regular jobs always failed. When the immediate push was removed in place of the regular job we seemed to have nothing new reaching the facebook catalogue.
Like you I think it may be fine if you’re running a smaller store with less items but it just didn’t work for us.

@bobpassaro I don’t know, we removed the plugin a few months ago after reports a few people had been removed as admin on their own pages when trying to upgrade to the new version. We weren’t willing to risk it. For a plugin that really only needs to generate a feed for facebook to have permission to remove admins was just a big no for us. Granted that was never the intention, but the fact it happened at all was enough for us to look at other options and now we use a plugin that generates a feed, doesn’t require any permissions over our pages, doesn’t try to integrate messenger (which we never needed), and doesn’t generate a load of errors in the action scheduler.
I do wish the devs of this plugin well especially because they took over from Facebook who hadn’t really done anything with it in a long time, but we’ve moved on to something more suitable for us.

Thanks for the reply RK.

I finally figured it out by reading through the code (includes/admin/class-wc-admin-log-table-list.php). For anyone who may need it in future:

add_filter('woocommerce_status_log_items_per_page', 'return_500');
function return_500(){
    return 500;
}

just add that to your functions.php

Hi Simon @skyverge,

Apologies the emails saying I had a reply had gone into spam ??

I’ve checked and we’re definitely set at 600 for php execution. WooCommerce Status page extract:

Server environment
Server info:		nginx/1.14.0
PHP version:		7.2.24-0ubuntu0.18.04.6
PHP post max size:		20 MB
PHP time limit:		<strong>600</strong>
PHP max input vars:		1000

but I agree, one part of the action scheduler log says ‘Fatal error Maximum execution time of 60 seconds exceeded’ while another says ‘action timed out after 300 seconds’ and another ‘Fatal error Maximum execution time of 120 seconds exceeded’. We also have ‘PHP Fatal error Allowed memory size of 1073741824 bytes exhausted (tried to allocate 20480 bytes)’ which if my math is correct is 1G of mem (which is again interesting since we have WP_MAX_MEMORY_LIMIT = 512M and WP_MEMORY_LIMIT = 128 set in wp-config).

I’ve actually been reading up on the action scheduler as we’ve just written a plugin to sort orders to queues as they come in and we’ve opt for using the scheduler so it doesn’t impact the generation of woocommerce pages for the customer.
We’ve noticed some of the jobs are taking a time to start as the action scheduler is running the facebook stuff (and it’s definitely in the in-progress status for longer that 30/60 seconds, currently looking at one (5 minutes 47 seconds ago)), so we’ve had to increase the concurrent batches to 3 (instead of 1) so that the in-progress facebook job doesn’t impact other jobs. However I did read about increasing time limits and batch size for action scheduler. We may give that a go or alternatively use wp-cli to fire the scheduler which suggests it may not encounter such problems.

I also agree with @awr10e every 15 mins does seem a bit excessive, we’d be lucky to have new products or updates weekly. Given the (at least some) jobs are running for a quite a time, it must be taking quite some resources to generate this feed so often.

Fingers crossed for the new API version ??

Mar 2020: Was just about to kill this plugin, but can see from another review reply that skyverge has taken over this plugin. I really really hope they manage to sort out the slowness of it. Currently trying to bulk edit and publish 100 products (with variations) in batches of 5 at a time, and this plugin takes sooooo long the page is timing out. It really need to move whatever it’s doing to the background and stop messing up the WooCommerce Admin.

• This reply was modified 5 years ago by Marius L. J..
• This reply was modified 5 years ago by Marius L. J.. Reason: Removed profanity

Update: 29/10/19 (since I can’t edit my own review)

As someone else has recently point out, this plugin caused my account to be locked out needing me to reset my password and review all recent actions before I could get back in.
This happened multiple times over a week before I just gave up renewing the API key. That solved the problem of our site taking ages to update products. Without it being able to connect to FB saving was lightening fast.

I’d planned to make a load of changes, renew the key and just sync the entire catalogue over night but I forgot to and kept forgetting.

Now I’ve gone to do it, renewing the API key says it’s successful but reloading the page says it’s expired. I can’t renew the key and can’t upload all our new products to fasebook.

I really wish you could give no stars, it really doesn’t deserve the 1 star.

Plugin is badly supported, broken and even when it does work interferes with store admin. I’ve written plugins and use others where big processing is offloaded to a cron event instead of running immediately. Such a simple change could make a world of difference to the admin interface (that is, if it ever works again).

Agree, I always use the keyboard to confirm but now have to move around the screen a lot more. On desktop not as much of an issue but laptop with trackpad it’s just wasted time. It’s not just the confirmation box, the whole feel is a lot more spread out and having to move around.

Personally I also preferred the old way it was integrated into wordpress admin. You could easily get to the site posts or whatever and back to MainWP. Now it feels like your locked in to MainWP and have to ‘Go to WP Admin’ all the time. If you have a dedicated blog for MainWP then I’m sure you’d be happy with it, but I actually use the blog it’s on.