Lots of issues

  • David Decker

    (@daveshine)


    8 years ago

    Hi there!
    I think the idea for this plugin is really interesting to have a color palette/ style guide to be used in the Block Editor.

    However, most of the plugin is not working yet, below I list the issues:

    – colors are properly visible within Gutenberg Editor (backend) but don’t get applied on the frontend yet
    – the admin settings page is only partly working: tab “Style Guide” and tab “CSS Reference” are not visible at all
    – viewing both tabs is possible when I manually change the URL to tab=style-guide or tab=css –> but no tab label
    – and for CSS page it is completely empty, only style guide page then lists the palette

    What is confusing:

    – what does “Status” do at all? How it is determined?
    – why is the platte set in the Customizer when there is no preview needed?
    – it would make much more sense to setup a color palette on your admin page which is then set for usage within Gutenberg AND the Customizer and other instances where colors are used –> so basically you would set a palette before desigining/layouting in Customizer or creating posts, pages etc.

    Would love to see these issues fixed, otherwise the plugin is not usable and makes no sense at all.

    Thank you in advance! 🙂

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Dave Ryan

    (@dryanpress)

    8 years ago

    Hi David

    * If colors aren’t showing in your theme, check that wp_head(); is in the Theme — that’s where the CSS gets added. I will add an additional helper to force output the markup.
    * This custom function determines whether the palette is coming from the Theme, WP Block Ink or the default WordPress palette.
    * To see all the tabs, you’d need to set a custom color theme in the Customizer (which are added to the Colors tab to centralize color options — there’s a link from that status page). At present the plugin doesn’t yet build a style guide or reference for a Theme’s definition.

    Thread Starter David Decker

    (@daveshine)

    8 years ago

    @dryanpress
    Hi David!

    Yes, I tried all of that already but it didn’t work so I posted here.
    I tried on one install (local) with the new “Atomic Blocks” theme. I could set a palette in Customizer – and it appeared in Gutenberg. I could use in Gutenberg and it worked within the Gutenberg Editor — but on preview or frontend view of the site the colors did not appear, sadly.

    The very same things happened when trying on a another install (on a hosting provider, non-local) with the popular “Astra” theme.

    I tried everything a dozen times or so in both installs as I thought it was just me and I did anything wrong, however, I think it just didn’t work properly…

    In both cases the additional tabs in backend settings also did not appear!
    I researched your plugin code and could manually access those tab URLs in the browser, though.

    Also, in the Customizer I had issues with the “Prevent Non-Palette Colors” setting (on/off switch) as it seems to not properly safe and it is unclear what it does, what it prevents.

    My view is:
    Your plugin seems to be really useful (!) when it would be working properly. I hope you can follow my report and can reproduce it.

    I would suggest to improve the user guidance and texts in the plugin so it is a lot clearer what it does – especially on your backend settings page. I would just bring the color pickers there and let the user set the palettes there – and have them also appear on any Customizer color pickers. Would make so much more sense.

    Also the settings tabs should be appear permanently — if they have no content then say it to the user.

    But you have them appear in your screenshots here on .org but users (at least myself) are unable to have them appear in their installs. Makes no sense to me.

    Again, don’t get me wrong, your plugin has lots of potential – if the above things would get fixed.

    Thanks a lot in advance.

    Thread Starter David Decker

    (@daveshine)

    8 years ago

    @dryanpress
    Hi David!

    Yes, I tried all of that already but it didn’t work so I posted here.
    I tried on one install (local) with the new “Atomic Blocks” theme. I could set a palette in Customizer – and it appeared in Gutenberg. I could use in Gutenberg and it worked within the Gutenberg Editor — but on preview or frontend view of the site the colors did not appear, sadly.

    The very same things happened when trying on a another install (on a hosting provider, non-local) with the popular “Astra” theme.

    I tried everything a dozen times or so in both installs as I thought it was just me and I did anything wrong, however, I think it just didn’t work properly…

    In both cases the additional tabs in backend settings also did not appear!
    I researched your plugin code and could manually access those tab URLs in the browser, though.

    Also, in the Customizer I had issues with the “Prevent Non-Palette Colors” setting (on/off switch) as it seems to not properly save and it is unclear what it does, what it prevents.

    My view is:
    Your plugin seems to be really useful (!) when it would be working properly. I hope you can follow my report and can reproduce it.

    I would suggest to improve the user guidance and texts in the plugin so it is a lot clearer what it does – especially on your backend settings page. I would just bring the color pickers there and let the user set the palettes there – and have them also appear on any Customizer color pickers. Would make so much more sense.

    Also the settings tabs should be appear permanently — if they have no content then say it to the user.

    But you have them appear in your screenshots here on .org but users (at least myself) are unable to have them appear in their installs. Makes no sense to me.

    Again, don’t get me wrong, your plugin has lots of potential – if the above things would get fixed.

    Thanks a lot in advance.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Lots of issues’ is closed to new replies.