Do you want to be part of the WordPress story?

One of the great goals of the WordPress community for this year 2015 has been the internationalization the translation of all the ecosystem, and for this they are collaborating many users who, in addition to enjoying all that WordPress offers us, also want to contribute their bit to this wonderful CMS even way of life for many.

Apart from the official translations of the WordPress software and the official website which has been permanently and consistently maintained for years, during this year other related projects have begun to be translated, such as WordPress pages. org of the plugins and themes directories, or the WordCamp Central sites and the local websites.

 wordpress españa espaà ± ol web

Also, there are equipment of collaborators translating each of the mobile applications and other parts of the WordPress world.

The last big decision has been upload to the translation system (GlotPress) all the themes and plugins of the official directories so that the same community of users can / can return the developers the favor of having placed their creatures in our hands.

 directory topics wordpress español

Especially with the plugins, they will all be uploaded and made available for translation although they already have their own translation at least in this initial load.

Later, if the developer prefers to keep his own translation, he will only have to include it in the package before sending it. If you do not offer translation files, they will be available to the community to translate them, of course as long as they are ready to translate .

 directory plugins Spanish wordpress ]

What does this imply?

Well, two fundamental things:

  1. The experience of using WordPress and its websites will be friendlier for all users who do not speak English. It was even shocking for many users to have all the administration and themes by default in Spanish and to access to add themes or plugins that the page and the description of each topic or plugin were in English.
  2. A huge workload is looming for the current translation teams . Until now, a small group of collaborators had to translate the official themes of each version, the complete administration area, the network administration, the plugins included in each version, the applications for iOS and Android, and the packages additional, called Meta, as the theme for official websites by country, the central WordCamp site, and some other things. But now the task is huge, they are there, waiting, all issues (at least 1,440 ready to translate) and plugins (almost 40,000) of the respective official directories. And, of course, there is also all the WordPress documentation of Codex .

Needless to say, we all owe unconditional love to the volunteers who, altruistically, use part of their time constantly to offer us WordPress and , in particular, that is in Spanish.

But they have / we have to be more, many more, and with the help of all we will soon have and offer WordPress entirely in Spanish .

I want to collaborate in the translations of WordPress!

 glotpress español españa

If you have a deep knowledge of English and want to collaborate with WordPress translations it is very easy, you just have to follow these simple steps: [19659022] Create your own account on WordPress.org from this link .

  • Review the manual of the official WordPress translator and also the conventions in Spanish . [19659023] Move to GlotPress choose projects with pending chains and start translating, it's very simple and intuitive.
  •  translate wordpress in glotpress

    With your already created WordPress.org account you will also be able to participate in the discussion and announcement site of the WordPress polyglot team created with P2 to be dynamic and everyone can participate actively.

    In addition, the translation team of WordPress Spain also has a Slack channel in which we coordinate for translations, to which you can request access here .

    I do not speak English, how can I help? ?

     forums wordpress español españa

    There are many ways to give back to WordPress everything that it offers us, for example:

    And what do I gain collaborating with WordPress?

     equipo translation wordpress spanish spain

    The most important and fundamental thing is that by collaborating with any of the WordPress projects you are helping them to keep alive and moving forward, getting better and bigger, guaranteeing their future .

    ] But you also get personal benefits, such as earning respect and recognition from the community, learning and enjoying teaching others, becoming a WordPress guru expert business opportunities , make many good friends and possible collaborators in projects, be part of the history, the present and future of free software in general and of WordPress in particular but above all you will be happier ]because the WordPress community is full of great people who are happy to collaborate and learn.

    What are you waiting for? We are all of us but we are not all of us, we are missing you. Enter the community and become part of the WordPress story .

    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:

    Visual resource map of the WordPress template hierarchy

    The WordPress template hierarchy is the basis for the creation of WordPress themes and in Codex there is a good amount of resources available to know how to create themes and modify them, but not always navigate between pages WordPress.org is the best option, right?

    Perhaps for this reason Rami Abraham was bundled and created a visual resource map in which you can see all the templates and dependencies between them, with the plus that each of the elements links to its corresponding page in the WordPress Codex thus creating a wonderful resource for developers and WordPress lovers in general.

    map of the hierarchy of templates hosted on GitHub, of course admits making bifurcations (or forks as you prefer) so I've encouraged myself and created the version in Spanish to generate l enjoyment of all.

    If you dare, you can collaborate on the official page of WPhierarchy or in the Spanish branch of HierarchyWP .

    Serious vulnerability that affects plugins and WordPress themes • WordPress Help

    Vulnerability takes advantage of misuse of functions add_query_arg () and remove_query_arg () . For years there has been incorrect information in the WordPres Codex s, which although it was modified about a year ago, seems to have led many developers to assume that these functions can do escape ] of user actions at the time of using esc_url () .

    400 of the more than 37,000 plugins of the official WordPress.org repository have been audited, finding the vulnerability up to 15 of them, among which are some as popular as WordPress SEO of Yoast, Jetpack, P3, Download Monitor, which is not a very broad sampling but can give a first impression of the scope of the problem . [19659007] The complete list of the plugins in which the vulnerability has been found is the following:

    Some such as All in one SEO pack or JetPack have already been updated and do not currently contain the vulnerability but check your installation if you are using some insecure version of one of these plugins.

    The vulnerability is not new by far, so if you develop plugins or themes you should review the updated Codex documentation to adapt your code to verify that you are not making undue use of the functions add_query_arg () and remove_query_arg () and that it is not insecure.

    Do you want to help WordPress development?

     wordpress-logo

    WordPress is a CMS made by the community and for the community and without the support of themselves at this time it would not be the best CMS that there would be at present, we can all be part of this community that contributes to the development of this CMS that has helped us many times in daily life.

    There are many forms of collaborate with the WordPress project the source code, testing errors in different environments, creating patches, functions, testing new versions, etc.

    In this article we will recommend some ways you can collaborate with WordPress remains one of the best tools at the web level.

    Trac is an open source software which uses WordPress to manage all types of errors, by generating tickets you can report any error What you have found, security problems, a bad update, you can also manage suggestions for the next versions of the CMS. In this way the community that is behind all WordPress will be able to analyze each of our opinions and give them a solution as soon as possible.

    Work with the WordPress kernel

    Since WordPress is created by the community, anyone can collaborate with the WordPress. base of the code, with this I do not mean that anyone can directly modify the base of all the source code, in order to make these changes it is necessary to create a patch file with the respective changes and send it for review. If these changes are accepted you will probably be in the next version of WordPress.

    To collaborate with code changes and others it is necessary to use Subversion .

    Publication of Plugins and Themes

    To make the publication of some of these two the most indicated is to send them to the directory of plugins and themes that WordPress incorporates on your page, below are the links where they can be sent, in them are the indications of how to do it, just enough to have a account created on wordpress.org

    Plugins: wordpress.org/plugins/add/

    Topics: wordpress.org/themes/upload/

    Create the next documentation

    codex.wordpress.org/Mailing_Lists#Documentation

    Creating documentation is a little tedious and even boring but it is something we all need at some point in order to solve problem s, a good way to collaborate with the community is to update and create the documentation for the next version of WordPress, although it is true that in our Codex we still find outdated documentation of versions much earlier than the actual version and makes it necessary for someone to do this task especially for new users who are part of WordPress.

    Another way to help and not only the community that develops WordPress but also the people who start in this world is collaborating and giving answers to the different topics that are created daily in the attendance forum, here I share the Spanish forum but in each language there is a different one.

    If what you want is a little more agility when looking for solutions, WordPress also has very active chat rooms, to participate you only need to have an IRC client on your PC.

    The main WordPress room is #wordpress [1 9459010]there is also the room dedicated to the development # wordpress-dev and as you can see the rest.

    In the ideas section of WordPress, proposals for the next versions are compiled, here you can vote for the ones that most call your attention and think suitable for a next version, all these ideas are reviewed before beginning with the development of a new version to evaluate its implementation in WordPress.

    These are the main ways to help the WordPress evolution, if you know others that also help, you can comment on them in our comments section.

    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:

    The 10 commandments of the WordPress developer

    Being WordPress developer does not require special abilities, different from those of programming in PHP or CSS, but if there is tips that can make a difference and develop solid developments and, above all, without problems for him or his clients.

    That is why I thought it convenient, because the tips are right, translate this list prepared by Floris P. Lof :

    1. Always define WP_DEBUG to true during development

    You can not imagine the number of code error notifications that you will receive from plugins and themes. All these low level warnings can cause memory failures, which will reduce the performance of the site by consuming more memory than necessary. WP_DEBUG is also a very useful tool to discover if you are using obsolete functionality.

    2. Stay tuned to the WordPress code and CSS standards

    The WordPress standards have been established after years of experience. If you abide by these rules you will get a clean and easily readable code for yourself and others. Hence the slogan "the code is poetry" ..

    3. Comment your code

    Your code should not only be easy to read by others but you should be able to let the rest understand why you chose to write a code in this or that mode. There are many ways to dress a saint, but explain your choice following the instructions in Codex .

    4. Learn how the WordPress "core" works, read the actual lines of code

    You should know how WordPress works internally. When are the plugins loaded in mulsitis? When are requests made to the database? When are the files loaded? and all that. You can learn a lot from reading the "core" of WordPress.

    5. Use the functions and internal WordPress APIs whenever you can

    Do not dwell on the wheel, before writing code learn if there is a function or procedure that is already in the "core". Learn from the "core", as I have pointed out before, and discover how everything works. You will be surprised by everything you will find there. Some examples would be these utility functions .

    6. Put pommery to your code

    There are many people who write code for WordPress in themes and plugins. And it's quite possible that your function name, or variable class, is the same as someone else's. For that reason you should always put pomp, like your initials or your website. For example (AW):

    aw_display name ();

    7. Never trust the user's action! Sanitiza & escape!

    This is a major problem, now and maybe forever. WordPress is loaded with tools that allow you to write secure sites. A good idea would be the chapter 6 of this book . You already had it, right?

    8. Use nonces

    This would be an extension of the previous commandment. Using "nonces" ensures all the functionality your forms need. Review this Codex page

    9. Locate your code

    In Europe, unlike in America, we are very used to writing in several languages, so it is not surprising that a client asks you to have a theme or plugin available in another language or dialect. [19659003] So write your code thinking that it is "internationalizable". This will make adding another language in the future easier.

    10. Performance, performance, performance

    You have to develop high performance sites. In all the code that you write or include, be it a request to the database, PHP code, HTML, CSS, JavaScript or attachments as images, always bear in mind the performance. Every nanosecond counts.

    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:

    Check if your WordPress theme meets the standards

    Whether you are a developer of topics, or an administrator or blogger who is aware of the standards, you are sure would like to know if the theme that you use or are programming meets WordPress theme review standards .

    There is an official page in the codex where you have the standards compliance guidelines for WordPress themes, which you can use as a checklist for your theme, but what if we automate it a bit?

    Well it's also very easy, because we have a plugin, Theme check that once installed, from your page of administration, located in " Appearance -> Theme check ", makes a check of any topic that you have installed in your WordPress even if it is not active.

    The only advice is that you previously activated [19659006] wp_debug something that you should do even before installing them, because you will have an extra revision by means of the error messages in any operation, it is a pain in the ass to have it always active but now it would be a good opportunity for you to wp -config.php you had the line …

    Then, if you want, you pass it to false or you delete the line .

    Once you choose the subject to check and click on the button " ] Check it "will offer you in the same window a series of warnings or recommendations to adapt the theme to the standards . And yes, also the default themes, like Twenty Eleven, use functions that could be improved, as you can see in the capture.

    It is a great tool especially for developers, but also if you are a client and you want to try the work that someone else has prepared.

    A final advice, click on the box labeled " Supress INFO " if you do not want notices of manual changes that you have made to This is what will show you mainly.

    There is also something similar for plugins ( Plugin-check ) but it has not been updated for a long time so it is not reliable.

    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:

    All WordPress source code • WordPress Help

    When we have seen web applications and WordPress function listings, I did not notice that there is also an official website where all the WordPress code can be displayed online, function by function.

    So today we are going to add one more address to our list of sites to review and learn more about the WordPress source code: phpdoc .

    Best of all, you can browse all WordPress functions, filters and hooks by version, even in what has to come. Once inside the code browser you will find an explanation of what it is for and examples of use, which is much easier to use than Codex itself.

    And I do not wrap it up anymore, we simply list the resources for developers from WordPress that we have seen so far:

    Search the WordPress Codex from the front page of your website

    Okay, this trick is a bit of a geek, but surely for blogs like Help WordPress makes a lot of sense, when you're reading any post, do a search on the WordPress Bible , the Codex and document more.

    Anyway, if you cheer up with this trick, that grace has it in that you can customize it – of course – to your liking and look where you want, just you will have to add (as always) a small code to the function plugin or file functions.php of your active theme to add a great and functional additional search engine, which will return you Codex WordPress results .

    1

    2

    3

    4

    5

    6

    7

    8

    9 [19659004] 10

    11

    12

    13

    14

    15

    16

    17

    function wp_codex_search_form () {

    global $ wp_admin_bar $ wpdb ;

    if ( ! is_super_admin () || ! is_admin_bar_showing () ] )

    return ; [19659000] $ codex_search = '

    <input class = "adminbar-input" maxlength = "100" name = "search" size = "13" type = "text" value = "' . __ ( ' Find something in the Codex ' 'textdomain' ) . '"/>

    '[19659027];

    / * Add the menu item * /

    $ wp_admin_bar -> add_menu ( array ( 'id' = > 'codex_search' 'title' = > __ ( 'Search in the Codex' 'textdomain' ) 'href' 39] = > FALSE ) ) ;

    $ wp_admin_bar [19659076] -> add_menu ( array ( 'parent' = > 'codex_search' 'title' = > $ codex_search 'href' = > FALSE ) ] ) ;

    }

    add_action ( 'admin_bar_menu' 'wp_codex_search_form' [19659027] 1000 ) ;

    The function add_menu () used, which we have already seen in other examples, accepts some parameters that you can also adapt to your tastes and needs:

    QueryPosts, as the WordPress Codex should be

    The Codex is the WordPress Bible but I've always thought that it lacks functionality for to quickly document any function or hook needed to program.

    If I had to choose the next Codex tool I know it would be something very similar to QueryPosts .

    QueryPosts is a website that offers a predictive search (shows results as you type) of WordPress functions and, once you have identified the one you want, then, first, a list of the arguments that you can use, as well as the path where " call "to the function.

    In that screen, in addition, you can click on the function name, and then have a very complete screen in which we describe the same, its uses and we are given up to the. Everything very visual, simple and usable.

    Come on, what the Codex should have, do not you think?

    Thumbnail linked to permalink • WordPress Help

    WordPress allows us to include thumbnails on the cover of our site in a simple way, but by default that thumbnail does not link to the permanent link.

    If you want the thumbnails, or highlighted images if you prefer call them, have a link to the permalink of the entry you just have to add the following code in the file functions.php of your active topic:

    add_filter ( 'post_thumbnail_html' 'wps_post_thumbnail' 10 3 ) [19659000];

    function wps_post_thumbnail ( $ html $ post_id $ post_image_id ) {

    $ html = '<span class = "removed_link" title = "' . get_permalink ( $ post_id ) . '">' . $ html . '' ;

    return [19659018] $ html ;

    }

    Then, it would be convenient to make an adjustment in the loop so that if not there are thumbnails do not try to link to permalink in any way, this: