Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter therede

    (@therede)

    Status update: after investigation I found out that rolling back to 7.2.2 solves the issue.
    Something in 7.2.3 seems to causes the error when editing the product pages.

    Thread Starter therede

    (@therede)

    Hi Andrew & Alexgso!

    The removing of the files in /uploads/ did not help.

    Reinstalling the plugin fixed the issue! thank you for the support!

    • This reply was modified 3 years, 10 months ago by therede.
    Thread Starter therede

    (@therede)

    I have changed 2 thins to test:
    – added “test” to on of the socials in Pictogram titel
    – added “XX” to the widget header title

    Both have no influance on the behavrior / displaying of the icons

    Thread Starter therede

    (@therede)

    Hi Andrew!

    Thanks for the quick response!

    For the console output: yes I have tracked down these issues to 1 specific plugin, not of SiteOrigin. After deactivating this plugin, errors in console dissapeared, but issue on Social Widget remains.

    After that I have deactivated all pluggins on the site and the issue persists. Only active pluggins are SiteOrigins Page Builder, Widgets Bundle & CSS. Currently installed versions are:
    Page Builder (Version: 2.12.0)
    Widgets bundle (Version: 1.18.2)
    CSS (Version: 1.2.14)

    Other actions I have performed to check the origin of the problem:
    – Purged Browser cache
    – Checked in incognito view
    – Purged Server side caches.
    After these checks, with all non-siteorigin pluggins disabled the issue still persists.

    – currently the site is still down, and you can check the current output. We will be resuming “normal” operations around 15.00 CEST.-

    Looks like he is searching for the same option as I am. My topic was: https://www.ads-software.com/support/topic/use-of-google-tags-manager/

    For GTM (google tags manager) to work, you have to fire of a the Main FB-pixel from there. If the Main pixel isn’t available, the event wont be logged and it should be sufficient. Pixel caffeine can still implement all the events on the pages, but needs to leave the main pixel code handling out (and source to GTM).

    A checkbox somewhere in settings like: USE GTM for main pixel handeling, should be sufficient. (I know, in the code some bigger changes are required to get this done and functional).

    To be fully GDPR & Coockiennotice / concent complient I am realy waiting for this feature to be implemented in Pixel Caffeine. If this takes to long I’m forced to go and search for a other plugin, which I WOULD LIKE! ??

    I can assist with testing under GTM if required. (got GTM Setup to handel this)

Viewing 5 replies - 1 through 5 (of 5 total)