Forum Replies Created

Viewing 12 replies - 1 through 12 (of 12 total)
  • Bump for this one. Can we get an update?

    Thread Starter yellowpeach

    (@yellowpeach)

    Bumping this again as no response. Thanks

    Thread Starter yellowpeach

    (@yellowpeach)

    Any chance of a response on this one? It seems that currently your plugin doesn’t work with any sites that are built on Bedrock.

    Normal media uploaded to WordPress’ media library correctly saves to Bedrocks upload directory /web/app/uploads. However your plugin must use a different function for getting the upload path as it’s storing it in /web/wp/wp-content/uploads which means those images are wiped when we next do a WP update.

    Thanks

    I’m getting the same issue

    Thread Starter yellowpeach

    (@yellowpeach)

    Yes that’s correct, we’re just using the standard card processing option.

    That’s a little disappointing that there isn’t a simple solution here – we’ll need to explore if Advanced Processing is an option otherwise we’ll need to look at using another plugin. I would certainly recommend documenting this issue in your plugin as we wasted lots of time digging around trying to resolve this issue only to realise it’s a known problem.

    Thread Starter yellowpeach

    (@yellowpeach)

    Have finally got around to logging a bug report: https://github.com/Yoast/wordpress-seo/issues/17321

    Thread Starter yellowpeach

    (@yellowpeach)

    I’m happy to be alerted on updates of this one until it’s reserved, so makes sense to keep it tracked under the same ticket.

    Thread Starter yellowpeach

    (@yellowpeach)

    Hi there,

    Ok, if you can please keep us posted. To confirm, it’s not anything to do with the custom product type – if I add the high number of post_meta to a ‘simple’ product type (which comes as part of WooCommerce core) the issue is still there.

    It’s purely down to Yoast + a large number of post meta. I haven’t tried it, but my guess would be that this issue is the same whether it’s a WooCommerce product or any post type.

    Many thanks,

    Thread Starter yellowpeach

    (@yellowpeach)

    Hi there,

    Having tested a bit more, I can see that it’s something related to post_meta & Yoast.

    We use the standard WooCommerce ‘simple’ product type and also a custom product type which has a couple of fairly large ACF repeater tables in.

    The ‘simple’ WooCommerce products have no additional fields in so are in essence a bog standard WooCommerce product setup which has no performance issues, however the custom product type (‘Room’) has all the additional fields in due to the customisation required.

    Checking the database and comparing the 2 product types, the ‘simple’ product has around 50 post meta rows, whereas our custom product type ‘room’ has over 2,000. I manually deleted half of those rows to cut it down to 1,000 and the performance issue was gone, so it definitely seems to be the number of data being loading and that causing issues with Yoast.

    To confirm, that amount of data is required in these products due to the complexity of them. We’ve also tested removing the ACF fields from the product page so that when you edit a product, the fields aren’t actually there – just in case it’s an issue with how ACF initialise the fields, but the issue still persists. Again even with these products with large amount of data in, as soon as we disable Yoast they load instantly again so it’s almost as if the Yoast metabox initialisation speed is dependant on the amount of post meta assigned to the post.

    Hope that gives you a bit more detail, but the best thing I can suggest is to insert a large number of post meta for a product (2,200 in our case) and then try loading the product edit screen and you should get the same issue.

    Many thanks,

    Thread Starter yellowpeach

    (@yellowpeach)

    Yes we already had the content analysis plugin installed so that didn’t help.

    I’ve just gone to submit a bug report, but your website is done… “There has been a critical error on this website.”

    Thread Starter yellowpeach

    (@yellowpeach)

    Hi there,

    As I mentioned in my original comment, we’ve already tested using a core WP theme (TwentyTwenty), and also just having the required plugins (ACF, WooCommerce and Yoast), but the issue is still there.

    If I look at the network waterfall, it’s very clear that the waterfall stops when hitting the SVGs being loaded in the Yoast meta box CSS file – exactly as mentioned in the other forum thread that I included in my original message. Here is a screenshot to show this: https://ibb.co/7CJx2XW. The waterfall is at around 3 seconds up to this point, and then does nothing until 20 seconds at which point this SVG loads, the page becomes interactive again and the remainder of the page loads.

    Thanks

    Thread Starter yellowpeach

    (@yellowpeach)

    Hi there,

    Yes we’ve got everything running up to date (WP core, plugins etc). We’ve also ran the data optimization but it made no difference.

    Our products are slightly more custom than a standard WooCommerce store, so we don’t use the post_content and instead pull data from custom fields etc so the post_content editor is always empty for all products.

    That said, we do have a custom WooCommerce product type which loads quite a few ACF fields in the back-end where data is stored. Two scenarios explained below:

    ? “Simple” WooCommerce product type – This is basically just the standard WooCommerce product with no additional fields. Yoast seems to load pretty efficiently in this instance.
    ? Our custom WooCommerce product type – In this product type, we have quite a view ACF fields that are loaded specifically for these types of products and these are the ones that seem to take an age to load.

    Initially we thought it may just be the number of fields being loaded from ACF that was taking the time, but again when we de-activate Yoast or disable it for the product post type, the page loads pretty much instantly which shows that’s not the issue.

    We also tried taking all the ACF fields out for the product pages that were slow, but the issue still persists. The post meta would still all exist for that product though so I don’t know if that would make any difference.

    Thanks

Viewing 12 replies - 1 through 12 (of 12 total)