Comments on: WordPress Plugin Pet Peeve #1: Hardcoding wp-content http://willnorris.com/2009/05/wordpress-plugin-pet-peeve-hardcoding-wp-content there's more to life than this Sun, 31 Jul 2011 08:06:56 +0000 hourly 1 http://wordpress.org/?v=3.4-alpha-19719 By: WPBook 1.4 Released | Open Parenthesis http://willnorris.com/2009/05/wordpress-plugin-pet-peeve-hardcoding-wp-content#comment-39504 WPBook 1.4 Released | Open Parenthesis Mon, 04 Jan 2010 15:20:36 +0000 http://willnorris.com/?p=618#comment-39504 <p>[...] Removed hard coded references to wp-content and plugins directories (See http://willnorris.com/2009/05/wordpress-plugin-pet-peeve-hardcoding-wp-content) [...]</p> […] Removed hard coded references to wp-content and plugins directories (See http://willnorris.com/2009/05/wordpress-plugin-pet-peeve-hardcoding-wp-content) […]

]]> By: SwfObj Updates for WP 2.8 » orangeSplotch.com http://willnorris.com/2009/05/wordpress-plugin-pet-peeve-hardcoding-wp-content#comment-32034 SwfObj Updates for WP 2.8 » orangeSplotch.com Wed, 17 Jun 2009 02:56:19 +0000 http://willnorris.com/?p=618#comment-32034 <p>[...] it would get errors when they tried to use the SwfObj plugin. There’s a good post on how to correct the wp-content hardcoding problem if you are guilty of it [...]</p> […] it would get errors when they tried to use the SwfObj plugin. There’s a good post on how to correct the wp-content hardcoding problem if you are guilty of it […]

]]> By: Will Norris http://willnorris.com/2009/05/wordpress-plugin-pet-peeve-hardcoding-wp-content#comment-32024 Will Norris Tue, 16 Jun 2009 18:32:56 +0000 http://willnorris.com/?p=618#comment-32024 <p>@mattc: heh, no worries. I've wondered if calling this series "pet peeves" is too negative. Perhaps just "best practices" would be better? Glad to hear that it helped you fix your plugin though! :)</p> @mattc: heh, no worries. I’ve wondered if calling this series “pet peeves” is too negative. Perhaps just “best practices” would be better? Glad to hear that it helped you fix your plugin though! :)

]]> By: mattc http://willnorris.com/2009/05/wordpress-plugin-pet-peeve-hardcoding-wp-content#comment-32023 mattc Tue, 16 Jun 2009 18:16:04 +0000 http://willnorris.com/?p=618#comment-32023 <p>I just recently discovered that my plugin is guilty of this offense. Apologies to everyone I've offended up to now. Thanks to your post, I quickly corrected the error.</p> I just recently discovered that my plugin is guilty of this offense. Apologies to everyone I’ve offended up to now. Thanks to your post, I quickly corrected the error.

]]> By: WP-HOTWords 4.4 | bernabauer.com http://willnorris.com/2009/05/wordpress-plugin-pet-peeve-hardcoding-wp-content#comment-31773 WP-HOTWords 4.4 | bernabauer.com Sat, 06 Jun 2009 02:09:13 +0000 http://willnorris.com/?p=618#comment-31773 <p>[...] do plugin WP-HOTWords. Na versão 4.4 as modificações são poucas, mas necessárias. Hoje descobri que eu papei mosca em relação as normas de plugins para a versão 2.6 do WordPress. Isto mesmo! A [...]</p> […] do plugin WP-HOTWords. Na versão 4.4 as modificações são poucas, mas necessárias. Hoje descobri que eu papei mosca em relação as normas de plugins para a versão 2.6 do WordPress. Isto mesmo! A […]

]]> By: WordPress Plugin Pet Peeve #2: Direct Calls to Plugin Files — Will Norris http://willnorris.com/2009/05/wordpress-plugin-pet-peeve-hardcoding-wp-content#comment-31529 WordPress Plugin Pet Peeve #2: Direct Calls to Plugin Files — Will Norris Tue, 02 Jun 2009 20:05:51 +0000 http://willnorris.com/?p=618#comment-31529 <p>[...] Will Norris Thoughts on Identity, OpenID, WordPress, and Life Skip to content BlogAboutProjectsArchives « WordPress Plugin Pet Peeve #1: Hardcoding wp-content [...]</p> […] Will Norris Thoughts on Identity, OpenID, WordPress, and Life Skip to content BlogAboutProjectsArchives « WordPress Plugin Pet Peeve #1: Hardcoding wp-content […]

]]> By: Will Norris http://willnorris.com/2009/05/wordpress-plugin-pet-peeve-hardcoding-wp-content#comment-31514 Will Norris Tue, 02 Jun 2009 00:33:07 +0000 http://willnorris.com/?p=618#comment-31514 <p>well, sure I <strong>could</strong> (or use mod_rewrite like Joseph suggests). But it would be much easier if people would just fix their plugins.</p> well, sure I could (or use mod_rewrite like Joseph suggests). But it would be much easier if people would just fix their plugins.

]]> By: David Recordon http://willnorris.com/2009/05/wordpress-plugin-pet-peeve-hardcoding-wp-content#comment-31513 David Recordon Tue, 02 Jun 2009 00:19:49 +0000 http://willnorris.com/?p=618#comment-31513 <p>Couldn't you always create a symlink if you wanted to make this work for plugins that hardcode paths?</p> Couldn’t you always create a symlink if you wanted to make this work for plugins that hardcode paths?

]]> By: Joseph Scott http://willnorris.com/2009/05/wordpress-plugin-pet-peeve-hardcoding-wp-content#comment-31409 Joseph Scott Mon, 25 May 2009 15:33:40 +0000 http://willnorris.com/?p=618#comment-31409 <p>I've run into this problem with a few plugins as well. I got tired of fixing plugin each time a new version of the plugin was released, so I added a few mod_rewrite rules to ensures that the requests ended up in the right spot.</p> <p>I ended up adding those rules to my 'WordPress in a separate directory from SVN' post:</p> <p>http://josephscott.org/archives/2009/02/installing-wordpress-as-a-subversion-checkout-or-external-in-a-subdirectory/</p> I’ve run into this problem with a few plugins as well. I got tired of fixing plugin each time a new version of the plugin was released, so I added a few mod_rewrite rules to ensures that the requests ended up in the right spot.

I ended up adding those rules to my ‘WordPress in a separate directory from SVN’ post:

http://josephscott.org/archives/2009/02/installing-wordpress-as-a-subversion-checkout-or-external-in-a-subdirectory/

]]>