aliasguru
Forum Replies Created
-
Forum: Plugins
In reply to: [Book a Place] Slowdown on RefreshNever mind, found it to be in /js/public.js
setInterval(refreshScheme, 5000);
Change the 5000 to whatever value in milliseconds the refresh shall happen in. Again, this would be nice to be able to control from outside (backend). I’ve set it to 60.000, would there be any issues to be expected from that?
Thanks,
aliasguruForum: Plugins
In reply to: [Book a Place] Very slow processing and paypal does’t workHi ArtkanMedia,
Thanks for your reply. In my case, with the help of a programmer today, we found and solved the issue. The problem is that the website I am working on is running on https. There is two lines in your plugin which then fail to load, both in class-book-a-place.php, and the Terminal in Inspection Mode throws errors.
change those two lines:
in public function enqueue_styles():
wp_enqueue_style('qtip', 'https://cdn.jsdelivr.net/qtip2/2.2.0/jquery.qtip.min.css', null, false, false);
and in public function enqueue_scripts():
wp_enqueue_script($this->plugin_slug . '-qtip', 'https://cdn.jsdelivr.net/qtip2/2.2.0/jquery.qtip.min.js', array('jquery'), false, true);
In both occasions, I had to replace the http with https, now the plugin works fine for me. Is there a possibility for you to provide a generalized solution?
Thanks again,
aliasguru- This reply was modified 8 years, 2 months ago by aliasguru.
Forum: Plugins
In reply to: [Book a Place] Very slow processing and paypal does’t workI’m having the same issue, but without the PayPal part. Adding a seat to the cart never finishes. When I hit F5 to reload the page, the item is in the cart. But then, clicking on ‘Checkout’ does nothing.
Also, I constantly see the ‘this seat cannot be booked’ message, right from loading the page, it never disappears. But here’s the weird thing: This issue only happens to me when using the PRO version. The FREE one works fine. And in addition, it only happens on a site that uses Divi. On another site where I did a quick test, also the PRO version works fine.
What could be causing this conflict? In another thread here it is mentioned it could be a JavaScript issue, but how can I track this down?