Also, appears to redirect to the main domain, when the site I’m working on is on a sub domain.

// post_test.php
<?php $test = isset( $_POST[ 'test' ] ) ? $_POST[ 'test' ] : false; ?>
<form method="POST">
  <textarea name="test"><?php echo $test ? $test : 'lol "test"'; ?></textarea>
  <input type="submit">
</form>

// post_test_wp.php
<?php require_once 'wp-load.php'; ?>
<?php require_once 'post_test.php'; ?>

Basically, when we submit the post_test.php form resulting text field will contain the following text:

lol "test";

While post_test_wp.php will result in the following “slashed” values:

lol \"test\";

This will obviously break compatibility with 3rd party libraries that I maybe have to integrate with WordPress, and it’s just incredible that someone thought it’s a good idea to modify such an important global.

I know that ship to fix that has sailed, as there are many plugins and code that “depend” on this behaviour now, but I’m interested if any WordPress historian maybe knows the reason why this was done in the first place, just as a piece of trivia.

I’m assuming it was an attempt to “sanitize early” by some misguided soul, or to prevent SQL injections in some way.

How close are my guesses?

Why the option ‘Block IPs who send POST requests with blank User-Agent and Referer’ is not activated by default, unlike the neighboring options?

Any specific reasons?

If the only process is to fix, is constantly clear the BB cache I’m going to have to find another way to implement headers and footers.

Thanks in advance.

Thanks & Regards,

For example, when doing a security checkup in the iThemes plugin, the result is to disable the theme editor and one is told (in a round-about-way) to gain access to the file system so as to be able to edit themes, etc.

BUT, WHY?

NO reason is given for what I suppose is someone’s idea that the editing of themes using the WP admin interface is a security risk.

I suspect I’ll receive many replies telling me to ask this question of the plugin developers as opposed to this forum — but I ask you to realize this question is only a specific case of a more general question about WHY things are recommended.

Why im i having a database table with:
Yoast_seo_links – containing alots of (7, 1, 0), values
AND
Yoast_seo_meta

Im not using this anymore, and the plugin have been deactivatet and deleted….

The reason WP is still better in many scenarios is thanks to the amazing 3rd party plugin developers like Yoast, Woocommerce, and myriads of others and the fast and easy “ajaxified” interface.

To put something in a core that at least 10 theme/template “frameworks” doing way better AND still OPTIONAL is absurd.

The funniest that some of the people think it’s the future. The future would be to improve the core functionalities (because there’s a lot to improve) and leave to the user to choose the editor.

In Joomla world, for example, EasyBlog is doing the block editing interface for years (and it’s executed way better compared to Guttenberg) but – for example – for a news portal it apparently slows down the editors work (yes we tested it). Unfortunately, it slows down the work in many other areas and time and effectiveness nowadays is almost everything.

As an option? Sure.

At the core? Why would I choose this when there are better ones out there if a blogger needs it?

____________________________

8 months later:

We tested 8 months later at several of our clients. Same results.

Our clients range from complete newbies to seasoned blog and news portal publishers from 20 to 76 years old women and men (although most of them are not English speakers).

I wonder how the Gutenberg team executes UX tests comparing the current and the Gutenberg editor?
It’s hard to imagine having so fundamentally different results for our teams.

What are your key comparison points when comparing the two editors?