Something went wrong. Please try again and, if the issue persists, please contac

  • Hello, the date picker on the mentioned website periodically fails with the message:

    “Something went wrong. Please try again and, if the issue persists, please contact us.”

    Clearing the cache (WP Fastest Cache) temporarily fixes this, but I can’t figure out what the source of the issue is. It only started a few weeks ago and I don’t see this happen on other websites that are on the same hosting server with the same plugins and the same (caching) settings.

    Do you have any idea what this might be?

    The developer console gives a 403 forbidden error on admin-ajax.php when this happens.

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support tonysupport

    (@tonysupport)

    Hi JP,

    Thanks for contacting us.

    The issue could be related to how the caching plugin is caching the JavaScript files associated with our plugin.

    Does your caching plugin offer an option to whitelist specific pages, plugins, or plugin assets from being cached?

    If so, we recommend whitelisting the page where the date picker is used, or the JavaScript files related to our plugin, to ensure they are not cached.

    I have excluded that page from caching to see how it goes.

    However, I have 9 websites with this booking plugin and all these sites also have that caching plugin with the exact same settings. Only this site has this issue and only since a few weeks.

    The only other difference is that this particular website is the only one that uses the premium version (sorry, didn’t think about that before). We have max reservations and max people specified, but if we get this error we get it for all dates, and clearing the cache fixes it.

    Is there a difference in the free and premium version that could be affected by caching?

    Why would it throw error 403 on /wp-admin/admin-ajax.php and not on /picker.js?

    Any other ideas why this could happen on this specific site and not on the others?

    Hi, just to let you know that the issue seems to be fixed by excluding the reservation page from cache.

    Following questions remains though:

    1. Is there a difference in the free and premium version that could affect caching (the issue doesn’t happen on sites with the free version)?
    2. Why would it throw error 403 on /wp-admin/admin-ajax.php and not on /picker.js?
    3. Any other ideas why this could happen on this specific site and not on the others?

    Thanks
    JP

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.