Activity
Newest
Oldest
Kayleigh Bates
Merged in a post:
Bring Back Boilerplate
Julian Bosdari
I have never understood why the ability to pre-populate a text field in a template with editable "boilerplate" text was removed. For example, where we list attributes in a description field such as Size:, Colour:, Scent: etc then every time a writer has to do this they either need to copy and paste from somewhere else or type out the list of attribute headings again. And again...
Adam Hawes
I miss it too. It could be a toggle (just like plain text) to enable it in a field. Would be super useful.
Deanna Adams
I also used this feature a lot and miss it now it is gone. I contacted GatherContent about it and was told that it was removed because it confused a lot of people :) . Voting in support of this!
Kayleigh Bates
Thomas Hallett
I think this was a feature of the old version and was really useful. Some fields in the content we're creating at the moment have identical copy except for a couple of figures. Currently I'm having to copy and paste the default text into a field but it would be much easier if the default text could be included in the template then edited as needed when creating the content.
Robin Maylone
Hi Victoria,
Thanks for the update. Correct me if I’m wrong, but I’m not sure if these are the same things. The new thread discusses putting instructions in a text field. I was actually talking about putting copy in the field from the “Edit template” or “Create template” screen. For example, sometimes we have a CTA that appears on every page of the website. Without this feature, we need to re-key or copy and past the same CTA on every page. Previously, we were able to include this text on the “Edit template” screen and it would appear on every page that followed the same template. Make sense?
Victoria Bresman
Merged in a post:
Creating Tables in Templates
Viji Valency
While creating templates, it would be great if the work area or the content field space would be editable and we can add a table there in that field. The reason this would be better is that while creating templates, there is sometime a need to make a table in the field space which is constantly used in that field and when it is placed in the template there would be no repetitive work of adding tables repeatedly to each item.
Kayleigh Bates
Thanks for sharing your thoughts 👍
The 'default text' area of a field now shows grey lines, when viewed on a template.
We made this change due to how default text worked. It worked well when you first added it, but updating it was another matter!
Instead, you can use the instructions text underneath a field to house your 'default text'. A field's instructions are now always present when editing content. That means that you can easily copy and paste the text shown into the field above.
Here's a help article that shows how to use a field's instructions:
I hope that helps 😊
Julian Bosdari
Kayleigh Bates: Can you explain how to do this with HTML? So for example I want a standard heading (Washing Instructions, Assembly Instructions or some such and I want it as an H2. Right now <h2>Washing Instructions</h2> when cut and pasted from the instructions field comes across as text in italics.
Julian Bosdari
Anyone there? This is such an abominable attempt at a work-round for something that is so basic that it makes the Gathercontent sufficiently unwieldy for us to be evaluating alternatives.
Victoria Bresman
Merged in a post:
Ability to edit template instructions field from within ticket
Mal Flynn
With this most recent update, the template instructions are no longer able to be edited from within the ticket. I would like to be able to set up a number of default instructions per field, then delete instructions from within the ticket to leave instructions specific to that ticket's task.
Davide Bellone
We really need this
Load More
→