Lucky 1.3 Rewrite

This plugin gets around Apache 1.3’s greedy rewrite rules. It’s called “Lucky 1.3″ in honor of the infamously greedy 1.3 version of Apache. It works around a very odd bug in Apache 1.3’s mod_rewrite which causes it to use “greedy” regexes, even when it shouldn’t.

Read more about this annoying bug »

Not For WordPress 2.0

If you use this plugin with WordPress 2.0, then it will bork all sorts of stuff all over the place.

That’s the bad news. The good news is that WP2.0 is built in such a way that you don’t need this plugin, even if you’re using Apache 1.3! That’s because WP2 handles the URI processing internally, rather than off-loading it onto Apache configuration files.

There will not be a WP2.0-compatible version of this plugin, ever. That’s because it’s obsolete as of WP2.0. I, for one, couldn’t be happier. This plugin is a kludge at best, and has been a royal pain to maintain, even though it was interesting to build. Since the newest version of WordPress doesn’t seem to require this plugin, I probably won’t be dealing much with bugs or problems.

Current Version: 0.4; Status: Late Beta, a few known minor issues

The bug reported below regarding date-based permalinks has been fixed. This should work for almost all permalink styles, and will correct cruftless search URIs, category feeds, and any other WP-generated “greedy” RewriteRules. It’s recommended for any and all Apache 1.3 systems using cruft-free URIs.

Known Bugs

When using permalink styles that mix %category% and numerical items, such as /%year%/%monthnum%/%category%/%postname%/, you may see weird behavior. It’s recommended to either use just /%category%/%postname%/, or, if you must use numerical items such as %year%, %post_id%, etc., then don’t use %category% in the permalink. I am working on tracking down the source of this bug, but it’s a bit tricky, and I have a lot of other stuff to do that actually pays the bills. If you want to use permalinks that mix %category% and numerical items, then please leave a comment below, and I’ll work with you to try and debug this issue.

Note: The warnings regarding using non-numeric items in your permalink structure, and this causing problems accessing stylesheets and other files, are no longer valid. WordPress version 1.5.1 and above checks to see if the request matches a filename before applying any of the rewrite rules. This means that, if you’re requesting a particular file (such as a stylesheet, javascript file, or anything else), it will work even if the request looks like a possible permalink.

Not Really a Bug, but an Issue to Consider

By default, the WordPress rules work something like this:

  1. If the request matches a file or directory, serve that.
  2. Otherwise, if it matches a WordPress-ish URI, then do whatever we should do. (Something like index.php?foo=bar, usually.)
  3. Otherwise, let the server do whatever it does when it can’t find something.

If it looks like a WordPress-ish URI, but doesn’t actually match any posts, like /category/blabdeelgloop or some such, then you’ll get the WordPress 404 page. (Generally handled by 404.php in your template folder.) If a request doesn’t look like a WordPress URI, and also doesn’t match anything, then you’ll get your server’s regular 404 page, which usually looks like this by default. However, the logic changes somewhat when you’re using this plugin:

  1. If the request matches a file or directory, serve that.
  2. Otherwise, if it matches a non-greedy WordPress-ish URI, then do whatever it should do. (Something like index.php?foo=bar, usually.)
  3. Otherwise, call wp-htaccess.php, which does this:
    1. Look at the request and try to match it up to something. If it matches, then set the $_GET superglobal, and call index.php.
    2. If not, then just call index.php and hope for the best.

So, the long and the short of it is, you won’t get server-generated 404 messages any more. Any requests that aren’t found will get the WordPress 404 page instead of your default server 404.

Some might call this a feature, others a bug. Since my WordPress 404 page just calls my regular 404 handler, I look at this as normal. However you look at this, you can’t say you weren’t warned :)

Your Stupid Plugin Borked My Site!

I’m sorry to hear that. Did you follow the instructions?

Follow these steps to debug the problem:

  1. Delete wp-htaccess.php.
  2. Remove all the wordpress-generated rules from your .htaccess file.
  3. Log into the back-end and disable the plugin.
  4. Re-save your permalink settings.

Your site should work again.

Now, let’s figure out why it died.

I’m happy to receive bug reports, and will gladly help figure out why it isn’t working. If you’re polite, then there’s even a chance that I’ll fix it to make it work the way that you need it to. But I need the following information to do that. Don’t bother submitting a bug report without answering these questions:

What are you using as your permalink style?

Some styles work better than
others. See if it works when you use something like /%category%/%post-name% or
/%year%/%monthnum%/%post-name% with the plugin enabled.

Is anything being written to the .htaccess?

If not, then chances are that .htaccess is not writable. chmod it 0777 and try again.

Is anything being written to wp-htaccess.php?

If not, then that’s the problem. Create the file manually, upload it, and chmod it 0777.

If data IS being written to the wp-htaccess.php file, then try adding some debug code to it. Open the file in a text editor. Near the bottom of the file, you’ll see this line:
include dirname(__FILE__) . '/index.php';
Replace that with:
print_r( $_GET );
and view the results in a web browser. That will tell you what wp-htaccess.php thinks your URI means. If you just see the regular blog page, or it’s still an HTTP 500 error, then try another URI, preferrably one that would normally make Apache 1.3 choke.

If you can access your server’s error log, then it’d be good to look in it for error messages that might tell you what it’s choking on.

Ok, I followed the instructions, and I got you your information, and I still can’t figure it out.

Tell me about it.

Instructions

If you have Apache 2.0, then you don’t need this. (You’ll know if the “permalinks” setting works with %category% permalinks. If it does, then you don’t need this.)

  1. Make your WordPress root directory server-writable. If you don’t feel like doing that, then fine. Just create a file called wp-htaccess.php, and upload it to your WordPress root, and make it server-writable. If you haven’t already, you’ll also want to make your .htaccess file writable so that WordPress can update it.
  2. Save apache13htaccess.php.
  3. Upload to your /wp-content/plugins/ directory.
  4. Activate the plugin in your plugins management page.
  5. Do something to make WordPress re-create your .htaccess file. (For example, go to the Options → Permalink page, and click “Update Permalink Structure,” or create a new static Page.) This will re-generate all your .htaccess rules and also populate the wp-htaccess.php file with the appropriately juicy goodness.

Any rules that might get greedy are off-loaded into wp-htaccess.php. If a request doesn’t match anything, then it falls into that file, which crunches the Request URI, analyzes it based on the greedy generated rules, and then calls index.php once it’s figured out what it needs to get.

Happy Permalinking!

46 Responses to “Lucky 1.3 Rewrite”

  1. On August 16th, 2005 at 16:44:03, Isaac Said:

    Applied to 0.1 version, bug no longer relevant.

    Warning:

    There appears to be a bug if you use this plugin with permalinks like: /%year%/%monthnum%/%postname%/

    I’ll post a solution when I figure out why this is. It works perfectly if you use /%category%/%postname%/, however. If you are already using this plugin, and you want to stop using %category% permalinks, then deactivate it before changing your permalink structure!

  2. On August 17th, 2005 at 13:08:38, pgrote Said:

    Hi! I appreciate this plugin, but cannot get it to work. When I download from your site there is no extension, so I made it PHP.

    When I upload to my site and look in plugins, it doesn’t show as a plugin, but displays all the code across the three columns for plugins.

    What am I doing wrong?

  3. On August 17th, 2005 at 13:22:08, Isaac Said:

    Click on the link. You’ll be taken to a page that shows you the source code.

    Click on the link that says Save this file.

    :)

  4. On August 18th, 2005 at 13:23:59, iampariah Said:

    Hi, Isaac. I just tried your plugin, but it doesn’t seem to work entirely.

    With the plugin running, I can now include %category% in the permalink structure without getting server 404. Instead I get a WP 404 page.

    The plugin created wp-htaccess.php just fine.

    Help? See it in action here: http://www.designorati.com/news/

  5. On August 18th, 2005 at 14:19:37, Isaac Said:

    iampariah,

    That does seem odd, and I can reproduce the error. Does it work when you use either /%category%/%postname% or /%year%/%monthnum%/%postname%?

    Try this:
    Open up wp-htaccess.php, and add this line at the bottom, right before the ?>

    print_r( $_GET );
    ?>

    That should spit out the result of the script at the bottom of the page. Send that to me.

    Or, if you’d prefer, you can just wait until I get a chance to dig into this on my local computer, which may be a few weeks. (I’m a best man this weekend.)

  6. On September 27th, 2005 at 06:03:03, heather Said:

    i was glad to find your plugin, as i had major trouble with category based structures before.

    building a new site, i tried it first with just making .htaccess writeable, and found that i was getting the word ‘category’ before the /%category%/%postname%/… but in the options > permalinks I have not set a category base.

    so i found your plugin when i looked into this problem. installed it, and i’m still getting the error. i tried deleting my .htaccess file, but then it just freaked out and gave me 404 errors for all my links.

    this is the site: http://demo2.sligoarts.com/

    so i deactivaated the plugin, replaced a new blank .htaccess file (writeable), and a new blank wp-access.php (also writeable). after activating, i checked that both were empty before going to options > permalinks to put in /%category/%postname%/ when i ‘updated permalink structure’ i still had the problem. the word ‘category’ appearing before the category/postname

    oh! i tried putting in the print_r( $_GET ); at the bottom of the wp-htaccess page, and i’m getting nothing. err… where is it supposed to appear? at bottom of wp-htaccess page?

    what should i try next? thanks for any help

  7. On September 27th, 2005 at 08:55:09, heather Said:

    Addenda: actually i’m getting incredibly weird behaviour. sometimes it looks like it’s fixed. i’m getting both behaviours, and it’s slightly more than confusing.

    1) I checked and saw the index page showing “Posted in Category” and these links to the caategory had ‘category’ appended first. And the sidebar Category list is giiving similiar links like this:
    http://demo2.sligoarts.com/category/artists-and-artforms/

    2) Yet, if i click on the link to the Title of the post, it is showing me category links to post with NO ‘category’ appended before the link.
    http://demo2.sligoarts.com/artists-and-artforms/consultants/caroline-clancy/

    Both work, but all I want is the 2nd to appear. So that the word ‘category’ is not appended first.

    Thanks for any leads!

  8. On September 27th, 2005 at 09:39:25, Isaac Said:

    Heather,

    The word “category” before the category base is actually normal. Look on your Manage » Permalinks page, right above the “category base” field:

    If you like, you may enter a custom prefix for your category URIs here. For example, /taxonomy/categorias would make your category links like http://example.org/taxonomy/categorias/uncategorized/. If you leave this blank the default will be used.

    WordPress needs *something* to say “this is a category URI, not a post.” Otherwise, if you had a URI like “/main-cat/sub-cat/”, then it couldn’t tell if you wanted a post with a postname of “sub-cat” or a sub-category named “sub-cat”. It would require some extensive work to remove the necessity for a category base:

    1. Prevent any posts from having a post-slug that matches a category slug.
    2. When interpreting the request, if a request comes in with a category that has multiple parts, first check if the last part matches a post slug, and if not, then load it as a category.

    The Lucky1.3 plugin cannot do anything about this. It seems from your comments like it’s actually working normally. If you don’t want to have the word “category” before your category links, then you can select something shorter or different, like “sections” or “c” or whatever.

  9. On October 21st, 2005 at 20:02:08, Orin Said:

    I wanted to note that it is possible to make categories and numbers play together, one just has to include an alphabetic character within any numeric part.

    Exempli gratia:
    /%category%/y%year%/%monthnum%/%day%/
      will return:
    /audio/y2005/10/16/

    I wanted to alert you to that, but I also had a question regarding the last reply you gave. If I were to completely abstain from using multiple categories per post (as I do), wouldn’t the concerns of category-slug conflicts be moot? If I were to avoid having pages with the same name as a category, would it be feasible to have http://www.blogname.com/%category%/ ?

  10. On October 24th, 2005 at 19:45:37, Orin Said:

    I just noticed that I’ve been getting an odd php parse error since I started using the plugin. This error remains even when I turn off the plugin, delete the wp-htaccess.php file, and clear/recreate my .htaccess.

    Warning: ob_start(): output handler ‘ob_gzhandler’ cannot be used after ‘URL-Rewriter’ in /home/(dir-name)/public_html/(blog-name)/wp-includes/functions.php on line 585

    Any clue what the issue is?

  11. On October 25th, 2005 at 10:08:21, Isaac Said:

    Orin,

    Go to your “Options > Reading” section (/wp-admin/options-reading.php) and see if GZip encoding is turned on.

    Try turning that off.

  12. On October 25th, 2005 at 10:14:01, Isaac Said:

    Orin,

    Re: No Category Prefix

    The problem is that WordPress would have to enforce a rule that categories and posts can’t have the same slug. It would be a pretty good idea for an enhancement, but it doesn’t do that currently.

  13. On October 27th, 2005 at 07:52:23, jez Said:

    First of all, thanks mr. lucky rewrite!
    You saved me from getting headaches, because mod.rewrite and permalinks did work, but viewing the categories on my website http://www.h4×3d.com didnt work.
    After installing your script it did magicly-
    but I had to delete the old htaccess file at first,
    create a new one, chmod to 777, chmod your script 777, go to wp admin, go to permalink structure, then click update, then checked - did work. then chmodded my htaccess 644, chmodded your script 755 and voila. now it does work.

    thanks again.

  14. On October 28th, 2005 at 06:09:43, Orin Said:

    Thanks Isaac, turning off gzip compression efficiently removes the error. I worked around my other problem by having my rules such that “www.blog.com/cat-name/” does lead to the category with .htaccess. But Wordpress refuses to natively support category links without a base when using <?php the_category>. I solved this problem by hard-coding my category links like so:

    <a href="<?php echo get_settings('home'); echo '/'; foreach((get_the_category()) as $cat) { echo $cat->category_nicename
    .'/" title="'. category_description($cat->cat_ID) .'">'. $cat->cat_name .'</a>'; } ?>

    In that chunk you’ll notice that it also displays the category description as a title like in >wp_list_cats>, a nice little feature. The two things you need to make sure are A)no page matches a category slug; and B) you have only one category assigned per post. Both of these are no problem for me, but I’m not sure how others want to use it… just putting my info out there.

  15. On November 2nd, 2005 at 18:02:27, flicknut Said:

    Can you tell me the purpose of wp-htaccess.php? I have Wordpres in my public_html folder, so I’m not allowed to change the permissions. I created wp-htaccess.php and uploaded the file to public_html and made it writable 777. However, the file size never changes.

    I have Apache 1.3.33 and I’m trying to use /%category%/%postname%/ for my permalinks. I have your plugin installed, but I get a 404 error every time I click on a permalink. Do you know why this is? Thanks.

  16. On November 2nd, 2005 at 18:16:47, flicknut Said:

    Hey I was able to figure out what was wrong. After I followed #4 in your instructions, I had to navigate to “permalinks” in my control panel and hit “Update Permalink Structure”.

    Then code was written to wp-htaccess.php, and now everything is working properly!!! I think you should add a #5 to your instructions because I didn’t realize I had to update my permalink structure after installing your plugin since I already had it set to /%category%/%postname%/. Perhaps something like this for dumb people like me:

    4. Activate the plugin in your plugins management page.
    5. Update your permalink structure in the control panel.

    Thanks a lot for a great plugin!!!

  17. On November 2nd, 2005 at 18:30:44, Isaac Said:

    True that, flicknut.

    I’ll make that more clear in the instructions. Glad that you got it working, and thanks for the tip :)

  18. On November 4th, 2005 at 01:49:41, jason Said:

    Hi Isaac,

    I followed the instructions exactly as written but server 404 pages appear instead of permalinks. I have verified that I am positively on apache 1.3.33 and have repeated the install just in case. Any ideas here?

    Jason Hendricks

  19. On November 4th, 2005 at 02:09:47, jason Said:

    Ummm….nevermind. I deleted the .htaccess file and then updated the permalink structure, and all is well? Don’t know, but it’s fixed so whatever. Great plugin, thank you sir!

  20. On November 17th, 2005 at 07:23:24, heather Said:

    i’m trying to use the
    $_SERVER['PHP_SELF']
    …to redirect an email subscription form to itself. but instead of getting the name of the current file, i’m getting wp-htaccess.php…

    and then including this php breaks the search function so i get wp-htaccess.php?s=somthing

    http://demo2.sligoarts.com/list/arts-features/ebulletin/ alas…

    should i forget about this?

  21. On November 17th, 2005 at 10:11:24, heather Said:

    please ignore message above. i just uninstalled the plugin, and made new htaccess… so link is broke. sorry!

  22. On January 26th, 2006 at 13:54:06, Making Money » Blog Archive » Using Permalinks Said:

    [...] %category% does not work correctly with some implementations of mod_rewrite in Apache versions prior to 2. If you are using Apache 1 and experience problems with using %category, either do not use %category% in your permalink structure, or refer to Schlueterica’s plugin (http://isaacschlueter.com/plugins/i-made/lucky-13-rewrite/). [...]

  23. On January 27th, 2006 at 13:53:57, Rodney Said:

    I’m running apache 1.3 and I just followed the instructions for your plugin but after I regenerated the htaccess file, I got internal server errors (code 500) everywhere (in the blog, in the wpadmin, etc)

    Any ideas why this would happen? I have my wp install in my websites root directory, but I also have an index.html page (that’s the default page that shows when you browse to the domain). The index.html page is just a temporary page until I get my wp install working correctly.

    Could it be a problem with the mod rewrite and the similar filenames (index.html and index.php in the same folder)?

  24. On January 30th, 2006 at 00:31:32, Gary Said:

    After upgrading Wordpress to 2.0 finally (I use dialup… it took forever……), and then noticed that this plug-in doesn’t work. DOH! So then I looked around for other methods of how to beat this, then I noticed another writing by you about it, tried it out… works.. sort of. It just doesn’t pick up the CSS sheet correctly. It thinks the css is a 404 for some weird reason.

    Anyways, I really hope that you come out with another plugin to fix this problem or post here on how to fix it… until then my blog will just look like something from the mid-90s. (I don’t want to wait another 5 years before it downgrades :\)

  25. On February 1st, 2006 at 20:07:00, Gary Said:

    Thanks for the update on this. However I don’t know what the problem is, WordPress 2.01 is only working halfly for me. I can finally see my homepage but when the links are clicked it 404s. :\ Just weird… my blog is at http://chickencamels.poemofquotes.com if you want to check it out.

  26. On February 1st, 2006 at 20:38:15, Gary Said:

    Nevermind. For some weird reason it started to work without changing anything (besides changing the permalinks over and over…), I don’t think it was the cache because I hard refreshed a few times :\ Confusing.

    I even changed the permalinks to the ‘default’ and it didn’t work. Then I changed it back to /%category%/%postname and it suddenly worked… Anyways, good job on the Lucky 1.3 Rewrite, and I too am glad we will no longer need it. Best of luck on all your other scripts.

  27. On February 1st, 2006 at 20:45:54, Blog back up after upgrade » Chicken Camels: Sports, Reviews, Leisure Said:

    [...] A few days ago, without doing farther investigation, I upgraded to the new (at the time) WordPress 2.0. However, little did I know that my permalinks wouldn’t work due to the ‘greedy 1.3′ bug in apache and no fix (I was using Lucky 1.3 Rewrite before). [...]

  28. On February 8th, 2006 at 18:28:04, Rodney Said:

    You wrote:

    The good news is that WP2.0 is built in such a way that you don’t need this plugin, even if you’re using Apache 1.3! That’s because WP2 handles the URI processing internally, rather than off-loading it onto Apache configuration files.

    This doesn’t seem correct because I’m running wordpress 2.0 and trying to use the /%category%/%postname%/ permalink structure and it still gives 404 errors with apache 1.3

    I can understand how the plugin would be a headache to support for all future versions though :)

  29. On February 14th, 2006 at 17:16:54, Rodney Said:

    This doesn’t seem correct because I’m running wordpress 2.0 and trying to use the /%category%/%postname%/ permalink structure and it still gives 404 errors with apache 1.3

    My mistake, I just tested the category/postname permalinks with the 2.0.1 version and they are indeed working properly. I didn’t know they fixed this in the .0.1 release.

    My apologies :)

  30. On May 18th, 2006 at 05:22:39, NC PHP Developers » wp-rss2.php Said:

    [...] http://isaacschlueter.com/code/apache13htaccess.php <?php /* Plugin Name: Lucky 13 Rewrite Plugin URI: http://isaacschlueter.com/plugins/i-made/lucky-13-rewrite/ Description: Works around Apache 1.3’s “greedy” mod_rewrite.Source: isaacschlueter.com [...]

  31. On June 23rd, 2006 at 11:36:34, lovelyd Said:

    That goodness for google. I was really having a hard time understanding my permalink problem. I have Linux,Apache 1.3 and the permalinks don’t work no matter what I try. But now after finding your plugin my problem is I also have Wordpress version 2.0.2 which is from my understanding a version of 2.0 What can I do . .?

  32. On June 23rd, 2006 at 12:01:06, Isaac Said:

    Sorry to hear your permalinks aren’t working. WP 2.0 does the same thing (roughly) that Lucky13 does, so the plugin is no longer needed.

    What format are you trying to use for permalinks? (IE, what do you have set in http://www.lovelyd.com/BigBodyDiva-Blog/wp-admin/options-permalink.php?)

    I notice that you have /?p=12 when you click on the title of one of your blog posts, and that seems to be working fine.

  33. On June 24th, 2006 at 11:24:21, lovelyd Said:

    My permalinks worked fine with yahoo hosting but now I am using godaddy hosting.I want to optimize my blog for search engines so I want to change the format to something like
    http://lovelyd.com/BigBodyDiva-Blog/2006/sample-post/
    but I can’t seem to change it from it’s default format of
    http://lovelyd.com/BigBodyDiva-Blog/?p=123
    also noticed my .ht is blank.
    Nothing I try seems to work.

  34. On August 22nd, 2006 at 07:25:47, KiÅŸisel Yazılar » Blog Archive » Permalinks for WordPress Seo & Friendly url ’s Said:

    [...] Note on using %category% %category% does not work correctly with some implementations of mod_rewrite in Apache versions prior to 2. If you are using Apache 1 and experience problems with using %category, either do not use %category% in your permalink structure, or refer to Schlueterica’s plugin (http://isaacschlueter.com/plugins/i-made/lucky-13-rewrite/). [...]

  35. On September 9th, 2006 at 10:22:36, Wordpress: A prettier permalink dummy guide - Not your typical monster Said:

    [...] %category% does not work correctly with some implementations of mod_rewrite in Apache versions prior to 2. If you are using Apache 1 and experience problems with using %category, either do not use %category% in your permalink structure, or refer to Schlueterica’s plugin [...]

  36. On October 14th, 2006 at 04:58:13, Bisohbet.Com WordPress » Permalink Types Said:

    [...] %category% does not work correctly with some implementations of mod_rewrite in Apache versions prior to 2. If you are using Apache 1 and experience problems with using %category, either do not use %category% in your permalink structure, or refer to Schlueterica’s plugin (http://isaacschlueter.com/plugins/i-made/lucky-13-rewrite/). [...]

  37. On October 15th, 2006 at 15:36:56, OSC BLOG » Blog Archive » Tutorial One Said:

    [...] %category% does not work correctly with some implementations of mod_rewrite in Apache versions prior to 2. If you are using Apache 1 and experience problems with using %category, either do not use %category% in your permalink structure, or refer to Schlueterica’s plugin (http://isaacschlueter.com/plugins/i-made/lucky-13-rewrite/). [...]

  38. On March 4th, 2007 at 13:58:57, YMKM » Blog Archive » about drupal Said:

    [...] with using %category%, either do not use %category% in your permalink structure, or refer to Schlueterica’s plugin [...]

  39. On April 13th, 2007 at 07:09:02, Lucky 1.3 Rewrite - DevelopeNet.com Said:

    [...] to use �ggreedy�h regexes, even when it shouldn�ft. Author: Isaac Z. Schlueter Plugin Page [...]

  40. On May 7th, 2007 at 03:43:15, catch the digital flow » Blog Archive » Using Permalinks Said:

    [...] with using %category%, either do not use %category% in your permalink structure, or refer to Schlueterica’s plugin [...]

  41. On May 16th, 2007 at 14:02:50, Randy Roedl » Blog Archive » Randy’s Guide to using Permalinks by Wordpress Said:

    [...] %category% does not work correctly with some implementations of mod_rewrite in Apache versions prior to version 2. If you are using Apache 1 and experience problems with using %category%, either do not use %category% in your permalink structure, or refer to Schlueterica’s plugin (http://isaacschlueter.com/plugins/i-made/lucky-13-rewrite/). [...]

  42. On May 30th, 2007 at 07:24:07, Ultimate htaccess File sample Said:

    [...] Lucky 1.3 Rewrite [...]

  43. On June 6th, 2007 at 18:33:56, Blog Sakti Muda Media » Blog Archive Said:

    [...] %category% does not work correctly with some implementations of mod_rewrite in Apache versions prior to version 2. If you are using Apache 1 and experience problems with using %category%, either do not use %category% in your permalink structure, or refer to Schlueterica’s plugin (http://isaacschlueter.com/plugins/i-made/lucky-13-rewrite/). [...]

  44. On July 15th, 2007 at 10:03:51, apple Said:

    is posible modrewrirte categories?

    example

    http://isaacschlueter.com/categorie1.html

  45. On July 23rd, 2007 at 18:23:32, Social Commotion » Blog Archive » permalinks Said:

    [...] %category% does not work correctly with some implementations of mod_rewrite in Apache versions prior to version 2. If you are using Apache 1 and experience problems with using %category%, either do not use %category% in your permalink structure, or refer to Schlueterica’s plugin (http://isaacschlueter.com/plugins/i-made/lucky-13-rewrite/). [...]

  46. On August 24th, 2007 at 02:50:50, 衣袋向下 » Blog Archive » Using Permalinks Said:

    [...] %category% does not work correctly with some implementations of mod_rewrite in Apache versions prior to version 2. If you are using Apache 1 and experience problems with using %category%, either do not use %category% in your permalink structure, or refer to Schlueterica’s plugin (http://isaacschlueter.com/plugins/i-made/lucky-13-rewrite/). [...]

Leave a Reply

Comments are moderated like crazy using a variety of plugins. There is a very high likelihood that your comment won't show up right away, especially if you have never commented here before, but it was not deleted.

Please be patient, and do not post your comment more than once. It will show up once it is approved.

You must be logged in to post a comment.