WordPress already moves 16% of all Internet

WordPress is on such a growth curve that it will soon become a real monster, if it is not already, of the network.

Either on WordPress.org hosted on its own server or WordPress services. com, the fact is that WordPress already moves 16% of the Internet and keeps growing.

From time to time I share the figures of, for example, downloads of the new versions, and each new version exceeds

For example, the current WordPress 3.4, in a week already is on its way to 3 million downloads and that only in the first version, without updates, another symptom of the tremendous implementation of WordPress in the network.

BuddyPress 1.6 will require WordPress 3.4

If you are a user of BuddyPress the plugin that converts WordPress into a complete community with functions of social network, forums and messaging, you should know that in the list of changes is reflected that will require WordPress 3.4 .

So if you plan to upgrade to BuddyPress 1.6 when it is available before check that your theme and other plugins are compatible with WordPress 3.4 before to update to the new version of BuddyPress.

To the new version it looks good little so do not miss out on all news of BuddyPress 1.6 like privacy in profiles, integration with Akismet, incorporation of bbPress 2.0 and more, or WordPress 3.4 and go testing

WordPress Editor and Desktop in a single column "by default"

Yesterday Juan Santiago asked how it is done for that the WordPress Desktop is seen by default in a single column so you do not have to waste time giving explanations to your clients.

And since I am very well sent and, fortunately, it is very simple, here is the requested trick …

You just have to add some code to your function plugin or file ] functions.php of your active theme and you already have it, this:

// Editor to a single column by default

function so_screen_layout_columns ( $ columns

) {

$ columns [ 'post' ] = 1 ;

return $ columns ;

}

add_filter ] ( 'screen_layout_columns' 'so_screen_layout_columns' ) ;

function so_screen_layout_post () {

return 1 ;

} [19659002] add_filter ( 'get_user_option_screen_layout_post' 'so_screen_layout_post' ) ];

This trick is applied to the ticket editor, where it is especially interesting for users with small screens of Netbooks or even Tables, in which the HTML and Visual tabs sometimes overlap, or simply more space is needed to have everything by hand in the editor.

But since I know you're going to ask, here's the code, adapted so that the main Desktop window also comes to a column by default, in case you need it.

// Desktop to a single column by default

function so_screen_layout_columns ( $ columns

) {

$ columns [ 'dashboard' ] = 1 [19659008];

return $ columns ;

}

add_filter ( 'screen_layout_columns' 'so_screen_layout_columns' ) ;

function ] so_screen_layout_dashboard () {

return 1 ;

} ]

add_filter ([1 9459020] 'get_user_option_screen_layout_dashboard'

'so_screen_layout_dashboard' ) ;

As you see, it only requires a minimum change.

Make the "Screen Options" disappear from the WordPress Desktop • WordPress Help

Although there are many people who take a lot to discover the tab " Screen Options " of all the WordPress Desktop windows, there it is, and is very useful especially in the ticket editor.

Now, there are situations in which it does not interest that users walk " by tapping " those options and you prefer that they have the options that you have defined by default, something quite common in uses of WordPress as CMS .

For these occasions there is a very simple trick with which to make that tab disappear to avoid restless hands. You just have to add the following code to your function plugin (you can also do it in the file functions.php of your active theme but this is better in the plugin):

You save the changes and you already have it.

JetPack as a substitute for Feedburner for email subscriptions • WordPress Help

Feedburner is a very effective feed subscriptions manager and most of all is almost the only decent subscribe for email subscriptions but lately it seems that Google has it quite abandoned . If some time ago he had included the possibility of sending new publications to your favorite social profiles, not many months later he eliminated this functionality practically without warning and betrayal.

And this is just an example.

So why not look for a substitute for email subscriptions ?, it's more and why not look at a plugin that many of us already have installed? . Yes, I'm talking about JetPack which curiously has an email subscription system that also works great.

But you'll ask is it a good option or a substitute for Feedburner? surprisingly yes, and it improves in some aspects.

For example, its greatest virtue is that new publications are not sent once a day but are automatically issued thereby in less than half an hour your subscribers have in their email your new article .

Another advantage is that, when most email subscription plugins (there are and many) use the function ] wp_mail from WordPress, the email subscription system of JetPack sends the updates directly to the servers and from the servers of WordPress.com, which is responsible for distributing them .

There are more, and that is that your subscribers can manage his " readings " of WordPress.com and subscriptions to webs with this JetPack system in a single site, in his WordPress.com reader, and choose to send the publications.

Additionally, to You, you can follow the activity of subscriptions in the JetPack statistics system .

I think there are enough reasons, and more than Feedburner offers. Do you dare ?, Well let's see how to activate them …

1. Activate the JetPack subscription system

The first thing is to go to the JetPack screen (which you have to install before, of course) and activate the subscription system if you have not already done so.

2. Set up subscriptions

The next thing is to configure some subscription settings. For this you have a button just activate the subscriptions, but you will also find them manually in "Settings -> Comments" of the WordPress Desktop.

In both cases you get to these 2 adjustments, to decide if you offer a full subscription under the comments form of each entry or alone, or also to each new comment, which also serves as a subscriptions system to new comments, double function.

And what you will see on your site will look something like this:

3. Offer the subscription by email

In addition to the box we have seen before, like Feedburner, we have a form to facilitate the subscription by email anywhere on our site, in this case in the form of a widget, and very easy to configure.

In "Appearance -> Widgets" of your Desktop you will find the new subscription widget to be able to add it where you want from your sidebar …

From which you can configure As you like the messages that your visitors will see, to decide how to encourage them to subscribe, something like this could be …

If you want to personalize, and you're not afraid to touch code, you can tune to your liking the form following these indications .

4. Managing your subscriptions

Finally, in the JetPack statistics screen, you will find a message with the number of "followers" (this is only for you) at the left, which are the subscribers to your site.

If you click on the link of the " followers " you will see a full list of your subscribers, with their emails and the time since they subscribed, that for obvious reasons of respect for privacy I will not reproduce.

The emails they will receive are in HTML so they are fully operational for what a subscriber by email it must be offered, not like some subscription plugins by email, that send text-mode publications.

Also, as with Feedburner, your subscribers will receive a previous email to confirm the subscription, like so they can always manage their their scripts and cancel them so respect for the decisions of your subscribers is also total.

Something that is also great is that this system you have both WordPress.com and your WordPress hosted on your server.


As you can see, it is a complete system, if you hurry me more than Feedburner, which only offers a code to use in a widget and customize a bit, and the list of subscribers. The only thing that Feedburner gives you is a system for to export that list as an Excel or CSV file to customize the source and logo in the email and nothing else.

What nobody offers you, and that is the biggest handicap when deciding on one system or another, and for which sometimes it costs to be encouraged to change it is a system of "exporting import" subscribers, but it is not so serious, some will continue to receive their subscription by Feedburner, if you already had it, and the rest will do it from your JetPack, as simple as that.

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:

Video tutorials to create themes for WordPress • WordPress Help

Hello, I'm writing this time to recommend some video tutorials to learn how to create themes for WordPress. They are very easy to understand, and they are on the website of Cesar Cancino and made by Ricardo Antonio Gutierrez Morales . The truth is that other tutorials to create topics did not teach me as much as these, because they left things out of comprehension.

I hope it helps. They are very easy to understand.

Here I leave the topic that I am creating. It is missing the comments template and some more adjustments.

Disable automatic links in the comments

If you do not want links in the comments, or at least that those links are not active you can deactivate them all by default.

WordPress, by default, and unlike in the editor, makes any URL that someone puts in the comments is " clickable " that is, that it becomes an active link.

Of course, you can configure comment settings so that any comment with a link is in moderation queue, but remember that you must adjust it personally because by default it allows comments with a link, only for those that have 2 or more.

In any case, a way to avoid outbound links, and only the one who really wants to review a reference copy and paste the URL and visit it, and in the process limit the number of outgoing links of your site, then an excess of outbound links could penalize your SEO positioning is to use this trick.

All you have to do is add the following code to your function plugin or inside the file functions. php of your active topic:

You save the changes and that's it, the URLs in the comments will no longer automatically become links.

Nice trick found a while ago in WPrecipes which I never remembered to share until now

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:

bbPress 2.1 beta 1

It seemed that the thing had stopped but no, we already have the first beta of bbPress in its version 2.1 which soon, very soon, will be available in its final version, since remain very few open development lines .

Version 2.1 will solve a good number of failures, and the main novelties are the following:

At the moment, although it is not advisable to use betas in running sites, ] you can download bbPress 2.1 beta 1 and try it in a test forum.

WordPress Constants – Complete list and description

In the " back room " of WordPress you do not have an entry field for every possible modification. Only some are available through an action or filter, and for some changes you will have to define or change a PHP constant .

In this article, for you to have a query tool, you have the [19659004] list of all native WordPress constants not including obsolete constants.

A constant is an identifier (name) for a simple value. As the name suggests, that value can not change during the execution of a script. A constant, by default, is case-sensitive, and by convention the identifiers are always uppercase ( PHP docs ).

General

  • AUTOSAVE_INTERVAL # [19659009] Defines a range in which WordPress should auto-save.
    Value: time in seconds (Default: 60 )
  • CORE_UPGRADE_SKIP_NEW_BUNDLED #
    It allows you to skip new files in packages as in plugins and / or themes in updates.
    Values: true | false
  • DISABLE_WP_CRON # [19659009] Disables the WordPress cron function.
    Value: true
  • EMPTY_TRASH_DAYS #
    Controls the number of days before WordPress permanently deletes entries, pages, attachments, and comments from the recycling bin.
    Value: t Time in days (Default: 30 )
  • IMAGE_EDIT_OVERWRITE #
    Allows WordPress to overwrite an image before editing or saving the image as a copy.
    Values: true | false
  • MEDIA_TRASH #
    Activate / Deactivate the recycle bin function for the media.
    Values: true | false (Default: false )
  • WPLANG #
    Defines the language in which WordPress will be used.
    Values: For Spanish en_US
  • WP_DEFAULT_THEME #
    Defines the default theme for new sites, it also serves as backup in case of failure of the active theme.
    Value: [19659018] theme name (Default: twentyeleven )
  • WP_CRON_LOCK_TIMEOUT #
    Defi ne a period of time in which a single "cronjob" will be completed. From WordPress 3.3 .
    Value: time in seconds (Default: 60 )
  • WP_MAIL_INTERVAL #
    Defines a period of time in which a single email request can be made.
    Value: time in seconds (Default: 300 )
  • WP_POST_REVISIONS #
    Enables / disables the entry review function. A number greater than 0 defines the number of revisions for entries.
    Values: true | false | number (Default: true )
  • WP_MAX_MEMORY_LIMIT #
    Allows you to change the maximum memory limit for some WordPress functions.
    Values: See in PHP docs (By default : 256M )
  • WP_MEMORY_LIMIT #
    Defines the memory limit for WordPress.
    Values: See in PHP docs (Default: 32M for Multisite 64M )

State

  • APP_REQUEST #
    Defined if there is a request for the publication protocol Atom .
    Value: true
  • COMMENTS_TEMPLATE #
    Defined if the comment template is loaded.
    Value: true
  • DOING_AJAX #
    Defined if there is a request AJAX .
    Value: true
  • DOING_AUTOSAVE #
    Defined if WordPress is autoguarding entries.
    Value: true
  • DOING_CRON #
    Defined if WordPress is performing a cronjob.
    Value: true
  • IFRAME_REQUEST #
    Defined if there is a request inlineframe .
    Value: true
  • IS_PROFILE_PAGE #
    Defined if the user changes the settings of his profile.
    Value: true
  • SHORTINIT #
    Can be set to load only the half of WordPress.
    Value: true
  • WP_ADMIN #
    Defined if there is a request on the WordPress desktop. [194] 59029] Value: true
  • WP_BLOG_ADMIN #
    Defined if there is a request in / wp-admin / .
    Value: true
  • WP_IMPORTING #
    Defined if WordPress is importing data.
    Value: true
  • WP_INSTALLING #
    Defined in new installations or updates.
    Value: true
  • #WP_INSTALLING_NETWORK #
    It is defined if there is a request in the administration or installation of the network. From WordPress 3.3 before it was WP_NETWORK_ADMIN_PAGE .
    Value: true
  • WP_LOAD_IMPORTERS #
    Defined if you visit the Importer ( Tools → Import).
    Value: true
  • WP_NETWORK_ADMIN #
    Defined if there is a request in / wp-admin / network / .
    Value: true
  • WP_REPAIRING #
    Defined if there is a request in /wp-admin/maint/repair.php .
    Value : true
  • WP_SETUP_CONFIG #
    Defined if WordPress will be installed or configured.
    Value: true
  • WP_UNINSTALL_PLUGIN #
    Defined if a plugin is to be uninstalled (for uninstall.php ).
    Value: true
  • WP_USER_ADMIN #
    Defi ne if there is a request in / wp-admin / user / .
    Value: true
  • XMLRPC_REQUEST #
    Defined if there is a request in the API XML-RPC .
    Value: true

Routes, directories and links

  • ABSPATH #
    Absolute path to the root directory of WordPress .
    Default: path to wp-load.php
  • WPINC #
    Path relative to / wp-includes / . You can not change this.
    Default: wp-includes
  • WP_LANG_DIR #
    Absolute path to the directory with the language files.
    Default: WP_CONTENT_DIR / languages ​​ or WP_CONTENT_DIR WPINC / languages ​​
  • WP_PLUGIN_DIR #
    Route absolute to the plugins directory.
    Default: WP_CONTENT_DIR / plugins
  • WP_PLUGIN_URL #
    URL to the plugins directory.
    Default: WP_CONTENT_URL / plugins
  • WP_CONTENT_DIR #
    Absolute path to wp-content .
    Default: ABSPATH wp-content
  • WP_CONTENT_URL #
    URL to directory wp-content .
    By default: {Site URL} / wp-content
  • WP_HOME #
    URL of the cover of your WordPress.
  • WP_SITEURL # [19659009] URL to the root directory of your WordPress.
  • WP_TEMP_DIR #
    Absolute path to a directory where temporary files can be saved.
  • WPMU_PLUGIN_DIR #
    ] Absolute path to the plugins directory available in multisite.
    Default: WP_CONTENT_DIR / mu-plugins
  • WPMU_PLUGIN_URL #
    URL to plugins directory available in multisite.
    Default: WP_CONTENT_URL / mu-plugins

Database

  • DB_CHARSET #
    Defines the character map of the database.
    Values: See the MySQL docs (Default: utf8 )
  • DB_COL LATE #
    Defines the database comparison.
    Values: See the MySQL docs (Default: utf8_general_ci )
  • DB_HOST #
    Defines the database server.
    Values: IP address, domain and / or port (Default: localhost )
  • DB_NAME #
    Defines the name of the database.
    Value: name of the database
  • DB_PASSWORD #
    Defines the password for the database.
  • DB_USER #
    Defines the user for the database.
  • WP_ALLOW_REPAIR #
    Allows you to automatically repair and optimize database tables with /wp-admin/maint/repair.php .
    Value: true
  • CUSTOM_USER_TABLE #
    Allows you to define a custom user for the database.
    Value: name of the table
  • CUSTOM_USER_META_TABLE #
    Allows you to define a customized user meta table.
    Value: table name

Multi-site

  • ALLOW_SUBDIRECTORY_INSTALL ] #
    It allows you to install Multisite in a subdirectory.
    Value: true
  • BLOGUPLOADDIR #
    Absolute path to the load directory of the particular site.
    Default: WP_CONTENT_DIR /blogs.dir/ {Blog ID} / files /
  • BLOG_ID_CURRENT_SITE #
    Blog ID from the main site.
    Default: 1
  • DOMAIN_CURRENT_SITE #
    Domain of the main site
    Default: domain
  • DIEONDBERROR #
    When defined, errors in the database are displayed.
    Value: true
  • ERRORLOGFILE #
    When it is defined, database errors are saved in a log file.
    Value: route absolute to a file with write permission
  • MULTISITE #
    Defined if you are going to use Multisite.
    Value: true
  • NOBLOGREDIRECT #
    Defines a URL of a site to which WordPress should redirect if the record is closed or a site does not exist.
    Values: % siteurl% for the main site or Custom URL
  • PATH_CURRENT_SITE #
    Path to main site.
  • UPLOADBLOGSDIR #
    Path to base upload directory, relative to ABSPATH .
    Default: wp-content / blogs.dir
  • SITE_ID_CURRENT_SITE #
    ID of the main site network.
    Default: 1
  • SUBDOMAIN_INSTALL #
    Defines whether a sub-domain will be installed or not.
    Values: true | false
  • SUNRISE #
    When WordPres is defined, it will load the file /wp-content/sunrise.php . ] Value: true
  • UPLOADS #
    Path to the specific upload directory of a site, relative to ABSPATH .
    Default: UPLOADBLOGSDIR / {blogid} / files /
  • WPMU_ACCEL_REDIRECT #
    Activate / Deactivate support for X-Sendfile Header .
    Values: true | false (Default: false )
  • WPMU_SENDFILE #
    Activate / Deactivate support for X-Accel-Redirect Header .
    Values: true | false (Default: false )
  • WP_ALLOW_MULTISITE #
    When it is defined, the Multi-site function (Tools → Configure Network) will be available.
    Value: true

Cache compression of scripts

  • WP_CACHE #
    When WordPress is defined, it will load the file /wp-content/advanced-cache.php .
    Values: true | false ( Default: false )
  • COMPRESS_CSS #
    Enable / Disable compression of style sheets.
    Values: true | false
  • COMPRESS_SCRIPTS #
    Enable / Disable JavaScript file compression.
    Valid: true | false
  • CONCATENATE_SCRIPTS #
    Activate / Deactivate the consolidation of CSS and Javascript files before compressing them.
    Values: true | false
  • ENFORCE_GZIP #
    Enable / Disable gzip output
    Values: true | false

File system and connections

  • FS_CHMOD_DIR #
    Defines the read and write permissions of the directories.
    Values: See PHP Handbuch (Default: 0755 )
  • FS_CHMOD_FILE #
    ] Defines the read and write permissions of the files.
    Values: See PHP Handbuch (Default: 0644 )
  • FS_CONNECT_TIMEOUT #
    Defines the maximum time to establish a connection.
    Values: time in seconds (Default: 30 )
  • FS_METHOD #
    Defines the method to connect to the file system.
    Values: direct | ssh | ftpext | ftpsockets
  • FS_TIMEOUT #
    Defines the maximum time for a lost connection.
    Values: time in seconds (By defect: 30 )
  • FTP_BASE #
    Path to the WordPress root directory.
    Default: ABSPATH
  • FTP_CONTENT_DIR ] #
    Path to directory / wp-content / .
    Default: WP_CONTENT_DIR
  • FTP_HOST #
    Defines the FTP server.
    Values: Address IP, domain and / or port
  • FTP_LANG_DIR #
    Path to the directory with the language files.
    Default: WP_LANG_DIR
  • FTP_PASS #
    Defines the FTP password
  • FTP_PLUGIN_DIR #
    to the plugins directory.
    Default: ] WP_PLUGIN_DIR
  • FTP_PRIKEY #
    Defines a private key for SSH .
  • FTP_PUBKEY #
    Defines a public key for ] SSH .
  • FTP_SSH #
    Activate / Deactivate SSH .
    Values: true | false
  • ] FTP_SSL #
    Activate / Deactivate SSL .
    Values: true | false
  • FTP_USER #
    Defines the FTP user.
  • WP_PROXY_BYPASS_HOSTS #
    Allows you to define some addresses that will not pass through the proxy.
    Values: www.example.com, * .example.org
  • WP_PROXY_HOST #
    Defines the proxy address.
    Values: IP address or domain
  • WP_PROXY_PASSWORD #
    Defines the proxy password.
  • WP_PROXY_PORT #
    Defines the proxy port.
  • WP_PROXY_USERNAME #
    Defines the proxy user.
  • WP_HTTP_BLOCK_EXTERNAL #
    Allows you to block external requests.
    Values: true | false
  • WP_ACCESSIBLE_HOSTS #
    If you define WP_HTTP_BLOCK_EXTERNAL you can add servers that should not be blocked. [194] 59029] Values: www.example.com, * .example.org

Topics

  • BACKGROUND_IMAGE #
    Defines a default background image.
  • HEADER_IMAGE ] #
    Defines a header image by default.
  • HEADER_IMAGE_HEIGHT #
    Defines the height of the header image.
  • HEADER_IMAGE_WIDTH #
    Defines the width of the header image.
  • HEADER_TEXTCOLOR #
    Defines the font color of the header text.
  • NO_HEADER_TEXT #
    ] Enables / Disables support for text in the header.
    Values: true | false
  • STYLESHEETPATH ​​ #
    Defines the absolute path to the sheet of current theme styles
  • TEMPLATEPATH #
    Defines the absolute path to the template files of the current theme. [19659] 256] WP_USE_THEMES #
    Activate / Deactivate the activation of themes.
    Values: true | false

Debug

  • SAVEQUERIES #
    Enables / Disables the saving of queries from the database in an array ( $ wpdb-> queries ).
    Values: true | false
  • SCRIPT_DEBUG #
    Activate / Deactivate the activation of CSS and Javascript compressed files. Valid: true | false
  • WP_DEBUG #
    Enable / Disable debug mode in WordPress.
    Values: true | false (Default: false )
  • WP_DEBUG_DISPLAY #
    Enables / Disables the display of errors on the screen.
    Values: true | false | null (Default: true )
  • WP_DEBUG_LOG #
    Activate / Deactivate the writing of errors in the file /wp-content/debug.log ]
    Values: true | false (Default: false )

Security and cookies

  • ALLOW_UNFILTERED_UPLOADS #
    Allows uploads without filtering for administrators.
    Value: true
  • AUTH_KEY #
    Secret key.
    ] Values: See the generator
  • AUTH_SALT #
    Secret key.
    Values: See the generator
  • COOKIEHASH #
    ] Hash to generate names of cookies.
  • COOKIEPATH #
    Path to the WordPress root directory.
    Default: URL of the cover page without http (s): / /
  • CUSTOM_TAGS #
    It allows you to overwrite the list of secure HTML tags. Take a look at the file /wp-includes/kses.php .
    Values: true | false (Default: false ])
  • DISALLOW_FILE_EDIT #
    Allows you to disable editing of theme files and plugins with the WordPress editor.
    Value: true
  • DISALLOW_FILE_MODS #
    It allows you to disable the editing, updating, installation and deletion of plugins, themes and kernel files from the WordPress desktop.
    Value: true
  • DISALLOW_UNFILTERED_HTML #
    Allows you to disable HTML without filtering for all users, including administrators.
    Value: true
  • FORCE_SSL_ADMIN #
    Activa SSL for the accesses and the desktop.
    Values: true | false ( By default: false )
  • FORCE_SSL_LOGIN #
    Activa SSL for accesses.
    Values: true | false (Default: false )
  • LOGGED_IN_KEY #
    Secret key.
    Values: See the generator
  • LOGGED_IN_SALT #
    Secret key.
    Values: See the generator
  • NONCE_KEY #
    Secret key.
    Values: See the generator
  • NONCE_SALT #
    Secret key.
    Values: See the generator
  • SECURE_AUTH_KEY #
    Secret key.
    Values: See the generator
  • SECURE_AUTH_SALT #
    Secret key .
    Values: See the generator
  • SITECOOKIEPATH #
    Path to your site.
    Default: URL of the site without http (s): / /

That's it, complete! [19659003] And you know, when you know the code there's no spoon!

This list of constants and their descriptions is translated from original article by Dominik Schilling in WPEngineer for its great interest for all.

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:

Author and original link in the feed • WordPress Help

The other day, when we saw a mode of showing a hidden copyright to those who copy you more than one commented that this did not work for the RSS feed, the most common method to copy articles. [19659002] Well, we are going to create a code with which to add to the RSS feed the author and link to the original article. In this way, if they read you through an RSS they will have the original link, just like the author of the publication, and it will also work for those who copy your content from the feed.

The code to include, in your ] plugin functions or file functions.php of your active theme is as follows:

// Show link to post and author in feed

function attribucion_feed ( $ content [19659008]) {

if ( is_feed () ) ] {

$ output = '

Written by' . [19659007] get_the_author () . 'in <a href = "' . get_permalink ( ) . '">' . get_bloginfo ( 'name' ) . '. If you are not reading this in '. get_bloginfo (' name ') . ', you will find the original article here … <a href="' . get_permalink() . '"> '. get_permalink () . '.

' ;

$ content = $ content . $ output ;

}

return $ content ;

}

add_filter ( 'the_content' 'attribucion_feed' ) ;

Written by Fernando in WordPress Help. If you are not reading this in WordPress Help, you will find the original article here ... Author and original link in the feed .