Do you hate the WordPress Personalizer? Here you have the solution

And among those haters there are some developers who have gotten to work and have created a plugin that will return your WordPress to before the Customizer, at those not so distant times where we customized the WordPress aspect without leaving the administration.

The spawn is called Customizer remove all parts or WP-CRAP and, once installed and active, prevents the Customizer scripts from loading remove all links and buttons that carry the Customizer from the WordPress desktop and the administration bar. Come on, a full cleaning.

I do not know what you'll think of this idea, but to me it seems crazy, charming but crazy . The good thing is that the WordPress community is so wide and varied that it offers everything.

I'm not going to use this anti-Customizer plugin because I think this utility, despite the improvements that still needs is part of the future of WordPress to compete with platforms such as Wix or other constructors, known as " page builders " so in vogue these days, but for options that do not remain.

Robot Google does not access CSS JS files

Surely you have received in your email an email from Google Webmaster Tools now called Google Search Console which warns you that " Google's robot can not access the CSS and JS files of ", and of course, the scare is morrocotudo, not to mention if you have several sites and you have received a few messages of these, right? And you will receive them.

 google robot does not access css js

Well, everything has its explanation, and especially solution.

Why Google cares about CSS and JS files?

It is well known by all that what really matters about a web is the content, then what is this sudden interest of Google for the CSS and JS files?

The fact is that although Google is capable to properly track your website without loading CSS and, above all, without having to check each JavaScript, the reality is that each time more CSS and JavaScript plugins are used that also manage and show content, let's not say for visualizations from mobile devices.

In addition, Google likes to analyze the "quality" of websites and their visualization for the end user which is why he also cares, not only the content itself, but also also how your website will be displayed for the user Aryan, and for that reason you want to have "the full picture" of your website, and that includes CSS and JavaScript.

It's more does it sound like the importance of offering your website adapted to mobile? ] So that.


Why Google can not access CSS and JS files?

Simple, blame yours surely . Let me explain …

Historically, the recommended rules for file robots.txt the one that tells Google what to crawl and what not, included blocking internal WordPress folders , those that do not have content but are useful for the CMS. Logically I am referring to wp-admin and wp-includes .

In this way, the robots.txt typical and basic file of a WordPress installation is usually be a thing like this:

And it's fine to block the folder wp-admin since it's like the WordPress operating system that manages the management area, and there is nothing that interests Google and should not appear in the search results, but not so the folder wp-includes because there reside the JavaScript files that contribute to the rendering ] of your website, and its content .

In the notices that have been received since yesterday most of the errors are from JS since it is not so usual to block CSS files, but h And to review everything.

What's more, you should not only check the websites on which you have received notices but on all you have, for avoid Google tracking errors .

How do I get Google to access the CSS and JS files?

The first thing is to ignore the Google email (more or less) and go through the Google Search Console to perform These 3 steps:

  1. Review the blocked resources
  2. Modify the robots.txt file so that it stops blocking them
  3. Explore, process and validate your website from the section " Explore as Google " Search Console

See it?

1. Review blocked resources

Manage the affected website – or not – and visit the section called Google Index -> Blocked Resources . There you will see a chart and a list of blocked pages.

 resources blocked by google

In the list you will see a little bit of everything, but you should focus on the URLs that point directly to your website and click on that line to check which pages are blocked from your site.

You only have to click on any of them for Google to show you what actions you should take, and in this case, of the 3 options it offers you, you should go directly to the third one, to Tester robots.txt to check what you are blocking.

 resource blocked by google

In the tool, located in the menu Crawl -> robots.txt Tester of the Google Search Console, you will see your current file robots. txt and conveniently marked in red or yellow errors and warning s. In this case it is normal to find a very fat red error pointing to the folder / wp-includes / which you already know is from WordPress.

 robots. txt tester

How do I unlock pages with errors? Well, let's go to the second step …

2. Modify the robots.txt file so that it stops blocking them

To remove the locks obviously we have to modify the file robots.txt and we have several ways to do it

2.1 Modify the robots.txt file manually

If you are not afraid to modify files on your server simply access from your hosting panel or via FTP and manually edit the file robots.txt that you will find in the root folder of your site. Simply delete the line that blocks the CSS and JS, normally that says:

Save the changes and that's it.

2.2 Modify the robots.txt file with plugins

If you prefer to use plugins you can help with a couple from them. On the one hand there is a specialized one called WP Robots.txt that simply adds an editor of this file so that you add or remove rules to your liking. I think there's no need to tell you what you have to remove, right?

 wp robots txt plugin

You save the changes and drive.

The other possibility, which is which you will almost certainly use, is to use the SEO plugin file editor tool such as All in one SEO Pack or Yoast SEO which you will probably have already installed. In this case the process is as follows:

Modify robots.txt with All in one SEO Pack:

  1. Active modules of Robots.txt and File Editor from the menu Feature manager if they were not already.
     edit robots txt in all in one seo pack
  2. You access the File editor and delete the line that is causing the errors and save the changes.
     change robots txt all in one seo pack

Modify robots.txt with Yoast SEO:

  1. You go to Tools -> File editor
     activate editor seo yoast files
  2. If you do not already have a file created, or Yoast does not detect it, you give the button to create it
     create file robots
  3. Modify the file by deleting what is blocking Google and save the changes
     eli minar reference locked robots

It's really easy. Then just check that your file robots.txt has been saved correctly by accessing .

3. Explore, process and validate your website from the section " Explore as Google " of the Search Console

Once all of the above is done, all that remains is to validate your website, but first it is worth checking that Google no longer shows errors related to the file robots.txt .

To do this we will go back to the Google Search Console and go through the section Crawl -> robots.txt Tester to see if the new file is displayed and there are no errors. It may take a while, so do not panic if you do not see the new one on your first login.

 Robot tester after solution

When we already have the certainty of that there are no errors we go to the final cited step of Explore as Google to process and validate our website.

 explore as google

The page in question is in Crawl -> Explore as Google and the process is as follows:

  1. Press the button Get (or the one of Get and process ) for Google to explore our website. We must do this for each of the options in the drop-down that is just before the enormous red Get button, which are:
    • Desktop
    • Mobile: smartphone
    • Googlebot-Mobile: XHTML-WML
    • Googlebot- Mobile: cHTML
  2. We wait a few seconds for the process to be performed in the lower list and press the button that will appear called Send to the index .
     send to the index after processing

You must bear in mind that Google Search Console allows you only 10 posts per month to the index so do not be thrilled with this tool.

Nothing more, nothing less . With these simple steps Google will be able to correctly track your website. Of course, as I said before, do not wait to receive an email from Google to do the verification.

What do not you still use the Google Search Console? Well, you're already late . Not only allows you to check and improve the SEO of your website but it warns you of these errors and many others, some even related to WordPress .

Hala, share this so that others also know how to do it and it buzzes to the Google Search Console .

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:

WordPress security guide of the National Cryptographic Center

If you are looking for a WordPress security guide you may have finally found the definitive manual, at least in quantity and quality of content .

The creator of this jewel for every WordPress user and developer is nothing less than the National Cryptographic Center of Spain, which within its guides – where there is everything and good – you will find the 460 ] dedicated especially to WordPress .

The guide is enormously complete, with 94 pages covering almost everything, namely:

The guide itself and the information it provides It is top quality, with many good tricks, screenshots and codes. Perhaps the only downside that I can put is to focus on the use of iThemes Security plugin that, even being the most popular, I think it has better competitors, but otherwise is a great manual, with very valuable information , updated and quality. Essential .

What is said, a document essential in your WordPress library which you can download from the CCN page or from here on the following link.


How to turn off emails for automatic WordPress updates • WordPress Help

I think almost everyone will agree that automatic updates of WordPress security and maintenance versions introduced in version 3.7, they are an improvement of those that mark differences, but it also has its things, like the update notices.

Because, let's see, if you do not want WordPress to bother you having to update the security versions. What does it mean to notify you by email when it has done so? we had not been in that we trusted WordPress?

Ok, that's fine to have us informed but what does it mean when it has been updated? Nothing.

So said and done, we will see how to remove those annoying WordPress messages that has been updated to this or that version and that is very cool and protects you from such and such

 your wordpress site has been updated

Disable WordPress update emails with plugin

The most immediate solution, although you will tell me that a little beast, is to use such a plugin Majete and tremendous like Easy updates manager . That's right, it works for many other things, all related to WordPress updates, but among them is exactly what we are looking for: to deactivate that nightmare of emails that WordPress has been updated .

install, activate and go through the settings page, located in a prominent place as a submenu of the Desktop Start, and in the first tab you have it, there a little below, where it says Notifications . Just change the box to Disabled save the changes and fixed

 disable email updates wordpress

Incidentally, although I have already noted at the beginning, this plugin is the boat host . Everything related to the updates – or not – of WordPress you can manage with it, so take a look because it deserves it. As a summary it allows you all this:

  • Of course, disable the warning emails
  • Activate / deactivate all updates
  • Activate / deactivate the major updates
  • Activate / deactivate minor updates
  • Activate / deactivate automatic updates of plugins
  • Activate / deactivate automatic updates of themes
  • Deactivate automatic updates of translations (that in case you did not know they are updated alone taking advantage of any other update)
  • Decide which users can see and activate updates
  • Activate / deactivate automatic updates of plugins and themes one by one
  • … some more things

What's said, a gem

Disable emails from WordPress updates with code

If you prefer do not install a cojonoplugin like the previous one, but do it stylish and super pro 13]then nothing simpler to add to this utility plugin or to the file functions.php this line that I put at your disposal with great pleasure:

Save the changes and live the life, which are two days.

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:

How to improve WordPress emails?

For some time the WordPress Personalizer has been talking on the forums and websites since as Fernando explained well in this post there are many conflicting opinions, especially since the inclusion of the menus in it was approved.

I, as a plugin developer, had never used it for any and only knew it as a simple end user. Sometimes I found it useful and others just too loaded with options so I did not have an opinion for or against it and just preferred not to enter into debate.

If you are wondering what this has to do with WordPress emails, worry that we will get there, I just want to explain where everything is born.

In the last WordCamp that was made in my country, one of the speakers gave some advice on how to use the Customizer in plugins and I call so much my attention that I keep thinking about it.

A few days later, making a site for a client who needed to improve the design of the emails to send, I realized that the the only viable option was to use WP Better emails but I did not quite convince myself, so I decided to create my own plugin for edit an HTML template using the Customizer.

That's right co mo plugin was born Email Templates a simple plugin that you allows to use an HTML template to send emails instead of the boring text format that comes by default with WordPress.

 emails-templates "width =" 838 "height =" 366 "srcset =" 840w, https: / / 550w, 1252w "sizes = "(max-width: 838px) 100vw, 838px" /> </p>
<p> The plugin is very simple and you <strong> can change various aspects of the template </strong>such as colors, add a logo or text in the header and a little more text on <em> footer </em>. </p>
<p> It also includes a series of <em> placeholders </em> to use both in the template and in the content of the emails. And finally a button that allows you to send a test email to check that everything was as it should be. </p>
<p> Email Templates <strong> requires version 4.0 </strong> of WordPress because it uses some functions that were introduced in that version </p>
<p> If someone wants to help you can do it through <a href= GitHub or also help translate it .

Personally I think the Customizer is great, the API for using it is very simple and for an end user the experience can not be better since it sees all the changes instantaneously. Now it's just a matter of users getting used to it and the developers to implement it.

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:

Important security update • WordPress Help

You should have already available on your desktop, or you should have automatically updated WordPress to version 4.2.3, a major security update .

In particular WordPress 4.2.3 is an update that solves up to 20 errors, but above all an important threat of Cross Site Scriptiong (XSS), in addition to another error by which a user with the profile of Subscriber could use the meta case of the Desktop to post an entry.

Your Majesty the Customizer • WordPress Help

With the recent betas 3 and 4 there are new additions to the news of WordPress 4.3 and all the relevant ones have to do with the Customizer, which is gradually acquiring a vital importance in the present and future of WordPress .

If a few days ago we saw that the menus were also incorporated into the Personalizer controversial included, now it is the novelty of the site icon, or as it is called from now, Site Identity who adds to this one-on-one customization of the aspect of your WordPress.

But the thing is not there, since the same Personalizer leaves the nest of the management of the Appearance, having its own space in the site's administration menu, as a fundamental element of the personalization of your website.

And okay, it's okay, it's logical, but then should not it? pass the menu appearance under the command of his Majesty the Customizer … I say

More than anything because within the WordPress administration the Customizer continues to occupy space as a submenu of appearance, and in the administration of the site the links to the Widget management and Menus are still there in the main menu. Come on, an incongruity that I hope will be fixed so as not to continue dizzy with these nonsense.

What is WP_DEBUG and how to use it

If you are a developer, when you are programming a theme or plugin you must have a controlled environment but active WP_DEBUG ?. Well you should.

The activation of WP_DEBUG in WordPress development environments is greatly recommended . Putting it into operation is a simple operation that will reward you with great benefits for your work.

So let's see what this is about.

 stethoscope computer

What is WP_DEBUG? [19659007] WP_DEBUG is a simple permanent global variable, also known as PHP constant, introduced in WordPress 2.3.1, which you can use to enable or disable debug mode in WordPress .

Default mode debugging is inactive, but it is practically essential to activate it when you start a development work of themes or plugins .

WP_DEBUG is launched from the WordPress configuration file, the famous wp-config. php normally located in the WordPress installation folder, although you can find it somewhere else.

In principle the activation of WP_DEBUG is simple, you just have to put it in true or false depending on whether you want it to be active or inactive respectively.

In this way, to activate WP_DEBUG simply add the following line to the file wp-config.php :

And to turn debug mode off, change it to the following:

Una Once WP_DEBUG is active, debug messages and PHP notices will appear on the pages of your website. These messages usually help the developer to detect problems with the code, which might otherwise go unnoticed.

Now, the mere fact of activating WP_DEBUG is not enough. It is important to keep a record of errors for later review, something that we can also activate, better not?


If you want to save the errors and notifications in a registry file where you can review them afterwards, you just have to activate the WP_DEBUG_LOG functionality. Putting it in true will save all errors and messages in a file named debug.log located in the folder / wp-content / .

Activate WP_DEBUG_LOG is so simple, again, how to add this to the file wp-config.php :

Save changes made and from now on WordPress will keep a log of all messages and errors in the file debug. log . Then you just have to review the code of your work to solve it.

Now, it occurs to me that if we are already saving the messages and errors in a file, what is the need to continue seeing those ugly messages and errors on the screen while programs ?

We are going to see the solution to this annoyance.


If we already have a file of the errors and messages we can avoid that they are shown in the pages in which they are generated. for this you have to activate the PHP constant called WP_DEBUG_DISPLAY. Once the debug mode is still active, messages or errors will not be displayed on your site.

Again, it is very easy to activate it, you just have to add one more line to the file wp-config.php :

In summary , that if you want to activate the debugging, that the messages are saved but not shown, the lines to add to wp-config.php would be the following:

That's it … that's it … that's all friends

And now, it's not complicated but it's a very useful tool for the developer, essential I would say. When you create or modify code for WordPress it is vital to check any possible error in it to be able to solve it, to debug it and offer a clean and professional code to your clients .

Of course, then you have to remember to disable the WP_DEBUG debug mode when you finish scheduling, for obvious security reasons.

Did you know the WP_DEBUG debug mode? What's more, do you use it?

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 that we have not warned you.

Loading …

That may also help you: