Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 Apple Passbook | Event Espresso - Staging Server
I am in the process of developing Apple Passbook integration with Event Espresso. I could need some beta testers though before releasing it in the public.
Features right now:
– Full layout possibility (Event Ticket) with Strip of Background layout (see: http://developer.apple.com/library/ios/documentation/userexperience/conceptual/PassKit_PG/Chapters/Creating.html#//apple_ref/doc/uid/TP40012195-CH4-SW45)
– Header- Primairy- Secundairy- and Auxilairy field editing.
– Backfields
– Location relevance + date relevance (auto display on lockscreen)
I’m just starting to look into creating a passbook to facilitate all iOS users who purchase a ticket. What’s the best way going about getting one done?
My plugin creates a Passbook ticket for iOS with the same QR code off course than the actual ticket. You can customize the complete Passbook ticket to your needs (visual). You still need to create the certificates to generate these tickets on the developer site of Apple to let your users add such a ticket to their device.
If you have these certificates you can upload them in my plugin which does the magic for you.
Drop me an e-mail if you want to see an example (pascal@dreissen.nl)
Viewing 3 reply threads
The support post ‘Apple Passbook’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.