andresmolina
Forum Replies Created
-
Forum: Plugins
In reply to: [HashBar - WordPress Notification Bar] New WordPress compatibilityFound my license now.
Forum: Plugins
In reply to: [HashBar - WordPress Notification Bar] New WordPress compatibilityOk i download it manually from envato (where i purchase it) but it is asking for a license number, but i do not have any license number and i dont know where to find it on my envato market account.
Forum: Plugins
In reply to: [HashBar - WordPress Notification Bar] New WordPress compatibilityi can not see the pending update on my wordpress update panel
Forum: Plugins
In reply to: [HashBar - WordPress Notification Bar] New WordPress compatibilitySorry to insist, and i hope you dont get me wrong, but we are waiting for your plugin to be updated for the pro version we purchased on over 40 sites, because we cant update wordpress to 5.5 due to this incompatibility. Any expected time to be released?
Thanks
Kind regardsForum: Plugins
In reply to: [HashBar - WordPress Notification Bar] New WordPress compatibilityHi,
Did you release the new version? i can not see it under my pending to update plugins.
Thanks
Kind regardsForum: Plugins
In reply to: [HashBar - WordPress Notification Bar] New WordPress compatibilitythanks so much!
Forum: Plugins
In reply to: [HashBar - WordPress Notification Bar] New WordPress compatibilityI’m having same issue here, incompatibility with wordpress 5.5 and woocommerce 4.3.3 (and a bunch of other plugins) the checkout cant find final price, it stays thinking forever, and the console shows up the following:
main.js?ver=5.5:14 Uncaught ReferenceError: hashbar_wpnbp_localize is not defined
at HTMLDocument.<anonymous> (main.js?ver=5.5:14)
at i (jquery.js?ver=1.12.4-wp:1)
at Object.fireWith [as resolveWith] (jquery.js?ver=1.12.4-wp:1)
at Function.ready (jquery.js?ver=1.12.4-wp:1)
at HTMLDocument.J (jquery.js?ver=1.12.4-wp:1)
at HTMLDocument.c (rocket-loader.min.js:1)
at l (rocket-loader.min.js:1)
at t.simulateStateAfterDeferScriptsActivation (rocket-loader.min.js:1)
at Object.callback (rocket-loader.min.js:1)
at t.run (rocket-loader.min.js:1)Forum: Plugins
In reply to: [Super Page Cache] Woocommerce checkout 403 wc-ajax since latest versionEmail sent!
Forum: Plugins
In reply to: [Super Page Cache] Woocommerce checkout 403 wc-ajax since latest versionSure, i will send details right now, and yes, the woocomerce not to cache checkout page is enabled.
Forum: Plugins
In reply to: [Super Page Cache] Woocommerce checkout 403 wc-ajax since latest versionWe are not using fallback cache at the moment (we will once we fix this thing) and so, we are not using any TTL config.
We have just enabled on a testing site the latest version just to see that it throws a 403 again. Where should i send you login details for the site in case you want to test it yourself?
The actual error shows is as follows:
https://xxx.com/?lang=es&wfacp_id=16549&wfacp_is_checkout_override=no&wc-ajax=update_order_review
And if it helps this is server log line with the error shows:
[04/Aug/2020:18:32:42 +0200] “POST /?lang=es&wfacp_id=16549&wfacp_is_checkout_override=no&wc-ajax=update_order_review HTTP/1.1” 403 2 1167 0 “-” “-” “https://xxx.com/checkout/?lang=es” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36”
Thanks
Kind regardsWell… further testing.. i have to say is not Divi… but i can not seem to find the root of the problem, although i think is an incompatibility between yours and woofunnels.
Hey, i just did one test, and it seems to be an incompatibility between Divi Theme and your plugin, is there any easy fix? would you mind helping me? it is really important for us to fix this as we would LOVE to use your plugin.
I have sent you an email to the address I found on Alogritmika website [email protected]
Hmmm not sure how to share private details with you… i can send you a contact info on your algoritmika website if you want
Just as a heads up, i tried changing the order status manually and it still does not work, but i just realized we use a custom order status, so it might be the reason.