nathanwright

Hi Wojtek

Thats fixed the issues with it conflicting with themes that were using the same css class names but I notice that you have not added any additional class or id to things like H3 etc as you can see from the HTML your plugin produces. It would also be useful if your plugin added an id to the wrapping DIV so that things can be tweaked with CSS as at the moment this is not possible (not easily anyway).

Cheers

Nathan

<div><div><h3 class="">GDPR Request</h3></div>
			<div class="gdprpdr_entry-content"><p class="">To request a GDPR report please submit your email address below. We will email you a confirmation link to verify
			you are the owner of the account.</p>
			<form action="https://www.gdprhelp.je/gdpr-personal-data-report-request/?new_gdpr_request=1" method="post">
				<input type="email" name="email" placehoder="E-mail Address" required=""><br>

				<input type="checkbox" name="gdpr_request_form_checkbox" required="">
				<label for="gdpr_request_form_checkbox">I consent to having Jaz'ing Up GDPR! collect my email, IP address and browser request details for the purpose of generating the personal data report (to learn more about our privacy policy please visit our privacy policy statement).</label>

				<input type="submit" class="button submit gdprpdr_submit-button" value="Submit">
			</form></div></div>

It is a fresh wp install running wp 4.9.1 and no other plugins and default theme

Hi, I contacted Yith and they have said that the version of Select2 that they use in their plugins is the one that is supplied with WooCommerce. Is your plugin compatible with the version that is supplied with WooCommerce 3.x?

Hi Matthew

Thanks for the reply, I have actually had a plugin custom written to do what I need and have to say (for anyone else interested) it makes a massive difference in performance when you are loading plugins etc and should be in the WP core as an option.

Cheers

Nathan

Hi Marko

What I was thinking is one of the following:

* On all post types have an tab called “Hidden” and every meta box that is placed in that is hidden from view for “everyone”

* Alternatively on the place where you can set the permissions, have an additional check box called “Hide for Everyone”

Personally I would prefer the first option as this is much easier and visual to see what metaboxes you have hidden from everyone.

Nathan

One last thought that may be able to be done without you changing any code.

Lets say you have a link as follows:

http://www.aaaa.je/wp-admin/tools.php?page=the-page-name&name=fred&id=23

So the part that you want to match on is:

http://www.aaaa.je/wp-admin/tools.php?page=the-page-name

What if you could do something that happened before you do the hook e.g. in apache or elsewhere so that the incoming url looked like:

http://www.aaaa.je/wp-admin/tools.php/page/the-page-name/name=fred/id=23

The in your plugin you could do a match on:

http://www.aaaa.je/wp-admin/tools.php/page/the-page-name

And enable the child pages option which you already have. Ok this would only work when the parameters are in the set order but would handle many cases like this.

This would not effect the processing of your plugin as the matching would still be the same as it is doing now just what is being presented to your plugin would be preformatted.