Something went wrong while fetching events. ERROR

  • Resolved Emily G

    (@genevish-graphics)


    8 years, 4 months ago

    Something went wrong while fetching events.
    The request status is: 200
    The error thrown was: SyntaxError: JSON Parse error: Unexpected EOF
    Click here for technical details

    I have tried EVERYTHING in the book to fix this. I still have the issue. I have deactivated, installed and reinstalled (losing all my events mind you) and deactivated all plugins and switched themes, and no change. I also tried toggling the setting Strict compatibility content filtering (no change) as well as “Use frontend rendering” (no change, error still persists). The error shows specifically when you are trying to go from month to month in agenda view. Google searches of the issue have gleaned no other troubleshooting steps so I am posting here. Please help!

    • This topic was modified 8 years, 4 months ago by Emily G.

    The page I need help with: [log in to see the link]

Viewing 11 replies - 1 through 11 (of 11 total)
  • Benjamin

    (@bsokic)

    8 years, 4 months ago

    Hi @genevish-graphics,

    Have you tried these two steps?
    1. Make sure that your Calendar page is set to the right page in the settings.
    2. No need to use shortcode on a page set as the default in the plugin settings.

    Thanks,
    Ben

    • This reply was modified 8 years, 4 months ago by Benjamin.
    Thread Starter Emily G

    (@genevish-graphics)

    8 years, 4 months ago

    Hi Ben – Yes, of course. The plugin worked fine for years, and all of a sudden started throwing the error. Any other ideas to try?

    Benjamin

    (@bsokic)

    8 years, 4 months ago

    Do you know which PHP version you are using?

    Thread Starter Emily G

    (@genevish-graphics)

    8 years, 4 months ago

    Looks like 5.6

    Thread Starter Emily G

    (@genevish-graphics)

    8 years, 4 months ago

    OK upgraded php version to 7. Still same error. If we go with the Pro paid version can we get the issues resolved? I think my client will agree to going with the paid version, since they have been using this plugin for years now and really need to continue using it. Thank you!

    Chris – On the Grid Web Design LLC

    (@falcon13)

    8 years, 4 months ago

    Does it still do it when you are logged into the site? Are you using iThemes security plugin or something similar? If the “Filter Suspicious Query Strings in the URL” is on it will send 403 errors to browsers not logged in. I think it’s the “~” that is causing it.

    Thread Starter Emily G

    (@genevish-graphics)

    8 years, 4 months ago

    It does 🙁
    I don’t have any security plugin on right now. I checked the .htaccess file too and there is nothing there that is related to the plugin, since I deleted the old .htaccess and it was regenerated without it since deleting the plugin.

    Benjamin

    (@bsokic)

    8 years, 3 months ago

    Hi @genevish-graphics,

    Sorry for not replying sooner. If you still have this issue, can you please log into your Timely account and open a ticket by clicking on the Get Help link, or click here: https://dashboard.time.ly/account/get-help and we will continue there.

    Thanks,
    Ben

    @academiathemes

    (@academiathemes)

    8 years ago

    Hi,

    I had similar issues on two separate Multisite installations (both on Siteground), so I decided to check what the cause is.

    The same thing was happening in all themes, but it was working just fine on my localhost.

    So then I understood what the problem is: I have the habit of adding the 6G Firewall 2018 rules to all my live .htaccess files, and they restrict access to different links (like URLs that contain the ~ character).

    I removed these rules and bam! problem solved.

    I hope this will help someone in the future.

    UPDATE:
    This is the exact .htaccess line of code that was causing the issue:
    RedirectMatch 403 (?i)(~||<|>|:|;|,|%|\\|\s|\{|\}|\[|\]|\|)`

    Taking out just this line is sufficient to fix this error message:

    Something went wrong while fetching events.
    The request status is: 403
    The error thrown was:
    Click here for technical details

    I described the issue and solution in this post on the blog.

    embroideryallsorts

    (@embroideryallsorts)

    7 years, 9 months ago

    @academiathemes
    Thank you so much this fixed my problem, I was about ready to start looking for a different plugin as I had tried all of the other solutions that I could find.

    Benjamin

    (@bsokic)

    7 years, 9 months ago

    @academiathemes, thanks for sharing your solution, it will certainly help other users with the same issue.

    Best regards,
    Ben

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

The topic ‘Something went wrong while fetching events. ERROR’ is closed to new replies.

Tags