Moderator
t-p
(@t-p)
– Please check the error logs on your server for a more specific error message and see why it’s failing. If you need help locating them, ask your hosting provider to help you with that.
– If you cannot find error logs or if you don’t find any helpful info in the error logs, try Enabling debugging
@t-p:
Thank you very much for your help. With my very primitive and insufficient knowledge I did enable debugging and now I am receiving these error messages:
Strict Standards: Declaration of WC_Product_Booking::get_price() should be compatible with WC_Product::get_price($context = ‘view’) in /home/bookingrt/domains/bookingrometours.com/public_html/wp-content/plugins/woocommerce-bookings/includes/class-wc-product-booking.php on line 1328 Notice: woocommerce_get_page_id is deprecated since version 3.0! Use wc_get_page_id instead. in /home/bookingrt/domains/bookingrometours.com/public_html/wp-includes/functions.php on line 3829 Parse error: syntax error, unexpected ‘>’ in /home/bookingrt/domains/bookingrometours.com/public_html/wp-content/uploads/cache/anchor-themeforest-117anchor/_wplatte/_anchor.header.php-c359800a5b3f941e3696ff02fd8c2afc.php on line 117
Would you please tell me which one of these error messages are critical and causing my main problem?
Thank you
Vahid
Moderator
t-p
(@t-p)
Try deleting “woocommerce-bookings” plugin using FTP/ SFTP , or your web-host’s cPanel or whatever file management application your host provides (no Dashboard access required).
I did as you said, still the page is not loading and I still see this error message:
Parse error: syntax error, unexpected ‘>’ in /home/bookingrt/domains/bookingrometours.com/public_html/wp-content/uploads/cache/anchor-themeforest-117anchor/_wplatte/_anchor.header.php-c359800a5b3f941e3696ff02fd8c2afc.php on line 117
Any idea?
Thanks
Vahid
Moderator
t-p
(@t-p)
Try flushing any caching plugins you might be running, as well as server and/or browser caches. Not just your browser, but any op cache or content network cache as well such as Cloudflare. If your host provider has a “Purge Varnish” option or if you can ask your provider to flush memcache on your server. If you are using SiteLock, manage your caching there.
Finally… it is up and running, thank you so much.
