<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Alexandru Dinulescu&#039;s Thoughts&#187; Wordpress</title>
	<atom:link href="http://alexdweb.com/blog/tag/wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://alexdweb.com/blog</link>
	<description>This blog is about everything/anything related to XHTML/CSS and of course my favourite js library, jQuery.</description>
	<lastBuildDate>Thu, 09 Dec 2010 12:04:10 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Programming Mistakes</title>
		<link>http://alexdweb.com/blog/2010/01/05/programming-mistakes/</link>
		<comments>http://alexdweb.com/blog/2010/01/05/programming-mistakes/#comments</comments>
		<pubDate>Tue, 05 Jan 2010 14:56:40 +0000</pubDate>
		<dc:creator>Dinulescu Alexandru Adrian</dc:creator>
				<category><![CDATA[Stupid Things]]></category>
		<category><![CDATA[XHTML/CSS]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Stupid Mistakes]]></category>
		<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[Wordpress Themes]]></category>

		<guid isPermaLink="false">http://alexdweb.com/blog/?p=169</guid>
		<description><![CDATA[Hello This post is sort of a checklist of things to check before you upload you&#8217;re files on the webserver, and this will be updated with more things as time allows it. One of the most annoying things you can get is that if you maintain a localhost version of your website, and your live [...]]]></description>
			<content:encoded><![CDATA[<p> Hello </p>
<p> This post is sort of a checklist of things to check before you upload you&#8217;re files on the webserver, and this will be updated with more things as time allows it. </p>
<p> One of the most annoying things you can get is that if you maintain a localhost version of your website, and your live website has the google analytics code in it, when you upload your local files overwriting the files on the webserver, those newer files you have on your localhost may not have the google analytics script set, so you will end up like me with 1 week of uncounted traffic. Stupid and Newbie mistake, meh note to self, never push updates after midnight because shit may happen. </p>
<p><span id="more-169"></span></p>
<p> List </p>
<ul>
<li> Overwriting files on the webserver that have the Google Analytics code with files that do not have that code, Missing Traffic for the Lose <img src='http://alexdweb.com/blog/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' />  </li>
<li> Another thing that can go awkward is that if you do some sort of <acronym title="Hypertext Preprocessor<br />
">PHP</acronym> and you include/require files and you have a $path variable, when you upload the config on the server, make sure you change the $path from $path = http://localhost/ to $path = http://yourwebsite.com/. </li>
<li> Based on wordpress stylesheet files, if you have a <acronym title="Cascading Style Sheets">CSS</acronym> folder and you copy some <acronym title="Cascading Style Sheets">CSS</acronym> from the styles.css into a new file in the <acronym title="Cascading Style Sheets">CSS</acronym> folder, then you need to update any pathing for images. Normally all <acronym title="Cascading Style Sheets">CSS</acronym> files are in a specific folder so this is a non-issue, but with <acronym title="Wordpress">WP</acronym> you have to pay attention, else you spend 30 minutes trying to figure why it isnt working. </li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://alexdweb.com/blog/2010/01/05/programming-mistakes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress InanisMOD theme launch</title>
		<link>http://alexdweb.com/blog/2009/12/27/wordpress-inanismod-theme-launch/</link>
		<comments>http://alexdweb.com/blog/2009/12/27/wordpress-inanismod-theme-launch/#comments</comments>
		<pubDate>Sun, 27 Dec 2009 21:53:43 +0000</pubDate>
		<dc:creator>Dinulescu Alexandru Adrian</dc:creator>
				<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[InanisMOD Theme]]></category>
		<category><![CDATA[Wordpress Themes]]></category>

		<guid isPermaLink="false">http://alexdweb.com/blog/?p=161</guid>
		<description><![CDATA[Hello For the past 2 weeks or so i&#8217;ve been rewriting the Inanis Theme for wordpress, because i really liked the design and functionality offered but i hated the way it was coded. So i rewrote all the code. You can get the original Inanis Theme from here Check the readme.txt file inside for what [...]]]></description>
			<content:encoded><![CDATA[<p> Hello </p>
<p> For the past 2 weeks or so i&#8217;ve been rewriting the Inanis Theme for wordpress, because i really liked the design and functionality offered but i hated the way it was coded. So i rewrote all the code. You can get the original Inanis Theme from <a href="http://Inanis.net">here</a> </p>
<p><span id="more-161"></span></p>
<p> Check the readme.txt file inside for what was changed. I used the theme for some time over this blog and i didnt ran into any issues with it, so i have decided to launch it for everyone </p>
<p> The <acronym title="ZIP Archive">ZIP</acronym> file can be downloaded from <a href="http://alexdweb.com/blog/wp-content/uploads/2009/12/inanisMod_v1.3.zip"> Here </a>. Also i modified the comments-template.php file, <a href="http://alexdweb.com/blog/wp-content/uploads/2009/12/comment-template.zip">here</a> is the file, you can copy it INSIDE the wp-includes folder on your blog. </p>
<p> Basically what you have currently on this blog, is what you get when you download both files. The only special annotation i should make is that this theme does not support Internet Explorer 6 or older. I really think that 9 year old browsers should be dead, so please plan accordingly. </p>
<p> If you encounter any issues please let me know. I plan on expanding this theme with new functionality from time to time and i will release new versions. Currently the version is v1.3 (the v1.0 to current versions were test versions and 1.3 is the last stable release version). </p>
<p> Best Regards </p>
]]></content:encoded>
			<wfw:commentRss>http://alexdweb.com/blog/2009/12/27/wordpress-inanismod-theme-launch/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Redirecting WordPress Feeds to Feedburner&#8217;s</title>
		<link>http://alexdweb.com/blog/2009/12/26/redirecting-wordpress-feeds-to-feedburners/</link>
		<comments>http://alexdweb.com/blog/2009/12/26/redirecting-wordpress-feeds-to-feedburners/#comments</comments>
		<pubDate>Sat, 26 Dec 2009 20:19:49 +0000</pubDate>
		<dc:creator>Dinulescu Alexandru Adrian</dc:creator>
				<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[.htaccess]]></category>
		<category><![CDATA[Feedburner]]></category>
		<category><![CDATA[Feeds]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[RSS 2.0]]></category>

		<guid isPermaLink="false">http://alexdweb.com/blog/?p=158</guid>
		<description><![CDATA[Hello After scouring the web for like 1h in order to find this information, i did eventually find it, however it was in a couple of different posts on another blog. In order to keep stuff simple, let&#8217;s put everything together. Using the benefits of feedburner is a no-brainer, because you get a shitload of [...]]]></description>
			<content:encoded><![CDATA[<p> Hello </p>
<p> After scouring the web for like 1h in order to find this information, i did eventually find it, however it was in a couple of different posts on another blog. In order to keep stuff simple, let&#8217;s put everything together. Using the benefits of feedburner is a no-brainer, because you get a shitload of useful statistics. The only problem is that you will need to maintain 2 lists of feeds, your own internal feed + the official feedburner&#8217;s. And now depends on how many users you have subscribed.</p>
<p><span id="more-158"></span></p>
<p> A few notes first tho. First if you use your blog as a directory on your domain rather than a full directory, like http://example.com/blog/ instead of http://example.com/ then you will probably have 2 htaccess files. 1) for the main website and 2) for the blog itself. When you edit the htaccess, you must edit the BLOG htaccess which is usually found in your /blog/ folder if you use the blog-directory-thingy (if you dont, then your main-top-domain-level htaccess will be your blog&#8217;s. </p>
<p> Secondly you need to PUT THE CODE <strong>BEFORE</strong> the WordPress&#8217;s own rewrite rules (in case you are using permalinks, and if you dont use permalinks YOU SHOULD! </p>
<p> First off is you go to http://feedburner.com and make an account. Put your original feed there and make sure it displays properly. </p>
<p> Then Apply the code found below in the specific htaccess file on your server </p>
<h3> .mod_rewrite htacess thingy </h3>
<div class="codecolorer-container text default" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;width:435px;"><div class="text codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap">&lt;IfModule mod_rewrite.c&gt;<br />
&nbsp;RewriteEngine on<br />
&nbsp;RewriteCond %{HTTP_USER_AGENT} !FeedBurner &nbsp; &nbsp;[NC]<br />
&nbsp;RewriteCond %{HTTP_USER_AGENT} !FeedValidator [NC]<br />
&nbsp;RewriteRule ^feed/?([_0-9a-z-]+)?/?$ http://feeds.feedburner.com/YourFeedburnerFeedGoesHere[R=302,NC,L]<br />
&lt;/IfModule&gt;</div></div>
<p> This is just a quick thing, mostly using the default settings, but you really should read the full explanations found at: </p>
<ul>
<li><a href="http://perishablepress.com/press/2008/01/28/laser-focused-feeds-and-smarter-feed-management/">PersishablePress.com &#8211; Laser Focused Feeds and Smarter Feed Management</a></li>
<li><a href="http://perishablepress.com/press/2008/01/23/serve-yourself-why-feedburner-needs-a-feed-fix/">PerishablePress.com &#8211; Why Feedburner needs a feed-fix </a></li>
<li><a href="http://perishablepress.com/press/2008/03/25/redirect-wordpress-feeds-to-feedburner-via-htaccess-redux/">PerishablePress.com &#8211; Redirect WordPress Feeds to Feedburner via Htaccess redux</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://alexdweb.com/blog/2009/12/26/redirecting-wordpress-feeds-to-feedburners/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress DB possible issue -&gt; Blog Takeover</title>
		<link>http://alexdweb.com/blog/2009/05/08/wordpress-db-possible-issue-blog-takeover/</link>
		<comments>http://alexdweb.com/blog/2009/05/08/wordpress-db-possible-issue-blog-takeover/#comments</comments>
		<pubDate>Fri, 08 May 2009 18:04:49 +0000</pubDate>
		<dc:creator>Dinulescu Alexandru Adrian</dc:creator>
				<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[Nerd Rage]]></category>
		<category><![CDATA[Wordpress takeover]]></category>

		<guid isPermaLink="false">http://alexdweb.com/blog/?p=25</guid>
		<description><![CDATA[Hello Sometimes if your wordpress DB is down, you should normally get an error saying that the DB is unavailable and then some messages will appear with the possible cause of this, like the DB name is not found, the settings in the wp-config folder are wrong, and the like. However there is a case [...]]]></description>
			<content:encoded><![CDATA[<p> Hello </p>
<p> Sometimes if your wordpress <acronym title="DataBase">DB</acronym> is down, you should normally get an error saying that the <acronym title="DataBase">DB</acronym> is unavailable and then some messages will appear with the possible cause of this, like the <acronym title="DataBase">DB</acronym> name is not found, the settings in the wp-config folder are wrong, and the like. However there is a case that surprise surprise you get on the page with the INSTALLATION of wordpress and you&#8217;ve just lost your <acronym title="WordPress">WP</acronym> blog.</p>
<p> The file is found in wp-admin/install.php </p>
<p> As a good rule of thumb, it&#8217;s advisable to delete all readme.txt, nfo, info files from all plug-ins, there have been reports of some chinese bots crawling wordpress blogs for these, so save yourself some bandwidth and delete those </p>
<p> In order to make sure this doesnt happen at all, there are 3 methods </p>
<ul>
<li> Method 1: JUST <strong>NUKE</strong> the INSTALL.php file. After the blog has been installed you dont need this file anymore so just delete it </li>
<li> Method 2: htaccess file
<div class="codecolorer-container php default" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;width:435px;"><div class="php codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap"><span style="color: #666666; font-style: italic;"># PROTECT install.php<br />
</span><span style="color: #339933;">&lt;</span>Files install<span style="color: #339933;">.</span>php<span style="color: #339933;">&gt;</span><br />
&nbsp;Order Allow<span style="color: #339933;">,</span>Deny<br />
&nbsp;Deny from all<br />
&nbsp;Satisfy all<br />
<span style="color: #339933;">&lt;/</span>Files<span style="color: #339933;">&gt;</span></div></div>
</li>
<li> Method 3: Replace it entirely with something else that is written by you from the start </li>
</ul>
<p> Problem Fixed </p>
]]></content:encoded>
			<wfw:commentRss>http://alexdweb.com/blog/2009/05/08/wordpress-db-possible-issue-blog-takeover/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

