The latest version 3.0.0 isn’t working

+1

Also having lots of problems as a result.

Changelog also showing otter blocks and not Blocks CSS.

• This reply was modified 3 months, 1 week ago by Nathan Monk.

Hey @rose18,

Thank you for reaching out!

I tested this on a fresh instance, but didn’t encounter any issues. As you can see here – https://vertis.d.pr/i/VZY8P2, the Custom CSS accordion is still available in the sidebar.

Can you please clear the cache and see if the issue persists? If so, can you share some screenshots?
@nathansmonk, can you please share more details about the issues you encountered? Feel free to start a new thread.

Hi @andreearadacina21, thanks for your response, but it does not reflect my experiences. As a result, I don’t consider the issue resolved I’m afraid.

In my instances, the Blocks CSS accordion does not show. This is in multiple separate instances of WordPress.

I have tried deleting caches, and using a different browser entirely.

Screenshot as requested: https://d.pr/i/WdXqgK

Hi @nathansmonk,

Can you please update to the latest version and confirm you have the Custom CSS module enabled https://vertis.d.pr/i/4cpe5g ?

Thank you,

Rodica

@rodicaelena – When my wordpress core was 6.4.2 and when I updated this plugin to version 3.0.2, it still doesn’t work, the Custom CSS panel?was still missing.

When I updated the core to the latest version (6.6.1), the Custom CSS panel?shows up.

Hi @rose18,

Thank you for sharing that! Yes, the latest version of WordPress is also a requirement.

Kind regards,

Rodica

My plugin was already at latest version 3.0.2 thanks to auto-updates.

To clarify though, I am not using otter blocks. Just the standalone Blocks CSS plugin.

I upgraded WP from 6.5.5 to 6.6.1 and the CSS panel returned. If WP versions below 6.6.1 are no longer supported, it would be good to reflect this in the “WordPress version” in the plugin overview.

However, if this is not expected, then it may be a bug that has been introduced in the 3.0.0 release.

Hey @nathansmonk,

Thank you for sharing more details!

I managed to spot the behavior you mentioned and forwarded it to our development team for review. In the meantime, I am happy to see you can now use Blocks CSS as expected.

Best regards,

Andreea

Thanks @andreearadacina21 – I do have other sites that, for other reasons, cannot have their core updated right now. So the issue with the plugin persists for some of my other use-cases sadly. I am confident that many other users that will also be affected by this issue.

I look forward to an update about whether the bug will be patched, or if the WP Core requirements/dependancy will be updated to reflect what I am currently observing.

@nathansmonk,

The issue has already been forwarded to our products team for investigation. Unfortunately, we can’t provide a time frame for this to be resolved. We appreciate your understanding and will keep you posted as soon as we have updates.

Best regards,

Andreea

Hi @nathansmonk, @rose18,

I hope this message finds you well.

I am pleased to let you know that we recently released an update for Otter that addresses the issue you reported. We appreciate your patience and support during this process.

Have a great day ahead!