http://wordpress.org/support/ WordPress › Support User Favorites: nickajordan en Thu, 26 Nov 2009 06:51:20 +0000 http://wordpress.org/support/topic/187700/page/2#post-947011 Tue, 06 Jan 2009 16:20:36 +0000 bigcrags 947011@http://wordpress.org/support/ <p>Superb, I've sat on a zeus server for a year without fixing this because I didn't know how. Someone pulled me up for having rubbish URL's today and yours was the solution that worked. Thanks. </p> http://wordpress.org/support/topic/188959#post-864761 Mon, 29 Sep 2008 09:21:52 +0000 thecoup 864761@http://wordpress.org/support/ <p>Wow, this is terrible. My problem was a little different. The solution is below.</p> <p>On WP 2.6.1, the site worked initially with /%year%/%monthnum%/%postname%/. I have WP installed in /wordpress/. I kept the blog viewable at /wordpress as well for development. When I changed the blog address to the root <a href="http://codex.wordpress.org/Giving_WordPress_Its_Own_Directory">using these directions</a>, pretty permalinks stopped working. I switched it back to the /wordpress directory, without ever touching .htaccess and the pretty permalinks still didn't work! </p> <p>After trying many many things, the solution that worked for me:<br /> - dropped the www's from the wp and blog directory. this forced me to login again. put back the www's, and logged in again.<br /> - chmod .htaccess to 777<br /> - changed permalinks settings from default, to numeric, and then back to month and name. presto!<br /> - important: chmod .htaccess back to 644</p> <p>The weird thing: WP never had trouble changing the .htaccess file. I downloaded and checked that it was updated correctly. For some reason, things still wouldn't work as expected. The steps above are ridiculous, but they're what I did before things started working again... </p> http://wordpress.org/support/topic/187700/page/2#post-816257 Tue, 29 Jul 2008 15:05:28 +0000 magius2244 816257@http://wordpress.org/support/ <p>I am on a IIS server and I have tried adding the category base values and tag base values to resolve the issue as suggested and I still cannot view my posts except for the home page. Does anyone know when 2.6.1 is due? This is really frustrating and my traffic has plummeted. </p> http://wordpress.org/support/topic/187700/page/2#post-816027 Tue, 29 Jul 2008 07:39:46 +0000 Anonymous 816027@http://wordpress.org/support/ <p>adRem you are the man !! works perfectly after applying the script you provided. </p> <p>I was having exactly the same problem i.e. hosting WordPress 2.6 on a Zeus server and wanting the permalink.</p> <p>Thanks !</p> <p>Jaffer </p> http://wordpress.org/support/topic/187700#post-814471 Sun, 27 Jul 2008 03:32:32 +0000 Anonymous 814471@http://wordpress.org/support/ <p>Hi guys,</p> <p>I had the same problem with permalinks on a Zeus server. I wanted a simple custom <code>/%postname%/</code> rewrite (so for instance, the URL for the about page would have to be: <a href="http://www.domain.com/about/" rel="nofollow">http://www.domain.com/about/</a>), but I either ended up with the index.php pushing itself in (www.domain.com/index.php/about/) or a 404 Not Found error.</p> <p>The main issue seemed to be the Zeus server in my case. It does not work like the Apache .htacces mod_rewrite rules WordPress generates. They need to be converted into "Zeus-ish" regex.</p> <p>If you are running your WordPress blog on a Zeus server and are having problems with your permalinks after the recent update, try copy pasting this script into the appropriate rewrite rules field in your hosting admin panel. If you're not sure what/where that is, please ask your hosting provider for help. (If you pay them, they should help you with this!)</p> <pre><code>RULE_0_START: # get the document root map path into SCRATCH:DOCROOT from / # initialize our variables set SCRATCH:ORIG_URL = %{URL} set SCRATCH:REQUEST_URI = %{URL} # see if theres any queries in our URL match URL into $ with ^(.*)\?(.*)$ if matched then set SCRATCH:REQUEST_URI = $1 set SCRATCH:QUERY_STRING = $2 endif RULE_0_END: RULE_1_START: # prepare to search for file, rewrite if its not found set SCRATCH:REQUEST_FILENAME = %{SCRATCH:DOCROOT} set SCRATCH:REQUEST_FILENAME . %{SCRATCH:REQUEST_URI} # check to see if the file requested is an actual file or # a directory with possibly an index. don&#39;t rewrite if so look for file at %{SCRATCH:REQUEST_FILENAME} if not exists then look for dir at %{SCRATCH:REQUEST_FILENAME} if not exists then set URL = /index.php?q=%{SCRATCH:REQUEST_URI} goto QSA_RULE_START endif endif # if we made it here then its a file or dir and no rewrite goto END RULE_1_END: QSA_RULE_START: # append the query string if there was one originally # the same as [QSA,L] for apache match SCRATCH:ORIG_URL into % with \?(.*)$ if matched then set URL = %{URL}&#38;%{SCRATCH:QUERY_STRING} endif goto END QSA_RULE_END:</code></pre> <p>You can find the original script here: <a href="http://drupal.org/node/46508">http://drupal.org/node/46508</a></p> <p>It worked for me, and believe me... I'm very technically challenged ;-)</p> <p>cheers,<br /> adRem </p> http://wordpress.org/support/topic/187700#post-810590 Tue, 22 Jul 2008 01:14:57 +0000 estjohn 810590@http://wordpress.org/support/ <p>Silentwind, that might have worked for you, but it did not work for me. wish it had been that easy... I tried that more than a few times. </p> http://wordpress.org/support/topic/187700#post-810562 Mon, 21 Jul 2008 23:57:40 +0000 Anonymous 810562@http://wordpress.org/support/ <p>Hmm... Why you have to go through .htaccess.<br /> All I did just change my permalink setting to something else, save it, and change it back to my previous setting.<br /> Voila, it's work again.</p> <p>Like I wrote it <a href="http://bayu.freelancer.web.id/2008/07/18/wordpress-26-upgrade-experience/">here</a> </p> http://wordpress.org/support/topic/187700#post-808313 Sat, 19 Jul 2008 01:44:30 +0000 estjohn 808313@http://wordpress.org/support/ <p>Thanks.. unfortunately it was going back to 2.5 and not using 2.6 deleting the .htaccess didnt work, adding something to categories and tags didnt work, using index.php or removing it either one did not work. Only solution was to go back :( </p> http://wordpress.org/support/topic/187700#post-807116 Thu, 17 Jul 2008 22:15:11 +0000 7milesdown 807116@http://wordpress.org/support/ <p>looking at your site estjohn it seems you found a fix. </p> http://wordpress.org/support/topic/187700#post-805924 Thu, 17 Jul 2008 00:12:51 +0000 estjohn 805924@http://wordpress.org/support/ <p>Funny thing is, I am on apache on a *nix box... and 2.5 I had to use index.php/%postname%/ or it would not work.. now i can't use it or anything to get permalinks to work. Only the default works. Even using the default theme, no plugins.</p> <p>Same box, different site - default and with a theme, no plugins it works fine. /%category%/%postname%/</p> <p>I even copied the .htaccess over - rules, permissions, owner, everything exact same. I cant figure it out</p> <p>my .htaccess<br /> '<br /> # BEGIN WordPress<br /> &lt;IfModule mod_rewrite.c&gt;<br /> RewriteEngine On<br /> RewriteBase /<br /> RewriteCond %{REQUEST_FILENAME} !-f<br /> RewriteCond %{REQUEST_FILENAME} !-d<br /> RewriteRule . /index.php [L]<br /> &lt;/IfModule&gt;</p> <p># END WordPress<br /> '</p> <p>AA Rewrite Rules reports<br /> &gt; Permalink: /%category%/%postname%/<br /> &gt; Writable .htaccess file found<br /> &gt; mod_rewrite found<br /> &gt; Not using pathinfo style index permalinks<br /> &gt; Using mod_rewrite permalinks </p> http://wordpress.org/support/topic/187700#post-805459 Wed, 16 Jul 2008 16:51:23 +0000 Otto42 805459@http://wordpress.org/support/ <p>The schedule only gets pushed up for security issues, generally. This is not a security issue, and there's a known workaround that does indeed work.</p> <p>The roadmap has no date set for 2.6.1, however I'd be surprised if it happened in less than 3 weeks. </p> http://wordpress.org/support/topic/187700#post-805454 Wed, 16 Jul 2008 16:46:46 +0000 rawalex 805454@http://wordpress.org/support/ <p>Umm, Otto, I can read, I can also read that it ain't gonna get fixed until 2.6.1... </p> <p>milestone changed from 2.7 to 2.6.1.</p> <p>here is to hoping that 2.6.1 comes out, say, Friday. </p> http://wordpress.org/support/topic/187700#post-805361 Wed, 16 Jul 2008 15:54:01 +0000 Otto42 805361@http://wordpress.org/support/ <blockquote><p><em>In the meanwhile, perhaps we can figure out why something that worked fine (permalinks) was changed...</em></p></blockquote> <p>If you had been paying attention, you'd know that that has already occurred: <a href="http://trac.wordpress.org/ticket/7306" rel="nofollow">http://trac.wordpress.org/ticket/7306</a> </p> http://wordpress.org/support/topic/187700#post-805346 Wed, 16 Jul 2008 15:44:24 +0000 The Spook 805346@http://wordpress.org/support/ <p>I'm on IIS. The workaround Otto referred to worked, and my permalinks remained the same. </p> http://wordpress.org/support/topic/187700#post-804654 Tue, 15 Jul 2008 23:22:24 +0000 rawalex 804654@http://wordpress.org/support/ <p>I do not respect poor code. Poor code - and poorly tested code - is just that. I can't be anything other than amazed that this went out with this sort of a change in it.</p> <p>I'm not whining, but any suggestions for WP made by the people I am involved with has been ignored, many of them to do with significantly improving the queries and execution speed of wordpress. But that's okay.</p> <p>In the meanwhile, perhaps we can figure out why something that worked fine (permalinks) was changed, and perhaps we can find a way to roll back that part of the code? </p> http://wordpress.org/support/topic/188959#post-804502 Tue, 15 Jul 2008 21:08:15 +0000 Otto42 804502@http://wordpress.org/support/ <p>The effects of it should be to fix the problem. Makes sense, no? </p> http://wordpress.org/support/topic/188959#post-804501 Tue, 15 Jul 2008 21:06:40 +0000 arretx 804501@http://wordpress.org/support/ <p>Hmmm...okay I added category and tag bases, but I have no idea what that actually does:</p> <p>Category: /categories/<br /> Tag: /tags/</p> <p>What will the effects of this be? It also appears that my comments have been restored too...guess that makes sense since everything is dependent upon the permalinks working. </p> http://wordpress.org/support/topic/188959#post-804491 Tue, 15 Jul 2008 21:01:46 +0000 arretx 804491@http://wordpress.org/support/ <p>I see. So, is there going to be a fix for this? My site is completely useless as of now since none of the page links work, the comments don't work, etc., etc. It's all due to the permalink problem and I'm short of knowledge when it comes to "why" this happens. I can follow steps to fix if there are steps... </p> http://wordpress.org/support/topic/188959#post-804448 Tue, 15 Jul 2008 20:32:43 +0000 Saravanan07 804448@http://wordpress.org/support/ <p>Thx for the Help Otto42..;) </p> http://wordpress.org/support/topic/188959#post-804418 Tue, 15 Jul 2008 20:11:56 +0000 Otto42 804418@http://wordpress.org/support/ <p>There's a sticky on this subject:<br /> <a href="http://wordpress.org/support/topic/189058" rel="nofollow">http://wordpress.org/support/topic/189058</a></p> <p>@gregrickaby: Just because somebody makes a post doesn't mean we read it. He didn't post it anywhere else, including the bug tracker. </p> http://wordpress.org/support/topic/188959#post-804410 Tue, 15 Jul 2008 20:06:40 +0000 Saravanan07 804410@http://wordpress.org/support/ <p>Many people have reported permalinks not working after upgrading to 2.6. In all cases, these people have permalink structures that contain "index.php". This is a bug, detailed here: <a href="http://trac.wordpress.org/ticket/7306" rel="nofollow">http://trac.wordpress.org/ticket/7306</a> </p> http://wordpress.org/support/topic/188959#post-804408 Tue, 15 Jul 2008 20:05:39 +0000 Saravanan07 804408@http://wordpress.org/support/ <p>Hello..I have done a temporary fix for the problem. What you have to do is add some values in for the category and tag bases. The words "category" and "tag" will do just fine. As long as they are not blank, this should work around the bug.See the image:-</p> <p><a href="http://farm4.static.flickr.com/3228/2672367868_276c738559_o.png" rel="nofollow">http://farm4.static.flickr.com/3228/2672367868_276c738559_o.png</a> </p> http://wordpress.org/support/topic/187700#post-804404 Tue, 15 Jul 2008 20:01:37 +0000 Otto42 804404@http://wordpress.org/support/ <p>Well, bitching about the product doesn't make it any better. So stop it. If you want to be constructive, fine. But comments like "I am amazed..." are not appreciated and they rather lead those of us who actually try to contribute patches and code to the project to be very much inclined to ignore anything else you have to say.</p> <p>I respect expertise and knowledge. I do not respect whiners. </p> http://wordpress.org/support/topic/187700#post-804381 Tue, 15 Jul 2008 19:52:45 +0000 rawalex 804381@http://wordpress.org/support/ <p>otto, I use wordpress extensively, and it is important to me that the product works, or is at least functional without security holes. I hang around here hoping like heck that there will be a secure and reasonably up to date version so that I can get off the upgrade elevator at some point without being in a security risk situation. I also help a number of people out with their personal blogs, and end up seeing these problems because people are encouraged (heck reminded every time they log in) to make an upgrade that they may not need or want.</p> <p>why do you hang around here? Looking to meet new people? </p> http://wordpress.org/support/topic/187700#post-804364 Tue, 15 Jul 2008 19:43:24 +0000 Otto42 804364@http://wordpress.org/support/ <p>@rawalex:<br /> a) There's two workarounds there.<br /> b) If the first workaround works for you, then it does not affect Google or anybody else at all, because all your old permalinks will still work, and redirect to the new permalinks with 301 redirections, thanks to canonical redirects.<br /> c) The second workaround simply remedies the problem, the permalinks remain the same.</p> <p>So quite frankly, you don't know what you're talking about.</p> <p>As far as your amazement, WordPress is open source, and if nobody reports a problem with it, then it doesn't get found. I would think that this would be pretty obvious.</p> <p>Why do you stick around here anyway? You do nothing but troll and bitch about WordPress all the time. If you don't like it, then don't use it. </p> http://wordpress.org/support/topic/187700#post-804353 Tue, 15 Jul 2008 19:39:06 +0000 aarnet 804353@http://wordpress.org/support/ <p>@Otto42: Sorry, didn't know how to act. Now I know better. </p> http://wordpress.org/support/topic/187700#post-804136 Tue, 15 Jul 2008 17:34:46 +0000 rawalex 804136@http://wordpress.org/support/ <p>Otto, that work around is a pain in the butt for people who have been using it, plus a major problem for the search engines who are going to see all the pages as having disappeared or been removed from the site.</p> <p>I am amazed that something as simple as this made it out to a release version. </p> http://wordpress.org/support/topic/187700#post-804106 Tue, 15 Jul 2008 17:23:01 +0000 Otto42 804106@http://wordpress.org/support/ <p>Also, workaround is here:<br /> <a href="http://wordpress.org/support/topic/189058" rel="nofollow">http://wordpress.org/support/topic/189058</a> </p> http://wordpress.org/support/topic/187700#post-804104 Tue, 15 Jul 2008 17:21:51 +0000 Otto42 804104@http://wordpress.org/support/ <p>@aarnet: So you posted it here 6 days ago, but didn't bother to stick it on the bug tracker until 6 hours ago? Any particular reason?</p> <p>Bug reports do not go here. This is a support forum only. </p> http://wordpress.org/support/topic/187700#post-804090 Tue, 15 Jul 2008 17:12:26 +0000 aarnet 804090@http://wordpress.org/support/ <p>This is now a "critical" error with "high" priority. Take a look at <a href="http://trac.wordpress.org/ticket/7306" rel="nofollow">http://trac.wordpress.org/ticket/7306</a></p> <p>This error occurs no matter what server you use. This error <strong>only</strong> occurs if you use "index.php/%postname%/". </p>