Issues When Increasing the Responsive Breakpoint via Filter

[Sean]

Hi,

I’m using the tribe_get_mobile_breakpoint filter to increase the calendar’s default breakpoint to 960px (max-width of 959px for the small screen/mobile layout). While Month View looks good for the individual days (the days now display the “bullet point” on the dates that have events, up until the screen is 959px wide), there seem to be two issues:

1) The headers (Sunday, Monday, etc) are staying as the abbreviations (Sun, Mon, etc) only until the default breakpoint of 768px.

2) Clicking on a date that has events (a bullet point) in the mobile layout only works up until the default breakpoint. From that point up to the new breakpoint (959px), clicking on a day with events (those will a bullet point) does nothing; no events are shown below the calendar.

Essentially, the above two items both seem to still be respecting the default breakpoint, rather than the custom breakpoint that is being set via the filter. As noted in the supporting fields here, this has been confirmed on a clean install. Feel free to visit the url supplied to see what I mean.

Is this a known issue? Does the tribe_get_mobile_breakpoint filter only work when changing the breakpoint to something less than the default of 768px? Or is this a bug in that these two items are not responding correctly to the filter?

Thank you,
Karly

[George]

Hey Karly,

Thanks for reaching out.

The headers remaining as abbreviations is a default design choice of our plugin, and unfortunately can only be changed at this point with custom coding.

In regards to your second question, yes, this is a known bug and we are hoping to fix it in the next few releases. I’m sorry that I don’t have a specific ETA for the arrival of this fix! But: yes, it’s a bug. We have to fix the plugin JavaScript to make sure these features work as expected.

I hope this information helps!
George

[Sean]

Hi George,

Thanks for the quick reply! Good to know that the second issue is indeed a bug and will be fixed in an upcoming release.

Just to confirm on the abbreviations: right now, the day of week headers are not remaining as abbreviations up to the revised breakpoint. The full header (e.g. Wednesday) is being displayed above 768px (when I’ve set tribe_events_mobile_breakpoint to be 960). That is supposed to be happening? I just want to confirm, as when reading your original reply I read it to mean that the headers should remain as abbreviations up until whatever the breakpoint is (which again, is unfortunately not happening).

[George]

Hey Karly,

Sorry about not being clear on this – what you describe is actually part of the same bug in number 2, where the breakpoint’s changes are not being reflected by the JavaScript of the plugin. The JavaScript is what powers both the mobile day view, and the text-switching between “Full” day names and abbreviations.

So yes, the abbreviations change should be reflecting the mobile breakpoint too. It’s part of the same bug, unfortunately 🙁

I’m sorry about this bug, Karly, we have a ticket for it and are hoping to fix this in as soon a release as possible!

— George

[Sean]

Hi George,

Okay great thank you very much for clarifying. I’m actually glad to hear it is in fact part of the same issue as opposed to another scenario 🙂 If you can set this forum topic to be notified when a fix is released, it would be greatly appreciated.

Thanks again and looking forward to the upcoming releases!

Best,
Karly

[George]

Hey Karly,

Thank you for your patience and understanding with the bugs; real sorry about their existence to begin with.

I unfortunately cannot set a thread to be notified when a fix is released, but we do publish the changelog for each release in two locations:

• Inside the plugin itself, which is readable when an update arrives in your wp-admin directly.
• On http://theeventscalendar.com/blog, in the “release notes” for a given update.

These sources are updated and you can even subscribe to the blog with RSS or something if you’d like.

If this fix comes soon enough, then I can just update this thread directly 🙂

But if the fix doesn’t come before this thread is auto-closed by our Support Droid bot, then the above two sources are the best places to keep tabs on updates.

I have also elevated the ‘priority’ of these bugs, so hopefully this will help us get developer attention on them sooner.

Thank you for your patience! Please let me know if I can help with anything else.

– George

[Support Droid]

This topic has not been active for quite some time and will now be closed.

If you still need assistance please simply open a new topic (linking to this one if necessary)
and one of the team will be only too happy to help.

[Author]

Posts