d9media

Nevermind, I found it! Thanks! It is under here: /wp-admin/options-general.php?page=opening_hours_settings

Hm, really? I could see the manual sync button but I don’t recall seeing an automatic option. Yes downloaded latest version. Could you quickly describe how to activate it? Thank you for your quick response @designextreme ??

@anjiaoshi pretty much sums up the experience really well

Futhermore, I found this in technical implementation guide which raises more questions:

Determining Consent
Just like vendors, some publishers will need to wait for a consent signal before setting cookies or processing user personal data for one or more of the purposes they selected if they choose consent as their legal basis for one or more of the purposes.

To do this, publishers will need to update their website code to look for the consent signal. This can be done using the getPublisherConsents command from the IAB framework JS API. More info can be found here in the IAB Europe Transparency and Consent Framework JS API Specification.

Executing Code after Consent Collection
In order to perform an operation when the UI is closed (indicating the user has made a new choice of consents), the __cmp operation to register a callback (specific to the Quantcast Choice CMP, not part of the IAB JS API standard) is as follows:

__cmp('setConsentUiCallback', callback)

The callback will be invoked (with no arguments) the next time the UI is closed which indicates the user has made a new consent choice. To invoke the callback every time the UI is shown, this operation will need to be made before each time the UI is brought up with

__cmp('displayConsentUi')

My first impression of Quantum choice is that the solution will work out of the box without further configuration. I think it should be more clear that this plug-in doesn’t actually do anything except collecting the choice but the choice signal, without any actual effect on the loading of Google Analytics, Facebook Pixel etc.

• This reply was modified 4 years, 11 months ago by d9media.

I think this plug-in is somewhat misleading or at least missing some information.

On the Quantcast Choice FAQ it says:

Does Quantcast Choice block my vendor tags from firing on my site before consent is given?
No. Quantcast Choice is a piece of JavaScript tag that you will need to manage the sequencing of on your site similar to all other tags. From a compliance perspective, it’s recommended for the CMP to fire first, and all other vendor tags are held from firing until a user has made a choice. After a user has made a consent choice, then Quantcast Choice will share and transmit that consent to 3rd party vendors on the IAB Framework. Then those tags will fire based on the user’s consent decisions.

No information is given about the mechanism of this plug-in. From my understanding the plug-in will generate the consent popup for you but not actually defer any scripts unless explicitly programmed.

• This reply was modified 4 years, 11 months ago by d9media.

I’ve created a git repository with changes I propose to make the plug-in complying with WooCommerce property getters and additionally support for WooCommerce JetPack (more location options).

https://github.com/d9media-git/wc-customer-source-fork

I hope you will find this helpful ??

Unfortunately, I have to confirm the issue is still present with the latest version. I wasn’t able to fully debug the issue but the profile image seems to break regardless of text length in our case. I was able to achieve the desired behaviour to all boxes by adding the following CSS to our stylesheet.

/* AB Profile Box Break Issue */

@media only screen and (max-width: 600px) {
    .ab-block-profile .ab-profile-avatar-wrap {
        min-width: 50%;
    }
}

• This reply was modified 6 years, 1 month ago by d9media.

@chrystl

Thanks for pointing out the update.

I just downloaded the new version to the production site (which is not translated yet) but sadly I need to say that still in the string translation only text from yoast and widgets is listed (total of 26), whereas on the 1.6.x version that I use on the dev site, around 80 strings are shown.

It is the theme option strings that are not showing up anymore. The theme is build on Option Tree. But since I am not an expert in WP I can not provide you with more details about what could be the cause.

(I won’t blame the plug-in, don’t get me wrong. It is very bad practice among many WP themes to define content in the theme options anyway.)

You are welcome. Then I suggest the string probably got lost due to that. Exactly the same happened to me, I even thought I had flushed the strings by accident as well.

I couldn’t really find a statement by the plug-in author on this, even though it seems to affect quite a few sites from what I read on Themebrain. Whatever has changed from 1.6.x to 1.7.x needs to be fixed so the plug-in will be compatible again to those sites in the future. Unfortunately I couldn’t find WHAT has caused the error. Perhaps Chouby could provide a rollback for those affected.

Great plug-in though! I disabled update for Polylang for now so no more headache ??

Did you update the plug-in by any chance? I spend a few days scratching my head until I discovered that apparently in version 1.7.x theme strings are not recognized anymore. Is it a bug? I don’t know, but downgrading to 1.6.5 solved the issue for me. Had to delete a few entries in the database though, otherwise site would go into WSOD.

EDIT:

The site is running on Nation Hotel theme, which is partly build with Option Tree.

sorry, wrong thread. / deleted post