Backend: 'Categories' and EO textdomain

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Stephen Harris

    (@stephenharris)

    Hi Dirk,

    Is the request to add ‘Event’ before categories or add a text domain?

    As for the former, that they are ‘event’ categories is clear from context, and the aim was to keep the UI clean as possible.

    Regarding the textdomain, the textdomain really should be there – it’s not so that it picks up on WordPress’ translation files (which tend to be more complete then EOs). I shall update that in the next release though.

    Thread Starter dirk@d10n

    (@dirkd10n)

    Hi Stephen,

    with regard to clarity from context you are right. However, in an early dev phase of my project I decided to control a set of content-specific frontend colors by means of WP stock CATEGORIES (… added to <BODY> via the body_class mechanism). In the backend, I let my customer assign these stock CATs – depending on the content – to pages, posts and – events. Hence, in the backend on edit.php I currently get two rows titled ‘Categories’ – the stock CATs and the EO CATs. In the (event-)cat filter dropdown (still on edit.php), however, You use the term ‘Event Categories’, right?

    I could certainly modify the app design and create some custom tax for my purpose. Anyway, this is absolutely minor and the plugin is doing a great job. I was just curious how to tweak the EO CATs term and was surprised to find the above.

    Cheers,
    Dirk

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Backend: 'Categories' and EO textdomain’ is closed to new replies.