How to disable shortcuts in the format of the WordPress visual editor • WordPress Help

As you already know from WordPress 4.3 the format shortcuts have been introduced in the visual editor , that allow to give style to your text while you write without needing to resort to the icons of the editor's toolbar format.

The truth is that they are a blast, and I think it's an improvement very important, because they allow to apply styles of lists, titles and quotes in the fastest possible way, as you can see in this animated image:

 shortcuts format editor wordpress

Now, there are people out there, almost people I would say, who does not like, who prefers to apply formats to the traditional style: select text, click on corresponding icon; and you have to please everyone.

If you're one of those strange characters, take note, because you can turn off the formats, you just have to get involved with a bit of code . Open the file functions.php of the active theme or your utilities plugin and add the following code:

Save the changes and you will have disabled the format shortcuts the automatic Markdown from the visual editor of WordPress. The rest will continue to work as usual.

And you?

 Loading ... "title =" Loading ... "class =" wp-polls-image "/> Loading ... [19659100] NOTICE </strong>: this publication is two or more years ago, if it is a code or a plugin it might not work in the latest versions of WordPress, and if it is a news it could be obsolete. warned. </p>
</div>
</div>
<div id= Loading …

That may also help you:

Forks or copies? • WordPress Help

I do not know if you have heard about it but these days has been bundled in the WordPress community due to a controversial derivative of the creation of a fork (bifurcation, version) of the plugin Bloom by Elegant Themes created by LeadPages, which has been named Rapidology .

What should not happen in principle something as simple as someone has taken the source code of a plugin under the GPL license like all the Elegant Themes products, has created a version ( fork ) I have made some modifications and has uploaded it to the WordPress plugins directory (no, it is not a link error, it has been removed)

Rapidology vs. Bloom

 bloom-dashboard "width =" 838 "height =" 465 "srcset =" https://ayudawp.com/wp-co ntent / uploads / 2015/08 / bloom-dashboard-840x466.png 840w, https://ayudawp.com/wp-content/uploads/2015/08/bloom-dashboard-550x305.png 550w, https: // ayudawp. com / wp-content / uploads / 2015/08 / bloom-dashboard.png 960w "sizes =" (max-width: 838px) 100vw, 838px "/> </a> </p>
<p> As account Clay Collins, CEO of LeadPages <span class= in his blog it all started because LeadPages wanted to make a subscription plugin based on the wonderful Bloom of Elegant Themes, how to add new services, incorporate new settings and something more. Checked that the plugin was the GPLv2 license and got down to work.

When they finished it, they made it available to the whole community in the official plugin directory of WordPress.org

All right not ?

Well no, the thing has gotten complicated because turns out that Bloom is a paid plugin which is obtained by purchasing the complete package of Elegant Themes which includes, in addition to 87 topics, 6 fantastic plugins, among which is Bloom. The unit price is ridiculous, but that is almost the least, the important thing is that once again the melon of has been opened, what it really means to develop under a GPL license .

According to the GPLv2, subscribed by WordPress it turns out that the moment a topic or plugin uses a single function of the WordPress code or another product published under this license, it can automatically and should be distributed in its entirety also as GPL, with the same liberties to modify, adapt, distribute.

The only restriction, if anything, is that you must indicate – with links – what other software you have based on fork something that by the way they have fulfilled in Rapidology which is also GPL has the full source code on Github and link Elegant Themes even from its official website, clearly recognizing that it is a ]adaptation .

So where is the problem?

Well clearly that Elegant Themes has gotten pissed and has asked for the removal of the plugin from the official WordPress.org directory claiming that its fork is a mere copy because only the logo has changed, and the Automattic guys have listened to them. It's already bundled!

It turns out that it has opened cross-debates and accusations about what a fork and what a copy of whether the Constructor that has used Elegant Themes for Divi is a copy of Visual composer and so everything.Let's go, that has been brown relationship between them.

The response from WordPress.org

And not only that, but the good thing about Mika Epstein was "explaining" in the WordPress.org plugins blog what, for the purposes of the official directory, is understood by fork and copy, its differences, a bit as a justification for the withdrawal of Rapidology from the dir ectorio de plugins

In summary, it says that if you detect that someone has made an identical copy of your plugin, you can contact plugins@wordpress.org if they want to remove it, as long as one of these two conditions is met. :

  1. That it be an exact copy without modifications
  2. That the original work credit is not included

Come on, that they qualify, that they understand that a fork must be a "substantial" copy that it is something more than changing the name and the logo.

To me it is that it makes my hair this kind of thing. The nonsense has gone so far that they have even got into a stupid war of emoticons because the post of the CEO of Landscape used a sad one in his post and in that of WordPress.org they have put in his post his Cheerful version of the same emoticon. To unravel, to cry or I know.

The jilipollez is reaching delirious levels.

Is it the first time something like this happens?

Well, no, it was his thing at the time not only with the Constructor de Divi and the Visual Composer, but also remember the one that got together with WooCommerce, a fork of Jigoshop interestingly a company recently acquired by Automattic, or as with WP Sync DB a fork of the WP Migrate DB Pro plugin.

There are many more cases but the controversy and the angry debate only arises when these two conditions are met:

  1. The software " versioned " is paid
  2. Someone agrees to give their opinion and agrees with one of the parties in conflict

And in this case the two conditions have been met:

  1. Bloom is a paid plugin, and Rapidology is a free version of it
  2. The reason has been given to Elegant Themes (I do not know if provisionally) when removing the Rapidology plugin from the official plugins directory

And now what? [196] 59009] Well no idea, it seems that Rapidology will have to receive a good amount of modifications until it is allowed to appear in the official directory of plugins.

At the moment you can download Rapidology totally free on his official website . The appearance and use is the same as Bloom's, but they have improved the A-B tests and added integration with more services, such as HubSpot, Act-On, Marketo, etc.

Sir, I have doubts, is the GPL good? Is it ethical to copy? Better Burger King or McDonalds?

I understand you, but freedom has these things. The GPL license is a real virus as has been said out there, but I would say it is a good virus which allows free distribution of software and derivative works, which means more freedom and options for users of open source software, and that's good, always .

Controversies will continue to arise but if I have to choose bet because the GPL license is applied and the developers understand that everything that is sown is collected, and that open source software offers many really lucrative business models, which many are already taking advantage of; the business is not to sell licenses but to offer services .

With the GPL license users win, always.


And you, what do you think of all this move?


( Note: in case you have not noticed some of the links in this entry are affiliation, so if you buy a product it costs you the same but you pay me a coffee)

NOTICE : This publication is from two years ago or more. If it's a code or a plugin it might not work in the latest versions of WordPress, and if it's a news story it might be obsolete. Then do not say we have not warned you.

Loading …

That may also help you: