Goddamn Noise

The issue is fixed for me after updating the Astra theme to the 4.3.0 version.

Hi @bsfherman,

I’ve manually installed the 4.2.2 version of the Astra theme and I’ve cleared the Chrome cache too but I can’t see the eye icon. I’ve checked it and the eye icon’s HTML isn’t there where it should be.

Thanks for your help.

Thanks a lot for your help, Avinash. I’ve just submitted a ticket reporting this problem and providing you access to a staging site where you can test it.

Same problem here. The eye icon to hide the tittle is gone since 4.1.8 version and still missing in the 4.2.2 version.

Hi Filipe,

Not my mistake, it seems like there is a limit in WordPress core and it only shows the first 100 terms in the field. You can fix it with the get_terms_args() hook as I’ve explained in a previous message.

I tried a few filters related with how the metabox poulates things but it didn’t work, so I had to try other things and it worked with the get_terms_args().

Thanks again for your help.

Finally I found a way to fix it using the get_terms_args() filter and setting number equal to 0 wherever the category terms are requested from the database.

Hi Michael,

Thanks for your help.

The taxonomy is set to be hierarchical: to set a category term I have to check a checkbox and there is a field to search terms too.

It seems like a hard limit on the request to retrieve the terms from the database. I’ve deleted a few terms and when the number of terms in the taxonomy is equal to 100 or less there is no problem and all the terms are showed.

But, if the number of terms is greather than 100 then there are terms which are not showed.

Do you know of some hook I could use to remove that limit or what could I do to fix it?

Thanks a lot again.

I’ve just done it and it seems it is working again now even if I choose to use the Lazy Blocks on one post type only.

Thanks a lot for the quick fix!

Hi,

Thanks a lot for your reply. That is exactly the problem I’m facing. If I unselect the specific post type the Lazy blocks can be used again.

Is there any estimation about when the plugin update will be published?

Thanks again for your help!

More information about this issue (when I use the 3.0.0 version of Lazy Blocks):

While editing a post I click on the three dots on the top right corner and then click on “Preferences” and then on “Blocks” to list all the blocks and check if the Lazy Blocks are disabled. But the Lazy Blocks are not listed. If I try to search for the name of the Lazy Blocks I had previously created they are not found.

If I try to insert a new block an click on the “Show all” button of the WordPress block inserter to see the list of all blocks on the left, the Lazy blocks are not listed there either. If I try to search for the name of the Lazy Blocks I had previously created they are not found either.

I’m using the last version of WordPress and all the installed plugins.

Hi again,

I’ve been digging in to be able to provide more information about this problem.

I’ve checked the web server’s logs but I can’t see any errors there.

I’ve checked the browser console but I can’t see any errors either, only two warnings.

I’ve tried to disable all the plugins but it doesn’t work either with all the plugins disabled.

I’ve enabled WP_DEBUG but I can’t see any errors either when trying to add a new Lazy block from the WordPress block inserter.

If I downgrade to the last 2.x version I can find my Lazy blocks in the WordPress block inserter and can work normally.

If I upgrade again to the 3.0.0 version, my Lazy Blocks are gone and I can’t insert new Lazy blocks from the WordPress block inserter.

Does anybody know how to fix this or how to retrieve more information to debug the problem?

Thanks for the quick reply. I’ve just patched it myself until a new patched release will be available.

Thanks to you for the nice work.

Hi @rbaronqc,

I don’t understand the kind of solutions used to solve the problem and don’t understand why the ads should not be shown until the user gives the consent.

AFAIK, the user is giving the consent to use his personal data to customize the ads, and not giving the consent to see ads.

So, Google Adsense should check the IAB API to know if the user has given the consent to use his personal data to customize the Adsense ads.

If the user has given the consent, then Google should show customized ads.

And if the user has not given consent, Google should not show customized ads but it could show not customized ads.

But all of this should be transparent for the developer and as a developer you should not have to check it the user has given the consent to add or not the Google Adsense javascript code. You should add the Adsense javascript code and Google should manage all of that in the previsusly mentioned way.

Am I right?