Pro and Cons of the magazine style themes • WordPress Help

If you have ever wondered if you need or in which occasions to choose a magazine type theme you will surely have enough doubts in this regard, as if it will confuse your readers, if it will be easy to manage, etc.

This type of templates shows you the blog more as a portal and that feature, although attractive, can have its drawbacks.

If you think we will see the pros and cons of this type of magazine templates or Magazine Themes .

I think you should analyze each virtue and inconvenience, and see if this type of templates will adapt well to your type of blog and, well, I think that the conclusion is simple, and it is interesting to use a magazine-like theme if …

To finish, and if you are still determined to use a magazine-style theme, here are links to some free that offer their virtues but without spending a cent:

They're nothing that 40 themes magazine so you have to choose and, if you wish, we have translated some that you have available in the download area or visit Themes WordPress.

Blog Day 2008 – My 5 recommended blogs • WordPress Help

Today, as every year, it is celebrated on Blog Day on Day of the Blog . And one of the main activities proposed is the fact of recommend 5 blogs to your readers .

To not leave the subject, I will recommend 5 blogs – which you do not know yet – in which it is about WordPress, in all or part of its content. Here you have them:

I have not put the most famous, so that it also helps you to know new blogs of interest.

How to redirect from www.mydomain.com to mydomain.com • WordPress Help

I think the title makes it very clear what is going to be explained in this article, right? Something as simple as learning that our domain is accessible both by someone typing with www as without it . This issue can affect positioning – that horrible thing that I usually discuss with Augustus, so decide once and forget forever.

For this we can use ] three tools : plugins Google or our little hands writing a bit of code and, incidentally, learning something. This time I do not roll up, to the mess …

Plugins

From www.mydomain.com to mydomain.com WordPress no-www : You install it, active and you're done, you do not have what to do more.

From mydomain.com to www.mydomain.com WWW Redirect : Redirects both ways

Google

You access the Tools for Google Webmasters and you indicate in the corresponding section with what type of domain you prefer to be identified, or simply if you do not make a decision about it and anyone is worth. It is not an alternative method to the others but a recommended additional step.

.htaccess

We return to our old friend, the file .htaccess . This time it will help us redirect our domain. We will find it in the main folder where we install the blog and access it from an FTP client. We open it with our favorite code editor to add some lines depending on whether we want to change …

From www.mydomain.com to mydomain.com:

From mydomain.com to www.midominio.com:

I do not know if I've ever commented (ah yes, some time ago ), but I'm in favor of no-www because simplifies the network, makes it more nominal, with shorter URLs and, what the heck! because the www simply remains any current browser does not need it and it is a waste of time.

And you how do you have it, short or long? (the URL, it is understood)

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 2.6.2

When we are all preparing for WordPress 2.7 in geek ramblings have discovered that a WordPress 2.6.2 beta trac is available, which would point to a new version, and quite soon.

The changes of this version are not many, and point to problems with redirections, duplication of tags, insertion of images in Internet Explorer 7 or the integration of Gears in the browser Safari among others.

We'll see if we do not have new version next week at this rate I'm afraid so.

The entry WordPress 2.6.2 was first published in WordPress Help .

Open Forum on Blog Day 2008

The next August 31 (this Sunday) is celebrated a new Day of the Blog and, apart from the meme proposed on the global website it has been created a site in Spanish to bring together actions and initiatives of the Hispanic blogosphere: Blog Day .

As a restless person I am collaborating with the team of Blog Day in matters technical and also, within the proposed activities, I have been invited to a kind of online round table in which I will attend to as many consultations and conversations arise on the subject " Are there Bloggers? – Myths and Realities ", one of the topics that I usually deal with in CiberPrensa .

Other virtual meetings proposed, with guest bloggers of relevance as …

If you want to participate in the conversation, it will start on August 31 at 4:00 pm (Spanish time) and last – in principle – until 5:30 pm. The place is the Forum enabled for the purpose where you can already register to be ready for the Virtual Meeting . See you there!

Common XHTML errors in WordPress

Once you get into the ins and outs of the WordPress code and you lose the fear of learning and using a bit of code in your blog, it is quite frequent not to take into account some of the rules of XHTML .

And is that most of the WordPress themes as well as the structure internally, they use XHTML standards similar to HTML but more mature and stable. Despite this, there are some rules to follow to avoid incurring errors that, at times, can ruin the appearance of our blog or the articles we post. Let's see the most common …

Close all Tags

XHTML requires the closing of all tags. For example, in HTML you can open a tag

and not close it and your code will validate, but not in XHTML, and you may get unwanted visualization errors. That is why you should always close the tags. It has always been recommended to do so but with XHTML "must be done" .

The wrong way to do it would be this:

This is a paragraph

And the correct this one:

This is a paragraph

Tags with self-closing

XHTML emphasizes close ALL TAGS not just open ones. There are some elements such as line breaks or images that did not have HTML closing tags but have auto-closure in XHTML.

Tags that require self-closing are:


To apply the self-closing you must add /> at the end. For example:

Order of the Tags

Another very common error is the placement of the tag closures when several are combined in the same element. For example:

Akismet 2.1.8 and problem solved • WordPress Help

Although you may not yet see it in your administration panel, the update of Akismet 2.1.8 is already available that solves the problem of the massive erasure of spam that we reported yesterday and on which gave notice and solution . If you want to install it already, it is available at the official site . The changes have been similar to those proposed by g30rg3_x .

Patch to the error of Akismet 2.1.7 (updated) • WordPress Help

The problem was introduced in this change (lines 718/727)
http://plugins.trac.wordpress.org/changeset/61062/akismet/trunk/akismet.php

The solution is obviously to remove that change …
that is, change the line 727 that is found with:

if (! (isset ($ _GET ['recheckqueue']) || isset ($ _POST ['action'])))

By [19659006] if (! Isset ($ _GET [‘recheckqueue’]))

For now I can not get a patch because I am seeing the repercussions that this move causes to WP 2.7 (to see if I break something with the WP 2.7 support)
So for as long as they need a temporary patch to erase their thousands of spam comments there they have it.

In the example line of the 727 it is not $ _ POST ['action'] otherwise $ _ REQUEST ['action'] so do not be scared if you do not see that POST xD …

Now correcting my patch, to still maintain compatibility for WP 2.7 I suggest instead of using the anti patch. erior este …

As always it is to change the line 727 by:
if (! (isset ($ _GET ['recheckqueue']) || isset ($ _GET ['action'])))

As you can see we are only changing the REQUEST by GET.
The "logical" explanation of the failure (for the who want to understand) …
The failure occurs because when action is defined in a POST variable (when we delete or recover) the truth table is False True what gives true and as it is denied this True false causing that instead of proceeding with the deletion the akismet_recheck_queue () code be executed, preventing the deleted and recovered code from ever being executed.

As it says, it is better not to apply it unless it is a real problem for you to accumulate spam "captured" in your folder until the team of Akismet solves it.

For our part I have already communicated to Automattic the problem and the possible solution so if they get a patch this is not It is thanks to you, and in particular to the beast of the code g30rg3_x 😉

Duplicate content thanks to WP Super Cache • WordPress Help

Two versions are already in two days and the problem still persists fortunately reported by the same author of the plugin ]that if you activate the plugin WP Super Cache it is almost certain that search engines identify content of your blog as a duplicate .

This is because they are not applied correctly the rules to your file .htaccess and, if the structure of the links of your blog is friendly, of the type " miblog.com/mi-post/ ", once you activate the plugin what It does is create a copy of each post but in HTML format.

So, if someone links you to that post and you have the bad luck that both the original URL and the redirect to the cached page , get the attention of the search engine bots, could be interpreted as duplicate content ]

If this is your case, what you must do to fix it, and be able to activate the plugin is to modify the .htaccess file and add these two lines twice :

RewriteCond% {REQUEST_URI}! ^. * [^/] $
RewriteCond% {REQUEST_URI}! ^. * //. $

They are twice because they must go in each of the two blocks of code that WP Super Cache includes in your .htaccess file. At the end you must have this complete block:

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: