Home › Forums › Additional Help › Extensions › PDF tickets Extension / problems
- This topic has 29 replies, 4 voices, and was last updated 5 years, 11 months ago by Cliff.
-
AuthorPosts
-
December 15, 2017 at 1:05 pm #1406728CliffMember
Since that .zip was named “tickets_template”, please confirm if that’s the actual name of your folder. Also, please confirm the full file path of where this folder is located on your system.
December 15, 2017 at 10:15 pm #1406981IlkkaParticipantHi,
The correct folder name is tickets. And the file is from the following path:
/wp-content/themes/Avada-Child-Theme/tribe-events/tickets
1. We got the links for the tickets working. So we managed to find the correct details from the database for generating the link.
2. Also the file for the pdf naming we managed to do with our own domain name.
So these are not a problem anymore. Only the styling of the pdf.
Thanks.
ilkka
December 18, 2017 at 2:09 pm #1408247CliffMemberI’m glad you got things sorted.
Because it seems you’re only missing something simple like padding/margin, I’d suggest getting things to work without the use of !important
I’m recommending this until https://github.com/mpdf/mpdf/issues/524 is resolved.
Please let me know how your troubleshooting goes.
December 19, 2017 at 9:47 pm #1409431IlkkaParticipantHi,
Thanks for your reply. Removing all !important does not have any effect on the pdf. The pdf still looks exactly same. Originally i think the important rules came from email.php template. However it does not have any effect. The Emailed ticket is 100% accurate and the pdf conversion is not. No rules are working for the pdf.
Being just curious how are your results turning out from pdf conversion. If you make a pdf ticket from your system is the generated pdf as it should be?
Any other suggestions for this…
ilkka
December 20, 2017 at 8:48 am #1409926CliffMemberCould you send me your new email.php that no longer has !important in it that you tested and is working in email but not in PDF?
December 20, 2017 at 10:14 am #1410067IlkkaParticipantThis reply is private.
December 22, 2017 at 3:35 pm #1411986CliffMemberThis reply is private.
December 23, 2017 at 1:04 am #1412141IlkkaParticipantThis reply is private.
December 27, 2017 at 2:22 pm #1413559CliffMemberI was asking for a copy of one of your actual emails so I could report to the mPDF team. However, I simplified it and reported just from my own testing: https://github.com/mpdf/mpdf/issues/591
You can keep an eye out there if you want.
December 28, 2017 at 11:51 pm #1414333IlkkaParticipantHi,
Okay thanks. I will see it from there. Lets see what are the results.
ilkka
December 30, 2017 at 8:15 pm #1415350CliffMemberSounds good. Thanks for your understanding.
January 1, 2018 at 6:44 pm #1415797CliffMemberCheck out https://github.com/mpdf/mpdf/issues/591#issuecomment-354695239
If you want additional help with mPDF styling, please utilize https://stackoverflow.com/questions/tagged/mpdf
January 23, 2018 at 8:38 am #1433636Support DroidKeymasterHey there! This thread has been pretty quiet for the last three weeks, so we’re going to go ahead and close it to avoid confusion with other topics. If you’re still looking for help with this, please do open a new thread, reference this one and we’d be more than happy to continue the conversation over there.
Thanks so much!
The Events Calendar Support TeamMay 16, 2018 at 3:47 pm #1532273CliffMemberIlkka, we’ve published an update to PDF Tickets at https://theeventscalendar.com/extensions/pdf-tickets/
Version 1.1.0 auto-detects when something is out-of-date, such as if the Event’s details are changed, and auto-deletes these out-of-date PDFs.
See the changelog for the new deletion methods that exist, which you could use in your own customizations. Please open a new ticket if you need additional support on this or another issue regarding PDF Tickets.
Thanks for contributing by sharing your use case!
-
AuthorPosts
- The topic ‘PDF tickets Extension / problems’ is closed to new replies.