How to disable the Gutenberg editor on custom content types

The advent of the publisher Gutenberg is getting closer and we want it or not as the main feature of WordPress 5.0 so we better prepare ourselves, to love it or to hate it.

If you just do not want it, I already explained how to deactivate Gutenberg completely but if you're still thinking about it, but you know that there are custom content types (celebrities custom post types ) in which you do not want to load for technical reasons or whatever, here's the solution.

As the same code indicates, you just have to change the content type Custom (CPT) code for yours where you do not want Gutenberg to load.

How to meet the RGPD in bbPress

Do not forget, bbPress is also WordPress but interestingly almost nobody has remembered that this system forums also has to adapt to the General Data Protection Regulations (RGPD).

And the truth is that there is not much, although it makes sense.

Privacy policy

There is not much because you do not need a tool specific for the privacy page because bbPress is a plugin for WordPress, then with the tool included in WordPress you already have it .

Yes you have to add the specific information of the data that you collect in your forums , which at least are:

  • Username
  • User email
  • IP address

Cookies

You also do not need anything specific for cookies because any cookie plugin you already have and cum pla with the RGPD also applies to bbPress .

Data availability

The same goes for data export, a priori, but not, here nobody has remembered bbPress ]because in principle WordPress does not export data from bbPress forums.

So on this occasion we do need help.

For this, luckily, there is a plugin, bbPress GDPR that adds the bbPress compatibility with WordPress data export and deletion tools .

When installing and activating it, the data export may include:

  1. Forums (Deletion / export if requested by a user)
  2. Discussions (Deletion / exportation if requested by a user)
  3. Answers (Deletion / exportation if requested by a user)

In this way we can already comply with this part of the RGPD.

Anonymized data

But it turns out that bbPress captures and, above all, it shows by default the IP of the users of the forums and that is because it captures them.

Here we can do 2 things:

  • Continue capturing IPs and inform the user before registering in the forum and in our privacy policy page
  • Do not capture IP addresses.

For this last one I have not found any plugin, but you can add this custom function to your customizations plugin that, now, will anonymize your users .

Actually the function does not erase or avoid the capture of the IPs, what it does is that they are all 127.0.0.1, which is the same as not collecting them, when assigning a generic to all users.

] A fix? Yes, but the goal is achieved, which is what matters.


And nothing else. If you know of any other way to comply with the RGPD in our forums bbPress and it's slow to tell us in the comments.

Loading …

That may also help you:

How to adapt Divi, Extra and Bloom to the RGPD

As it is clear and notorious that there are many users of Divi Extra and even the Bloom newsletters plugin Bloom all of Elegant Themes we are going to do a review of how you can adapt to the RGPD if you use them.

Deactivate Google Maps API and Google Fonts [19659004] If you do not want your web made with Divi to share your users' data with the Google Maps API and much less through Google Fonts you can disable both possibilities. [19659007] In Divi> Theme Options just do not put a Google Maps API key and disable Google Fonts your theme will use the installed fonts.

You can also remove the Google Fonts from Divi as we saw the other day . [1 9659007] In Bloom you can also disable Google Fonts in your settings …

Upload your own sources, or even Google Fonts (private)

If you want to continue using Google Fonts with Divi you can always upload them manually from the divi you just have to download them and upload them, but they will not use external scripts that extract information from your visitors.

You can do it with any module, as you see in the following screenshot …

Excludes the IP address of the subscription banners

A new functionality of the Optin de Divi that has gone very unnoticed is ] the possibility of not saving the IPs of the users who fill in your forms .

And it is important, because the IP address is considered by the RGPD as personal data . So if you collect it you must inform, and if you do not want it at all, Divi gives you the option not to collect it .

Simply uncheck the box " Include IP Address " in the advanced settings tab of the otpin form

It is not mandatory, you just have to make the decision of what to do, and you will know what to report.

Also you can do the same in Bloom's subscription forms .

Protects security in your optin forms

Another little-known adjustment is the possibility of applying attributes that protect the security of users who fill out your forms .

And yes, also the RGPD requires you to protect your users' data .

To do this, also in the Advanced settings tab of module optin p You can apply the attributes external, noopener, noreferrer which will protect your users from the vulnerability known as tabnapping or target blank .

Data Collection

Since the last versions, Divi does not collect any data from your users thus helping you to comply with the RGPD.

Only collects data in tests A / B, which calls multivariate tests for which uses the IP addresses of anonymous visitors to determine which users to serve a test or

Add the 1st layer of information to your optin forms

Another new option is the possibility of including a field in the bottom of your optin forms, with your first layer of information. You have it in the content settings of the form.

Add acceptance boxes

To comply with the RGPD, now in Divi and Bloom, thanks to the integration with fields Customized, you can add acceptance boxes and also save that consent.

It is up to each provider how to add them, but in this link you have the procedure for each provider compatible with Divi and Bloom .

Basically the procedure is as follows:

  1. Add the custom fields in the account of your newsletter service.
  2. Once they exist, when you configure it in Divi and Bloom you can select them.
  3. In the visual constructor choose the one you want, checkbox of acceptance for example, and you add it to your forms

Add link to your privacy policy

Once you have your custom field, now also with Divi and Bloom you can add a link to your pol Privacy policy to the text that accompanies the acceptance box, as in the following capture:

Divi contact forms that comply with the RGPD

In advance I tell you that , although you can create forms with Divi that comply with the RGPD you have to make a small ñapa / trick .

First add your form as always and add a new field, choose type Checkboxes and next to the box you put your text in my example with an asterisk at the end, then we see why.

It's important that the box is not checked in the Options , because the RGPD forbids it, and the field is mandatory.

Now add a new field, and choose type Text area . In the Title box, you enter your first layer information as required by the RGPD. Again mark the field as mandatory.

This type of field does not allow formats, but the RGPD does not ask for it either, at least it fits a lot of text and it will not occupy a lot of space in your form. [19659007] With this you already have everything we can do with the fields of the form, and that is that no field allows us to link to our privacy policy.

The structure of the form will look like this:

[19659007] To get it, just below the form, add a text module, and that's where we put the text and link to our privacy policy, putting an asterisk first, to relate this field to the previous one of the selection box, so that is understood and each part forms a whole.

The final structure of our form will be as follows:

And our Divi form that complies with the RGPD will be this way:

[19659007] Logically, the first layer of information should be relevant, yours, not the example I have used. If you just save the forms in your email, put it, of course.

And if, after having seen and tested the above, you do not stop, or want to use a simpler system, you can use the plugin to fulfill the RGPD with Divi, Extra and Bloom .

You just have to customize your texts in the new settings screen and it will be displayed when the user clicks on your forms optin .

It looks great, it does not slow down subscriptions, it does not hide your pretty forms, it's easy to configure and will help you easily comply with the RGPD in your subscription forms .

After clicking on the subscription form the overlay is shown


As you can see, Elegant Themes has put the batteries in place, and continues to take care of its users, also with compliance with the RGPD, making it easier to add the new elements with the that protect privacy and right os of our users.

Loading …

That may also help you: