How to show the hidden modules of Jetpack • WordPress Help

If we recently saw how to disable the hidden modules of Jetpack using a custom link and some additional trick, today I will show you the easiest way to access them.

I mean that in the latest versions of Jetpack has been simplified to call it somehow, the desktop of this mega plugin, and the result is that not all modules are shown .

This would not be bad in itself if it were not because there are several hidden modules that are active by default something that I think an error then makes decisions for the user which limits their freedom of what modules to use the plugin do not you think?

Well, for fully recover control of the Jetpack plugin and activate only the modules you want you need all the modules, not just the ones that the Automattic team has decided to see.

And, although it is not very obvious, there they are, there is a link to access it s.

You only have to access any configuration page of Jetpack and go to the bottom of the whole of it .

There you will find a footer in which there are a few links of those usually irrelevant, with information about versions and things like that.

But no, in this case there is a link that, although it does not show with its text clearly what it is for, besides other things, from there you can access all modules.

Exactly, from that DEBUG link you access the so-called Jetpack debugging center in which, in addition to debugging information, below you have the coveted link to all your modules .

[19659004] Well that's it, give it and you'll see the complete interface with all Jetpack modules so you can deactivate the ones you do not use and activate only the ones you want.

Loading …

That may also help you:

How to disable ads and promotions of the Jetpack plugin for free

If you have installed the Jetpack plugin in your free plan you will have noticed that, from time to time, ads appear on your desktop encouraging you to buy your superior plans, backup copies, video, SEO, etc.

You'll see them after posting entries, encouraging you to hire your backup service, when you visit your desk offering advanced statistics, a little bit of everything.

Well, even if it's something nothing documented, you can deactivate those warnings, so you and your customers will not be bothered .

The trick is quite simple, you just have to add the filter with the parameter that deactivates it to your customizations plugin or to the file functions.php of the theme child .

You save the changes and they will not bother you anymore cross-selling ads.

Jetpack eliminates Omnisearch do you want to recover it?

But at the moment the users, and in love, of this tool we have been orphans almost.

Fortunately in the WordPress world nothing dies, it is renewed, it forks, it recreates . So if you want to continue using OmniSearch you can install this tool on your own.

You do not have to do anything, you just install the plugin and you have a search engine in your WordPress management much more organized and practical.

How to remove devicepx-jetpack.js to speed up your website

If you are running the Automattic JetPack plugin you are probably observing in the performance analysis of your web a slowdown due to the script devicepx-jetpack.js which is there to serve images of avatars in large size on screens with high resolutions.

It is actually a script that has almost no sense, less for its purpose, and is an additional script that increases the weight of your pages and slows down their load .

The concrete lines that load the script in the file jetpack.php are these:

The script works loading the file devicepx so you have to disable it with a wp_dequeue in the file functions.php of the son theme or in your customizations plugin :

How to fix HTTP 403 connection error with Jetpack • WordPress Help

An increasingly common error when trying to connect the Jetpack plugin to your account on WordPress.com is the well known like HTTP 403 which tells you that the Jetpack server could not connect to your site.

It's kind of ugly …

Why does the HTTP 403 connection error occur with Jetpack?

For your site to connect with the Jetpack servers in order for modules such as statistics, Photon and many others to work that require connection your web must have enabled the XML-RPC protocol which allows two-way connections between servers.

Ok, so what is XML-RPC?

In case you have not yet you knew, in every installation of WordPress there is a file called xml rpc . [19659010] php located in the root folder of your installation which is the one that allows this type of communications through the XML-RPC protocol .

This protocol is what allows, for example, that you can connect to your sites from the WordPress mobile application, that you can connect Jetpack and many other plugins that use direct server-to-server connection.

Do you want more information about what it is ?, here: What is XML? -RPC and what is it for .

Is there a problem with XML-RPC?

Yes, because it is like an open port to your website, that any attacker with bad intentions could use to take advantage of the known as pingback vulnerability .

Until version 3.5 of WordPress you could activate or deactivate this protocol in your settings but this option was removed , inexcusably, what he has facilitated not a few major attacks on WordPress sites .

How to disable XML-RPC?

The protocol XML-RPC can be disabled in several ways namely …

Disable XML-RPC from .htaccess

Just add this to your file . htaccess :

An alternative method is the following:

Save changes, of course.

Disable XML-RPC from wp-config.php

Also easy, before require_once ( ABSPATH . 'wp-settings.php' ) ; adds the following:

And save.

Disable XML-RPC with a function

You can also add the following code to your customizations plugin or to file functions . php of active topic:

Disable XML-RPC with plugins

You have a lot of free plugins in the WordPress plugins directory that are used to deactivate, completely or selectively, the protocol XML-RPC.

Disable XML-RPC to brava

More expeditious; simply access from the file manager of your server or by FTP to the folder of your WordPress installation and rename or delete the file xml rpc . [19659010] php .

But … should I really turn off XML-RPC?

Well it's something you should decide, but before making that decision review this list of the amount of WordPress functionalities that could stop working if you deactivate it .

My general advice is that you deactivate it, and if you see that something – important – does not work you activate it selectively (then we see how).

Okay, but I did not know that or deactivated anything. Why do I get an error?

Fortunately, yes, fortunately, more and more WordPress users are committed to the security of their websites, and as a result they install security plugins for protect your web And of course, many of these plugins inactivate the XML-RPC protocol.

If this is your case, you should review the settings of your security plugin and avoid blocking it, as simple as that. Where is it ?, depends on each plugin. For example, WordFence does not deactivate but others do.

To not block XML-RPC in iThemes Security go to Security [19659009] -> Settings -> Settings of WordPress and enables XML-RPC , inactive by default if you have this module active.

Another very popular plugin is All in One WP Security . In this case you can disable / enable XML-RPC in Security WordPress -> Firewall -> Rules b á sicas de Firewall – > WordPress XMLRPC & Pingback Vulnerability Protection and there unmark the box called " Completely Block Access To XMLRPC ".

If you want, you can check the following box, which keeps the functionality of XML-RPC but protects you from the pingback vulnerability that I have told you before.

Very cool everything but what if Jetpack does not work that way? I want a solution!

Vaaaale, there may be more things, like your hosting provider has it inactive by default, something that I'm also encountering lately, or other strange causes.

If you've read all of the above and you have clear that you have not deactivated XML-RPC neither manually nor with plugins, and you still want to use Jetpack, then I give you THE FINAL SOLUTION take note …

THE FINAL SOLUTION

It's just 2 steps …

Allows connections to XML-RPC

Open the .htaccess file and add the following:

Save the changes.

With this already we are allowing the connections that JetPack needs and other applications

Disables the dangerous methods of XML-RPC

Next – IMPORTANT – installs and activates this fantastic plugin by Samuel Aguilera that it maintains active XML-RPC at the same time as it protects you from its vulnerabilities by removing the following methods from this protocol:

  • pingback.ping
  • pingback.extensions.getPingbacks
  • X-Pingback of the headers HTTP

You have nothing to configure, is installed, you activate it and it is ready .

Once real Once these 2 steps are completed, you should be able to connect your site with Jetpack and safely …


Questions, opinions, kisses and hugs to the author of this article?

Loading …

may also help you:

Always use the same image in the related JetPack entries • WordPress Help

Not so long ago we saw a lot of tricks for customize the related entries of JetPack and, although I left this on purpose in the bedroom because I did not think anyone would use it, the other day a reader got me out of my error and asked me how it would be done.

I mean forcing the JetPack related input module to always use the same image .

I certainly did not see it utility but the truth is that each web is a world so …

If you want that the related JetPack entries always show the same image regardless of the linked entry, add the following code to your customizations plugin or to the file functions.php of the active theme if you prefer:

function same_imagen_jetpack ( $ post_id $ [19659013] args ) {

$ permalink = get_permalink ( [19659008] $ post _ id ) ;

$ url = apply_filters ( 'jetpack_photon_url' 'http://misitio.com/wp-content/uploads/2016/06/imagen-fija.png' ) ;

return array ( array (

] 'type' = > [19659033] 'image'

'from' = > 'custom_fallback' [19659002] 'src' = > esc_url ( $ url ) ,

'href' = > $ permalink

) ) ;

}

add_filter ( 'jetpack_images_get_images' 'misma_imagen_jetpack' 10 2 ) ;

How not , remember to change the path of the example image to the one you want to strar

Add support for the JetPack social menu

Since version 3.9 the JetPack plugin included the new module called Social menu which allows to create a new menu location in which to include social icons ]

To implement the compatibility of the JetPack social menu the developers of themes must carry out these actions:

Notwithstanding what is said in point 4, JetPack applies certain basic styles, and uses Genericons to create the menus, so if you like them the same you can skip that step.

What is Photon and how does it work? • WordPress Help

One of the most interesting modules of the plugin JetPack is perhaps also one of the most mysterious or unknown so let's put some light on this little free wonder called Photon .

What is Photon?

 jetpack-photon "width =" 550 "height =" 331 "srcset =" http://bootstrapx.com/wp-content/uploads/2018/07/jetpack-photon-550x331.jpg 550w, https://ayudawp.com/wp-content/uploads/2016/01/jetpack-photon-768x462 .jpg 768w, https://ayudawp.com/wp-content/uploads/2016/01/jetpack-photon-840x506.jpg 840w, https://ayudawp.com/wp-content/uploads/2016/01/jetpack -photon.jpg 1080w "sizes =" (max-width: 550px) 100vw, 550px "/> </a></p>
<p> Photon is <strong> one of the modules that you can activate in the JetPack plugin </strong>and being one of the most interesting is curiously those that are inactive by default. </p>
<p> According to the pr oppia web of JetPack, Photon is defined as <strong> an image acceleration service for sites hosted on WordPress.com or connected via JetPack </strong>. This means that it will require less loading time in your hosting and <strong> images </strong> will be loaded faster for your visitors. </p>
<p> The same module describes its function: </p>
<blockquote>
<p> Improve your site by uploading images from the CDN (Content Delivery Network) of WordPress.com. We cached your images and served them from our servers, which reduces the burden on your Web storage provider in a single click. </p>
</blockquote>
<p> That is, it comes to be <strong> a kind of content delivery network or CDN </strong> (Content Delivery Network) in the style of Amazon S3 or CloudFlare, but <strong> hosted on WordPress.com servers </strong>and best of all, <strong> at no cost </strong> nor have to configure anything or create new DNS or anything like that. </p>
<h2><span id= How does Photon work?

To use Photon you just have to go to the JetPack page of your WordPress installation and from the configuration menu or main menu, Activate it

Once active there is nothing to configure, it has no settings page, it works automatically from that moment a copy of each one is created of your images on the servers of WordPress.com and the next time someone visits your website you will see your site as always but the images, instead of showing the copy hosted on your server will be displayed on the servers of WordPress.com, adapted to the right size

Apparently nothing will change on your website, except that it will go faster since the images are loaded from much faster and optimized servers.

If you upload an image to illustrate a new publication the process is the same, your site is connected via JetPack with WordPress.com and will also host the image on your servers, so that it is ready by the time you post it and is visible on your website.

The only way to that someone realizes that you are not hosting the images on your server will be reviewing the published URL of each image, as you can see in the following example before and after activating JetPack's Photon:

As you can see the image is no longer on the web server but on the WordPress.com CDN, of type i1.wp.com /tusitio.com. If you notice it even retains the same relative path of upload and image name.

Some interesting details that you did not know about Photon

  • Photon filters the content but does not make any changes to the WordPress database. ] Photon only acts on the images in the entries and on the highlighted images (image thumbnails)
  • Photon acts on both the old and new entries.
  • Photon only hosts the whole image you upload, without its copies Minor, performing a resize appropriate to the content based on the size values ​​to insert that you define when inserting the image in your entry, the HTML attributes of width and height. In case you do not define any size attribute, it adapts to the maximum container of your input.
  • Photon compresses without loss all the images it hosts using OptiPNG or jpegoptim.
  • Photon is not just a content delivery service but also an image manipulation service. Photon can resize, crop, adjust brightness, contrast and zoom levels and even apply filters to images .
  • If you activate Photon you do not lose anything, your images are still uploading to your server.
  • With Photon you do not save hosting space, because your images keep uploading to your server and creating different sizes.
  • If you deactivate Photon you do not lose anything, the images hosted on your server are loaded.
  • Photon only stores, resizes and serves gif, png and jpg images.
  • Photon can only serve images of servers that serve port 80 (99.99% of the planet's web servers)
  • Photon does not enlarge the images, which would also be horrible and pixelated, it only resizes to smaller sizes, to adapt to the content.
  • If your server takes more than 10 seconds to upload the image to Photon, in the course while uploading the image will appear on the page as if the image is missing, with the resource and broken image.
  • Photon also stores and serves animated gifs but if it requires some resizing then it would be static (this is so even if they are hosted on your server).
  • Photon does not update the cache, it lasts forever. If you want to "update" an image you will have to change the name or upload another one instead.
  • The stacked galleries of JetPack use Photon to work, in fact the images of this type of galleries will be loaded from the WordPress.com CDN even if you do not have active Photon, which means that they activate a "version" of Photon in reality. If you do not want to use Photon you can activate the DEBUG mode of JetPack .
  • Photon also acts on the image thumbnails that are displayed in the JetPack related Entries module.
  • You can use Photon and your cache plugin without problems. In the CDN tab you simply have to indicate that you do not use a CDN, even though you are actually using it.

Does Photon harm my website?

Photon and SEO

In principle might seem that all are advantages when activating Photon because by offering a faster load of your website due to the higher speed of the WordPress.com servers when serving your images, the result is an improvement in many whole navigation experience

And yes, that's true. Activating Photon you get a few load times of your web, which results in better performance and positioning for search engines in the aspect of speed but …

but "is that on the other hand you can lose positioning in the search engines by losing all the traffic to your images which will no longer point to your website but rather to the WordPress.com servers. This is true with any CDN but you must take it into account and weigh what contributes more to the performance and positioning of your website: the speed or visits to the images .

But you must take it into account, as what is clear is that the images hosted on your server will no longer be indexed in Google, that's the case.

Anyway, in my opinion there is no color, it is much better to offer a few load times, taking into account that the traffic coming from images is of very low quality, with some times of permanence in the page ridiculous .

If I have to put in a balance the traffic by the images in front of the of speed and reduction of bounce rate I am clear that Photon wins.

If, in addition, in passing we eliminate the harmful effects of hotlinking on our website because although do it to us no longer consume resources of n Our server, in this sense the advantages win over the inconveniences.

In any case, it is a decision that you must make based on your knowledge and previous statistical analysis, and subsequent checks, as there are situations in which it is better to choose the positioning coming from images. It occurs to me, for example, if you have an infographics site or similar.

Photon ghost URLs

It has been detected that Photon can generate additional URLs on your site even if it is not active, this is because JetPack activates it in part always, for example for the module of related inputs. Fortunately you can disable it completely using the following filter:

Photon and HTTPS

It has been detected that Photon does not get along with SSL certificates because it accepts HTTPS but returns HTTP, but it has an easy solution by applying the following filter: [19659062] add_filter ('jetpack_photon_reject_https', '__return_false');

add_filter ( 'jetpack_photon_reject_https' '__ return_false' )

Rights of transfer of images

Another aspect to take into account would be if there is any right to copy and print the images that you must fulfill, for example if you have assigned rights to an image for your site , but not to house it in a C DN in which case you would have to, or extend the agreement or not activate Photon only for that / s image / s. It's a special case but you have to say it all.

Are there more free CDNs besides Photon?

Of course there are some, but you should bear in mind that none is so easy to activate and use as Photon, here are some how many alternatives to Photon:

So should I use Photon?

If you're not already using another CDN, it's highly recommended. You get the same service but without any cost and without having to configure anything, it works instantly and you get the same as with any of these services, except for the additional features of WAF (Web Application Firewall) that some include.

With Photon you get :

  • Shorter load times.
  • Lower bandwidth consumption of your server.
  • Usability improvements and user experience.
  • Reduction in bounce rate.
  • Less consumption of resources. from the server, which no longer has to display the images.
  • Fewer requests to the database to display the images.
  • You save the cost of a CDN.

In summary, that Photon is one of the reasons why JetPack is a highly recommended plugin, especially for sites hosted on servers with few resources.

JetPack has its stuff and I criticize it a lot, but certainly Photon is a very favorable point, a lot . If you need a CDN and do not want to spend the money it costs or get into cumbersome configurations, or pay an expansion of resources on your server, then Photon is the best option, no doubt.

NOTICE : this publication is two or more years ago. 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: