|
Armando Gelardi
|
July 14, 2012 at 10:42 am
Hi,
I am having some trouble with the ticket link which is in the confirmation email sent after registering.
On the PC everything works fine. But on the iPad when I click on the “Download/Print Ticket (Name Lastname)” link the browser misinterpret the link.
On the pc the correct link is:
http://my-domain/?ticket_launch=true&id=89&r_id=1-500161c2e932b&html=true
but on the iPad the link (viewing the same email as on the pc) the link becomes:
http://my-domain/?ticket_launch=true&id%EF%BF%BD&r_id=1-500161c2e932b&html=true
As you can see the id=89 is replaced with id%EF%BF%BD
I did some more testing (also on my dev. install) and it seems this error occurs only when the confirmation mail sent to the attendee contains the [ticket_link] shortcode.
case 1: confirmation (attendee) email without ticket link
Dear [lname], thank you for your registration.
confirmation email received by attendee doesn’t contain any link so I can’t verify.
registration email received by system admin does contain the ticket link and this link is working both on pc and on iPad.
case 2: confirmation (attendee) email with ticket link
Dear [lname], thank you for your registration.[ticket_link]
confirmation email received by attendee contains the ticket link and this link is NOT working on iPad.
registration email received by system admin does contain the ticket link and this link is also NOT working on iPad.
For this test I used the custom confirmation email edit box on the Event edit page.
So the only change I made between case 1 and case 2 is adding the [ticket_link] shortcode to the confirmation email…
Any suggestions why this is happening and how to solve this?
Thanks in advance for any help.
some extra info:
The replacement is different on the two servers (both on hostgator but different accounts,same WP version 3.4.1, same EE version 3.1.24.2.P and same EE_Ticketing v2.0.6-beta) but remains the same for different events. On one server it replaces ID=## with id%EF%BF%BD on the other with idF)
|
|
Josh
|
July 16, 2012 at 9:10 am
This sounds to me like a possible conflict with another plugin. I tested this on our sandbox site and opened the confirmation email in a iPad and the ticket opened up with no problems. Try deactivating some of the plugins you have installed and running a test.
|
|
Armando Gelardi
|
July 17, 2012 at 3:45 am
Hello Josh,
I disabled all plugins except for:
EE_3.1.24.3.P
EE_Ticketing_2.0.6-beta
and I tested again…unfortunately have the same error with ticket link on iPad.
I’ll do some more testing with a clean install of WP and EE.
|
|
Josh
|
July 17, 2012 at 11:33 am
I might be worth taking a look at the .htaccess file for rewrite rules that may be set up.
|
|
Armando Gelardi
|
July 17, 2012 at 2:18 pm
I managed to receive a working link in the confirmation email on my iPad:
On my DEV server I disabled all plugins again. I also disabled all EE plugins. Then I deleted these tables:
wp_events_answer
wp_events_attendee
wp_events_attendee_checkin
wp_events_attendee_cost
wp_events_attendee_meta
wp_events_member_rel
.
Then I re-enabled only these plugins:
EE_3.1.24.3.P
EE_Ticketing_2.0.6-beta
In the event setup I selected a trial email (that didn’t work before) and made some (front-end) registrations.
Now, when I open the email on the iPad the ticket link is working!!
.
So I suppose something has gone corrupt on my database and doing this “reset” operation the ticket link in the iPad is working correctly.
I’ll do some more testing to try to understand this behavior.
|
|
Josh
|
July 18, 2012 at 7:16 am
Did you compare the .htaccess files between the dev and live servers?
|
|
Armando Gelardi
|
July 20, 2012 at 9:54 am
Josh, I verified the .htaccess files on both servers.
The both contain the standard settings wordpress writes in it.
\#BEGIN WordPress
RewriteEngine On
RewriteBase /
RewriteRule ^index.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
\#END WordPress
.
I’ve added the “\” escape char just for the styling here on the forum, otherwise # would have given a h2 tag to the text following.
.
so nothing strange there!
I’ll keep on digging…
|
