1
0
-1

We have some TM form properties that we inject into some of our 4.3 Composer custom blocks. This makes it much easier to update them.

But we cannot work out how to format text that way. If we use the Composer text editor tags in a TM form property, they show up as static text in the form.

Is there a way to do this?

 

PS:  About to update to 4.4 finally, but doubt that makes a difference?

 

Thanks,

Lin

    CommentAdd your comment...

    1 answer

    1.  
      1
      0
      -1

      Hey Lin, I've never heard of anybody wanting to store styling attributes in TM properties and I must say I'm not sure that I would recommend this approach. If it is easier to change styling in the TM admin console than in the Composer design tool then there is something amiss. Perhaps an example would help relieve my concerns.

      If you don't want to use the Composer style sheets to do your styling, you can apply your own CSS file and add CSS classes to your components. You could potentially look at a solution that retrieves the CSS from outside the form but this would require some JavaScript trickery I think.

      I'd like to understand more on why you want to do this in the first place.

      1. Lin VanOevelen

        An example: we currently have a 'Description' form property in TM that gets inserted into the Landing page.

        We are now considering putting that inside the Composer form s the separate landing page is causing issues with for example the in app FB browser. But we would prefer not to have to republish the form from Composer to TM if links or contact details in that blurb change.

        So I am trying to find a way to continue using the TM Description property to manage this. The Description is usually several paragraphs with some text formatting, like italics and hyperlinks.

        We successfully use a TM property to add text to the receipt block in most of our forms already, but so far it's only been one liners. I want to find out if we can do it if we need to use <p>/[p] tags etc.

      2. Lin VanOevelen

        PS: it may be personal choice but we most definitely prefer to do our styling in straight html compared to using the composer text editor/template language.

      3. Ben Warner

        Hey Lin, your example of including rich text in a form makes sense. I've not done this before.

      CommentAdd your comment...