pswgru2011
Forum Replies Created
-
Thank you for the suggestion. Disabling the “Use the output buffer” option under “Encode contact data” resolved the conflict, and Amelia’s styling and interactivity are working correctly again. Appreciate the quick help!
Thank you for the suggestion. I have now switched off “Interne Formulare schützen” (Protect internal forms) and “Schutz erzwingen” (Enforce protection) in addition to “Puffer abfangen” (Capture buffer) — see the screenshot of the current settings attached. However, the problem persists unchanged: the Amelia booking calendar only displays the category headings, while the actual selection fields (service, staff member, etc.) either fail to load or are not interactive (see second screenshot).
Only when I deactivate the entire CleanTalk plugin does the calendar work correctly again. I have now tested several settings individually, without success.
I am an insurance broker, not an IT professional, so I am not able to carry out further technical troubleshooting (JavaScript conflicts, AJAX requests, console analysis) myself. Since CleanTalk has now been clearly confirmed as the cause, I would ask that the CleanTalk support team actively look into this and specifically determine which part of the plugin is conflicting with Amelia — ideally by accessing my website directly, if access is required for that.
I would greatly appreciate a concrete solution rather than further testing suggestions.
It wasn’t caused by the cache plugin. I cleared the cache and also disabled the plugins, but the problem still persisted
Hello,
Follow-up: We found the root cause by comparing full page source (View Source) with CleanTalk active vs. deactivated.
With CleanTalk active, the following stylesheet is completely missing from the :
This is Amelia’s own core stylesheet — without it, the booking calendar has no styling and its form elements become unusable (this matches our reported symptoms exactly).
Additionally, several other stylesheets are missing from the page when CleanTalk is active but present when it’s deactivated:
- wpb_flexslider-css (WPBakery)
- wp-block-buttons-inline-css, wp-block-columns-inline-css, global-styles-inline-css, core-block-supports-inline-css (WordPress core block styles)
This suggests CleanTalk is interfering with the enqueueing/output of certain stylesheets sitewide, not just for Amelia specifically.
We also noticed that ctPublic (your own plugin’s JS object) reports “advancedCacheExists”:true on our site. Could CleanTalk’s interaction with our caching setup be causing incomplete/stale HTML to be served when CleanTalk is active? This would explain why entire tags are missing from the page source rather than just being blocked at the network level.
Could you investigate why these specific stylesheets fail to enqueue when CleanTalk is active?