|
Listen Up
|
April 22, 2016 at 2:27 pm
Hi — I’ve searched the forums and attempted most of the fixes, but still cannot get the EE4 table view plugin or the ticket selector to look good on mobile. I’m using the latest version of WP and the latest version of EE4 (and the table view plugin). Magic Liquidizer plugin works the best as far as making the tables viewable on mobile… but totally screws up the ticket selector to where it’s just not functional. I read in one of your responses that it’s possible to dequeue the Magic Liquidizer script on the event page… but don’t have the faintest idea of how to actually do that.
Can you guys help? It’s imperative that our table view is mobile friendly and the entire registration process.
|
|
Lorenzo Orlando Caum
|
April 26, 2016 at 4:27 am
Hello,
There is a template option for the Events Table View plugin that will let you show less content:
[ESPRESSO_EVENTS_TABLE_TEMPLATE template_file=’espresso-events-table-template-toggle.template.php’]
The single event pages which includes the ticket (pricing option) selector along with registration checkout should be already mobile friendly across multiple devices (e.g. tablet, mobile phone, computer). Could you share a link to any event page?
—
Lorenzo
|
|
Listen Up
|
April 27, 2016 at 10:05 am
I have everything showing in the table view that I want; that’s not the issue. The issue is that it’s not mobile friendly at all.
The issue with content is in the ticket selector. I have all of the information that I don’t want turned off, but the ticket selector itself is not responsive. Magic Liquidizer makes it responsive, but not functional (you can’t choose a quantity… along with other weird issues). When we turn off Magic Liquidizer, the table shows the correct info., but is not responsive.
Here’s a link: http://listenupws.com/events/listen-up-san-francisco/
Thanks!
|
|
Lorenzo Orlando Caum
|
April 27, 2016 at 10:26 am
Hi,
On the Events table view template, you can switch it to the other view which is more mobile friendly. There isn’t enough space to show all of that information in the default view on a small screen.
I’m not familiar with the Magic Liquidizer plugin but the ticket selector should already be mobile responsive along with registration checkout.
Could you turn off that plugin so we can take a look at your page?
Thanks
—
Lorenzo
|
|
Listen Up
|
April 28, 2016 at 5:58 pm
The plugin is turned off. 🙂
|
|
Listen Up
|
April 28, 2016 at 6:00 pm
When I try [ESPRESSO_EVENTS_TABLE_TEMPLATE template_file=’espresso-events-table-template-toggle.template.php’] for the events table, it disappears.
|
|
Lorenzo Orlando Caum
|
April 28, 2016 at 6:30 pm
Hello, could you try this updated custom CSS which will override some the styling from your theme?
https://gist.github.com/anonymous/594188225f555c46cd30ee3db5982f20
There may need to be a couple more minor adjustments but that was a improvement when using an iPhone emulator to view the page.
—
Lorenzo
|
|
Listen Up
|
May 1, 2016 at 5:38 pm
So, that definitely improves the appearance of the ticket selector and table view add-on, but the code slows down the page loading time on those pages to the point where they are useless… and, clicking the Register button on the table view add-on results in a “Cannot parse this response” message. These problems clear up when the custom css is deleted.
|
|
Lorenzo Orlando Caum
|
May 2, 2016 at 7:48 am
Hello,
There was some custom CSS that was already added to the site to make some changes. Those additions that I shared are just a few lines that override Avada so the ticket selector is more mobile friendly (and also continue working with the custom CSS that was there before).
I was not familiar with the “cannot parse response” error so I ran some searches and found this result on the Apple support forums:
https://discussions.apple.com/thread/7052331?start=0&tstart=0
Is this happening on multiple iOS devices?
What happens if you temporarily deactivate all plugins and reactivate Event Espresso 4 and the Events Table View Template add-on?
Do you still see the slow performance and/or the parse response?
—
Lorenzo
|
