WordPress.org

1. affiliatetip
   Member
   Posted 5 years ago #

   I just moved from MT to WordPress and I was hoping to change the naming convention of the files from the default (http://blog.affiliatetip.com/?p=1249) to a version that paralleled what I was doing on MT to make the redirect work (http://blog.affiliatetip.com/archives/ask-shawn-collins-affiliate-efficiency-tools/).

   I made this change in Options > Permalinks to use this: /archives/%postname%/

   But the files still exist at the default link type and the urls with the post title in them are pitching 404 errors.
   However, those links are showing up in the blog when you click a post title or the links to the latest posts.

   Anybody know how I can make it happen so that the files are living in the /archives folder with the format of the post title?

2. Samuel B
   moderator
   Posted 5 years ago #

   That should work. Are you getting the confirmation dialog that they are updating?
   Also, remember from your dashboard, to update them, you must have the .htaccess CHMOD 666.

3. scorched
   Member
   Posted 5 years ago #

   hi, this sounds like exactly the same issue i've been having.

   • root of site is managed by wp2.1 as per giving WP its own dir
   • permalinks work fine in this context for pages & entries

   however as soon as the permalink setup is changed to _any_ other format, all goes pear-shaped.

   i've searched a lot on the forums and seen a huge # of issues related to this but nobody seems to have managed to get to the bottom of it.

   my system is

   • OpenBSD 4.0
   • default chrooted apache + mod_rewrite + mod_webdav
   • blog is installed in /var/www/wordpress/ and softlinked from /var/www/htdocs/wordpress/
   • php5-hardened modules
   • wp 2.1 fresh from svn "a few days ago"

   /var/www/htdocs $ cat .htaccess
   # BEGIN WordPress
   <IfModule mod_rewrite.c>
   RewriteEngine On
   RewriteBase /
   RewriteCond %{REQUEST_FILENAME} !-f
   RewriteCond %{REQUEST_FILENAME} !-d
   RewriteRule . /index.php [L]
   </IfModule>
   
   # END WordPress

   I've left my blog with the faulty settings at present so you can take a look & see what is currently failing.

   the desired settings were

   • custom prefix for categories -> /tags
   • custom permalink structure -> /archives/%postname%

   cheers, scorch

4. affiliatetip
   Member
   Posted 5 years ago #

   When I update, I get the message: You should update your .htaccess now.

   Towards the bottom, it reads:

   If your .htaccess file were writable, we could do this automatically, but it isn’t so these are the mod_rewrite rules you should have in your .htaccess file. Click in the field and press CTRL + a to select all.

   And then there is the code for the .htaccess file. I've added it and FTP'd over.

   The code:

   <IfModule mod_rewrite.c>
   RewriteEngine On
   RewriteBase /
   RewriteCond %{REQUEST_FILENAME} !-f
   RewriteCond %{REQUEST_FILENAME} !-d
   RewriteRule . /index.php [L]
   </IfModule>

   Also, I've changed chmod to 666 (it was previously 644).

   Still getting 404 errors for the links.

5. BenBarber
   Member
   Posted 5 years ago #

   I am having the same problem, I am running the latest version 2.1.2 and want my permalinks as:

   /journal/%category%/%postname%/

   But this is not working for me I get a 404 error when I follow a url.

   /%category%/%postname%/ works fine though?

6. BenBarber
   Member
   Posted 5 years ago #

   Solved it!

   The error was caused by me having /journal also set as the category base, which is the option below the Custom permalink structure settings.

   so I now have my permalinks as:

   /journal/%category%/%postname%/

   and my category base:

   /archives/

   Works like a charm!

7. daftska
   Member
   Posted 5 years ago #

   I found the answer for OpenBSD 4.0.

   edit your httpd.conf file in /var/www/conf/ to have
   "AllowOverride All" instead of "AllowOverride None"

   AllowOverride None means that no .htaccess file can actually do anything. There are other options for AllowOverride, but I enjoy doing lots of .htaccess edits, so I put it to all.

   Hope that fixes your problem!

Topic Closed

This topic has been closed to new replies.