Bugs concerning 3.5

Home Forums Calendar Products Events Calendar PRO Bugs concerning 3.5

Viewing 15 posts - 1 through 15 (of 16 total)
  • Author
    Posts
  • #124069
    Lars
    Participant

    Hi, we found a number of bugs in 3.5:

    1. Updating to 3.5 failed: https://www.dropbox.com/s/l60pd290nx0j8vc/Screenshot%202014-03-28%2010.23.46.png

    2. Not possible to change “Default view”. The dropdown automatically selects the first ticked view from the “Enable event views” list.

    3. Scrolling down in Week View both time and calendar grid disappears:
    https://www.dropbox.com/s/0kc55uxd9ed1jq5/Screenshot%202014-03-28%2011.20.46.png

    4. What happened to the fact that Week and Month view (in 3.5) should automatically move forward in time and show events created i.e. two month ahead instead of sticking with showing “no available events” for the specific realtime week or month? ECP should show next upcoming events in both Week and Month view – flip forward and show these.

    #124070
    Lars
    Participant

    This reply is private.

    #124218
    Lars
    Participant

    5. Besides the Calendar title columns being way to high and dates not vertical centered: https://www.dropbox.com/s/d9a92ni2h75w7p9/Screenshot%202014-03-28%2016.40.08.png
    the height of the dark grey columns expands when resizing browser window: https://www.dropbox.com/s/kkwnfkvrb5xzaie/Screenshot%202014-03-28%2016.43.36.png and expands even further when upsizing the browser window again.

    6. There’s also a bug in the date link i.e. “/events/2014-10-06/” causing 404 error.

    #124405
    Barry
    Member

    Hi Lars,

    I’m sorry to see you’ve hit so many issues – but thank you for reporting them as it’s certainly useful feedback and we’ll quash what we can as quickly as we can 🙂

    1. Updating to 3.5 failed: https://www.dropbox.com/s/l60pd290nx0j8vc/Screenshot%202014-03-28%2010.23.46.png

    This is entirely possible – but actually is handled by WordPress and its success is contingent on file permissions allowing the update process to run without hindrance. So, regrettably, this one is to a large extent out of our hands and I’m not sure how much we can do here to help on this one.

    The best advice if you hit this is to update manually.

    2. Not possible to change “Default view”. The dropdown automatically selects the first ticked view from the “Enable event views” list.

    I can replicate the same thing: we’ll get this slated for a fix as quickly as we can (do note you should still be able to change the default view – it’s just that the choice doesn’t “stick” within the context of the settings page).

    3. Scrolling down in Week View both time and calendar grid disappears:
    https://www.dropbox.com/s/0kc55uxd9ed1jq5/Screenshot%202014-03-28%2011.20.46.png

    Try scrolling up/down here: http://danishmaritimedays.org/events/week/2014-10-06/
    Password: testklaus

    Hmm, that’s not too good but nor is it something I see locally. Please do open a new thread for this and let us know if it is something that is specific to your theme and we can try to help from there.

    4. What happened to the fact that Week and Month view (in 3.5) should automatically move forward in time and show events created i.e. two month ahead instead of sticking with showing “no available events” for the specific realtime week or month?

    Can you clarify what you mean here – were you told that this would be included in 3.5 in a different thread?

    5. Besides the Calendar title columns being way to high and dates not vertical centered: https://www.dropbox.com/s/d9a92ni2h75w7p9/Screenshot%202014-03-28%2016.40.08.png
    the height of the dark grey columns expands when resizing browser window: https://www.dropbox.com/s/kkwnfkvrb5xzaie/Screenshot%202014-03-28%2016.43.36.png and expands even further when upsizing the browser window again.

    I can certainly replicate the second half of this where resizing the window alters the height of that row: I’ll get this logged and we’ll try to address it as quickly as we can.

    6. There’s also a bug in the date link i.e. “/events/2014-10-06/” causing 404 error.

    That’s definitely annoying and curious it cropped up with the latest release – though again this is one I cannot replicate locally. Please do create a new thread for this and we’ll do our best to help.

    Thanks again for taking the time to report these issues.

     

     

    #124534
    Barry
    Member

    3. Scrolling down in Week View both time and calendar grid disappears:
    https://www.dropbox.com/s/0kc55uxd9ed1jq5/Screenshot%202014-03-28%2011.20.46.png

    Lars: apologies on this one – we can indeed replicate and are going to get a fix in motion as soon as possible. Can you try adjusting your end-of-day-cutoff setting to 1am (or later) and see if that mitigates this problem?

    #124551
    Lars
    Participant

    Hi Barry,

    3. Changing “End of day cutoff” setting to 1am sorted the problem, though it still needs a fix?

    4. Yes, I got a clear impression on that from you here: “these are geared at making week view start at whatever time the earliest event in a given week is” (https://tri.be/support/forums/topic/adjusting-time/). You write “…in a given week” – but problem is that the neither Month or Week View shows the earlist event in a given month/week. It shows the events in the current realtime month/week – so for us using TEC/ECP for our conference events in October (week 41) we cannot make your calender show these events unless using John Godley’s “Redirection” plugin and this major setup: https://www.dropbox.com/s/l2m0ahjxoend7b8/Screenshot%202014-03-29%2000.30.21.png

    6. This occured with the 3.5 update so it must be your end

    #124553
    Lars
    Participant

    This reply is private.

    #124668
    Lars
    Participant

    5. Why has this style=”height: 68px;” been set for all columns in the tribe-grid-header? It’s supposed to look like this: https://www.dropbox.com/s/vq3zf4r8x7u4scv/Screenshot%202014-03-29%2011.57.15.png … in general the CSS is a mess with various differences i.e. between List View and Map View concerning font-size, height between events, etc. Why not trying to look these displays look the same or even just share the same classes?

    #124686
    Cynthia Lockley
    Participant

    5. I also have this question. My calendar view on my home page had larger fonts and overlapped day names after I upgraded to 3.5. As there were other problems with this upgrade, I dropped back to 3.4 for now. It would be very helpful to have just one set of CSS rules for headers so they are consistent. Trying to find where the specific CSS is for particular parts of the calendar is a real headache. If I can find it, I’ll add my mods to my child theme’s style sheet. But sometimes, you can fix it in one place but not in another place. Some hidden CSS elsewhere overrides it.

    #124701
    Lars
    Participant

    @Cynthia: Exactly it is a real headache working with this calendar. This is just some of the huge amount of CSS we had to write up ourselves – just to make the calendar look somewhat nice:
    https://www.dropbox.com/s/ttxhc7azr8y7q5g/Screenshot%202014-03-29%2017.10.28.png

    #124817
    Lars
    Participant

    @Barry: Regarding #6 on my buglist it turns out that unless “Day” is ticked on the “Enable event views” the URL will return 404 error.

    #124828
    Lars
    Participant

    7. This doesn’t work since update 3.5:

    // Runs the <title> element through our custom filter
    // add_filter(‘wp_title’, ‘filter_events_title’);
    // If you are using Yoast delete the above line and uncomment the following one
    add_filter(‘wpseo_title’, ‘filter_events_title’);

    // Tribe events: Manually set title for each page
    function filter_events_title ($title) {

    if ( tribe_is_map() && !is_tax() ) { // Map View Page
    $title = ‘My Title Here’;
    }
    return $title;
    }

    #125107
    Lars
    Participant

    8. “Costs” in Single View Details returns nothing and collapses on top of “Event Category” : https://www.dropbox.com/s/sbiufy1cwpwt4eb/Screenshot%202014-03-31%2014.54.12.png

    #125171
    Lars
    Participant

    8. Sorry, this bug was caused by our own CSS.

    #125570
    Barry
    Member

    I definitely appreciate that since issues have been introduced by the recent update it is tempting to group them together in a single thread – but it actually makes it harder for us to assist. For any subsequent issues, please post new threads and stick to one issue per thread, unless they are very closely linked.

    3. Changing “End of day cutoff” setting to 1am sorted the problem, though it still needs a fix?

    It definitely does need a fix – we’re working on it right now 🙂

    4. Yes, I got a clear impression on that from you here: “these are geared at making week view start at whatever time the earliest event in a given week is” (https://tri.be/support/forums/topic/adjusting-time/). You write “…in a given week” – but problem is that the neither Month or Week View shows the earlist event in a given month/week.

    I’m sorry for the confusion, what I said was admittedly a little ambiguous.

    What I meant was that, when a week is being viewed if the earliest event any day that week is (for example) 9am then the week view grid would initially set itself to 9am as the first row (though you would still be able to scroll up).

    I didn’t mean that month view would automatically jump to August, if that is when the next upcoming event happens to be.

    5. Why has this style=”height: 68px;” been set for all columns in the tribe-grid-header? It’s supposed to look like this: https://www.dropbox.com/s/vq3zf4r8x7u4scv/Screenshot%202014-03-29%2011.57.15.png …

    Again, there is a bug which we are working to resolve. If you see an inline style being set it is generally being handled dynamically rather than as the result of a sylesheet.

    6. This occured with the 3.5 update so it must be your end

    6. (follow up): Check url here: https://www.dropbox.com/s/6t8y2ufc1j2cw2h/Screenshot%202014-03-29%2000.37.38.png

    It may well be on our side, nonetheless I would once again ask that you post a new thread for this issue. Similarly, for your subsequent issues #7-8, please also create new threads if required and one of the team will be happy to assist.

    Likewise, Cynthia, if you need assistance for your specific issue please post a new thread of your own (or if it is a general suggestion/request with regards to how CSS is handled our UserVoice page is also suitable).

    To avoid any confusion I am going to close this thread out – we will continue to progress the bugs we have already acknowledged of course and will be more than happy to help with any other issues in separate threads.

    Thanks!

Viewing 15 posts - 1 through 15 (of 16 total)
  • The topic ‘Bugs concerning 3.5’ is closed to new replies.