• Resolved peter8nss

    (@peter8nss)


    I’m getting 404 errors since upgrade from 6.5.0.1 to 6.51:

    • wp-content/plugins/events-calendar-pro/src/resources/css/tribe-events-pro-theme.css
    • wp-content/plugins/events-calendar-pro/src/resources/css/tribe-events-pro-full-mobile.css
    • wp-content/plugins/events-calendar-pro/src/resources/css/tribe-events-pro-theme-mobile.css

    The problem is still present in release 6.5.1.5.

    I know these are event calendar pro directories (Pro plugin currently at latest release 6.5.0) but I’m part of a “Not for Profit” organisation that has kindly been given the pro license but that doesn’t include using the official support. Hence, raising it here.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support tristan083

    (@tristan083)

    Hi @peter8nss ,

    Thank you for reaching out.

    Our product management team is aware of this issue. Our team is actively working on a fix for this.

    In the meantime, we recommend removing the lines 124-140 from Assets.php until a resolution is available.

    Internal Bug Ticket Reference: TECTRIA-89

    We will keep you updated on the progress of this issue and notify you once a fix is available. Your patience on this matter is highly appreciated.

    We’re seeing the same issue, and have temporarily worked around it with this filter:

    add_filter('tribe_asset_enqueue', function ($enqueue, $asset) {
    if (in_array(
    $asset->get_file(),
    ['', 'tribe-events-pro-theme-mobile.css', 'tribe-events-pro-theme.css', 'tribe-events-pro-full-mobile.css'],
    true
    )) {
    return false;
    }

    return $enqueue;
    }, 10, 2);
    Plugin Support Darian

    (@d0153)

    Hi samedwards

    Thanks for sharing your workaround for this issue.
    As always, when implementing a custom snippet, it’s a good practice to test it first on your staging site before applying it to your live site. This helps to avoid any unnecessary downtime to your live site.

    @peter8nss @samedwards

    If you have other questions or concerns, and for us to follow WordPress Forum Guidelines, please open a Support Ticket on our Help Desk.

    Thread Starter peter8nss

    (@peter8nss)

    That workaround should stop requests for these files – so it should remove the 404 errors, but presumably the files were being requested because they were intended to do something. Would it be better to copy and rename the equivalent files from the non-pro plugin?

    Plugin Support Darian

    (@d0153)

    Hi @peter8nss

    In previous versions of the plugin, those files had already been deleted, and the calendar does not use them anymore. The problem is that it was attempting to access a file that no longer exists, and the workaround from samedwards resolves this issue.

    I hope this helps. If you have other questions or concerns, please open a Support Ticket on our Help Desk.

    Plugin Support Darian

    (@d0153)

    Hi there,

    It appears that we haven’t heard back from you in a while, so I’ll assume that the matter has been resolved. If you need any more help, feel free to start a new thread and we’ll be happy to assist you.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘404 error accessing CSS’ is closed to new replies.