Falls short

  • Thanks for the plugin. I just disabled it because it really falls short on a couple of reasons.

    First, why use Gutenberg as the editor for this post type? Gutenberg is the most hated editor ever (don’t believe me, just check their reviews). If it wasn’t forced on us, 9/10 would disable it.
    If you are going to use Gutenberg, why not use Gutenberg custom fields so the custom fields is seamlessly integrated into the editor? Right now there’s just this ugly looking metabox in the bottom of Gutenberg on Events.

    Second reason is kind of the same topic. As a UX and PHP developer myself, i don’t understand why the time field is a textfield where you expect a from-to input, formatted in a specific way. This is such bad practice, and honestly the reason i ditched the plugin because it didn’t seem professionally developed in my opinion (sorry i am very sceptic in my plugin choice).
    I really suggest you use the browser-native time field, and separate from/to fields in 2 separate fields. It will also make custom querying against the DB alot easier.

    I hope you take this review as constructive critisism and not as an attack.

    Best luck in the future.

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

  • Well, as an outside observer, I’d say it looks more like agressive criticism.

    Keep up the good work Guido! As I’m sure you know, it’s appricated by many of us.

    Thread Starter boutzamat

    (@boutzamat)

    @lelimousin lol. no one asked you mr. Outside Observer.
    There’s nothing agressive about it so please stop trying to make it sound like it.
    It’s constructive critisism exactly as described. I find a couple of things about it to be bad, and i provide feedback on it. So yeah, please go somewhere else with your negativity ??

    Plugin Author Guido

    (@guido07111975)

    There’s nothing agressive about it so please stop trying to make it sound like it.

    IMO your tone of voice is agressive. So I do like it when other users stick up for me.

    Time field is a text field indeed. When I start thinking about changing it (so I could support iCal for example) it already had a couple of thousands installs. That’s why I did not change it.. yet. But I do agree, this can be better.

    First, why use Gutenberg as the editor for this post type?

    Plugin has basic support for the block editor and support for the classic editor, that’s it.

    Right now there’s just this ugly looking metabox…

    The appearance of the meta fields is default WordPress.

    Guido

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Falls short’ is closed to new replies.