We just stumbled upon a problem with our PAHT templates, and were wondering if anyone had a solution to it.
The way we have set up our templates is that we start with a "blank", which has our logo at the top and our boilerplate instructions and legalese at the bottom, with a broad gap in the middle for ticket design elements. That blank serves for most or ideally all ticket designs for any given season.
Then for each specific ticket design we use the form editor to fill in the gap with labelled text fields for each relevant ticket design element. So far so good. But the problem is, depending on which elements go with a specific design, and where they are placed, we also need some labels, like "Section:" or "Row/Seat:". We had always done this by adding them as additional text fields using alphanumeric labels so that they wouldn't be confused as design elements, and that worked great. Until it didn't. Now those elements are simply omitted from the output PDF, so our seat numbers, etc. just float in space without explanation.
To be clear, after trying to debug the issue and researching old ticket PDFs we discovered that this hadn't been working properly for over 8 years. I had worked up most of a multi-paragraph rant about how many times I discover that some standard Tessitura process we have hasn't been working properly for the better part of a decade, and employees and customers have simply been unhappily grinding through it, but that's probably not helpful at this juncture. The best I can come up with here is to say that it's extremely demoralizing.
Anyway, is there a way around this that anyone else is using? Is there some other element type thing that we can add in that is ignored (and properly rendered) by TPS?
I can upload our ticket design blank if that helps. I add fields into design elements that I created in the template.
To be clear I pieced this together out of google, forum posts and gaffers tape.
2111.pdf