Print at Home Issues on iPad, iPhone?

We have also had this issue. We've also had the same symptom occur when patrons used Preview, rather than Adobe Reader, on a Mac. That particular issue seems to be better in 10.7 (or at least, I can't replicate it anymore).

We were never able to find a fix on the iOS side, though. Interestingly, even if you open the PAHT in Adobe Reader for iOS, it still doesn't display properly. If we have more of these issues, our next step is to start playing with the font selections themselves, though we're not using anything other than standard fonts in our template.

Has anyone tried this in v11 yet?

We have also had this issue. We've also had the same symptom occur when patrons used Preview, rather than Adobe Reader, on a Mac. That particular issue seems to be better in 10.7 (or at least, I can't replicate it anymore).

We were never able to find a fix on the iOS side, though. Interestingly, even if you open the PAHT in Adobe Reader for iOS, it still doesn't display properly. If we have more of these issues, our next step is to start playing with the font selections themselves, though we're not using anything other than standard fonts in our template.

Has anyone tried this in v11 yet?

Hi Christian -

We newly launched PAHT and are on v11 and I've had one piece of feedback that the ticket data is blank on an ipad. We're looking into it and I'll let you know we find anything!

- Heather

Folks having issues with iPad PDF rendering - check your PAH config file (ETicketServerServiceLive.exe.config)

Make sure that the USE_LABEL setting in the appSettings node is set to true:

 <appSettings>
       <add key="WEBSERVICE_URL_SECURE" value="your api" />
       <add key="WEBSERVICE_URL" value="your api" />
       <add key="USE_LABEL" value="true" />
</appSettings>

Check the documentation for PAH because you'll also need to make sure the <FontSettings> are set appropriately - it can be a little bit of a hassle because you'll need to manually create a FontSetting key for every ticket design element you have on the PAH.

Apparently there is some sort of issue with iPads and the embedded font delivered from the PDF. If you use this feature of the PAH service, the PDF renders just fine on the iPad PDF viewer and in iBooks.

Good luck! 

Edit: I should qualify this as working for v10 - not tried it with v11 yet.

Unknown said:

Make sure that the USE_LABEL setting in the appSettings node is set to true:

Thanks for this. We did a little testing of this (under v10) and can confirm that our previously mostly-blank-on-iOS PAH ticket PDFs look much better on my iPhone (and would on an iPad, too, I assume) with USE_LABEL enabled.

We've turned it off again for the moment, since we'd have to set up approximately one zillion FontSettings keys for our various PAH ticket design PDFs, but on the bright side, all of that can be done ahead of time with USE_LABEL set to False, until we're ready.

Hi everyone,

I just stumbled on this thread as we're having the same issue in Version 11 and trying to find a solution. We tried the fix Nathan suggested but it didn't work - does anyone have any other pointers? 

Cheers,

Meg

Unknown said:

 

I just stumbled on this thread as we're having the same issue in Version 11 and trying to find a solution. We tried the fix Nathan suggested but it didn't work - does anyone have any other pointers? 

 

We did eventually set USE_LABEL to True as per the above. It was fiddly to set up, since you need code in your config file for every element of every PDF template you use, e.g.

<!-- pdf 2301 -->

<!-- 9233 Perf. Date -->

<add key="2301_9233_FontFamily" value ="Helvetica" />

<add key="2301_9233_FontSize" value ="16" />

<!-- 9234 Perf. Description -->

etc. etc.

It was worth all the fuss of setting up, though, since getting this set up, complaints from iOS-using patrons re: PAH PDFs have vanished.

Thanks Chris,

I'll pass that on to our Tess Admin and hopefully our iOS complaints will disappear too!