• The strength of this plugin is its completeness at back-end level (ie data). There are many options, some other plugin don’t have. It does support really well Polylang. And this is a real plus. Unfortunately, the front-end configuration (ie layout on the screen) is not easy at all. Organizing how should appear events, list of events, the order of elements, … is pretty tricky has it requires to dig into the hooks file of the plugin. Other plugin do really better at this level.

Viewing 3 replies - 1 through 3 (of 3 total)
  • At this point in time, this is an accurate review providing too high a rating.

    Plugin Author dFactory

    (@dfactory)

    Thanks for the review guys.

    THe frontend part Is made in a similar way to WooCommerce any many other complex plugins (even though we agree it’s not perfect).

    So we’d love to hear more about the the possible improvements and how you see the frontend templating organized.

    We have an idea of template parts enabled/disabled in plugin settings, but would be great to hear your ideas too.

    Thx,
    Bartosz Arendt
    dfactory team

    • This reply was modified 7 years, 5 months ago by dFactory.
    Thread Starter lwvr123

    (@lvr123)

    The best would be, by page-type, a text field where you could describe how this page should be laid-out, with some basic html and tags for each type of data.
    Example:
    Events list, single event:

    <h3>EVENT_TITLE</h3>
    EVENT_DATE
    EVENT_SHORT_TEXT
    EVENT_ORGANIZER
    EVENT_LOCATION

    Event detail:

    <h1>EVENT_TITLE</h1>
    EVENT_DATE
    EVENT_FULL_TEXT
    EVENT_ORGANIZER
    EVENT_LOCATION

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Strong data at data level and Polylang support’ is closed to new replies.