Tag Archive for 'WordPress'

Important Update: Google (XML) Sitemaps Generator with qTranslate support (Version 3.1.6.3)

wordpress-logo-notext-rgb[1]

I’ve just released the version 3.1.6.3 of the Google (XML) Sitemaps Generator with qTranslate Support WordPress Plugin.

Two important things have been fixed:

  • Support for blogs without qTranslate (it won’t give fatal errors anymore)
  • Correct naming of the plugin in the WordPress Repository (as “Google XML Sitemaps with qTranslate Support”). The incorrect naming may cause the ones who have downloaded previous versions of the plugins to get updated to the original version (the one that does not support qTranslate).

I really recommend updating since you may not receive the notifications for this version of the plugin but for the original one (which does not support qTranslate).

You can download the latest version from the original post page:

Incoming search terms for the article:

Google (XML) Sitemaps Generator with qTranslate support now available at the WordPress Repository

wordpress-logo-notext-rgb[1]

Just to make the things easier for the ones using the Google (XML) Sitemaps Generator with qTranslate Support WordPress Plugin, I’ve just released it in the WordPress repository as “google-xml-sitemaps-with-qtranslate-support“.

This enables you to get easily notified when a new version is available and to use the automatic updating feature (from the WordPress admin panel).

You can download the latest version from the original post page:

Incoming search terms for the article:

Updated: qTranslate support for the Google (XML) Sitemaps Generator WordPress Plugin 3.1.6 (2nd Release)

wordpress-logo-notext-rgb[1]

Although, as I said in the original post, I had not originally written the code modifications to enable the qTranslate support for the Google (XML) Sitemaps Generator WordPress Plugin, I decided to make some corrections myself to do the following things:

  • Home page now appears in the different languages in the sitemap.
  • Entries not written in the default language do not appear anymore in the sitemap. Now, just the written languages appear. (Thanks Blutarsky for notifying the bug)

The updated code modifications and the new download version are in the original post:

Incoming search terms for the article:

How to fix the “You do not have sufficient permissions to access this page” message in WordPress

I’ll tell you my story, but you may be in the same situation having done something completely different, so keep reading…

One day, some time ago, I was very happily installing the WP-Security-Scan WordPress plugin, and I got an analysis result saying that I should change the default WordPress database table prefix in order to make harder the potential SQL Injection attacks…

WordpressAuthorization_TablePrefix1

Keep reading…

Incoming search terms for the article:

Hide WordPress Visual Editor Tab 1.01

Hide WordPress Visual Editor Tab has been updated to the 1.01 version to make it also work when creating new posts and pages. In the previous (1.0) version, it just worked while editing already created posts and pages.

Remove_Visual_Tab_Removed

To download the latest version, please visit the original Hide WordPress Visual Editor Tab post.

Incoming search terms for the article:

qTranslate support for the Google (XML) Sitemaps Generator WordPress Plugin

wordpress-logo-notext-rgb[1]

Some time ago, Qian Qin, the author of qTranslate, has published what should be modified on the Google (XML) Sitemaps Generator WordPress Plugin to make it support qTranslate.

However, this has never reached any of the releases of this plugin. (Qian Qin says he sent an e-mail to the author and I’ve done it myself, with no response).

So, I’m going to publish what should be modified on the plugin (for the ones who may want to do them themselves) and then, leave the link to download the modified version I prepared. I’ll be updating it for each new release.

Update: I’ve made some code corrections myself to include the different translations of the home page and not to include the entries not written in the default language (just include the written languages). The download and the code snippets have been updated to reflect the changes. If you wish more details, please go to the post of the update.

Update (2009-09-30): I’ve updated the naming of the plugin at the WordPress repository and the support for blogs without qTranslate installed. For releases before the 3.1.6.3, you may get notified for the original version updates (and not for this version supporting qTranslate), so I really recommend updating. If you wish more details, please go to the post of the update.

Keep reading…

Incoming search terms for the article:

How to remove the “Visual” tab from the WordPress post/page editor

There are lots of people (like me) who just use the HTML mode of the WordPress Editor… Sometimes, you cannot just disable the WYSIWYG editor (in my case, I cannot do it because I use the qTranslate plugin to enable the creation of posts in different languages)… For this people, having the Visual editor tab, might be a very big problem…

Lets say you’re writing a post in the HTML tab…

Remove_Visual_Tab_HTML

And you click by mistake the Visual tab…

Keep reading…

Incoming search terms for the article:

WP-No-Format WordPress Plugin (Prevent HTML Code Formatting/Modification)

For the ones used to work with WordPress editor’s HTML mode and hate when it creates <p>s and reorganize <br/>s on its will (among other things), I’ve made this plugin.

I’ve been searching a lot for this kind of functionality and, since I couldn’t find any plugin which let you decide which parts of the code you’d want to leave “unformatted”, I started to write my own…

WP-No-Format

It’s very simple to use. After activating it, you can just type:

<!-- noformat on -->

on the WordPress editor, just before the part you want to protect, and from that point on, WordPress won’t touch the HTML code you write.

If you want to resume the standard “formatting” you have to type:

<!-- noformat off -->

And that’s all!

GNU GPL v3 WP-No-Format is licensed under the GNU GPL v3 (attached)…

Update (version 1.1): added convert_chars function support. Before, some characters got converted to HTML entities (for example, when writting “&&” appeared as “&#038;&”). [Update recommended]

Here is the change log.

Latest WordPress version tested with: 2.8.4

Incoming search terms for the article: