Creative Themes

Hi @zax007,

Thanks again for the reply.

1. Yes, correct, both actions will have $type as they argument
2. Why you call this action if the element itself is not present on the page? If you need to put something even if hero isn’t present, you need a more higher level action, not the one tied to that element.
3. Disabled means fully removed from HTML
4. I totally understand your concern about default values, but in your case you were already playing with the framework internals. And when you start to do that, you need to take care of doing things exactly like the framework is doing. You can copy a half solution and then hope everything will just work.

I hope this makes sense.

Hi @zax007,

Sorry for the delayed reply.

It’s totally normal that you get null in response for this function. First of all, you need to understand that blocksy_get_page_title_source() function is dependent on the current page and it returns null if the page title is disabled for the page you’re currently on.

That is, before attempting to even call blocksy_akg_or_customizer, you need to make sure blocksy_get_page_title_source() is non-null.
Also, blocksy_akg_or_customizer() has a 3rd argument, which is absolutely needed to cover all the cases — the default value.
If you’d look in inc/components/hero-section.php, we provide a correct default value when attempting to compute the hero type (type-1 or type-2):

		$actual_type = blocksy_akg_or_customizer(
			'hero_section',
			blocksy_get_page_title_source(),
			$default_type
		);

—

But, to make things easier for you, we could supply the hero type as an argument to the blocksy:hero:after action, so you don’t have to compute it yourself.

Please let me know if this sounds good and I’ll prepare this small improvement for the action for the next update.

Sorry again for the delayed reply. All the best!

• This reply was modified 3 years, 10 months ago by Creative Themes.
• This reply was modified 3 years, 10 months ago by Creative Themes.

Hi @prabuddh09,
Could you please share a link to the page where this happens?

Hello @acejou,
As I can see you are using the pro version of our theme, in this case please submit a support ticket on this link because this forum is for free users only.

I understand what do you mean now 🙂

Well, in past we had our own lazy load functionality and we where able to add a CSS transition/animation to all images that are in the process of lazy loading.

In the previous update we got rid of our solution and implemented the WordPress native lazy loading functionality because it has already a very good support in all browsers.
The only thing is that the WordPress native lazy loading doesn’t have a transition applied to all images while they load, but this doesn’t mean that your images are not lazy loaded 🙂

If you will take a closer look at your website source code, you can see that all images have an attribute loading="lazy", please see this video – https://d.pr/v/lUBbHp

So, to sum up, everything works like it should, the only thing is that there is no image animation when the image is loaded, but that’s not a problem from our side, this is how WordPress lazy load works.

Hope this makes sense.