Gmads

Hello Aert,

Indeed, it does. Ah… I missed that setting.

Given that blocked content has to do with marketing cookies, I’d say that it should only enable that specific category.

Thanks once again,
Guillermo

Hello,

Just a quick update regarding the Yandex plugin.

I finally solved this by reinserting the Yandex Metrica counter function into the “Run asynchronous scripts on consent,” and by modifying the plugin to block the code that inserts the function into the page. Now I can have the cookies blocked until the user consents, and still have the reports at the WP dashboard.

Thanks again for your advice,
Guillermo

Hello Leon,

I was doing some testing and giving it some time, but I guess that it may have had to do with my setting not being all finished correctly, as I mentioned in my other thread. After fixing the set-up and running the wizard, all the cookies were listed and, the plugin is now working fine.

Thanks very much for your help,
Guillermo

Hello Aert,

Yes, I have pending doing the IP anonymization, just as I did for Analytics, but even so, it would have been great to have the cookies actually not set until the user consents to the statistical cookies, just as with those of Google.

No, no e-commerce data used. My client’s site is very simple in this respect because, at least for the moment, they only need to have a general idea about how the site is being used.

Hopefully at some point the Complianz plugin will be able to also put on hold Yandex cookies ??

Thanks for your help,
Guillermo

Hi Leon,

Well, it seems that I was doing a few incorrect things because I had not actually grasped the correct way to set up everything, but after some long thinking, given your tips, I finally figured it out:

1. Disable all cookie-related plugins.
2. Log off from WP.
3. Set the browser to allow all cookies and disable the “do not track me” feature.
4. Clear all cookies.
5. Open a normal (not an incognito/private one) browser window.
6. Visit the site and navigate around a bit, specially where cookie-setting services might be (like YouTube videos).
7. Log on to your WP site.
8. Enable de Complianz plugin, and run de wizard.

These steps will set the correct environment for the plugin wizard to actually find all the cookies that are created, and the services used. Once the plugin has the correct info, one then may reconfigure the browser to its original settings, and continue to work with an incognito window, if that is what one is used to.

My site’s Cookie declaration page is now listing correctly all the cookies.

Thanks a lot,
Guillermo

If I disable the plugin… I would then miss the statistics block shown at the dashboard, which would then defeat the purpose of having this plugin. I think there is something here that I’m not getting about this “removing the function from the page.”

Thanks,
Guillermo

Hello Leon,

I originally did the test in a private window. What I noticed is that if I accept all from the start, then it runs fine without appearing again. The issue, it seems, happens if I start by accepting only a subset, then, even if afterwards I accept them all the message reappears.

I’ll test this again and let you know about it.

Thanks very much,
Guillermo

Hello Leon,

I kind of imagined that, but I wasn’t sure about how to proceed; I also imagined that maybe the plugin would scan the code and block the referenced script ??

So, I should then simply disable the Yandex plugin, or remove it all together?

Thanks,
Guillermo

Hello Leon,

Ah! Yes, the update page indicated that updates were available. That did it. So now the policy is being displayed in Spanish. Thanks!

Regarding the fonts service, I had disabled it manually at one of the steps of the wizard, but I saw it listed at the end. It is not critical.

Okay, I’ll check the translation page and work on it.

Thanks once again both for your help.
Guillermo

Hello Aert,

I didn’t know that. Okay, I just changed the language to “Spanish”, cleared the cache, reran the wizard (which still listed the Google Fonts service, which I am now self-hosting since a couple of hours ago), and reloaded the page… it still showed in English.

Yes, I could contribute to the es_mx translation, though I would need to see about the steps to do it.

What else could we attempt to do to make this work?

Thanks,
Guillermo

Hello Leon,

As I had read other posts regarding language issues, I had already checked, but just in case, I double checked:

https://i.postimg.cc/Hx20BxgM/doubled-checked.png

First emphasized area: Mexican Spanish (at the General Settings page).
Second emphasized area: WP Spanish-version (5.4.2-es_MX).
Third emphasized area: All translations are updated.

I added the shortcode to my original Cookie Policy page (declaracion-de-cookies), which is not as complete as the one generated by the wizard, and yes, the cookie list is displayed, though all mixed up: most of the texts in English and a few parts in Spanish: “We use Google Fonts for mostrar fuentes web.” ??

Well, while this could more or less work, I think it would be best to have it all in Spanish.

I have a cache plugin (Cache Enabler), but I have also made sure of clearing it.

The Compianz plugin version is 4.6.10.

Thanks again for any suggestions you may have,
Guillermo

Hello Jordy,

Thanks for your comprehensive answer. I hadn’t followed-up because I had to put on hold working on the site for a few days, but I’m back to it. I’ve been doing some tests in order to understand a bit more this subject.

First, to answer my own question: yes, one does have to go through every post to select each WP gallery and change it to the wished new one via the Gutenberg block menu. And also “yes”, if for one reason one wants to uninstall whichever plugin was used one has to repeat the same process and change each gallery into the WP standard one, otherwise one would end up with the following error message:

Your site doesn’t include support for the “uninstalled-plugin-name” block. You can leave this block intact, convert its content to a Custom HTML block, or remove it entirely.

Given that everything is just HTML code, I had initially assumed that this process had to be done only when using shortcode-based plugins, but this is not so, it actually has to be done regardless of the inner workings of the plugin, that is, irrespectively of them using a shortcode or HTML code. So, there’s no real difference in using either of them, one has to manually change everything via the Gutenberg block menu, to and fro.

What I learned about this “block” thing is that they are just pieces of HTML code surrounded by comments whose content defines the type of block. A paragraph block, for example, is just a starting “wp:paragraph” comment, followed by the paragraph itself and ended with a “/wp:paragraph” comment.

Indeed, shortcodes will not go away any time soon, but the recommendation is to change them, as indicated in the FAQ.

“We would recommend people eventually upgrade their shortcodes to be blocks.”
https://developer.www.ads-software.com/block-editor/principles/faq/#how-do-shortcodes-work-in-gutenberg

As there exists a standard shortcode block, which is just the original shortcode surrounded by the corresponding opening and closing comment lines, I’d say that the recommendation implies using HTML code instead of just leaving the shortcode.

Anyway, given all the converting and possible reconverting, I decided to stick with the standard gallery, but I’ll consult my client about all this.

Once again, thanks for your answers.

Cheers!

Hi amboutwe,

Thanks for your answer and the reference. In this case the problem had to be with the browser, a very old version was being used: Chromium 49.

Cheers!

Ok, after some Googling and reading a few articles, and for anyone newcomers that may be just starting with WP and plugings, it turns out that the so-called WP Shortcodes will become a thing of the past, as the new WP (5.0 upwards) is based on a new paradigm: Gutenberg Blocks.

Given this new underlying mechanism, if one wants to stay on the safe side, at least on a long-term basis, one should then forget about shortcodes. The real question should not have been how to convert the new default WP blocks (be them for a gallery or any other element) into a shortcode, but the other way round.

While it certainly seemed tempting to go throught my site and change every gallery block into a shortcode so as to then be able to use the Meow plugin, specially because even if I later were to uninstall it my site would not break because the plugin actually uses the WP shortcode, it has now become clear that this would be a step backward. Yes, shortcodes work and there is even a shortcode block, but it does seem a better strategy to stop using them.

What options does one have?

1. Use the WP default gallery Gutenberg block code.
2. Look for a gallery plugin that natively uses block code.
3. Wait for the Meow Gallery to migrate from shortcodes into blocks.
4. Keep on using shortcodes.

— References

https://www.ads-software.com/support/topic/shortcodes-vs-blocks-2/

https://wptavern.com/wordpress-developers-learn-how-to-convert-shortcodes-to-gutenberg-blocks

https://www.affordablewebsiteorlando.com/learn-convert-shortcodes-gutenberg-blocks-wordpress-developers/

https://www.codeinwp.com/blog/adapt-your-plugin-for-gutenberg-block-api/

Or just google something like “wordpress shortcodes or gutenberg blocks.”

Cheers!

It is said that a lack of an answer is an answer by itself, so I guess I must have stated the obvious. Time to look somewhere else.

Thanks.