Justin Hall

Forum Replies Created

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • in reply to: Can't Edit Recurring Series – Browser Crashes #1363014
    Justin Hall
    Participant

    I ended up stumbling upon the answer to my problem. I tried to load the edit page for a recurring event with Developer Tools open. It never timed out and I just let it keep load and after about 10 minutes, it loaded and the event had a ton of exclusions going back 18 months. Apparently, all the exclusions where keeping the page from loading. So, after doing some searching with this knowledge I found the threads below.

    https://theeventscalendar.com/support/forums/topic/event-exclusion-error/

    https://theeventscalendar.com/support/forums/topic/past-recurring-events-listing-as-exclusions/

    The Cleanup Recurring Event Exclusions plugin did the trick.

    in reply to: Can't Edit Recurring Series – Browser Crashes #1361790
    Justin Hall
    Participant

    I changed to PHP 7 several days ago after reading the Performance Considerations article that you recommended.

    When I try to edit an existing recurring event, the page seems to freeze up while it is loading rather than time out. I often get a “Page unresponsive” dialog error.

    When I create a new recurring event with similar recurring settings and exclusions, I can go back and edit it. The edit page usually loads in about 4 or 5 seconds.

    I tried loading the edit page for an existing page with javascript disabled and it loaded. I saved it and it saved without the recurring setting and exclusions since javascript was disabled.

    I enabled javascript and tried to edit the event that I just saved and it loaded fine. I set up the recurring settings and exclusions and saved and now I can go back and edit that event.

    It seems like the events are corrupt and re-saving them would fix the issue but I can’t get them to load without going through the process above. There are a lot of recurring events, all with exclusions so this would be a lot of work. I am hoping to not have to ask the client to do this. Any thoughts?

    Thanks!

    in reply to: Can't Edit Recurring Series – Browser Crashes #1360493
    Justin Hall
    Participant

    Hi Victor,

    Thanks for the resources. I have the Caching month view HTML setting checked and I am using WP Super Cache for page caching.

    I changed the Month view events per day to 5 and that seems to clear things up on the front-end.

    The issue with not being able to edit previously entered recurring event remains. I can edit new recurring events. It seems like these events could be corrupt but the odd thing is that they all load properly on the front end.

    How do I know that they are corrupt? If they are, are there any options for fixing them?

    Thanks,
    Justin

    in reply to: Can't Edit Recurring Series – Browser Crashes #1356731
    Justin Hall
    Participant

    Here are a couple of the events with the issue…
    http://www.ymcashoals.org/event/muscle-works-leslieashley-2/2017-12-30/
    http://www.ymcashoals.org/event/all-6-lanes-available-4/2017-12-30/

    I was made aware of the issue a few days after the WordPress 4.8.2 update. None of the plugins or themes had been updated.

    It appears this is continually getting logged to console as the edit event page loads…

    load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,plupload&ver=4.8.2:3 [Violation] Added non-passive event listener to a scroll-blocking ‘touchmove’ event. Consider marking event handler as ‘passive’ to make the page more responsive.

    On the front-end, the calendar doesn’t always load completely. It may load through the 19th. Then you can refresh and it may load through the 21st. Then you can reload and the whole month may load.

    in reply to: Can't Edit Recurring Series – Browser Crashes #1355763
    Justin Hall
    Participant

    Victor,

    It happens when trying to edit any existing recurring event.

    I created a new recurring event, saved it and was able to go back and edit it.

    I enabled WP_DEBUG and WP_DEBUG_LOG and reproduced the issue a few times but it didn’t produce a log file.

    Thanks,
    Justin

Viewing 5 posts - 1 through 5 (of 5 total)