Support

Home Forums Event Espresso Premium Ticket order in EE4 Editor resets after Publishing

Ticket order in EE4 Editor resets after Publishing

Posted: January 13, 2015 at 3:50 am


John Ballment

January 13, 2015 at 3:50 am

Hi,

I need the tickets in my event to be in a specific order therefore I use the drap and drop icon to change the order and publish the event. The event publishes in the right order however the next time I come to edit the event it resets the ticket order.

Please find video showing the sort order (adult then child tickets) and after publishing it reorders but on the registration page they have the original (saved) order. The video is at https://www.dropbox.com/s/vd7s06wscvcogk1/ee4-ticket-reorder.mov?dl=0

I’m using EE4 4.4.8.p and PHP 5.5.16. I have EE4 Calendar, Mailchimp and Social Sharing plugins install and are currently all up-to-date.

Thanks

John.


Tony

  • Support Staff

January 13, 2015 at 9:01 am

Hi John,

I’ve been running through setting up some events with multiple tickets and then re-ordering these, this works without the issue posted in the video on those events so need to try and narrow this down a little.

Can you tell me how these tickets were created. As in did you create a single ticket then duplicate that same ticket multiple times or did you continually create a ‘new’ ticket for each one?

If you open up chrome dev tool and go to console, then load the event editor, do you see any Javascript errors?


John Ballment

January 13, 2015 at 6:55 pm

Hi Tony,

Yes most of the entries have been made using the duplicate feature and they do seem to be being grouped with their original ticket.

The JavaScript console shows the following but these all seem trivial to me:

7 Consider using ‘dppx’ units, as in CSS ‘dpi’ means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual ‘dpi’ of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi)
Consider using ‘dppx’ units, as in CSS ‘dpi’ means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual ‘dpi’ of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi)
2admin.php?page=espresso_events&action=edit&post=397&edit_nonce=2e7f1316c9:1 Consider using ‘dppx’ units, as in CSS ‘dpi’ means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual ‘dpi’ of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi)
tinymce.min.js?ver=4107-20141130:9 Consider using ‘dppx’ units, as in CSS ‘dpi’ means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual ‘dpi’ of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi)
Navigated to http://sydney.anglo-indian-reunion.com/wp-admin/admin.php?page=espresso_events&message=1&action=edit&post=397&edit_nonce=2e7f1316c9&return=editpost
7 Consider using ‘dppx’ units, as in CSS ‘dpi’ means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual ‘dpi’ of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi)
Consider using ‘dppx’ units, as in CSS ‘dpi’ means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual ‘dpi’ of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi)
2tinymce.min.js?ver=4107-20141130:9 Consider using ‘dppx’ units, as in CSS ‘dpi’ means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual ‘dpi’ of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi)
tinymce.min.js?ver=4107-20141130:9 Consider using ‘dppx’ units, as in CSS ‘dpi’ means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual ‘dpi’ of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi)
Navigated to http://sydney.anglo-indian-reunion.com/wp-admin/admin.php?page=espresso_events&message=1&action=edit&post=397&edit_nonce=2e7f1316c9&return=editpost
7 Consider using ‘dppx’ units, as in CSS ‘dpi’ means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual ‘dpi’ of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi)
Consider using ‘dppx’ units, as in CSS ‘dpi’ means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual ‘dpi’ of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi)
2tinymce.min.js?ver=4107-20141130:9 Consider using ‘dppx’ units, as in CSS ‘dpi’ means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual ‘dpi’ of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi)
tinymce.min.js?ver=4107-20141130:9 Consider using ‘dppx’ units, as in CSS ‘dpi’ means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual ‘dpi’ of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi)

Regards

John.


Dean

January 14, 2015 at 4:12 am

Hi,

Yeah those console notifications do not seem relevant.

I’ve also run some tests on multiple tickets (over 30) and not run into the issue either.

Can you try disabling all plugins except EE and try again please?


John Ballment

January 15, 2015 at 4:21 am

Hi Dean,

I’ve disabled the other EE plug-ins but the problem persists.

Regards

John.


Dean

January 15, 2015 at 5:07 am

Is it possible to get your login details in order to look into this?

If so, please send them via https://eventespresso.com/send-login-details/

NOTE: login details need to be Admin level and FTP details are appreciated.


John Ballment

January 15, 2015 at 2:38 pm

Hi Dean,

Do you have an RSA public key that I can put on the server for FTP access? As this is a hosted instance the login gets you into the shell, cpanel and our billing account. And being a hosted instance I don’t have root access to create new users.

I’ll send through some credentials for our wordpress instance shortly.

Regards

John.


Dean

January 16, 2015 at 3:27 am

Hi John,

Don’t overly worry about FTP access at the moment. If I need it I’ll get back to you about it.


Roel

January 27, 2015 at 7:03 am

I had the same problem using google Chrome. Using Safari did rearrange the tickets.


Dean

February 2, 2015 at 6:45 am

Hi,

Firstly I am really sorry in the delay in getting back to you, this thread somehow got misplaced.

I took a look (in Chrome) and could replicate your issue on your site, but all my local testing has so far failed to replicate it.

Roel’s idea of using Safari also made no difference for me.

As such I think it would be wise to troubleshoot the site by disabling all addons except EE.

If the issue persists, please advise.

If the issue goes away, please re-activate each plugin one by one, testing the ticket order each time.


John Ballment

February 5, 2015 at 6:43 pm

Hi Dean,

I disable all plug-ins except for EE (which I recently upgraded to 4.5.4) and it’s still doing the same thing.

Regards

John.


Dean

February 6, 2015 at 3:40 am

Hi John,

Thanks for checking that. After discussing the matter with a colleague, we think this might be tied to the date times. We have opened up a developer ticket to look into it in more detail. I’ll ask for this thread to be updated when we know more.


John Ballment

February 6, 2015 at 3:53 am

Thanks Dean, let me know if there is anything I can do to help.

Regards

John.


Dean

February 6, 2015 at 5:32 am

Will do, but I think it’s either a bug or a user experience issue (i.e. an intended feature that is not working out as planned). We will have to wait and see what the developers say.


Conmy Center

February 13, 2015 at 12:29 pm

Seems to be affected by the order of the Event Datetimes. Moving these completely re-arranged my ticket order.


Tony

  • Support Staff

February 13, 2015 at 12:47 pm

Hi,

We are investigating this, can you tell me if all of the events tickets are assigned to all of events datetimes or are some tickets assigned to specific datetimes?


Conmy Center

February 13, 2015 at 2:14 pm

They are assigned to specific date times. There are 13 ticket types that are assigned to 1 or more the 3 datetimes. – See it here; http://www.clearwatercommunitysailing.org/events/summer-camp/


Josh

  • Support Staff

February 16, 2015 at 9:54 am

Hi everyone,

We’re currently testing a fix for this issue. If testing goes well, the fix will be included in Event Espresso 4.6.7.p.


Josh

  • Support Staff

February 16, 2015 at 7:44 pm

Hi everyone,

The fix was included in Event Espresso 4.6.7.p, which is available to download now.


John Ballment

February 16, 2015 at 10:18 pm

Thanks Josh, this version has fixed my problem.


Tony

  • Support Staff

February 17, 2015 at 2:09 am

Thank you for letting us know John,

I’m glad the update fixed this.

The support post ‘Ticket order in EE4 Editor resets after Publishing’ 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.

Event Espresso