mike8040

Moin,

dann anders. Welches Produkt soll “Taggleich” darstellen??

No, we are using CusRev since two years.. Anyway thanks. Then some other plugin is adding that

?h, wollte ihr mich ver?ppeln? Was macht den die One Button L?sung von euch dann wenn nicht das ganze Layout ver?ndern? Die würfelt das komplette Checkout Layout auf Grund der besonderen deutschen Bürokratie durcheinander. Deutschland ist vermeintlich das einzige Land auf der Erdkugel die an der Abfolge einer Online Kasse fachsimplen muss…. Natürlich beeinflusst somit Germanized das Layout eines Shops. Nicht nur unsere..
Punkt ist, die Optionen wie Software Download / Gebraucht Artikel etc sind deaktiviert. Warum rendert ihr diese überhaupt und es ladet Dinge im Dom die keine Verwendung finden?? Sowas wie das hier würde es verhindern und man spart sich noch styling code….

document.addEventListener("DOMContentLoaded", function() {
    const gebrauchtwarenOption = document.querySelector('.germanized-used-goods-option'); 

    const checkboxPlaceholder = document.querySelector('.wc-gzd-checkbox-placeholder-data-used-goods-warranty');
    
    if (gebrauchtwarenOption && gebrauchtwarenOption.checked) {
        checkboxPlaceholder.setAttribute("data-checkbox", "used_goods_warranty");
    } else {
        checkboxPlaceholder.style.display = "none";
    }
});

Wie ich eingangs sagte, hat wer diese Woche im WP Ecosystem am Checkout rumgedoktert. Mir ist das unn?tige Rendern erst durch den Layoutfehler aufgefallen, auch wenn Germanized diesen vielleicht nicht verursacht hat, bleibt fundamental die Kritik, dass die Elemente von euch überhaupt erst geladen werden.

As I said, nothing was changed on the settings on WooCommerce or your plugin itself basically more than 24 months. So this must have happened by an update or a conflict with your plugin or Woocommerce. There is no use of additional plugins handling tax

Prices entered with tax: Yes, all prices are entered with tax
Do not adjust taxes based on location: This was never changed at all and is also a new option or at least differently phrased than the old version of this plugin.

I really can not go with that the plugin was not changed, as obviously I set it up to 1:1,19 to get the desired prices back then for Non-EU Customers and this is not working anymore. So obviously there was a change made with no warning to it. The field isn’t active anymore and has a switch. The whole interface and option did change too. So how to force this plugin to use the regular price and not this magical exchange price. Magical because there is no basic calculation leading to the resulting price your plugins puts out. It is not an additional 19% to the regular price. How to force the plugin to use the regular price set and not correct every price on by one. This also was not necessary with the old version

Regarding the other stuff: You offer the plugin not for the good of society or because you’re on a selfless mission. The goal is to sell your premium subscription. If we need the additional features and the plugin works flawlessly, we are happy to pay. But don’t expect people to grovel just because it’s free, especially when basic functions suddenly become faulty… What is upsetting here that basic features are changed without the warning which is easily possible to add as a note on the pushed update version.

• This reply was modified 8 months, 2 weeks ago by mike8040.
• This reply was modified 8 months, 2 weeks ago by mike8040.

No, but the field disappears with Germanized being deactivated. Had a caching issue so the field was still there even with Germized being deactivated. I’ve asked them what it is and where to define it because there is no hint or indication in their settings

• This reply was modified 10 months, 1 week ago by mike8040.

Thanks for the reply. At least it is great you have it on the roadmap. Those reminders are a sensitive topic. Not everyone likes them. I keep your plugin and it’s changelog on the radar. Would be really great if you update that topic.

Thanks for the reply. I had a look on the docs / Github. Unless I study PHP development this is just gibberish. Can you just state if any Cookie Consent solution can grab that cookie and script automatically and pull it into their blocking system appropriately to wait for the user consents like with all other cookies like GA4?

The feature itself is great and if the customer is fine with it, good. We do not want a lawsuit just because a code line was missing.

Amazing. Thanks for the update. I will have a chance to test later in the day and get back if it is fixed.

Same issue here. I see it also that this should be handled in the core not by us users. And I may understand it incorrectly but I do not find or like the offered solution to add a genereic image for all facebook shares. For instance the product shares should show the individual product image

Ok, thanks for clarification but for the said countries in EU to be safe we need to ask for consens. For instance with Cookiehub it is not able to block those cookies, because it says they will be set before consent. So even with Automatic Blocking by CookieHub enabled which is able to block any common tracking (GA for instance), it is not able to block you order attribution cookies and is asking to fix this by the shop owner.

So how to block those cookies before consens?

Your docs on it are useless in that regard. I do not understand why your solution is set up that common and widely used consent plugins aren’t able to block those cookies before user consent-

• This reply was modified 11 months, 2 weeks ago by mike8040.

I am experiencing the exact same error, and it is definitely not a minify/combing issue as assumed here. Furthermore, the assumption does not explain why version 1.8.4 works under the same conditions what I wrote in the message before.

Same here and normal Site tracking is not working with it. In other words, one can not see which site is visited (version 2.0.1 here). Prior release (Version 2.0.0) of this plugin was not working at all as not data was send and the cookie was not even set! What is up with this plugin???? Does it even get tested before being pushed?

//Edit: Rollback to 1.8.4 and the classic site tracking is working again…

• This reply was modified 1 year ago by mike8040.
• This reply was modified 1 year ago by mike8040.
• This reply was modified 1 year ago by mike8040.
• This reply was modified 1 year ago by mike8040.

Hi. Thanks for the prompt response! Just send you the details.

//Edit: Hey there, quick update. It comes down to WC GA integration is my take. They complete crashed it against the wall with version 2.0.0. I just updated to 2.0.1 and some real time data is available again, but is still not working properly. The classic site tracking data is broken. Console say:
wcgai.trackClassicPages is not a function

Some users seem to already reported that in their forum.

Changelog of their 2.0.1
Fix – Resolve Google Analytics not loading if gtag already exists on the window object.

So I’m sorry. I guess this is all not COAS related but a deep WC GA issue.

//Edit: Maybe it helps anyone. I rollback to WC GA integration 1.8.4 and classic and ecommerce tracking is working again. Also COAS does it Job well and serves the gtag locally like communicated. It was all down to broken functions with the plugin by WooCommerce.

• This reply was modified 1 year ago by mike8040.
• This reply was modified 1 year ago by mike8040.

Hey there,

thanks a lot for your response and explanation. So to understand it correctly. I only have WC GA Integration enabled and CAOS is enabled with its Compatibility Mode and the general and ecommerce tracking should work?
Unfortunately that was not my finding. Once compatibility mode was active no tracking was available. I took care that the cookie banner was no interfering, but that did not resolve the issue. The cookie was not even set looking in the dev tools application tab. Right now I have CAOS disabled again. Because of Adult content I can’t share the URL here.

Thanks a lot!