bgin

Thank you for taking the trouble to study my problem. I knew that the path of my .ccs style files was correct. My custom blocks worked fine until recently (It was probably when I upgraded to wordpress V6.4.2 that the problem arose).
What troubles me is that the problem doesn’t exist on my development site. Then I remembered that I’d created all my custom blocks on the development machine and transferred them to the production site, by copy and paste, which I didn’t keep a log of. Based on this, I had a doubt about the orthodoxy of my manipulations. For example, I noticed that the guid of the posts created in the production site included the url of the development site.
So I created a new custom block directly on the production site, to check whether I should take this observation seriously. Unfortunately, the new block doesn’t call the style rules built into the block-….css file either.

So, for the time being, I’m sticking with the workaround I indicated. It’s a bit of a shame, as you lose the encapsulation of Genesis blocks.

As you can see, I’ve made great progress in English. Thanks to DeepL! ??

Thank you.

• This reply was modified 1 year, 1 month ago by bgin.

Unfortunately, I’ve aligned the plugins on my production and development sites and I still haven’t found the normal behavior of the production site.

Hello,

I’ve just discovered that my development site is working normally in version 6.4.2.
I’m going to look for differences (plugins, page code), as the twenty twenty theme is at the same level.

Thanks for you answer.
The path of the css files is the same as the php’s one.
it is : https://voce-tolosa.com/wp-content/themes/twentytwentytwo-vt/blocks

I hope this information will usefull for you to explain the problem.

Thanks for your answer.