<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for axew3.com</title>
	<atom:link href="http://www.axew3.com/b10g/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.axew3.com/b10g</link>
	<description>axew3 web home</description>
	<lastBuildDate>Tue, 07 Sep 2010 19:52:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>Comment on a post from &#8230; by axew3</title>
		<link>http://www.axew3.com/b10g/2010/09/a-post-from/comment-page-1/#comment-1504</link>
		<dc:creator>axew3</dc:creator>
		<pubDate>Tue, 07 Sep 2010 19:52:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.axew3.com/b10g/?p=528#comment-1504</guid>
		<description>the 1.0.7 version has been released with the wp-w3images.php file suitable for new 3.0 templates of wordpress.
It is possible to modify the wp-w3images.php file to be suitable also with old templates or old wordpress installations, i can help in this if there is some request. A simple tutorial can be done with easy steps.</description>
		<content:encoded><![CDATA[<p>the 1.0.7 version has been released with the wp-w3images.php file suitable for new 3.0 templates of wordpress.<br />
It is possible to modify the wp-w3images.php file to be suitable also with old templates or old wordpress installations, i can help in this if there is some request. A simple tutorial can be done with easy steps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on a post from &#8230; by axew3</title>
		<link>http://www.axew3.com/b10g/2010/09/a-post-from/comment-page-1/#comment-1503</link>
		<dc:creator>axew3</dc:creator>
		<pubDate>Tue, 07 Sep 2010 16:47:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.axew3.com/b10g/?p=528#comment-1503</guid>
		<description>p.s i think David have use the w3images version 1.0.7 (the latest) with a wordpress prior to version 3.0.0 or better.
It is possible to download, if this is the case, the old w3images 1.0.3 that is compatible with old wordpress versions.
&lt;a href=&quot;http://www.axew3.com/b10g/wp-content/downloads/wp_w3images-gallery_1.0.3.zip&quot;&gt;w3images 1.0.3&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>p.s i think David have use the w3images version 1.0.7 (the latest) with a wordpress prior to version 3.0.0 or better.<br />
It is possible to download, if this is the case, the old w3images 1.0.3 that is compatible with old wordpress versions.<br />
<a href="http://www.axew3.com/b10g/wp-content/downloads/wp_w3images-gallery_1.0.3.zip">w3images 1.0.3</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on w3images 1.0.7 pre release logs by axew3</title>
		<link>http://www.axew3.com/b10g/2010/09/w3images-1-0-7-pre-release-logs/comment-page-1/#comment-1487</link>
		<dc:creator>axew3</dc:creator>
		<pubDate>Fri, 03 Sep 2010 17:56:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.axew3.com/b10g/?p=513#comment-1487</guid>
		<description>The above reported bug problem with captcha has been solved so the w3images 1.0.7 is on the way, for this night Italy time it will be released.</description>
		<content:encoded><![CDATA[<p>The above reported bug problem with captcha has been solved so the w3images 1.0.7 is on the way, for this night Italy time it will be released.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on w3images 1.0.7 pre release logs by axew3</title>
		<link>http://www.axew3.com/b10g/2010/09/w3images-1-0-7-pre-release-logs/comment-page-1/#comment-1486</link>
		<dc:creator>axew3</dc:creator>
		<pubDate>Thu, 02 Sep 2010 22:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.axew3.com/b10g/?p=513#comment-1486</guid>
		<description>there is a problem with new captcha class implemented in the online pre-release version 1.0.7: testing out an image upload, it return ever wrong answer even if the passed security code is correct. The answer after image upload is ever &quot;security code mismatch&quot;. This problem seem to come out only on gnu-linux based servers.
The actual available to download 1.0.6 version of w3images still do not implement the new captcha security check, so it is not affected by this wrong behavior.
The new w3images 1.0.7 will be released as soon as this captcha related problem is fixed.</description>
		<content:encoded><![CDATA[<p>there is a problem with new captcha class implemented in the online pre-release version 1.0.7: testing out an image upload, it return ever wrong answer even if the passed security code is correct. The answer after image upload is ever &#8220;security code mismatch&#8221;. This problem seem to come out only on gnu-linux based servers.<br />
The actual available to download 1.0.6 version of w3images still do not implement the new captcha security check, so it is not affected by this wrong behavior.<br />
The new w3images 1.0.7 will be released as soon as this captcha related problem is fixed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on phpBB with WordPress by axew3</title>
		<link>http://www.axew3.com/b10g/2010/08/phpbb-with-wordpress/comment-page-1/#comment-1441</link>
		<dc:creator>axew3</dc:creator>
		<pubDate>Wed, 11 Aug 2010 13:39:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.axew3.com/b10g/?p=507#comment-1441</guid>
		<description>as WordPress do not use sessions to authenticate users (it mean that if an user have not enabled cookies on his browser, can&#039;t correctly authenticate himself for a correct login  on Wordpress), it seem to me that at least, if an user have not enabled cookies on browser, by the way can still login to phpBB.
Look this scenario: phpBB + WordPress integrated as unique login/registration.
If the Wordpress login system is used for both login, an user will not logged in on phpBB if user have not enabled cookies.
If for both login the phpBB login system is used instead, an user will be logged correctly on phpBB also if cookies are not enabled on his browser, but so, when redirected to WordPress he will not become recognized as registered. Almost untilthe user do not enable cookies on browser.
This the reason why on this bridge i go to code, i think the better way to unify systems is by using phpBB login system that use also sessions to manipulate users data.
The benefit on using an unique login in this way: the wordpress login widget, when user perform a submit login action, redirect user to phpBB login system, it authenticate the user logging in him on phpBB before, and so after the login has been correctly executed on phpBB, will be automatically redirected to previous wordpress page, where if cookies are enabled, will be also logged in. If cookie aren&#039;t enabled on user&#039;s browser, than he will not login on wordpress but at least on phpBB he will result correctly logged thank to sessions (and only for this browser session of course: in this case as cookies aren&#039;t used to store on user&#039;s pc the credentials for next eventually auto login).</description>
		<content:encoded><![CDATA[<p>as WordPress do not use sessions to authenticate users (it mean that if an user have not enabled cookies on his browser, can&#8217;t correctly authenticate himself for a correct login  on WordPress), it seem to me that at least, if an user have not enabled cookies on browser, by the way can still login to phpBB.<br />
Look this scenario: phpBB + WordPress integrated as unique login/registration.<br />
If the WordPress login system is used for both login, an user will not logged in on phpBB if user have not enabled cookies.<br />
If for both login the phpBB login system is used instead, an user will be logged correctly on phpBB also if cookies are not enabled on his browser, but so, when redirected to WordPress he will not become recognized as registered. Almost untilthe user do not enable cookies on browser.<br />
This the reason why on this bridge i go to code, i think the better way to unify systems is by using phpBB login system that use also sessions to manipulate users data.<br />
The benefit on using an unique login in this way: the wordpress login widget, when user perform a submit login action, redirect user to phpBB login system, it authenticate the user logging in him on phpBB before, and so after the login has been correctly executed on phpBB, will be automatically redirected to previous wordpress page, where if cookies are enabled, will be also logged in. If cookie aren&#8217;t enabled on user&#8217;s browser, than he will not login on wordpress but at least on phpBB he will result correctly logged thank to sessions (and only for this browser session of course: in this case as cookies aren&#8217;t used to store on user&#8217;s pc the credentials for next eventually auto login).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on phpBB with WordPress by axew3</title>
		<link>http://www.axew3.com/b10g/2010/08/phpbb-with-wordpress/comment-page-1/#comment-1437</link>
		<dc:creator>axew3</dc:creator>
		<pubDate>Tue, 10 Aug 2010 14:48:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.axew3.com/b10g/?p=507#comment-1437</guid>
		<description>&lt;h3&gt;Questions and answer to start coding the new integration ...&lt;/h3&gt;

&lt;ol&gt;	&lt;li&gt;what system should control the registration/login procedure?&lt;/li&gt;
	&lt;li&gt;what system should be used to manage users? (prune, addition, single deletion ...)&lt;/li&gt;
&lt;/ol&gt;
Think that we should use the more sophisticated phpBB system for users registration, while manual addition or prune of users can be maybe performed on both administrations.
Of course after the login, if it is done inserting credentials in wordpress side, but using the phpBB login system, the user will be redirected to the proper coming page.
Three widgets for the wordpress side are necessaries at minimum: &lt;em&gt;online forum users, login/out, last posts/topics&lt;/em&gt;.
</description>
		<content:encoded><![CDATA[<h3>Questions and answer to start coding the new integration &#8230;</h3>
<ol>
<li>what system should control the registration/login procedure?</li>
<li>what system should be used to manage users? (prune, addition, single deletion &#8230;)</li>
</ol>
<p>Think that we should use the more sophisticated phpBB system for users registration, while manual addition or prune of users can be maybe performed on both administrations.<br />
Of course after the login, if it is done inserting credentials in wordpress side, but using the phpBB login system, the user will be redirected to the proper coming page.<br />
Three widgets for the wordpress side are necessaries at minimum: <em>online forum users, login/out, last posts/topics</em>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on phpBB with WordPress by axew3</title>
		<link>http://www.axew3.com/b10g/2010/08/phpbb-with-wordpress/comment-page-1/#comment-1436</link>
		<dc:creator>axew3</dc:creator>
		<pubDate>Tue, 10 Aug 2010 14:45:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.axew3.com/b10g/?p=507#comment-1436</guid>
		<description>I love the way phpBB is coded. Effective and simple, but it is only my opinion of course.
The new integration plugin wordpress + phpbb will be coded in few steps as the login code for phpBB has been already detected.
The integration can be after improved of all needed things such last forums posts widget, online users widget (maybe added as code to the users online plugin installed here and very well done), and more, or for phpBB side, latest blog entries etc.
The integration can be practically effective and full as we like.</description>
		<content:encoded><![CDATA[<p>I love the way phpBB is coded. Effective and simple, but it is only my opinion of course.<br />
The new integration plugin wordpress + phpbb will be coded in few steps as the login code for phpBB has been already detected.<br />
The integration can be after improved of all needed things such last forums posts widget, online users widget (maybe added as code to the users online plugin installed here and very well done), and more, or for phpBB side, latest blog entries etc.<br />
The integration can be practically effective and full as we like.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on w3images 1.0.6 logs pre release by axew3</title>
		<link>http://www.axew3.com/b10g/2010/07/w3images-1-0-6/comment-page-1/#comment-1435</link>
		<dc:creator>axew3</dc:creator>
		<pubDate>Sun, 08 Aug 2010 13:27:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.axew3.com/b10g/?p=457#comment-1435</guid>
		<description>the code has been sufficiently improved to be released as 1.0.6.
The w3images-options.php file has not been updated but it from the first 1.0.0 version, was the only one that always have work well with all strict necessary features, also if it can be more elegant, and also more immediately useful (to grab images &lt;i&gt;id name&lt;/i&gt; for example, or to organize a better menu builder). It will be better on next versions.
While in this 1.0.6 the code will include:
&lt;ol&gt;
	&lt;li&gt;a better items menu list thanks to a recursive function.&lt;/li&gt;

	&lt;li&gt;redundant code fixed where disclosed.&lt;/li&gt;

	&lt;li&gt;more fix.&lt;/li&gt;
&lt;/ol&gt;

</description>
		<content:encoded><![CDATA[<p>the code has been sufficiently improved to be released as 1.0.6.<br />
The w3images-options.php file has not been updated but it from the first 1.0.0 version, was the only one that always have work well with all strict necessary features, also if it can be more elegant, and also more immediately useful (to grab images <i>id name</i> for example, or to organize a better menu builder). It will be better on next versions.<br />
While in this 1.0.6 the code will include:</p>
<ol>
<li>a better items menu list thanks to a recursive function.</li>
<li>redundant code fixed where disclosed.</li>
<li>more fix.</li>
</ol>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Recursive Php function for items menu list by axew3</title>
		<link>http://www.axew3.com/b10g/2010/07/recursive-php-function-for-menu-list/comment-page-1/#comment-1433</link>
		<dc:creator>axew3</dc:creator>
		<pubDate>Sat, 07 Aug 2010 20:31:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.axew3.com/b10g/?p=487#comment-1433</guid>
		<description>The code of the improved function that will be added to the w3images images gallery plugin for wordpress version 1.0.6 has been already published at w3it.org,
to the following uri:
http://www.w3it.org/forums/showthread.php?890-Recursive-Php-function-for-items-menu-list&amp;p=9822#post9822</description>
		<content:encoded><![CDATA[<p>The code of the improved function that will be added to the w3images images gallery plugin for wordpress version 1.0.6 has been already published at w3it.org,<br />
to the following uri:<br />
<a href="http://www.w3it.org/forums/showthread.php?890-Recursive-Php-function-for-items-menu-list&#038;p=9822#post9822" rel="nofollow">http://www.w3it.org/forums/showthread.php?890-Recursive-Php-function-for-items-menu-list&#038;p=9822#post9822</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Recursive Php function for items menu list by axew3</title>
		<link>http://www.axew3.com/b10g/2010/07/recursive-php-function-for-menu-list/comment-page-1/#comment-1431</link>
		<dc:creator>axew3</dc:creator>
		<pubDate>Fri, 06 Aug 2010 20:17:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.axew3.com/b10g/?p=487#comment-1431</guid>
		<description>The function has been updated and improved: as needed now list correctly for each section the relative list of belongs subsections.
The new 1.0.6 version will be released within this Sunday, at max Monday.
The new &lt;em&gt;w3images menu list&lt;/em&gt; as you can see it is now here at axew3.com, is still not implemented on the available w3images images plugin for wordpress 1.0.5 version. You can install the w3images 1.0.5 and after, simply overwriting plugins files, update to latest 1.0.6. It is easy and immediate as any other (+ or -) easy and useful WordPress plugin.
I hope to find out the time to improve also the &lt;a href=&quot;http://www.axew3.com/b10g/w3images-for-wordpress-how-to-use-it/&quot;&gt;w3images how to page&lt;/a&gt;.
Any help request or question in reply on one of the many started threads here in the blog. Upload of the w3images plugin to the subversion plugins directory at WordPress.com will be done also as soon and will be used to give the w3images gallery images plugin for WordPress available for download and improvements, to anyone as released as GPL3. Enjoy (and maybe help if you can!)</description>
		<content:encoded><![CDATA[<p>The function has been updated and improved: as needed now list correctly for each section the relative list of belongs subsections.<br />
The new 1.0.6 version will be released within this Sunday, at max Monday.<br />
The new <em>w3images menu list</em> as you can see it is now here at axew3.com, is still not implemented on the available w3images images plugin for wordpress 1.0.5 version. You can install the w3images 1.0.5 and after, simply overwriting plugins files, update to latest 1.0.6. It is easy and immediate as any other (+ or -) easy and useful WordPress plugin.<br />
I hope to find out the time to improve also the <a href="http://www.axew3.com/b10g/w3images-for-wordpress-how-to-use-it/">w3images how to page</a>.<br />
Any help request or question in reply on one of the many started threads here in the blog. Upload of the w3images plugin to the subversion plugins directory at WordPress.com will be done also as soon and will be used to give the w3images gallery images plugin for WordPress available for download and improvements, to anyone as released as GPL3. Enjoy (and maybe help if you can!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on w3images 1.0.6 logs pre release by axew3</title>
		<link>http://www.axew3.com/b10g/2010/07/w3images-1-0-6/comment-page-1/#comment-1385</link>
		<dc:creator>axew3</dc:creator>
		<pubDate>Sun, 18 Jul 2010 13:28:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.axew3.com/b10g/?p=457#comment-1385</guid>
		<description>A bug more to be fixed for 1.0.6:
the notice advice about images moderation on submit, appear also when it should not, for example when who is submitting is an user that have  power to upload images without moderation.</description>
		<content:encoded><![CDATA[<p>A bug more to be fixed for 1.0.6:<br />
the notice advice about images moderation on submit, appear also when it should not, for example when who is submitting is an user that have  power to upload images without moderation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on w3images 1.0.5 change log by axew3</title>
		<link>http://www.axew3.com/b10g/2010/06/w3images-1-0-5-change-logs/comment-page-1/#comment-1382</link>
		<dc:creator>axew3</dc:creator>
		<pubDate>Thu, 15 Jul 2010 22:39:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.axew3.com/b10g/?p=346#comment-1382</guid>
		<description>added a page for this hack to nofollow, the topic here was really not appropriated but the idea has come out and i have try it and report here.
The page for the rel nofollow on wordpress solution and tips about has been created and you can contribute to to improve it of course, comments are open in this related page:
http://www.axew3.com/b10g/avoid-rel-nofollow-on-wordpress-how-to/</description>
		<content:encoded><![CDATA[<p>added a page for this hack to nofollow, the topic here was really not appropriated but the idea has come out and i have try it and report here.<br />
The page for the rel nofollow on wordpress solution and tips about has been created and you can contribute to to improve it of course, comments are open in this related page:<br />
<a href="http://www.axew3.com/b10g/avoid-rel-nofollow-on-wordpress-how-to/" rel="nofollow">http://www.axew3.com/b10g/avoid-rel-nofollow-on-wordpress-how-to/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Avoid rel=&#8221;nofollow&#8221; on wordpress how to by axew3</title>
		<link>http://www.axew3.com/b10g/avoid-rel-nofollow-on-wordpress-how-to/comment-page-1/#comment-1381</link>
		<dc:creator>axew3</dc:creator>
		<pubDate>Thu, 15 Jul 2010 22:32:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.axew3.com/b10g/#comment-1381</guid>
		<description>&lt;h3&gt;More examples for different scenario on avoiding rel nofollow addition in WordPress posts, pages or comments: authors, contributors ...&lt;/h3&gt;

&lt;strong&gt;instead of:&lt;/strong&gt;
&lt;code&gt;
// START hack to avoid administrators rel=&quot;nofollow&quot;
global $current_user;
if($current_user-&gt;user_level &gt; 9){
return $text;
}&lt;/code&gt;


to &lt;strong&gt;avoid rel nofollow on wordpress for all users, the code that need to be added as indicated for two times in place of the above, are these following two lines of code&lt;/strong&gt; (one is a comment in true)) substituting the above that avoid &lt;em&gt;no nofollow&lt;/em&gt; only for administrators:
function wp_rel_nofollow_callback( $matches ) {
immediately after this line ADD the following code:
&lt;code&gt;// eliminate for all users the rel nofollow addition on wordpress:
return $text;&lt;/code&gt;</description>
		<content:encoded><![CDATA[<h3>More examples for different scenario on avoiding rel nofollow addition in WordPress posts, pages or comments: authors, contributors &#8230;</h3>
<p><strong>instead of:</strong><br />
<code><br />
// START hack to avoid administrators rel="nofollow"<br />
global $current_user;<br />
if($current_user->user_level > 9){<br />
return $text;<br />
}</code></p>
<p>to <strong>avoid rel nofollow on wordpress for all users, the code that need to be added as indicated for two times in place of the above, are these following two lines of code</strong> (one is a comment in true)) substituting the above that avoid <em>no nofollow</em> only for administrators:<br />
function wp_rel_nofollow_callback( $matches ) {<br />
immediately after this line ADD the following code:<br />
<code>// eliminate for all users the rel nofollow addition on wordpress:<br />
return $text;</code></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on w3images 1.0.5 change log by axew3</title>
		<link>http://www.axew3.com/b10g/2010/06/w3images-1-0-5-change-logs/comment-page-1/#comment-1380</link>
		<dc:creator>axew3</dc:creator>
		<pubDate>Thu, 15 Jul 2010 21:48:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.axew3.com/b10g/?p=346#comment-1380</guid>
		<description>well it work very well! the test has returned the correct code untouched. I think a Page for this modification argument should be added to help anybody like to hack his wordress for this . In short by the way, this is the tricky i have think to solve this issue about &lt;em&gt;rel nofollow&lt;/em&gt; on wordpress, and without add a plugin, but with all possibles needed about who should or not be affected by this wordpress behavior ( addition of rel=&quot;nofollow&quot; on a tags ).
&lt;h2&gt;How to hack formatting.php on WordPress to avoid nofollow additions on &lt;a&gt; tags&lt;/h2&gt;
&lt;strong&gt;in this example we go to avoid the rel=&quot;nofollow&quot; additions on &lt;a&gt; tags only for administrators when they add contents to blog&lt;/strong&gt;.

&lt;strong&gt;OPEN&lt;/strong&gt; the file &lt;em&gt;wp-includes/&lt;strong&gt;formatting.php&lt;/strong&gt;&lt;/em&gt; file with a text editor and search for these following two lines of code as indicated and add the code (the mentioned lines of code are related the two functions involved on wordpress rel=&quot;nofollow addition and are sequentially).

&lt;strong&gt;Search the following line of code:&lt;/strong&gt;
&lt;code&gt;function wp_rel_nofollow( $text ) {&lt;/code&gt;
&lt;strong&gt;immediately after this line ADD the following code:&lt;/strong&gt;
&lt;code&gt;// START hack to avoid admin rel=&quot;nofollow&quot; 

 global $current_user;
 if($current_user-&gt;user_level &gt; 9){  
      return $text;
    }

  // END hack to avoid admin rel=&quot;nofollow&quot;&lt;/code&gt;

&lt;strong&gt;Search the following line of code:&lt;/strong&gt;

&lt;code&gt;function wp_rel_nofollow_callback( $matches ) {&lt;/code&gt;
&lt;strong&gt;immediately after this line ADD the following code:&lt;/strong&gt;
&lt;code&gt;// START hack to avoid administrators rel=&quot;nofollow&quot; 

 global $current_user;
 if($current_user-&gt;user_level &gt; 9){  
      return $text;
    }

  // END hack to avoid admin rel=&quot;nofollow&quot;&lt;/code&gt;

Save the file and upload overwriting the default formatting.php. Now when an user with administrative power go to post contents, Wordpress will not add the rel=&quot;nofollow&quot; attribute.

Consideration: maybe it is not necessary to call this function because declaring as &lt;em&gt;global&lt;/em&gt; &lt;em&gt;$current_user&lt;/em&gt; is sufficient at this wp loop point?</description>
		<content:encoded><![CDATA[<p>well it work very well! the test has returned the correct code untouched. I think a Page for this modification argument should be added to help anybody like to hack his wordress for this . In short by the way, this is the tricky i have think to solve this issue about <em>rel nofollow</em> on wordpress, and without add a plugin, but with all possibles needed about who should or not be affected by this wordpress behavior ( addition of rel=&#8221;nofollow&#8221; on a tags ).</p>
<h2>How to hack formatting.php on WordPress to avoid nofollow additions on &lt;a&gt; tags</h2>
<p><strong>in this example we go to avoid the rel=&#8221;nofollow&#8221; additions on &lt;a&gt; tags only for administrators when they add contents to blog</strong>.</p>
<p><strong>OPEN</strong> the file <em>wp-includes/<strong>formatting.php</strong></em> file with a text editor and search for these following two lines of code as indicated and add the code (the mentioned lines of code are related the two functions involved on wordpress rel=&#8221;nofollow addition and are sequentially).</p>
<p><strong>Search the following line of code:</strong><br />
<code>function wp_rel_nofollow( $text ) {</code><br />
<strong>immediately after this line ADD the following code:</strong><br />
<code>// START hack to avoid admin rel="nofollow" </p>
<p> global $current_user;<br />
 if($current_user->user_level > 9){<br />
      return $text;<br />
    }</p>
<p>  // END hack to avoid admin rel="nofollow"</code></p>
<p><strong>Search the following line of code:</strong></p>
<p><code>function wp_rel_nofollow_callback( $matches ) {</code><br />
<strong>immediately after this line ADD the following code:</strong><br />
<code>// START hack to avoid administrators rel="nofollow" </p>
<p> global $current_user;<br />
 if($current_user->user_level > 9){<br />
      return $text;<br />
    }</p>
<p>  // END hack to avoid admin rel="nofollow"</code></p>
<p>Save the file and upload overwriting the default formatting.php. Now when an user with administrative power go to post contents, WordPress will not add the rel=&#8221;nofollow&#8221; attribute.</p>
<p>Consideration: maybe it is not necessary to call this function because declaring as <em>global</em> <em>$current_user</em> is sufficient at this wp loop point?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on w3images 1.0.5 change log by axew3</title>
		<link>http://www.axew3.com/b10g/2010/06/w3images-1-0-5-change-logs/comment-page-1/#comment-1379</link>
		<dc:creator>axew3</dc:creator>
		<pubDate>Thu, 15 Jul 2010 21:42:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.axew3.com/b10g/?p=346#comment-1379</guid>
		<description>related the modification of the file formatting.php and avoid wordpress to add the rel=&quot;nofollow&quot; attribute i think there is a good solution: i just try out it now, and i think it will work so well!
In minutes the how to will be updated in this same comment ... some minute more ...
this is a test: the modification very simple done on two functions in the file formatting.php of wordpress, should avoid rel=&quot;nofollow&quot; additions to &lt;a&gt; tags in case the author is an administrator or just any other group or even single users who you&#039;ll like to exclude from this wordpress behavior.
Test this image link, it should return after insertion without rel=&quot;nofollow&quot; as formatting.php has been hacked now here at axew3.com:
&lt;a href=&quot;http://www.axew3.com/b10g/wp-content/plugins/w3images/images/9.jpg&quot; rel=&quot;shadowbox[w3images]&quot;&gt;&lt;img src=&quot;http://www.axew3.com/b10g/wp-content/plugins/w3images/images/tb_9.jpg&quot; /&gt;&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>related the modification of the file formatting.php and avoid wordpress to add the rel=&#8221;nofollow&#8221; attribute i think there is a good solution: i just try out it now, and i think it will work so well!<br />
In minutes the how to will be updated in this same comment &#8230; some minute more &#8230;<br />
this is a test: the modification very simple done on two functions in the file formatting.php of wordpress, should avoid rel=&#8221;nofollow&#8221; additions to &lt;a&gt; tags in case the author is an administrator or just any other group or even single users who you&#8217;ll like to exclude from this wordpress behavior.<br />
Test this image link, it should return after insertion without rel=&#8221;nofollow&#8221; as formatting.php has been hacked now here at axew3.com:<br />
<a href="http://www.axew3.com/b10g/wp-content/plugins/w3images/images/9.jpg" rel="shadowbox[w3images]"><img src="http://www.axew3.com/b10g/wp-content/plugins/w3images/images/tb_9.jpg" /></a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on w3images 1.0.6 logs pre release by axew3</title>
		<link>http://www.axew3.com/b10g/2010/07/w3images-1-0-6/comment-page-1/#comment-1377</link>
		<dc:creator>axew3</dc:creator>
		<pubDate>Thu, 15 Jul 2010 14:20:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.axew3.com/b10g/?p=457#comment-1377</guid>
		<description>&lt;h2&gt;done:&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Changed the &lt;em&gt;Thickbox name&lt;/em&gt; replaced from &lt;strong&gt;&lt;em&gt;Shadowbox&lt;/em&gt;&lt;/strong&gt; in relate admin menu options.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2&gt;to be done:&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Check and rewrite the images-options.php file.&lt;/li&gt;
&lt;li&gt;list sub directories names and not only total images numbers&lt;/li&gt;
&lt;li&gt;associate filename to images in administration for an easy image identification useful to insertion of images o n posts and pages.&lt;/li&gt;
&lt;li&gt;better  images display in administration&lt;/li&gt;
&lt;li&gt;a better gallery output?&lt;/li&gt;
&lt;li&gt;....&lt;/li&gt;
&lt;/ol&gt;

... request here in reply something more for w3images ...</description>
		<content:encoded><![CDATA[<h2>done:</h2>
<ol>
<li>Changed the <em>Thickbox name</em> replaced from <strong><em>Shadowbox</em></strong> in relate admin menu options.</li>
</ol>
<h2>to be done:</h2>
<ol>
<li>Check and rewrite the images-options.php file.</li>
<li>list sub directories names and not only total images numbers</li>
<li>associate filename to images in administration for an easy image identification useful to insertion of images o n posts and pages.</li>
<li>better  images display in administration</li>
<li>a better gallery output?</li>
<li>&#8230;.</li>
</ol>
<p>&#8230; request here in reply something more for w3images &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on w3images 1.0.5 released as GPL 3 by axew3</title>
		<link>http://www.axew3.com/b10g/2010/07/w3images-1-0-5-released-as-gpl-3/comment-page-1/#comment-1375</link>
		<dc:creator>axew3</dc:creator>
		<pubDate>Wed, 14 Jul 2010 22:38:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.axew3.com/b10g/?p=392#comment-1375</guid>
		<description>&lt;strong&gt;the &lt;a href=&quot;http://www.axew3.com/b10g/w3images-for-wordpress-how-to-use-it/&quot; rel=&quot;nofollow&quot;&gt;w3images images gallery plugin for wordpress how to page&lt;/a&gt; has been updated.&lt;/strong&gt;</description>
		<content:encoded><![CDATA[<p><strong>the <a href="http://www.axew3.com/b10g/w3images-for-wordpress-how-to-use-it/" rel="nofollow">w3images images gallery plugin for wordpress how to page</a> has been updated.</strong></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on w3images 1.0.5 change log by axew3</title>
		<link>http://www.axew3.com/b10g/2010/06/w3images-1-0-5-change-logs/comment-page-1/#comment-1369</link>
		<dc:creator>axew3</dc:creator>
		<pubDate>Mon, 12 Jul 2010 12:42:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.axew3.com/b10g/?p=346#comment-1369</guid>
		<description>About images that can be added to any post and page by using the &lt;img&gt; tag, (you can add also the simple w3images random thumbnails function on posts and pages installing a plugin like &lt;em&gt;php exec&lt;/em&gt; that allow to execute php code directly inside posts and pages) there is a problem with the attribute &lt;strong&gt;rel&lt;/strong&gt; adopted on w3images to open full images view on shadowbox, that is also used in WordPress as explained with also many criticism at this wordpress &lt;a href=&quot;http://codex.wordpress.org/Nofollow&quot; rel=&quot;nofollow&quot;&gt;link Nofollow&lt;/a&gt; page.
Practically, the rel=&quot;nofollow&quot; attribute is added to any &lt;a&gt; tag (links) on comments or posts.
Why this? The reason is: discourage spam.
In fact Google had time ago add this policy: any link that is containing the &lt;em&gt;nofollow&lt;/em&gt; attribute will not influence the site ranking.
Unfortunately, not only jquery but also others library routines like to use the attribute rel for various scope, and in wordpress this is a limit in this case. If the &lt;em&gt;rel&lt;/em&gt; attribute is used for &lt;em&gt;nofollow&lt;/em&gt;, can&#039;t be used for another scope in the same element (the markup validator will notice about &lt;em&gt;duplicate attribute rel&lt;/em&gt; error checking the document.
Adding a single image to a post and display it by using the &lt;em&gt;rel=&quot;shadowbox[w3images]&quot;&lt;/em&gt; to open and see the full image with Shadowbox will work, but as just above sayd, wordpress add also another attribute &lt;em&gt;rel&lt;/em&gt; after the &lt;em&gt;rel=&quot;shadowbox[w3images]&quot;&lt;/em&gt;, and the xhtml validator will return duplicate attribute for the &lt;a&gt; tag and the page will return invalid markup validation for this (if there aren&#039;t more xhtml markup errors of course!) in case we try to validate as xhtml the page. There are wordpress plugins to disallow/allow the &lt;em&gt;rel&lt;/em&gt; attribute mentioned in the wordpress page linked above, but i don&#039;t have try out any of these. 

I think, it is needed and is best to have an option that leave to an administrator or editors and so on while are writing, the possibility to choose if it need to be enabled or not on contest.
Hope next releases of wordpress will contemplate this possibility.
... ... ...
i will continue here with wordpress and rel=&quot;nofollow&quot; considerations, 
just returned to home and i gave water to my plants.
this is a test of an &lt;a&gt; tag with rel attribute value = shadowbox[w3images] that should display full image onclick event:

shadowbox[w3images] test: &lt;a href=&quot;http://www.axew3.com/b10g/wp-content/plugins/w3images/images/2.jpg&quot;   rel=&quot;shadowbox[w3images]&quot; rel=&quot;nofollow&quot;&gt;&lt;img src=&quot;http://www.axew3.com/b10g/wp-content/plugins/w3images/images/tb_2.jpg&quot; /&gt;&lt;/a&gt;

as reported above, wordpress add &lt;em&gt;rel=&quot;nofollow&quot;&lt;/em&gt; to links while save/update and this is the returned code in this case:
&lt;blockquote&gt;&lt;a href=&quot;http://www.axew3.com/b10g/wp-content/plugins/w3images/images/2.jpg&quot; rel=&quot;shadowbox[w3images]&quot; &lt;strong&gt;rel=&quot;nofollow&quot;&lt;/strong&gt;&gt;&lt;/blockquote&gt;
so nice! Two different attribute rel, the last one with value &lt;em&gt;nofollow&lt;/em&gt;.
Possibles solutions at this time: &lt;ol&gt;
&lt;li&gt;you can install plugins that allow to remove the nofollow attribute on wordpress posts and pages links&lt;/li&gt;
&lt;li&gt;you can with easy modify the two functions contained on file &lt;em&gt;wp-includes/&lt;strong&gt;formatting.php&lt;/strong&gt;&lt;/em&gt; in a way that avoid the rel addition (substantially easy, it is sufficient to comment off all instructions contained in these two functions: this trick let return posts or page&#039;s content untouched, without the addition of the rel attribute to &lt;a&gt; tags&lt;/li&gt;
&lt;li&gt; ... maybe there is another tricky, easy and speedy solution that i still do not know and i hope to find out without many investigations :)&lt;/li&gt;
&lt;/ol&gt;
the attribute rel=&quot;nofollow&quot; is added by wordpress after all other attributes if there are in the &lt;a&gt; element, so the Shadowbox ajax effect will work because the parser will take as valid the last one rel attribute founded on the way: as browsers (for what i remember and hope it is correct info) parse documents from down to up (on the contrary), the &lt;em&gt;rel=&quot;shadowbox[w3images]&quot;&lt;/em&gt; will be the last one parsed.


</description>
		<content:encoded><![CDATA[<p>About images that can be added to any post and page by using the &lt;img&gt; tag, (you can add also the simple w3images random thumbnails function on posts and pages installing a plugin like <em>php exec</em> that allow to execute php code directly inside posts and pages) there is a problem with the attribute <strong>rel</strong> adopted on w3images to open full images view on shadowbox, that is also used in WordPress as explained with also many criticism at this wordpress <a href="http://codex.wordpress.org/Nofollow" rel="nofollow">link Nofollow</a> page.<br />
Practically, the rel=&#8221;nofollow&#8221; attribute is added to any &lt;a&gt; tag (links) on comments or posts.<br />
Why this? The reason is: discourage spam.<br />
In fact Google had time ago add this policy: any link that is containing the <em>nofollow</em> attribute will not influence the site ranking.<br />
Unfortunately, not only jquery but also others library routines like to use the attribute rel for various scope, and in wordpress this is a limit in this case. If the <em>rel</em> attribute is used for <em>nofollow</em>, can&#8217;t be used for another scope in the same element (the markup validator will notice about <em>duplicate attribute rel</em> error checking the document.<br />
Adding a single image to a post and display it by using the <em>rel=&#8221;shadowbox[w3images]&#8220;</em> to open and see the full image with Shadowbox will work, but as just above sayd, wordpress add also another attribute <em>rel</em> after the <em>rel=&#8221;shadowbox[w3images]&#8220;</em>, and the xhtml validator will return duplicate attribute for the &lt;a&gt; tag and the page will return invalid markup validation for this (if there aren&#8217;t more xhtml markup errors of course!) in case we try to validate as xhtml the page. There are wordpress plugins to disallow/allow the <em>rel</em> attribute mentioned in the wordpress page linked above, but i don&#8217;t have try out any of these. </p>
<p>I think, it is needed and is best to have an option that leave to an administrator or editors and so on while are writing, the possibility to choose if it need to be enabled or not on contest.<br />
Hope next releases of wordpress will contemplate this possibility.<br />
&#8230; &#8230; &#8230;<br />
i will continue here with wordpress and rel=&#8221;nofollow&#8221; considerations,<br />
just returned to home and i gave water to my plants.<br />
this is a test of an &lt;a&gt; tag with rel attribute value = shadowbox[w3images] that should display full image onclick event:</p>
<p>shadowbox[w3images] test: <a href="http://www.axew3.com/b10g/wp-content/plugins/w3images/images/2.jpg"   rel="shadowbox[w3images]" rel="nofollow"><img src="http://www.axew3.com/b10g/wp-content/plugins/w3images/images/tb_2.jpg" /></a></p>
<p>as reported above, wordpress add <em>rel=&#8221;nofollow&#8221;</em> to links while save/update and this is the returned code in this case:</p>
<blockquote><p>&lt;a href=&#8221;http://www.axew3.com/b10g/wp-content/plugins/w3images/images/2.jpg&#8221; rel=&#8221;shadowbox[w3images]&#8221; <strong>rel=&#8221;nofollow&#8221;</strong>&gt;</p></blockquote>
<p>so nice! Two different attribute rel, the last one with value <em>nofollow</em>.<br />
Possibles solutions at this time:
<ol>
<li>you can install plugins that allow to remove the nofollow attribute on wordpress posts and pages links</li>
<li>you can with easy modify the two functions contained on file <em>wp-includes/<strong>formatting.php</strong></em> in a way that avoid the rel addition (substantially easy, it is sufficient to comment off all instructions contained in these two functions: this trick let return posts or page&#8217;s content untouched, without the addition of the rel attribute to &lt;a&gt; tags</li>
<li> &#8230; maybe there is another tricky, easy and speedy solution that i still do not know and i hope to find out without many investigations <img src='http://www.axew3.com/b10g/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </li>
</ol>
<p>the attribute rel=&#8221;nofollow&#8221; is added by wordpress after all other attributes if there are in the &lt;a&gt; element, so the Shadowbox ajax effect will work because the parser will take as valid the last one rel attribute founded on the way: as browsers (for what i remember and hope it is correct info) parse documents from down to up (on the contrary), the <em>rel=&#8221;shadowbox[w3images]&#8220;</em> will be the last one parsed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on w3images 1.0.5 change log by axew3</title>
		<link>http://www.axew3.com/b10g/2010/06/w3images-1-0-5-change-logs/comment-page-1/#comment-1368</link>
		<dc:creator>axew3</dc:creator>
		<pubDate>Sun, 11 Jul 2010 21:53:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.axew3.com/b10g/?p=346#comment-1368</guid>
		<description>At one point in the little presentation of w3images 1.0.5 i have give for sure one important point, that i think is a valuable argument to be discussed also in a different, well explained thread: the w3images is a &lt;strong&gt;secure plugin&lt;/strong&gt;.
Someone skilled can find out any possible problem that i have not consider while coding w3images images plugin for wordpress? I think by the way, it is not possible from my point of view.
Finally the code is here available for everybody and maybe the time can answer much better than any other consideration: axew3.com wordpress can be accessed through w3images plugin in some way? I say no because:
&lt;ol&gt;
	&lt;li&gt;functions that do not are checked for malicious variables are that contained and executed in the administration contest: if somebody can access wordpress administration folder, there is nothing w3images can change in this scenario.&lt;/li&gt;
	&lt;li&gt;the &quot;public code&quot; use specifics variables checked by a stronger pattern that do not leave much fantasy to any eventually tips.
This is the pattern:
&lt;code&gt;&quot;/[^a-zA-Z0-9_-]/&quot;;  // strong pattern&lt;/code&gt;
only letters, numbers, hyphens and underscores. Should be used in the &quot;public code&quot; a variable that isn&#039;t checked by this pattern to bypass this simple but effective security measure.&lt;/li&gt;
&lt;/ol&gt;
Any suggestion, help, discussion, answer, question or whatever you like about here is very appreciate.

</description>
		<content:encoded><![CDATA[<p>At one point in the little presentation of w3images 1.0.5 i have give for sure one important point, that i think is a valuable argument to be discussed also in a different, well explained thread: the w3images is a <strong>secure plugin</strong>.<br />
Someone skilled can find out any possible problem that i have not consider while coding w3images images plugin for wordpress? I think by the way, it is not possible from my point of view.<br />
Finally the code is here available for everybody and maybe the time can answer much better than any other consideration: axew3.com wordpress can be accessed through w3images plugin in some way? I say no because:</p>
<ol>
<li>functions that do not are checked for malicious variables are that contained and executed in the administration contest: if somebody can access wordpress administration folder, there is nothing w3images can change in this scenario.</li>
<li>the &#8220;public code&#8221; use specifics variables checked by a stronger pattern that do not leave much fantasy to any eventually tips.<br />
This is the pattern:<br />
<code>"/[^a-zA-Z0-9_-]/";  // strong pattern</code><br />
only letters, numbers, hyphens and underscores. Should be used in the &#8220;public code&#8221; a variable that isn&#8217;t checked by this pattern to bypass this simple but effective security measure.</li>
</ol>
<p>Any suggestion, help, discussion, answer, question or whatever you like about here is very appreciate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on w3images 1.0.5 change log by axew3</title>
		<link>http://www.axew3.com/b10g/2010/06/w3images-1-0-5-change-logs/comment-page-1/#comment-1333</link>
		<dc:creator>axew3</dc:creator>
		<pubDate>Sat, 10 Jul 2010 21:47:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.axew3.com/b10g/?p=346#comment-1333</guid>
		<description>the w3images gallery images plugin for wordpress has been released.
Check it here http://www.axew3.com/b10g/wp-w3downloads.php</description>
		<content:encoded><![CDATA[<p>the w3images gallery images plugin for wordpress has been released.<br />
Check it here <a href="http://www.axew3.com/b10g/wp-w3downloads.php" rel="nofollow">http://www.axew3.com/b10g/wp-w3downloads.php</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
