• Resolved sneax1980

    (@sneax1980)


    Today we have noticed the following ERROR message which appears on top of our events calendar page whenever we select category or page through to next month.

    Something went wrong while fetching events.
    The request status is: 200
    The error thrown was: SyntaxError: Unexpected token <

    We have the following software versions installed.

    WordPress Plugin 4.4.1
    Calendar 2.3.7

    PLEASE NOTE
    >> The WordPress update has only just updated today due to a server issue which required a re boot.
    >> The issue has ONLY occurred since the WordPress update.
    >> We have tried de activating all Plugins and this did NOT solve the problem.

    Here is a link to our events page.
    https://www.zabikers.co.za/events/

    Its seems OBVIOUS that there is a CLASH with your current version and the current version of WordPress… ARE YOU AWARE OF THIS??? Can you HELP???

    Kind Regards
    Simon Morton.

    https://www.ads-software.com/plugins/all-in-one-event-calendar/

Viewing 15 replies - 1 through 15 (of 26 total)
  • Similar problem. I now get the following when clicking to the next month. But then if I refresh the page it works fine. Something isn’t quite right.

    “Something went wrong while fetching events.
    The request status is: 200
    The error thrown was: SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data”

    Thoughts anyone? Site is at https://www.leevasey.co.uk/gigs-calendar/

    Many thanks,
    Chris

    Also happening on another site of mine at https://www.deano.org.uk/gigs-calendar/ so clearly there’s an issue with the plugin and WP compatibility in my opinion.

    Thread Starter sneax1980

    (@sneax1980)

    I reported a BUG two days ago and still no reply…

    I have been using Time.ly All-in-One Events Calendar now for while and in the beginning your support was GREAT!!

    This is the first time that I have had to use this new forum…
    I am VERY DISAPPOINTED with the lack of support.

    In your opening READ THIS FIRST section you say:

    1.
    Priorities and response time
    We’re looking over the forum every day, and our priorities are, in the following order: critical bugs requiring hotfixes, major bugs that affect multiple users, troubleshooting issues raised by Core+ and all paid plugin users. Any of these can take up to 7 days (although our users appreciate that we’re mostly responding in 1-2 days), or sometimes even more.

    I am REPORTING A BUG and in the same thread another gentleman is reporting the same on two of hos website since the latest WordPress Update.

    2.
    Inquiries that we cannot commit to address
    We’d love to address every problem raised on the forum, but unfortunately, as Ben is the only support person, although he is extremely dedicated, he cannot provide support to free users (troubleshooting, answering questions, CSS and other code tweaks). If time permits, we would gladly help, but we need to set the expectation that it’s not supported.
    Please check-out our Hub and Pro hosted plans for many extra features and 24 to 48h response time via “Get Help” feature inside the plugin.

    I don’t understand what you are saying here!
    Seems like you are ONLY giving priority to the PRO Hosted plans.

    I am using HUB and I have Add Ons – Venues and Front End submission.
    Does this mean that I fit into the category for NO SUPPORT???

    If this is the case then please advise what I need to do to get professional support as right now you plugin starting to look like a very BAD option for me to keep on using going forward.

    Regards
    Simon.

    Hey guys, thanks for the patience and for reporting this bug, I’m raising it right now to engineering.

    sneax1980, we have the same one very dedicated person on support, Ben, which is some days busier that other days… and probably this was one of those days, thanks for your understanding.

    Indeed, Hosted Hub and Pro customers have a “Get Help” button on the upper right side of their admin dashboard. Raising tickets through that form goes through a different system that is prioritized.
    Do you have a hosted hub plan? Can you please tell me your time.ly account email address, and what’s the plan registered there for you? or send it to us at [email protected]?

    Thread Starter sneax1980

    (@sneax1980)

    Hi There
    Has an engineer looked yet into the issue that i am having?

    I have looked at your website for better support options.
    It seems that there is NO WordPress platform solution which offers anything
    better that this forum.

    I run a professional media site, i really need a support solution with a faster turnaround.. I don’t expect this for free. You can invoice if needs be just HELP please!

    I really like your plugin – but i am probably going to have to look for a alternative as you guys are really dropping the ball when it come to support!!!!

    WHY DON”T YOU OFFER PREMIUM SUPPORT for WordPress?

    Best Regards
    Simon.

    sneax1980, Ben will look at this as soon as he can. Unfortunately we don’t have support over weekend, except for wide outages.

    Can you please respond to my previous question about what subscription you have?

    Hosted hubs have the most prioritized support, but we’re trying to find other options for plugin users as we well, give that there are way more factors even outside the plug-in than can influence its behaviour/performance.

    I am really sorry, but we’re doing the best we can… Thanks for your understanding

    Thread Starter sneax1980

    (@sneax1980)

    Hi

    Thanks for you quick response!

    I did look at the HUB solution but this is not for me as I need a plugin for WordPress.
    If there was a prioritized support for WordPress plugin then I would BUY this!

    Kind Regards
    Simon

    Hi Simon,

    I’m sorry to hear that you have had issues with the plugin and my apologizes for not responding sooner.

    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.
    3. Try turning on/off “Strict compatibility content filtering” in Events -> Settings –> Viewing Events.
    4. Try turning on/off “Use frontend rendering” in Events -> Settings –> Advanced.

    Also, do you use a cache plugin?

    Thanks,
    Ben

    Hi Ben, I take it that your response applies to me too!! I have tried your suggestions 1 – 4 but that does not change things. I use W3 Total Cache.

    As it loads correctly on refresh, it would appear to me to be a cache issue.

    Look forward to a prompt solution. I actually thought that version 2.3.8 was addressing this in view of Changelog info, but clearly not. Incidentally 2.3.8 was meant to improve loading speed by enabling Front-end Rendering by default, but box is not checked by default.

    Thanks, Chris

    Hey rodeboy, enabling Front-end Rendering by default is available for new users only…

    Okay, thanks for the clarification. Can Steve and myself now have a solution to our problem please?

    I use the plugin on several of my sites and they all have the same issue which does not look good for my clients, or on me.

    Can you give this some priority now please?

    Thanks, Chris

    Hi guys,

    We are investigating the issue but I have more questions than answers for now, as it’s difficult to reproduce this bug. It happens just in some relatively rare environments. Perhaps, it’s something related to the server configuration you have. Caching plugins also can play their role in that.

    What actually happens, is that when you click somewhere in Calendar (to change the view, date, etc) – it sends an AJAX request to the server. Instead of JSON data it gets the full HTML page as a response, despite the fact it asks for JS only in it’s HTTP headers. Our plugin tries to parse this response as it could be some JS and throws a “Syntax error”. Though it’s not a syntax error, but rather a content type mismatch.

    Our development team (including myself) are working hard on that and I believe we’ll have some good news quite soon.

    Thanks for your patience!
    Pavel.

    Thank you for the update Pavel. I found the same issue reported here at https://time.ly/forums/topic/syntaxerror-unexpected-token/ and working my way through this I did all of the following;

    1. Go to Events->Calendar Themes and change the calendar theme to Vortex. If it’s already Vortex, change it to a different theme (eg: Plana) then back to Vortex.
    2. Go to Events->Theme Options and hit the “Save Options” button (without changing anything).
    3. Go to Settings->Permalinks (in the WP settings) and hit “Save Changes” (without changing anything).
    4. Within ithemes security plugin uncheck for an option about removing “suspicious query strings”

    At present I can (somewhat nervously!) report that it seems to be okay and not throwing out this error anymore. I don’t know which of these solved the issue, or if indeed it is solved on a long term basis. I provide the feedback as it may help your investigations Pavel.

    I will check my sites tomorrow.

    By the way, I love the plugin … when it is working well! However its temperamental nature with updates (both itself and with wordpress) does test my patience at times!

    Chris

    P.S.

    If you can send us some information related to your server (like .htaccess files, any specific configuration features, plugins you use) – it will help us a lot to speed up resolving this issue.

    And of course, temporarily disabling other plugins can help to find the inter-plugins conflicts, if there are any. Does it work for you if you have other plugins disabled? What theme are you using and have you tried to temporarily switch it to any other?

    If you decide to share any technical details with us, please send it all to [email protected].
    Thanks in advance for your help!

    Pavel.

    Great that it worked for you!

    I guess “suspicious query strings” is exactly how security plugins see every AJAX query =)

Viewing 15 replies - 1 through 15 (of 26 total)
  • The topic ‘Events – SyntaxError’ is closed to new replies.