• Resolved Daniel

    (@junglized)


    Hi everyone.

    Guys at Trew Knowledge, awesome plugin! I’d like to propose a few enhancements of the settings area to make it even better ??

    First: allow site admins to use TinyMCE instead of textarea for “Privacy Excerpt” and “Cookies” -> “How are these used”. That would make it possible to style it a little and use links in the content (to Privacy Policy Site for example)

    Second: turn “Cookies” -> “Cookies used” and it’s comma seprated list into something more eye friendly for frontend users, or allow site admins to use repeat text fields for storing cookies instead of comma seperated list.

    Third: Allow the plugin to recognize login cookies such as wordpress_logged_in_[hash] to allow users to block them as well (just in case the website project requires it). Right now, as I see it, only cookies from comma separated list are being considered as the ones which have to be blocked or allowed. The [hash] portion in the cookie differs between users so putting it in the list wouldn’t make the whole idea of managing that particular cookie work.

    Apart from that you seriously rule guys!!! Thank you!

Viewing 6 replies - 1 through 6 (of 6 total)
  • Hi,
    Did you try with wildcard for hash ?

    Thread Starter Daniel

    (@junglized)

    Hi Bonaldi,

    I don’t know what wildcard is ??

    EDIT:

    I managed to find an adequate information, didn’t know it’s called wildcard but hey, we learn through all our lives, don’t we?

    Thanks for pointing that out!

    That makes point number three irrelevant then ??

    • This reply was modified 6 years, 9 months ago by Daniel.
    • This reply was modified 6 years, 9 months ago by Daniel. Reason: information added
    Plugin Author Fernando Claussen

    (@fclaussen)

    Hi Daniel

    1.
    I plan on adding tinyMCE there to facilitate. You can add links if you want to by the way. You can manually do it.

    2.
    The reason why I choose to do comma-separated list instead of one per line or repeater fields is that believe it or not, some users can list up to 50 cookies into only one category. That would make each cookie category to be bigger than what they already are. But hey, if users want it, I’ll put it in. I wish WP allowed for polls in these forums.

    Some users requested something similar, but you would get the repeater field and a text field to explain what that cookie does. I’m still thinking about it because that would mean too much information on the front-end.

    3.
    As you probably found out already, we check for cookies using a “LIKE” comparison. If a cookie is named wordpress_logged_in_dn91hd198w12891, checking against wordpress_logged_in_ should return true.

    Thank you for your suggestions. I appreciate it.

    Thank you again @bonaldi. Sometimes you are even faster than I am to help users. \o/

    Thread Starter Daniel

    (@junglized)

    Fernando, you sir provide one of the best user supports I’ve ever dealt with! Seriously!

    Now, let’s cut to the chase ??

    1. …But add links with simple html tag? I tried that with Privacy Excerpt field. Whenever I wrap text with <a href="#">Privacy Policy</a>after saving settings the tag just disappears.

    2. Why not to let users add even 150 cookies if they want to? ??

    I had another thought just a few keyboard key presses ago about how cookies section could be sorted. Maybe it would be even better to add separate section for each cookie (in category section, so basically section in section). You create category, i.e. Necessary and in that category every cookie has three fields to fill out: name of a cookie, reason for use and additional information (such as external cookie privacy policy link). You press “Add cookie” button and another section with three fields for a cookie pops out. And when put that everyhing together it would form a nice clear table with all the information needed on the front end. ?? But obviously there would be no need for separate “How are these used:” and “Third party domain:” fields in cookie category section, because every separate cookie section would have those fields anyway. OK, maybe one tinyMCE field to write some general information about cookies placed in that particular category would do. Does whatever I write here make sense at all or am I mumbling? Do you think that would be too much information? Be honest ??

    3. Yes! With a little help from @bonaldi and a little knowledge of PHP I managed to get it working ??

    Thank you very much for willing to improve your work! Me and probably a lot of other GDPR plug-in users appreciate that!

    • This reply was modified 6 years, 9 months ago by Daniel.
    • This reply was modified 6 years, 9 months ago by Daniel. Reason: just a few edits
    Plugin Author Fernando Claussen

    (@fclaussen)

    Hi @junglized

    1.
    Hmm, maybe that is one field I am not allowing it. I know that some fields you can do it. But yea… A WYSIWYG field there would be good.
    I’ll try to add this to the Jun 12th update.

    2.
    I like your suggestion. I’ve been thinking about doing this for a while now.
    I’m only afraid that this might be too much information? Users are already overwhelmed with cookie settings enough as it is. Giving them another job (find what that one particular cookie does) will cause outrage. hahaha

    I want to do what you are saying, I’m just not sold on the individual “reason to use” field because of the reasons stated above.

    Thread Starter Daniel

    (@junglized)

    Hello @fclaussen,

    1. Yesss!! Thank you!

    2. You’ll do as you think is the best. I only dropped a few suggestions here ??

    Thank you very much for such a great support!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Settings enhancement’ is closed to new replies.