• Resolved nustefa

    (@nustefa)


    After updating to latest version I get a fatal error when loading the vikbooking dashboard page.

    I reproduced on a locally hosted website with the same results. The error appears to be originating from wp-content/plugins/vikbooking/admin/helpers/festivities.phpon line?1089.

    All components of the site are up to date. The admin subpages seem to be working correctly.

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author e4jvikwp

    (@e4jvikwp)

    Hi,

    Thanks for reporting this issue. We were informed just 20 minutes after the official release, and the issue was only affecting those who don’t use the Channel Manager plugin.

    The issue was immediately addressed, and so if you are a Pro user, please go through the “upgrade-to-pro” process again to resolve the issue. Alternatively, please edit the PHP file mentioned in the error message and comment that line of code by prepending two forward-slashes like //. That line of code is not needed when you don’t use the Channel Manager, and that’s why our fix now checks if Vik Channel Manager is installed.

    We apologize for the inconvenient, and thanks again for reporting the issue.

    The VikWP Team

    Thread Starter nustefa

    (@nustefa)

    Hello, the quick fix is working properly and I hope that you will issue the official fix for the booking engine soon. Thank you!

    Plugin Author e4jvikwp

    (@e4jvikwp)

    Hi,

    Yes of course, the commit with the fix was done already, but since we did not increase the plugin version, you are not going to see the fix as a new plugin update, because you’re already on the version 1.6.5.

    The issue was literally fixed just a few minutes after the initial commit, and so it is probably not necessary to increase the plugin version. In any case, we will definitely monitor the situation with the rest of our clients.

    It is totally safe for you to keep that line of code commented, because new plugin updates will obviously contain the proper fix.

    Thank you

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Fatal error after update to v1.6.5’ is closed to new replies.