Creative Themes

@mrskt00 Hello!

First of all, the post_thumbnail_html filter works just fine with Blocksy, I just gave it a go. But, in order for it to work, the post needs to have a real featured image attached to it (that is, has_post_thumbnail() has to return true for that post). Otherwise, the filter won’t even be called.

There are two options here (I would go with the 2nd one honestly):

1. Re-write the blocksy_get_featured_image_output() function in a child theme from the inc/components/single/single-helpers.php. Re-write the function implementation to pull the image from your custom source. Note: this will be quite tricky to implement and you will be on your own to maintain this function.
2. Follow this steps:
   • Rewrite your custom field to use attachment IDs (not URLs). I understand that this might or might not be possible, depending on where you’re taking your images from.
   • Implement a custom filter that we will give to you that will pull the image from that new source.

If you are okay with strategy #2 — please let us know and we’ll implement the filter in the next Blocksy release. We will also give you a beta version with the implementation and also an example code snippet that you can use as a reference.

If you absolutely must use URLs and not attachment IDs, please also let us know and we’ll think of something.

Waiting for your reply so that we know how to move forward.

Thanks and all the best!

• This reply was modified 3 years, 1 month ago by Creative Themes.

Hi @static1635,

That’s really weird, this is the first time when someone is reporting such an issue… Honestly I don’t really think this is somehow related to Blocksy but we can make a more detailed investigation.

Please find the debug.log file and send it to our email – hq@creativethemes.com

Waiting an email from you.

Have a good day!

@abbelal Hello!

We implemented this flow intentionally, because lots of things can break when people start removing our callbacks one by one (we rely mostly on such actions to do our WooCommerce customisations).

The proper way to go about is to implement a new filter to allow you to disable this behaviour (we already do this when we notice certain plugins that also do changes on the checkout form, as you can see from the source code in that file).

The new filter will be called blocksy:woocommerce:checkout:has-custom-markup and it will be available in the next Blocksy update. If you need, here’s a beta theme version with the implementation: https://bit.ly/3l7lD5h

Usage is pretty straightforward: add_filter('blocksy:woocommerce:checkout:has-custom-markup', '__return_false');

Hope this helps!

With pleasure @alfredo1216 🙂