Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #1140367

    It would so helpful to be able to apply a name to each catalog element, especially for restaurants who may have different versions of certain menus. This would make it easier when you have a multi-column layout and you want to figure out (from the page builder view) which column has which content. You could name this catalog “burgers to blt” for example. Is there a way to do this…other than burying such catalog elements inside of templates? Any advice is very much welcome and appreciated! Thanks K-team!

    #1140426

    Hey milkrow,

    Thank you for your suggestion, at the moment we do not have such a feature.

    As a workaround, you can add a text element on top of every catalogue element and hide the text element easily from the screen options.

    Best regards,
    Vinay

    #1141104

    I’m not so sure that is a viable workaround. That means the text element has to follow the catalog element around and requires twice the editing should the contents of the catalog change. It would be much more efficient and user friendly if you had a way to simply add a slug or descriptor to the catalog element. Would it be possible to submit this as a feature request?

    #1141569

    Hi milkrow,

    I will forward this as a feature request. Thank you for your input :)

    Best regards,
    Victoria

    #1141582

    Hi Victoria,
    Thank you. For anyone reading this pondering the same issue. If you make such a text element as a “label” that is hidden, you can drop it (and whatever content you’re labelling) into a column, then save that whole column as a template. Then you can drop that template on to other pages, or duplicate it and have different versions…if that suits your needs. If you’re passing off the editing to a client, it may be more helpful than not to include the label (hidden text element).

    What I have been doing is maintaining a non-published page of “originals” where I can edit, then resave the template (using same name). However, I believe once a template is changed, it doesn’t populate to the previous instances of that template. Correct?

    I believe if you commit such a template to a page, then include that page content via the Page Content element, you also would thereby have a way to maintain the original and have edits populate to each instance of that page content.

    Victoria may be able to confirm/refute that idea.

    #1141840

    Hi!

    In version 4.6.3 in “Developer” tab you will find option “Short description for backend” – this extends the displayed element name.Was added to many elements.

    Templates are static – when added to a page they are not updated when the source changes.

    Cheers!
    Günter

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.