Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter farisr

    (@farisr)

    Apologies – I didn’t mean to imply that I wanted to restore the data.
    The deletion was deliberate.

    What I want to do is remove the mysterious blank lines (showing only a date) in the Customer list.

    Following *some* of the suggestions in https://wordpress.org/support/topic/woocommerce-customers-section-shows-entries-with-zero-values/ I deleted the NULL records in in the wc_customer_lookup table (and cleared transients). There is now only one entry in the wc_customer_lookup table, and that’s for the only customer I didn’t delete.

    Unfortunately, this didn’t do anything. The blank lines are still there.

    The OP in the linked topic goes on to say “I had to manually delete _transient_wc_report_customers_ in the wp_options table now for the customers to disappear…”

    I’m not keen on doing this because I don’t know what this wp_options entry really is for.

    • This reply was modified 2 years, 3 months ago by farisr.
    Thread Starter farisr

    (@farisr)

    Thank you both for your responses.

    I regret that I am still confused. Please can I ask for your patience and understanding to help me better understand the issue?

    I have read and re-read https://complianz.io/google-maps-and-gdpr-what-you-should-know/ but it doesn’t seem to say anything to help me, other than to mention that the WP Google Maps plugin, which I am using, is specifically supported by the Complianz plugin.

    @jarnovos The WP Google Maps plugin integration is definitely enabled in Complainz. I’ve double-checked.

    I don’t quite understand the button situation though. To get the WP Google Maps map on the page, I use a WP Google Maps shortcode [wpgmza id=”1″] and have no control over the button (especially when integration is enabled).

    Also remember that the existing “I agree” button under the placeholder map does work, causes the page to refresh, enables the real map and also enables Marketing cookies automatically too.

    In essence, the “I agree” button under the placeholder map works in the way that I want/expect putting a tick in the “Marketing” cookies tick box and saving preferences in the Complianz cookie banner should work.

    @aahulsebos Other than making sure that I disable caching in the page in question (and I think I need to disable on the model url as well in my specific case) I’m not really sure what exactly you are telling me. I don’t really see any advantage to disabling integration – I prefer the integration.

    All I want, I suppose, is for the page to automatically refresh when Marketing is ticked, allowing the map to display, in the same way that the page refreshes and the map is turned into a placeholder when the Marketing tick is removed.

    I’m really sorry if I’ve misunderstood what you are trying to tell me.

    Thanks Mathieu … but I already have 4.7.0

    The issue does not appear to be CSS related (I HAVE modified the CSS). I don’t know enough about Themes to know for sure, but the errors being found do not appear to be Theme related.

    The errors I’m seeing are related to this “Elements should not have tabindex greater than zero”

    And the actual code is similar to the following:
    <a aria-label="Preferences" href="#" class="cc-btn cc-save cc-show-settings" tabindex="6">Preferences</a>

    But there are four errors in total, one each for the Preference, Accept All, Functional, and Cookie Policy links.

    These issues are found with the Axe WCAG tool and fall under WCAG Best Practices, apparently: https://dequeuniversity.com/rules/axe/3.5/tabindex?application=AxeChrome

    I have scanned using WAVE and it also find these same things.

    Do I have to regenerate the cookie banner or something to trigger the code changes?

    Or is the positive tabindex deliberate? After all, you want these buttons to be the “first” that are accessed, overriding anything else. Yet is is not Best Practice according to WCAG 🙁

    I am not an expert in this field so please don’t take anything I’ve mentioned here as any form of complaint or criticism.

    • This reply was modified 3 years, 7 months ago by farisr.

    Please may I add my vote needing WCAG 2.1AA compatibility?

    Unfortunately we deal with sites that absolutely require it, and this is now causing a serious problem 🙁

    I don’t suppose there’s an ETA so that I can keep my clients informed?

    Thread Starter farisr

    (@farisr)

    Will do. Thanks.

    Thread Starter farisr

    (@farisr)

    Thank you Leon. Your support is amazing and very much appreciated.

    I wish all Plugin publishers were as good.

    Thread Starter farisr

    (@farisr)

    Thanks Leon. URL added. There is no Consent section. I think you are right that this is why I’m confused on that element. I have updated it today and still the same.

    I agree that reCAPTCHA cookies are not functional. However, they are definitely not Marketing either.

    I see that I can modify the name if I choose to use Categories. I was using accept/reject. I think I can work with this. I will experiment. But I will leave it as for now so you can see the Consent section being missing.

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