Forum Replies Created
-
Posts
-
Hi Ismael
Turns out our host does have a security measure for those overseas. Apparently if you open it in a browser other than chrome it shows a basic logic test but in chrome it requires htaccess authentication. Anyway I’ve put the username/password details in the private content
Cheers
Hmm, that’s a bit odd. We haven’t set up any .htaccess rules that should require that. I did speak to my hosting provider and they were also unaware of anything going on. I know they do have some pretty tight security on some of their servers though and they asked if you could provide the following:
- A screenshot of the .htaccess login screen
- The country you’re trying to log in from
It seems a bit odd that you would be presented with .htaccess login and we wouldn’t a. Can you even see the site, or does that require .htaccess also?
Yep it’s happening on every post. If you go into Lessons you can edit any one of those. Lessons have been added by the sensei plugin, but I’ve been having the same issue on other sites with custom post types.
Yup I did. I’ve implemented it exactly as shown in that link. The actual builder works, it’s just that it reverts to the standard editor after saving.
Hi all, also having this problem. However I did some debugging myself. I noticed that the demo is using an older version of woocommerce ( or at least the add to cart script anyway ). The demo is using add-to-cart.min.js?ver=2.4.8 and my site is using ver 2.5.5
If you expand both of those files and look at line 3, v2.4.8 has: if (b.is(“.product_type_simple”)) { while v2.5.5 has if (b.is(“.ajax_add_to_cart”)) { on line 7. I added ‘ajax_add_to_cart’ class to the a.av-catalogue-item element and it all worked perfectly.
Until they release a fix, here’s a quick and dirty bit of code you can put in your functions.php file:
function add_ajax_class($text, $product){ $text = str_replace('add_to_cart_button', 'add_to_cart_button ajax_add_to_cart', $text); return $text; } add_filter('woocommerce_loop_add_to_cart_link', 'add_ajax_class', 10, 2);Or if you’re not using a child theme you can override the core file, however this is not recommended as you’ll lose any changes on updates ( although if it’s the update that fixes this that won’t matter )
Find wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/productslider.php on line 354 change:
$ajax_class = $product->is_purchasable() ? "add_to_cart_button" : "";
to
$ajax_class = $product->is_purchasable() ? "add_to_cart_button ajax_add_to_cart" : "";Hope this helps and hopefully Kriesi can test this and add it to a release soon.
Thanks for the great theme guys, and thanks for all the hooks and filters. Makes patching things like this waaaay easier :)
