UAGDay attribute polluting the code

  • Resolved cvladan

    (@cvladan)


    1 year, 6 months ago

    The problem is that the “UAGDay” attribute is constantly polluting the code even when this option is not being used in any way in Spectra. I kindly request that you investigate this issue and correct it so that if the “UAGDay” attribute is not being used, nothing is written to the code tag.

    Here is an example of how this issue is polluting the code:

    <!-- wp:group {"className":"whatever","UAGDay":[]} -->

    Thank you for your attention to this matter. I hope for a prompt resolution before my entire website becomes littered with unnecessary UAGDay attributes ??

    Of course, thank you for the elegant and useful set of blocks that you are developing and supporting completely free of charge.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support mohsinbsf

    (@mohsinbsf)

    Hi @cvladan,

    Sorry for the inconvenience caused to you.

    Can you please provide more detail steps to replicate the issue?

    Looking forward to hearing from you.

    Have a nice day!

    Thread Starter cvladan

    (@cvladan)

    Hi! I believe I’ve provided sufficient details, as I’m unsure how to explain more comprehensively. Should I mention that this involves Firefox, Windows and macOS, PHP7.4, and the latest WordPress? I think all these specifics won’t be of much help.

    As I’ve said, try anywhere to use the Spectra “Display conditions feature for the blocks” – the option “Day-You can select the days you want to disable.” Everything is clearly explained on the page https://wpspectra.com/docs/display-conditions-blocks/

    So, use that option on some core block, and then disable it. In the original post, you can see an example of what it looks like for core/group. Then look at resulting Gutenberg block code, even after not being used, or even if it wasn’t used but was just tampered with – why are there so many empty attributes left that should have been deleted?

    I can make a video if necessary? But I think it’s clear now.

    Plugin Support mohsinbsf

    (@mohsinbsf)

    Hi @cvladan,

    Thanks for the more details. I have replicated the issue and passed on the details to our developers to investigate the issue in detail. Rest assured, I will get back to you as soon as I receive an update from them. Till then, I appreciate your patience and understanding in this matter.

    Have a nice day!

    Plugin Support mohsinbsf

    (@mohsinbsf)

    Hi @cvladan,

    The dev team started working on this issue, we will release an updated version of the plugin as soon as it is done.

    Please feel free to open a new thread if you face any other issue.

    Have a nice day

    I have the same issue

    Plugin Support mohsinbsf

    (@mohsinbsf)

    Hi @chusterclock,

    Would you please start your own thread?

    Let’s help the forum stay “clean” as per the forum guidelines.

    Have a nice day!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘UAGDay attribute polluting the code’ is closed to new replies.