I have a frustrating issue with my PDP. I installed an app to make the packs (1pack / 2pack / 3pack) display nicer and now the price is not displaying correctly anymore. The app developers said it was about the theme though, not about the app.
Because the class changes - the logic has nothing to target anymore. For example if the page does not have compare price - the price class is “.price-item–regular”, but this class ends up dropping over to the compare price if there is one so the mentioned class no longer applies to that price.
–> How to change this logic so that the main price is always static, not sometimes 1 class then sometimes another ?
Was Kaching code in your theme added by an app automatically or it was added manually?
What happens is that this runs too early. The code tries to monitor document body element, but when the code runs, the document body is not yet loaded, that’s why the code fails and there pops up a console error mentioned above.
I’ve installed the app in my test store and it does not have this code in <head>
However, the app fails to update product price if compare_at price is set.
Now, looking at the app code I see that they have special selectors to cover for both situations (compare_at set and not), but the app seem to fail choosing or decides to update hidden element…
What I’d try to do – install a clean fresh Dawn from theme store.
Set up Kaching Bundles in this theme to replicate the problem in this clean theme.
Contact support again with this – “Your App does not work as expected in clean fresh theme”.
It can be that the Bundles app may conflict with other apps in your store or some custom CSS added – this is why it’s important to replicate in fresh theme copy without other app embeds enabled.
Finally – if App developers fail to fix it for you, you can always hire someone else to construct a fix. There are several possible ways to do it, but it’s always better to make an app work as expected.
Ah, yes – do not trust everything written in the forum – people tend to post AI hallucinations or some half-baked code.
At least, always keep a backup theme copy.
Ich schreibe dir mal hier auf Deutsch, da du in Deutschland ansässig bist. (PS: Es gibt auch eine deutsche Community!)
Dein Theme ist auf Basis Dawn zwar gut, doch durch die ganzen Sektionen hast du noch andere Probleme. Du nutzt swiper8 und swipe-9 - Versionen. Aktuell ist die Swiper12 aktiv. Daher kann auch der Fehler kommen. Sowas darf nicht ausgeschlossen werden - update deine Sektionen über die App des Sectionenherstellers. Damit hast du auch wieder den aktuellen Code drin. Solche Probleme sind meist schwierig zu finden, sobald alte Abhängigkeiten im Theme sind.
Good.
Would be great if you can share what has been done so others can benefit from your experience.
The problem seems to be resolved, but the code which generates the error in console is still there, and still errors.
While it does not break anything it’s still the code which runs and (at least) affects your site speed.
Ideally, I’d recommend to remove it.
You also have some CSS rules inside <script> element, this also does not work, but generate console error.
I’d remove that one too:
(PS: Es gibt auch eine deutsche Community!)