boothby

@codersantosh

thank you for your great support ??

Hi again,

i did a rollback to version 2.2.0. Now it works for me. So it must be something wrong with 3.0 and the following versions.

Best Regards ??

Hi @codersantosh

thank you for your fast response.

I have selected “random” for order by and “desc” or “asc” for order. I have tried both.

I have deactivated all plugins on my test server (and another server, from a different provider) and used the wordpress theme “Twenty Twenty”.

When I reload the page in the backend (gutenberg editor) other posts are shown to me. Then in the frontend it no longer works.

Best Regards ??

Hallo,

hei?t das, dass Beitr?ge die ?lter sind nicht gemeldet werden k?nnen?

$html = '<ul class="ez-toc-list ez-toc-list-level-1" style="display:none;">' . $html . '</ul>';

@lucio7 use this code. @jupplidhupplid thanks for your solution. That’s exactly what I needed!

Hi @ibiza69,

i mean it’s not that bad. That looks pretty good. You have only 20 (40) error messages in one day. This is of course not optimal but also not extremely bad. The number sequence “1988888454” and “5007494534” is definitely not the number of errors! It’s the number for the Ad blocks.

Hi @ibiza69,

are you using the latest version of Quantcast? i had the same error message when i was using version v16. The errors disappeared with v17.

I just looked it up and the errors are back. A lot less but they are back.

I’m not worried anymore, the problem is with google and not with us. They have to get the problem fixed.

Google published a new Consent Mode yesterday. It is now up to the individual CMPs to integrate this function. You can read more about here: https://support.cookiebot.com/hc/en-us/articles/360016047000

Maybe @rbaronqc can tell us if this has already been integrated at Quantcast.

@sneesel i did use Quantcast and switched to cookiepro just to test it out. Both CMPs have delivered similar results in the last three days. Currently I have very few error messages. I am looking forward to this evening when the new report is ready.

I did not receive any error messages on September 1st.

I replaced the CMP on September 2nd to see what happens. I had massive problems with this CMP the previous weeks. In today’s error report I had a number of 467 2.1a errors. Normally the number should be between 40,000 and 50,000 errors.

Either the reports are faulty or Google has made improvements and can process the signals of the CMPs better.

If you have implemented everything correctly, wait for the next few days. I think the number of errors will continue to decrease.

By the way, I did not use the stackoverflow script mentioned above.

@ibiza69

Maybe you did get on this site more visitors than the other days, that is probably the reason why the number of errors increases.

• This reply was modified 4 years, 2 months ago by boothby.
• This reply was modified 4 years, 2 months ago by boothby.

@reamca

use the second code and do it like in the image below:

View post on imgur.com

I have only tried it myself for a short time and it seems to work. But I did not test it properly.

• This reply was modified 4 years, 2 months ago by boothby.

@fanstebg

Nice that you solved this problem! Did you use this code?
https://stackoverflow.com/questions/63440572/how-to-display-or-block-personalized-adsense-ads-based-on-consent-for-iab-tcf-v2

• This reply was modified 4 years, 2 months ago by boothby.

@fanstebg
I have looked at one of your sites. Before you give your consent, countless cookies and ads are displayed. It does not work that way. As it looks like you are using many different advertising partners, after the grace period you won’t see any personalized ads there either. You have to block all ads and get permission from the users. Your site is not GDPR compliant in any way.

Hello everyone,

after I implemented everything correctly, this was also confirmed by the developer, there were still error messages every day.

Today was the first time I didn’t get any error messages. But the new report shows a total of 878 errors on August 31, while yesterday’s report showed a total of over 17,000 errors on August 31.

Maybe today’s file was not completed correctly.

I have tried different CMPs in the last two weeks and also set them up correctly, but still I kept getting the 2.1a error message.

If you have implemented everything correctly and Adsense is really blocked completely until the user has agreed, then don’t worry about it to much.

I’m almost sure that we can’t solve this error ourselves and that the problem lies with Google. I haven’t talked to anyone yet who could fix the 2.1a bug. Nobody in this thread has been able to do so either.

Hello @spacetime,

I have once again moved the adsense code into the footer. It works.

In the FAQ it says make sure you have Dynamic blocks set to client-side insert – TCF v2.0 based cookie needs to be checked client-side (in the browser).

I did this in the general tap and also on blocks.

Does this only apply to scripts that actually display something?

Thanks for your valuable time to answer these questions.