WordPress Tip on Permalink Options在WordPress秘诀就永久选项
This tip covers configuration in Options/Permalinks [Edit Permalink Structure] for WordPress users.此提示,包括配置在选项/永久[编辑永久性的结构]为WordPress用户。 My version is WordPress 1.5.我的版本是在WordPress 1.5 。
By default WordPress uses a query string to identify a post.默认情况下,在WordPress使用一个查询字符串,以确定一个职位。 This is neither search engine friendly nor human friendly.这既不是搜索引擎友好,也没有人类的友好。 A better way is to use a custom URI to better identify your posts.更好的办法是使用自定义的URI ,以便更好地查明您的职位。 Many bloggers include a date as part of the permalink.许多Blogger包括一个日期,作为部分的永久性。 I advise against it我奉劝反对 . 。 The date of the post is not so important as to be part of the URI!日期后不是那么重要,因为要的一部分,开放的我们!
My suggestion is to use a simple structure containing the post-slug as your Permalink URI.我的建议是使用一个简单的结构,含有后段塞作为您的永久开放的我们。 I use:我使用:
Structure: /index.php/archive/%postname%/结构: /的index.php /存档/ % postname % /
Note that there is an index.php embedded.请注意,有一个嵌入式的index.php 。 This is fine with search engines and humans too.这是罚款与搜索引擎与人类太。 And it will work great.它将工作的伟大。 It doesn’t require mod_rewrite functionality or change to htaccess.它不需要mod_rewrite的功能或改变htaccess的。 Something as simple as this will work in all configurations.一些简单的,因为这将工作在所有的配置。
For category base I use simply: /index.php/category类基地,我用简单: /的index.php /类别
This is just a simple example.这仅仅是一个简单的例子。 You can make your URI as complicated as you want.您可以作为复杂的,开放的我们您想要的。 Just remember to test it.不过,别忘了测试。
Personally I like it short and simple.亲自我喜欢它的短期和简单。
Update 1 : Please refer to the comments below for points and counterpoints on this topic. 更新1 :请参阅的评论,下面分和counterpoints关于这一主题的。
Update 2 : The objections raised by some people is that having an identical named title for posts will cause problems with WordPress. 更新2 :提出的反对意见,有些人是有一个相同的名称命名的职位会造成问题的WordPress 。 This is not a valid observation anymore.这是不是一个有效的观察了。 In other words you can have 10 posts named “Happy New Year” and WordPress will assign unique post-slug to each.在其他的话,您可以有10个职位,命名为“新年快乐”和WordPress所将指派独特的后段塞每个。 Simply said this approach is without any drawbacks AFAIK.简单地说,这种做法是没有任何缺点, afaik 。
Update 3 : Cem commented: 更新3 :杰姆评论说:
For future reference, I was able to get permalink URL rewriting working in WordPress by creating a php.ini at my domain root with the following configuration:以供日后参考,我是能够得到永久的URL重写工作在WordPress建立的php.ini在我的网域根目录具有以下配置:
cgi.fix_pathinfo = 1 cgi.fix_pathinfo = 1
cgi.force_redirect = 0 cgi.force_redirect选项设为= 0
Several people have found it useful on various environments including but not limited to IIS on windows as can be seen from the comments.几个人发现有用的各种环境,包括但不限于非法入境者在Windows中可以看出,从评论。 Thanks Cem for sharing!杰姆感谢分享!
BTW: Personally I use /archive/%postname%/ for my的BTW :我个人使用/存档/ % postname % /我的 Stem Cell Research Blog干细胞研究的博客 without requiring any changes.而不需要任何改变。
The greatest benefit is that you don’t have to embed index.php as part of URL, possibly slightly increasing your SERP.最大的好处是你不用嵌入的index.php的一部分,网址,可能略为增加您的serp 。
Filed under提起下 Headline News头条新闻 , , How To如何 , , Pro Blogging赞成Blogging , , Web网页 , , Windows在Windows , , WordPress在WordPress | |
| |
RSS 2.0 2.0 | |
Email this Article电子邮件此文章
You may also like to read您也可以想读 |




March 16th, 2005 at 12:19 pm 2005年3月16日在下午12时19分
I think you’re making a mistake discouraging the use if the date in URI’s.我觉得您作出一个错误,劝阻使用,如果日期在开放的我们的。 Wordpress does not require post slugs to be unique.在WordPress并不需要后段塞,以独有的。 So if all you is ‘/archive/slug’ the chances of having a collision go increase greatly over time.因此,如果您是' /存档/塞'的机会,有一个碰撞到大大增加一段时间。 Can you really be sure that in the next x years you’ll never recycle a post title, ever?你真的可以肯定的是,在未来的x年你将永远不会再用一职衔,任何时候都?
Adding the category helps, of course, because then you’d have to duplicate the title and category to cause problems.加入类别帮助,当然,因为当时您有重复的名称和种类会造成很多问题。 But the date adds a unique identifier to the string that is guaranteed not to be repeated.但日期增加了一个独特的识别标志,以字串,保证不会重演。
I use a month-year combination for my date field, figuring that within anygiven month I’m unlikely to repeat slugs.我使用了为期一个月的年组合为我的日期栏,计算,那就是anygiven一个月,我不可能重复段塞。 But even that could be seen as too restrictive by some.但即使这样,可以被看作是过于狭窄一些。
You’re also overlooking that adding the date adds a sense of relevance to your links.您也忽略了加入之日起增加了责任感,相关链接。 Do i care about content more than a year old?我关心的内容了一年多岁? No?没有? Then maybe I don’t need to follow that link i saved that’s dated 1999.然后,或许我不需要走这条连接我节省了那过时的1999年。
March 20th, 2005 at 4:03 am 2005年3月20日在上午04时03分
Why I discourage embedding date in URL’s (including WordPress Permalinks and also other CMS) 所以,我劝阻嵌入日期在URL的(包括在WordPress的永久及其他细胞质雄性不育)
The reasons I discourage date’s in a permalink are: It is redundant information as date is already part of the post information and need not be additionally within the url.基于上述理由,劝阻日期的,在永久是:它是多余的资料,作为日期的一部分,已经是该职位的信息和不必另外内部的网址。 Search engines like google, which gives importance to words in URL’s will … Google等搜索引擎,这使的重要性的话,在网址的意志…
March 20th, 2005 at 4:05 am 2005年3月20日在上午04时05分
Squeg, squeg ,
Please read my请阅读我的 article on this topic文章关于这一主题的 to specifically address your concern.专门处理您的关注。
Let me know your thoughts.让我知道您的想法。
March 21st, 2005 at 9:53 am 2005年3月21日在上午09时53分
I definitely agree that the data is not always necessary in a url.我绝对同意的数据并非总是需要在一个网址。 But I still think using it in most permalink structures does more good than bad.但我仍然认为用它在大多数的永久结构是否更良好的比差。
I will concede that the date makes the url “uglier.” So I recommend using the most compact date structure you can to meet your needs.我会让步,该日期的URL ,使得“ uglier ”所以我建议你使用最紧凑的日期结构,您可以以满足您的需要。 For some that may mean leaving it out.对于一些人认为,可能意味着离开它。 For me it means domain/archives/MM-YYYY/slug.这对我来说意味着域/档案/毫米-四位数年份/塞。 I wish i’d left the word “archives” out as the date pretty much implies that.我想我要离开这个词“档案” ,由于日期几乎意味着。
I’m not sure that I follow how having the date in the address “poisons” the search engines.我不知道我的后续如何有日期在施政报告“毒药”搜索引擎。 I’d like to hear more clarification on what you mean by this.我想听到更多澄清,你的意思,由这一点。
Almost all non “time-sensitive” information really is time sensitive if it’s old enough.几乎所有非“时间敏感”的资料,真的是时间敏感,如果它的旧有足够的。 The only real exceptions are pages where the content is continually updated/replaced with new information as it ages.唯一的例外是真正的网页内容不断更新/更换新的信息,因为它的千古罪人。
Take for instance, a guide to creating web-pages written in 1998.采取例如,指导创建网页的书面于1998年。 If it was well-written in 1998 it may have attracted many links, moving it up the search engines.如果这是精心撰写,在1998年5月,吸引了许多环节,提出了搜索引擎。 But if it has not been updated, then it is really quite behind the times with reguard to today’s best practices.但如果它尚未更新,那么,实在是相当落后于时代与reguard今天的最佳做法。 It may still be technically accurate within the framework for which it was created, but it’s still dated.它仍可能在技术上是准确的内部架构,它创建的,但它仍然不合时宜。 Someone looking at this page today needs to know right away that it’s old information and they should look elsewhere.有人看到本网页今天需要知道的权利以外,它的旧资料,他们应该看看其他地方。
As you can see from your own kubrik installation under wordpress, not every page actively displays the date in a prominent location.你可以看到从您自己的kubrik安装下的WordPress ,而不是每一页的积极显示的日期在一个显眼的位置。
It’s also worth mentioning that Wordpress (and probably other such systems) use the permalink you specifiy in your RSS as well as on your webpage.它的还值得一提的WordPress (也许等系统)使用的永久性你specifiy在您的RSS以及在您的网页上。 Many RSS readers will use the permalink, if it’s identified, as a unique identifier for the item in the feed.许多RSS阅读器将使用的永久性,如果它的发现,作为一个独特的识别码,该项目在饲料中。 Reader software can use that unique ID to enable further functionality for managing feeds and posts. Reader软件可以使用这种独特的编号,以便进一步的功能,管理饲料和职位。 In these circumnstances it’s even more beneficial to ensure that your permalinks are unique.在这些circumnstances它的更有利的,以确保您的永久性是独特的。
In the end, my comment isn’t so much about any given individual leaving the date out of their permalink structure.在年底,我的评论是没有这么多有关任何特定个人离开的日期离开自己的永久结构。 It’s about dissuading all users from including it without first considering both the pro’s and con’s of doing so.它的约劝阻的所有用户,包括它没有首先考虑这两个亲的和CON的这样做。 Using the date may not always seem necessary, but it does add a bit of “future-proofing” should your needs change.使用的日期可能并不总是似乎有必要,但它确实增加了一点“未来-校对”应您的需要改变。
My advice to new wordpress users when choosing a permalink structure would be to stick with “ugly” links for awhile until they can really get a feel for how they’d like to use their blog.我的意见,新的WordPress用户时,选择一个永久性的结构将坚持“丑陋”链接为一段时间,直到他们能够真正感受如何,他们想要利用他们的博客。 You can always add permalinks without causing damage.您可以随时添加,没有造成永久性的损害。 But once you set them up, you can’t really change the system without causing a lot of stuff that used to work, to fail.但一旦您设置他们,你真的不能改变制度,而又不造成了很多的东西用于工作,要失败的。
March 23rd, 2005 at 6:12 pm 2005年3月23日在下午6时12分
Actually, mainstream WP user and WP developers argue against NOT using a date structure in the permalinks.其实,主流用户可湿性粉剂和可湿性粉剂开发商辩称,对不使用的日期结构中的永久性。 This has been argued on the forums several times.这一直辩称,对论坛的几倍。
Let’s say that on January 1st, 2004, you post “Happy New Year!”, and then on January 1st, 2005, you post “Happy New Year”.让我们说,对2004年1月1日,你邮报“新年快乐! ” ,然后在2005年1月1日,你邮报“新年快乐” 。 You now have two posts at domain.com/happy-new-year and this sends your site into a spiral of chaos.您现在有两个职位domain.com /快乐新一年,这传送您的网站成为一个螺旋式的混乱。 Having some sort of date structure will prevent this.拥有某种形式的日期结构将防止这种情况出现。
March 24th, 2005 at 4:40 pm 2005年3月24日在下午4时40分
@MacManx I realize that this is a situation we need to guard against. @ macmanx我知道这是一个情况下,我们需要防范。 Wouldn’t it however be better to modify WordPress to ensure uniqueness of post slug?不会,但它更好地修改,以确保在WordPress的独特性后段塞? Let the title be same.让标题相同。 When WordPress realizes that the title is duplicate while publishing, it changes the post-slug to be unique by adding say date.当WordPress所了解到,标题是重复的,而出版,它的变化,后段塞,以独有的加入说日期。 However as the post slug is not viewed by the public at large it doesn’t affect the user and the viewer?不过,作为后段塞是看不到,由广大市民,这并不影响用户和观众呢?
What do you think.您怎么看。
@Squeg Thanks for your informative comments. @ squeg感谢您的翔实的意见。 I understand your concerns.据我所知,您的疑虑。 I have updated both my post to include a link to your comments, so people can read both and choose whatever suits them best.我有更新我的职位,包括一个可连接至您的意见,以便人们可以阅读和选择什么适合他们的最好的。
Personally I like it simpler without the date as I have already stated, accepting the risk of duplicate post-slug.我个人喜欢简单,无日期,正如我已经指出,接受的风险,重复后塞。 I may actually do something to remedy the situation wrt.其实我可以做一些事来补救这种情况wrt 。 duplication in line with my idea described above.重复,在符合我的想法上文所述。
Thoughts?思考?
March 25th, 2005 at 7:58 am 2005年3月25日在上午07时58分
While i like the date for a lot of things, I do agree sometimes it would be nice to ditch it.而我喜欢的日期了很多事情,我也同意,有时会好沟。 As we’ve both discussed, the biggest single inhibitor to leaving the date out of wordpress is that it doesn’t enforce unique post slugs.正如我们已经都讨论过的,最大的单一抑制剂离开的日期列WordPress的是它并没有执行独特的后段塞。 It does seem like it would be pretty simple to hack wordpress so that it guaranteed a unique post slug by checking the database for exising instances of it’s proposed slug and then appending a number or something to the end of the slug.它好像会很简单,以哈克的WordPress ,以便它保证了一个独特的后段塞通过检查数据库exising的实例,它提出的段塞,然后附加一个号码或一些到去年底,该段塞。 ( A warning at that time would be nice too, so you could modify the slug if you wanted. ) (一警告说,时间将可尼斯太,所以你可以修改塞如果你想) 。
I’d also like it to automatically truncate long slugs.我同样希望它会自动截断长段塞。 I know that might make it harder to determine what to type into the URL if you’re trying to guess (who really does that?) but it would definitely simplify the URLs.我知道可能会使它难以决定如何处理输入的网址如果您尝试猜(谁是否真的呢? ) ,但它肯定会简化的网址。 Some kind of options setting where you specified a maximum number of characters for the slug, would do the trick.一些种选项设置您指定的最多的字符数为塞,也将这样做的伎俩。
April 2nd, 2005 at 9:39 pm 2005年4月2日在下午9点39分
[...] rs, Link-blog03. [ … … ]自动仓储系统,连接blog03 。 April 2005 .htaccess 파일을 건드릴 필요 없는 방법 WordPress Tip on Permalink Options Comment RSS - [...] 2005年4月。 htaccess的파 일 을 건 드 릴 필 요 없 는 방 법的WordPress秘诀就永久选择评论的RSS -[ … … ]
April 9th, 2005 at 6:00 am 2005年4月9日在上午06点
WordPress Permalinks Updated 在WordPress的永久更新
I have updated my WordPress permalinks from:我有更新我的WordPress的永久从:
/year/month/day/TITLE /年/月/日/标题
to:到:
/archives/month/day/TITLE /档案/月/日/标题
I just think It would look alot better like that.我只是认为这会研究好多了一样。 That’s all :)….这是所有: ) … … 。
April 14th, 2005 at 6:51 am 2005年4月14日在上午06时51分
My server is running on Windows Server (brinkter.com) so I guess I’m SOL regarding permalinks.我的服务器是在运行Windows Server ( brinkter.com ) ,所以我猜我溶胶关于永久性。
Any workarounds?任何替代?
April 14th, 2005 at 7:04 am 2005年4月14日在上午07时04分
edit: that should be “brinkster.com” on the above post.编辑:应该是“ brinkster.com ”就上述职位。
April 14th, 2005 at 12:56 pm 2005年4月14日在下午12时56分
@Carlos The ideas in this post works on Windows server too. @卡洛斯的想法,在这个职位工程于Windows Server太。 In fact I have a copy of the site running on my Windows Apache server at Home.事实上,我有一个副本,该网站上运行我的Windows Apache服务器在家里。
This is the beauty of the idea.这是美丽的想法。 It requires no special features enabled for it to work on any platform.它并不需要特别的功能,使为它工作的任何平台上。
April 16th, 2005 at 4:47 pm 2005年4月16日在下午4时47分
Yes, but it seems you need to have Apache running.是的,但似乎您需要有Apache的运行。 What I meant was that brinkster runs Windows Server 2003 as their web server platform, as opposed to Apache for Windows.我的意思是说, brinkster运行Windows Server 2003作为他们的Web服务器平台,作为反对的Apache用于Windows 。 It seems you need apache’s mod_rewrite for the permalink options to work.看来你需要Apache的mod_rewrite为永久的选择工作。
Thanks.谢谢。
April 16th, 2005 at 11:22 pm 2005年4月16日在下午11时22分
@Carlos @卡洛斯
No it doesn’t need apache running.没有它不需要Apache的运行。 To use my tip above you do not need mod_rewrite capability nor do you need .htaccess.用我的秘诀以上您不需要mod_rewrite的能力,也没有您所需要的。 htaccess的。 That is the beauty and simplicity of the solution.这是美容和简单的解决问题的方法。 Just try it.只是尝试。 It will work.它将工作。
April 17th, 2005 at 4:50 am 2005年4月17日在上午04时50分
I get a “No input file specified.” when I try anything with the permalinks.我收到了“没有输入指定的档案。 ”当我尝试任何与永久。
April 17th, 2005 at 10:16 pm 2005年4月17日在下午10时16分
Am having issues too, trying to setup permalinks on Win2K3/IIS server.上午有问题,也试图安装永久性就win2k3/iis服务器。 It throws a 404 error, no matter what permalink structure i try!它抛出一个404错误,无论什么永久性的结构我尝试!
April 17th, 2005 at 10:32 pm 2005年4月17日在下午10时32分
@Sajin & @Carlos @ sajin & @卡洛斯
Try these exactly as typed (in Options/Permalinks) and let me know if you still have problems.试试这些正是作为输入(在选项/永久)和让我知道,如果您仍然有问题。
Structure: /index.php/archive/%postname%/结构: /的index.php /存档/ % postname % /
Category base: /index.php/category类文件: /的index.php /类别
April 18th, 2005 at 6:00 am 2005年4月18日在上午06点
Angsuman, tried again, making sure to copy-paste from your message.由Angsuman ,试图再次,使务必复制粘贴,从您的讯息。 I still get a “No input file specified” message.我仍然获得了“没有输入指定的档案”的讯息。 I’m waiting a while now, to see if this is some sort of database or configuration issue that needs some time to set itself.我等待,而现在,看看如果这是某种形式的数据库或配置问题,需要一些时间来为自己确定。
For example, this is how one of my post links looks like now:举例来说,这是怎样的一个我的帖子链接看起来像现在:
http://www.carlanga.com/blog/index.php/archive/using-crypto-hashes-salts-to-protect-database-privacy/ http://www.carlanga.com/blog/index.php/archive/using-crypto-hashes-salts-to-protect-database-privacy/
Does that look ok to you?这是否表示期待确定你?
Thanks!谢谢!
April 18th, 2005 at 6:06 am 2005年4月18日在上午06时06分
Waited a while… added a post… no luck.等待了,而增添了… …后没有运气。 It doens’t seem like this will work on non-Apache boxes.它doens't好像这将工作的非阿帕奇箱。
April 19th, 2005 at 2:09 am 2005年4月19日在上午02时09分
@Carlos I will check it out. @卡洛斯一世将检查出来。 It should be possible as it is using something very basic.应该有可能,因为它是用一些很基本的。
The reason I don’t have IIS, even on my home machine, is due to security concerns.我之所以没有非法入境者,即便是在我家的机器,是由于安全顾虑。
BTW: Have you faced aany security related issue with your IIS deployment?的BTW :你所面对的aany安全相关的问题,与您的IIS部署?
April 19th, 2005 at 2:17 pm 2005年4月19日在下午2时17分
@angsuman, @由Angsuman ,
Not that I know of, as Brinkster handles all the hosting (shared hosting).不,我知道,作为brinkster处理所有主办(共享托管) 。 They should keep all patches up to date, etc. But I haven’t had any problems so far in the 3 or 4 years I’ve been with them.他们应该保留所有补丁直至目前为止,等等,但我都没有任何问题,直至目前为止,在三或四年我一直在与他们。
Just now I noticed they offered PHP/MySQL support and thus installed Wordpress.刚才我注意到,他们所提供的PHP / MySQL的支持,因此安装的WordPress 。 I was using Radio Userland, via FTP, before.我是使用无线电userland ,通过FTP ,前。
April 22nd, 2005 at 5:34 pm 2005年4月22日在下午5时34分
My server runs Win2000/IIS5 and no problem with “index.php” permalinks.我的服务器运行win2000/iis5 ,并没有问题“的index.php ”永久性。 Perhaps this is specifically a Windows 2003 or IIS6 problem?也许,这是具体的Windows 2003或iis6的问题呢?
I run Apache2 on the same server and that’s where all the WP1.5 installs are.我运行的Apache2在同一台服务器上,这是所有wp1.5安装。 Permalink structure is defaulted to /%year%/%month%/%postname%/ for clarity.永久结构是拖欠/ % ,年% / %一个月% / % postname % /清晰。
April 24th, 2005 at 1:25 am 2005年4月24日在上午01时25分
@rust, @锈,
Do you have your Wordpress installation running on IIS5 or on the Apache server you have on the same machine?你有你的WordPress安装上运行的iis5或对Apache服务器你有在同一台机器上?
April 25th, 2005 at 10:33 am 2005年4月25日在上午10时33分
Just chiming in, but Carlos, any chance you have your index.php in a nonstandard location?刚刚在chiming ,但卡洛斯,任何的机会,您有您的index.php在一个非标准的位置? Maybe the link that’s supposed to be pointing at your index file really isn’t?也许连结的假定必须指出,在您的索引档,实在是不?
If that doesn’t seem to be the issue and you’re not using a default theme, you might try switching back to classic or kubrik.如果这似乎并不成为问题,您使用的不是一个预设的主题,您可以尝试切换回经典或kubrik 。 It’s *possible* that whatever theme you’re using doesn’t link to the code that parses the URL string aside from the standard GET stuff.它的可能* *无论主题您使用不会链接到代码解析URL字符串除了标准得到的东西。 Admittedly, I’ve not actually gone spelunking to find the code that’s supposed to be doing that parsing.无可否认,我已经没有了,其实spelunking找到代码的假定必须这样做剖析。
April 25th, 2005 at 3:49 pm 2005年4月25日在下午3时49分
Thanks Squeg.感谢squeg 。
I’m running the default theme… let me check if location has anything to do with this.我运行的默认主题…让我检查,如果地点有什么做的与此有关。 I have everything installed in a folder (www.carlanga.com/blog) but otherwise, it’s just as it came in the original file.我一切都安装在一个文件夹中( www.carlanga.com /博客) ,但否则,它只是因为它来在原始档案。 I unzipped and FTP’d. i解压缩和ftp'd 。
Thanks.谢谢。
April 26th, 2005 at 10:17 am 2005年4月26日在上午10时17分
Well that sounds like a pretty standard configuration.清楚,听起来像一个美丽的标准配置。 Double-check the options screen in your dashboard to make sure that both location boxes point at the correct location.仔细检查选项屏幕在您的仪表板,以确保这两个位置的方块点在正确的位置。 You might (and i’m totally just shotgunning here) try setting the blog address to您可能(我完全只是shotgunning这里)尝试订定的博客地址,以 http://www.carlanga.com/blog/index.php instead of just /blog.而不是只/博客。
Aside from that, I’d say it’s going to come down to server configuration.除此之外,我会说,这将会下降到服务器配置。 It’s possible the web server itself is choking on the oddly-formed URL.它的可能的Web伺服器本身是哽塞的就奇怪成立的网址。 And at that point, I don’t really have a lot of good ideas.在这一点上,我真的不有很多好的想法。 Honestly, what’s really wrong with “ugly” url’s anyway?老实说,什么的,实在不妥“丑陋”的网址的吗?
April 26th, 2005 at 8:45 pm 2005年4月26日在下午8时45分
@Squeg @ squeg
> what’s really wrong with “ugly” url’s anyway? >什么的,实在不妥“丑陋”的网址的吗?
?p=3756 type of url’s don’t get much google-love (not to mention they are ugly) ? P值3756类型的URL的没有获得多少Google的爱(不提他们的丑恶)
April 28th, 2005 at 2:42 pm 2005年4月28日在下午2时42分
So, has anyone gotten this to work under IIS?因此,有没有人得到,这下工作的非法入境者?
April 29th, 2005 at 5:12 am 2005年4月29日在上午05时12分
Not me, not yet.不是我,现在还没有。
April 30th, 2005 at 7:01 am 2005年4月30日在上午07时01分
Okay, last resort, you could try and get rewrites to actually work in IIS using something like this:好吧,最后的手段,您可以尝试并取得重写,以实际工作在IIS中使用的东西是这样的:
http://www.isapirewrite.com/
The lite version is free and might be enough for what you’re trying to do.该Lite的版本是免费的而且可能是不够的是什么,您试图这样做。
April 30th, 2005 at 7:15 am 2005年4月30日在上午07时15分
Here’s another possible option (free)这里的另一个可能的选项(免费)
http://www.motobit.com/help/url-replacer-rewriter/iis-mod-rewrite.asp
May 1st, 2005 at 2:43 pm 2005年5月1日在下午2时43分
Thanks Squeg.感谢squeg 。
Carlos, did you have any luck with these solutions?卡洛斯,你是否有任何侥幸与这些解决方案?
May 4th, 2005 at 2:55 am 2005年5月4日在上午02时55分
From what I see, I don’t think I could get either of those to work, as I’m on a hosted server.从我看到的,我不认为我能要么这些工作,作为我对所托管的服务器。 I’ll look closer at Isapirewrite and comment if anything good comes up.我会看看在密切isapirewrite和评论如果有什么好来了。
Thanks!谢谢!
May 4th, 2005 at 5:16 am 2005年5月4日在上午05时16分
How about changing your hosting provider如何改变您的托管服务提供商
I found Linux hosting providers are normally cheaper and comes with addl.我发现Linux的托管服务提供商,通常较便宜,并且还带有addl 。 capabilities like ssh, vps (some) etc.能力一样的SSH ,电子道路收费(部分)等。
May 4th, 2005 at 3:04 pm 2005年5月4日在下午3时04分
I thought about that… but then my hosting provider offered me a nice plan with PHP that was competitive with everything else out there and I decided the hassle of switching wasn’t worth it.我以为那… …但当时我的主机供应商愿意为我提供一个好的计划,用PHP ,这是竞争力,与一切的存在,并且我决定的麻烦开关是不值得。 I’d have to move all my data plus my email domain.我不得不提出我的所有数据,再加上我的电子邮件域。
They are about to start offering Linux hosting, so maybe all is not lost.他们是即将开始提供Linux的举办,所以,也许是不会遗失。
May 9th, 2005 at 5:52 pm 2005年5月9日在下午5时52分
I have tried to search the site for the reason for using index.php as part of the permalink structure.我曾尝试搜索网站的原因,使用的index.php的一部分的永久结构。 And of course it is hard to search for that since it is included on every page而且当然是很难寻找,由于它是包括在每一页
May 9th, 2005 at 11:27 pm 2005年5月9日在下午11时27分
@Gary @程介南
Finally a downside of using “index.php” as part of permalink最后一坏处用“的index.php ”的一部分,永久
Looks like however you succeeded.看起来像,但你成功了。
May 10th, 2005 at 1:17 pm 2005年5月10日在下午1时17分
Well, you won me over to the NoDateURI side.那么,你赢得了我给nodateuri的一面。 Being a noob with php, apache, etc, I was reluctant to do anything that might ‘break’ my site.作为一个noob用PHP ,阿帕奇等,我不愿意做任何可能'休息'我的网站。 But I backed up everything (including a spare copy of .htaccess) and said - go for it.但我作为后盾,一切(包括备件的副本。 htaccess的) ,并说-去。
It worked!!它的工作!
Then I realized all the links out in the wild world to my site were now probably broken.然后我意识到的各个环节,在野生世界在我的网站现在可能打破。 And even though I like my 404 message - I prefer people not get it.即使我喜欢404的讯息-我喜欢的人得不到它。
So, since I was being brave, I opened that back up copy of .htaccess and compared it with the new one.所以,自从我被勇敢的,我打开备份的副本。 htaccess的和比较,它与新一。 I think I figured out how all the regular expressions were doing what they were supposed to do enought to try something bold.我想我揣摩如何所有正则表达式正在做什么,他们假定做enought尝试一些大胆的。 I copied the lines that started with ^([0-9]{4}) and replaced the pattern at the end: i复制线,开始与^ ( [ 0-9 ] ( 4 ) )和取代的模式在年底:
`index.php?year=$1&monthnum=$2&day=$3&name=$4` `的index.php ?年= $ 1 & monthnum = 2元&天= $ 3 &名称= $ 4 `
with just:与刚才:
index.php?name=$4`的index.php ?名称= $ 4 `
In other words I removed:在其他的话i移除:
`year=$1&monthnum=$2&day=$3&` `年= $ 1 & monthnum = 2元&天= $ 3 & `
A quick test shows it worked - now the old links on my pingbacks, tracklogs, etc still should work.快速测试显示,它的工作-现在旧的链接我p ingbacks, t racklogs等仍应工作。 I emphasize ’should’ since I really have no clue about this stuff since I am an insurance agent and not a professional propeller head.我要强调'应该' ,因为我实在没有线索,对这个东西,因为我是一个保险代理人,而不是一个专业的螺旋桨头。
May 10th, 2005 at 1:56 pm 2005年5月10日在下午1时56分
WordPress Permalink Options 在WordPress的永久选项
As I read 2 posts on the Simple Thoughts blog about permalinks in WordPress I realized I wanted my permalinks to be ‘cleaner’.正如我读2个员额,对简单的思考博客约永久性在WordPress我意识到我想我的永久,以'清洁' 。
In the first article, [Why I discourage embedding date in URL’s (including WordPress Permalinks and also other CMS)](htt…在第一条, [为什么我劝阻嵌入日期在URL的(包括在WordPress的永久及其他细胞质雄性不育) ] ( HTT的…
May 25th, 2005 at 10:16 am 2005年5月25日在上午10时16分
[...] permalinks. [ … … ]永久。 At the very least, include the post name.在最低限度,包括邮政的名称。 Another recommendation can be found here.另一项建议,可以在这里找到。 05.25.2005 @ 10:15 AM by paul @ rwt [...] 2005年5月25日@上午10时15分由保罗@ rwt [ … … ]
June 1st, 2005 at 10:56 am 2005年6月1日在上午10时56分
Carlos:卡洛斯:
I have just set up WP on Win2k3/IIS6, and was pleasantly surprised to find no problems with permalinks.我刚才已成立可湿性粉剂win2k3/iis6 ,并惊喜地发现没有问题的永久性。 I have not installed any of the rewrite ISAPI filters.我也没有安装任何重写ISAPI筛选器。 This site is for internal organizational use only, so is not accessable to the public — you’ll have to trust me that permalinks are working!这个站点是为内部组织只使用,所以是不向公众开放-您必须信任我,永久性的工作!
My guess is that you don’t have access to the php.ini file (I wouldn’t give access to all users if I was the host!)我的猜测是,你没有接触到php.ini文件(我不会给获得的所有用户,如果我是东道主! )
If I’m right, ask your host to turn on the cgi.fix_pathinfo option for PHP.如果我的权利,请问您的主机,把对cgi.fix_pathinfo选项对于PHP 。 Even if they make the change in php.ini, it requires a restart of IIS to take effect, so they may not be able to do that immediately.即使他们作出改变,在php.ini中,它需要重新启动的非法入境者采取作用,所以他们未必能够这样做,立即。
If you begin hosting on your own server, and need to use IIS instead of Apache for some reason, try the suggestion on the WordPress Codex:如果您开始举办自己的服务器,需要使用的非法入境者而不是阿帕奇出于某种原因,尝试建议,对食品法典委员会的WordPress : http://codex.wordpress.org/User:ringmaster/IIS http://codex.wordpress.org/user:ringmaster/iis
Hope that helps.希望有所帮助。
June 8th, 2005 at 10:13 pm 2005年6月8日在下午10时13分
Well, this discussion make me, a newbie in WP, confused.那么,这次讨论使我,一个新手在可湿性粉剂,混淆。 What should I choose?我应该怎么选择呢?
June 8th, 2005 at 11:43 pm 2005年6月8日在下午11时43分
Choose the simple structure I suggested in the article.选择结构简单,我建议在文章中。 It will take you about a minute to setup, very search engine friendly and requires no special capability of your server like mod_rewrite or htaccess.这将带您约一分钟设置,非常的搜索引擎的友好并不需要特别的能力,您的服务器一样, mod_rewrite或htaccess的。
I summarized in the last line of the article: i总结了在最后一行的文章:
Simply said this approach is without any drawbacks AFAIK. 简单地说,这种做法是没有任何缺点, afaik 。
June 19th, 2005 at 9:40 pm 2005年6月19日在下午9点40分
For future reference, I was able to get permalink URL rewriting working in WordPress by creating a php.ini at my domain root with the following configuration:以供日后参考,我是能够得到永久的URL重写工作在WordPress建立的php.ini在我的网域根目录具有以下配置:
cgi.fix_pathinfo = 1 cgi.fix_pathinfo = 1
cgi.force_redirect = 0 cgi.force_redirect选项设为= 0
June 20th, 2005 at 4:32 pm 2005年6月20日在下午4时32分
I have posted this query at WP Forum but received no response.我已张贴在此查询可湿性粉剂论坛但没有收到任何回应。
Server: Linux/Apache服务器: Linux的/阿帕奇
WP: 1.5.1可湿性粉剂: 1.5.1
Themes: both my own and wordpress default.主题:无论我自己和WordPress所默认。
Plugins:插件:
Include page 1.0包括网页1.0
Last Post Since 1.0去年以来,邮政1.0
Static Front Page 1.0.2静态头版1.0.2
I have edited my Permalink structure as:我有我主编的永久结构为:
/%year%/%monthnum%/%day%/%postname%/ / % ,年% / % monthnum % / %天% / % postname % /
/category/%postname%/ /分类/ % postname % /
The links seems to be working fine but I get the following error at every post or category:联系似乎是工作的罚款,但我得到以下错误在各个岗位上,或3个分类:
WordPress database error: [You have an error in your SQL syntax.在WordPress数据库错误: [你有一个错误在您的SQL语法。 Check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1]检查手册,对应到你的MySQL服务器版本的权利,使用的语法附近''在1号线]
SELECT category_nicename FROM wp_categories WHERE cat_ID=选择category_nicename从wp_categories那里cat_id =
Then to make it simple I used:然后,使我用简单的:
/index.php/%year%/%postname%/ /的index.php / % ,年% / % postname % /
/index.php/archives/%post_id% /的index.php /档案/ % post_id %
without .htaccess没有。 htaccess的
Same result.同样的结果。
Any idea?任何想法?
June 20th, 2005 at 5:39 pm 2005年6月20日在下午5时39分
Look like a plugin related problem or related to the theme.看起来不像插件相关的问题或与之有关的主题。 Start by disabling all the plugins and see of the problem is solved.开始停用所有的插件和看到的问题是解决。 Then activate them one at a time to isolate the exact plugin causing it.然后激活它们一在一个时间,以隔离插件的确切原因引起的。
To test the theme try using the default theme and see if that solves the problem.测试的主题,尝试使用默认的主题和,看看是否解决问题。
This is not related to the permalink structure as far as I can tell from this description.这是无关的永久性结构而言,我可以告诉从这个描述。
June 20th, 2005 at 10:51 pm 2005年6月20日在下午10时51分
Angsuman thanks for your response.由Angsuman感谢您的回应。 The error shows up despite the theme or the plugin used.错误显示,尽管主题或插件使用。 I have tested and got the same error using the WP default theme and without plugins.我已测试,并得到了相同的错误使用可湿性粉剂默认的主题和插件。 Weird isn’t?奇怪的是不是?
My server provider says the system is okay but I have no arguments to discuss the database error.我的服务器供应商说,该系统是好的,但是我没有理据,讨论数据库错误。 So, it would be great if someone explains what the error message means.因此,将伟大的,如果有人解释了什么错误讯息的手段。
June 21st, 2005 at 12:19 am 2005年6月21日在上午12时19分
@Stopthepress Check the version of MySQL installed on your site. @ stopthepress检查版本的MySQL安装在您的网站上。 You should be able to find it in the control panel or your hosting provider will be able to tell you.您应该可以找到它在控制面板或您的主机供应商将能够告诉你。
AFAIK WordPress doesn’t support MySQL 5.x versions. afaik WordPress所不支持的MySQL 5.x的版本。 It works with 4.x versions.它与4.x的版本。
June 21st, 2005 at 12:15 pm 2005年6月21日在下午12时15分
Angsuman,由Angsuman ,
MySQL version is 4.0.22-standard MySQL的版本是4.0.22标准
June 21st, 2005 at 12:46 pm 2005年6月21日在下午12时46分
This is not linked to permalinks at all.这是没有联系的永久所有。 Comment out references to the_category() function everywhere in your theme.评论指出参考the_category ( )函数无处不在,您的主题。
Then your site will work.然后,您的网站将工作。
However it shouldn’t have been a problem in the first place.但它不应该有一个问题摆在首位。 Search/Ask in WP forum if your version of MySQL is supported.搜索/请问在可湿性粉剂论坛如果您的版本的MySQL的支持。
Re-instllating often helps with such spurious errors.重新instllating往往有利于这种似是而非的错误。 That is an option too.这是一个选项。
June 21st, 2005 at 10:44 pm 2005年6月21日在下午10时44分
Done!!!这样做!
Deleting the ‘the_category()’ function at the theme’s index.php solved the problem.删去' the_category ( ) '功能,在主题的的index.php解决了这个问题。 Fortunately the ‘the_category()’ function is not so important.幸好' the_category ( ) '函数不是那么重要。
The question is why the_category() function caused that weird behaviour in my theme and in the WP Default theme as well?问题是,为什么the_category ( )函数所造成的这怪异的行为在我的主题和可湿性粉剂,在默认的主题,以及? Hmmm if I get some spare time I will re-install to see what happen. hmmm ,如果我得到一些空闲时间,我会重新安装,看看有什么情况发生。
Thanks a lot Angsuman for your valuable comments.感谢了很多由Angsuman为您宝贵的意见。 Will post a link to this thread at the WP Forum in order to help other users suffering “Permalinkcitis”.会后一链接到本线程在可湿性粉剂论坛,以帮助其他用户的痛苦“ permalinkcitis ” 。
July 1st, 2005 at 10:33 am 2005年7月1日在上午10时33分
Genius here:天才在这里:
I already gave up de permalink-stuff, but today i upgraded wp to 1.5.1.3 .我已经放弃了永久德-的东西,但今天我升级可湿性粉剂,以1.5.1.3 。
I thought lets give it a try.我以为可以让给它一个尝试。
I followed Cems advice and voila it is working!我在cems的意见和voila ,这是工作!
without the .htacces, because i don’t have that file in my (shared) webspace.没有。 htacces ,因为我没有这方面的文件在我的(共用) webspace 。
Big thanks to Cem.大感谢杰姆。
July 8th, 2005 at 11:46 pm 2005年7月8日在下午11时46分
Just wanted to add my 2 cents, the trick Cem said seemed to work for me.只是想添加我的2美分,把戏,杰姆说,似乎对我的工作。 Specifically:具体来说:
Running Win2k3 on IIS6 and now it works perfectly fine.运行win2k3关于iis6和现在的工程完全罚款。 Thanx a bunch. thanx一群。
July 11th, 2005 at 3:08 pm 2005年7月11日在下午3时08分
I didn’t believe it would work, but like CEM (comment #44) and others said, this did the trick for me on Win2003 and IIS.我不相信它会工作,但像杰姆(评论编号44 )和其他人说,这样做的把戏,我对win2003和非法入境者。
August 2nd, 2005 at 12:22 pm 2005年8月2日在下午12时22分
Thank you so much!谢谢你这么多! I’ve been looking around forever for a solution to the IIS/Wordpress/Permalinks problem, and the php.ini thing worked!我一直在环顾永远为解决非法入境者/在WordPress /永久性的问题,和php.ini的事,工作! I’m so happy, thank you all so much.我很高兴,谢谢大家这么多。
August 9th, 2005 at 5:41 pm 2005年8月9日在下午5时41分
thanks, the tip about php.ini on iis saved me from tearing any more hair out.非常感谢,提示约php.ini中关于非法入境者救了我,从撕裂的任何更多的头发。
October 8th, 2005 at 11:33 pm 2005年10月8日在下午11时33分
[...] Wordpress is sooooooo cool. [ … … ]的WordPress是sooooooo冷静。 Just changed the url’s to be “search engine friendly.” I was researching how to do this manually, but then ran across a link from one of Wordpress’ support pages, which mentioned to change the options in the local Wordpress install’s permalinks section, add some code to the .htaccess file, and that was it!只是改变了URL的是“搜索引擎友好, ”我是研究如何执行这项操作的手动,但随后遇到一个链接从一个WordPress的支持页面,其中提到要改变的选项,在本地的WordPress安装的永久区段中,添加一些代码到。 htaccess的文件,这是它! How easy.多么容易。 I’ll probably donate some money to them soon.我会大概捐一些钱,他们很快。 They’ve built a fantastic tool.他们已经建立了一个神奇的工具。 [...] [ … … ]
October 20th, 2005 at 7:46 pm 2005年10月20日在下午7点46分
OMG HOLY 5H17 omg圣地5h17
CEM, you rule杰姆,你的规则
Thank you, I spent a couple days looking for this work around (came across this post more than once, just was too lazy to read the comments before谢谢你,我花了一对夫妇天内寻找这方面的工作围绕(碰到这个职位多于一次,刚才是懒得读评论前
) )
u guys rock u家伙岩
October 20th, 2005 at 8:05 pm 2005年10月20日在下午8时05分
has anyone noticed their admin console stop doing page redirects after executing actions since they installed the php.ini file to fix permalink?有没有人注意到他们的管理控制台停止做网页重新导向后,执行行动,因为他们安装了php.ini文件修复的永久?
I imagne it’s just something I’m missing from my php.ini… but I don’t know what to put in there i imagne这只是一些我失踪的从我的php.ini … …但我不知道要放什么东西到有
this happened to anyone else?这件事,以给他人?
October 26th, 2005 at 7:18 am 2005年10月26日在上午07时18分
Hi嗨
maybe it’sa good tip to know that when you use other seperation characters like: .也许这是很好的提示知道,当您使用其他分离字符,例如: 。 , | + instead of the / or - you can get serious errors , | +而不是/或-您可以得到严重的错误
so: /%year%.%monthnum%.%day%.%postname%.%post_id%所以: / % ,年% 。 % monthnum % 。 %天% 。 % postname % 。 % post_id %
does not work, but不工作,但
/%year%-%monthnum%-%day%-%postname%-%post_id% / % ,年% -% m onthnum% - %天% - % po s tname%-% p os t _id%
does…是否…
October 31st, 2005 at 9:29 pm 2005年10月31日在下午9点29分
It worked!它的工作! Thanks, really!谢谢您,真的!
November 9th, 2005 at 3:30 am 2005年11月9日在上午03时30分
Using the structure you suggested solved all my problems of no comments showing and categories not working.使用结构,你建议解决所有的问题,我没有评论显示和类别没有工作。 I don’t really know php and am new to this kind of blogging, but I’m so relieved and so thankful I could dance!我真的不知道, PHP和时新的这种博客,但我很欣慰和感激,让我可以跳舞!
Thanks from Italy感谢来自意大利
November 24th, 2005 at 1:50 am 2005年11月24日在上午01时50分
I suggest using the default structure: /index.php/%year%/%monthnum%/%day%/%postname%/ because this is computable with the other archive URL.我建议使用默认的结构: /的index.php / % ,年% / % monthnum % / %天% / % postname % /因为这是可计算与其他存档网址。 For example /index.php/%year%/%monthnum%/ shows all posts in that month and /index.php/%year%/ shows all posts in that year.例如/的index.php / % ,年% / % monthnum % /显示所有的职位,在这一个月和/的index.php / % ,年% /显示所有的职位,在这一年。 /index.php/%year%/%monthnum%/%day%/%postname%/ seams like the logical extension to me. /的index.php / % ,年% / % monthnum % / %天% / % postname % /煤层一样,合乎逻辑的延伸给我。
November 27th, 2005 at 10:16 pm 2005年11月27日在下午10时16分
Any suggestions for fixing this when the Windows web host provider won’t modify php.ini with the fix above?任何建议,订定这个当Windows的虚拟主机供应商将不会修改php.ini中与修复以上? WebHost4Life can’t/won’t make the change, and it doesn’t look like they’ll install the ISAPI filters referred to above, either. webhost4life不能/不会作出改变,并没有像他们将安装ISAPI筛选器上面提到的,无论是。
November 27th, 2005 at 11:41 pm 2005年11月27日在下午11时41分
How about uploading the file php.ini to your home directory yourself instead of relying on your web host?如何上载档案的php.ini到您的home目录自己,而不是依靠您的Web主机?
December 3rd, 2005 at 12:47 am 2005年12月3日在上午12时47分
[...] You can also try to follow blog.taragana.com by putting a php.ini file in your root folder. [ … … ]您也可以尝试遵循blog.taragana.com放一个php.ini文件在您的根文件夹。 Have a look at their update 3 it may be of some help.有一个看看他们的最新简报3 ,它可能会有一些帮助。 [...] [ … … ]
December 8th, 2005 at 10:38 pm 2005年12月8日在下午10时38分
I am attempting to get /archive/%postname%/ to work without having to write to WP’s .htaccess, but ran into a few problems.我试图获取/存档/ % postname % /工作,而不必写信给可湿性粉剂的。 htaccess的,但遇到的几个问题。 Allowing wp to write the code to WP’s .htaccess file overrides my RewriteEngine canonical redirect in my domain root .htaccess, that automatically parses all non-www versions of my domain to the www version to avoid possible duplicate content penalties.允许可湿性粉剂写代码可湿性粉剂的。 htaccess的档案压倒我rewriteengine典型重定向在我的网域的根。 htaccess的,即自动解析所有非www版本的我的网域到www版本,以避免可能重复的内容刑罚。 This problem only effects my /blog/ folder.这个问题只会影响我的/博客/文件夹。
Adding php.ini to my domain root with:加入到我的php.ini的网域根目录:
cgi.fix_pathinfo = 1 cgi.fix_pathinfo = 1
cgi.force_redirect = 0 cgi.force_redirect选项设为= 0
Doesn’t work.是行不通的。 Changing /index.php/archive/%postname%/ to /archive/%postname%/ results in “Not found on server” errors for all my other blog pages.改变/的index.php /存档/ % postname % / /存档/ % postname % /结果在“没有发现在服务器上”错误我的所有其他博客的页面。
I tried adding a similar RewriteEngine code to WP’s .htaccess, but that didn’t work.我尝试加入了类似的rewriteengine代码可湿性粉剂的。 htaccess的,但没有工作。
December 31st, 2005 at 10:01 pm 2005年12月31日在下午10时01分
I think you would be better of including index.php in your path like this blog.我想你会做得更好,包括在您的index.php的路径一样,此博客。
January 5th, 2006 at 8:34 am 2006年1月5日在上午8时34分
I’ve got a wordpress site running on Win2K/IIS5 (it’s an internal demo @ work, so not a huge choice of operating system and server).
Yesterday i set up permalinking with the following structure (and the php.ini file) and it worked fine:
Structure: /index.php/%year%/%monthnum%/%day%/%postname%/
Category Base: /index.php
Today i’ve tried installing a plugin (wp-hashcash), and now i find that my structure doesn’t work and i get loads of 404 errors. However my categories do still work.
So I tried rolling back the only thing that had changed and uninstalled the plugin, but that doesn’t fix the problem.
Would be grateful for any ideas at all, i’m completely at a loss. I’m wondering if the act of installing the plugin has made some irrevocable change, but i can’t see how..
January 5th, 2006 at 9:42 am
Stephen,
As I mentioned in the post above please use the following structure:
I do not encourage embedding date information in permalinks and Google engineer Matt Cutts agrees with me.
Angsuman
January 14th, 2006 at 11:35 am
Hey everyone. So after wrestling with this for a long time (Window XP sp2, IIS 5.1, PHP latest, WP 2.0, MySql 5) I started digging to figure out why my permlinks weren’t working (after following all your good instructions).
I ran into this msft article: http://www.microsoft.com/technet/security/tools/urlscan.mspx
I installed the newer version of urlscan, and turned on the following line in the ini file:
AllowDotInPath=1 ; if 1, allow dots that are not file extensions
(the ini file is in : D:\WINDOWS\system32\inetsrv\urlscan on my machine)
Then refreshing works (be sure to re-install urlscan and restart iis or reboot in order to get it to see the new ini info).
I hope that helps those who are still stuck with windows + iis & permalinks.
Cheers,
Danny
February 19th, 2006 at 2:13 am
[...] Secara otomatis WordPress dapat me-generate file .htaccess namun ada semacam bug -mungkin- yang menyebabkan permalink tidak berjalan, dari hasil search sama mbah Google saya dapat bbrp petunjuk antara lain di Using_Permalinks, wordpress-tip-on-permalink-options, How to configure WordPress to create search engine friendly URLs for permalinks? akhirnya dari petunjuk yang ada saya menambahkan kode berikut pada file .htaccess # BEGIN WordPress [...]
March 5th, 2006 at 11:20 pm
Kewl blog you got goin on up here.
Peace, JiggyWittit
May 5th, 2006 at 6:11 pm
[...] Das halten wir mal schnell fest. In der Wordpress FAQ wird beschrieben wie man auch ohne mod_rewite permalink-ähnliche links in wp-erhält. Mehr dazu auch hier [...]
May 7th, 2006 at 3:06 pm
I have wordpress 1.5.2 installed on window. My attempt to create permalinks without mod_rewrite using a php.ini file worked. see my blog at: http://www.multiculturaladvantage.com/ diversity-recruiting/
However, my posts are striped of all style sheet information. See a sample post: http://www.multiculturaladvantage.com/ diversity-recruiting/ index.php/ archive/ test-shaker-receives-top-honors-for-excellence-in-recruitment-advertising/
I have limited prgramming knowledge and no idea what it means or how to correct it. Does anyone have ny ideas?
Thanks Tracey
May 8th, 2006 at 11:31 am
Check how you specified your CSS file. It should be absolute path and not relative path (as it is most likely now).
July 21st, 2006 at 8:07 pm
All I know is - this is the ONLY thing that has worked for me to change my permalinks from the default to pretty. I used my postname only.
Thank you, thank you! No amount of reading I was doing was working for me and I finally found a link here from WP codex.
July 22nd, 2006 at 4:38 pm
Wow thanks so much for this tip. It is incredibly simple and works great. Just had to make sure the php.ini file is in the domain root. I used the following custom structure: “/index.php/%year%/%monthnum%/%postname%/”, on a Windows IIS 6.0 acct on shared hosting. The only thing I’m worried about now is if WP or the PHP installation on my host gets upgraded and this stops working in the future… THANKS!
July 22nd, 2006 at 7:52 pm
It will continue to work.
July 27th, 2006 at 8:12 am
Christy & Parker,
I am happy that it worked for you. Feel free to spread the word in your blogs
– Angsuman
August 3rd, 2006 at 8:05 pm
[...] I got stuck at this point because the resources I was finding online indicated that to do this on IIS, I needed to muck around with ISAPI rewriting. I can’t do that in a shared hosting environment, so I was in limbo until I found this link through the WordPress Codex. [...]
August 24th, 2006 at 10:06 pm
I am glad that my suggestion was helpful.
August 30th, 2006 at 8:04 am
[...] I finally managed to change my permalinks structure…from downright ugly (ie. http://www.sooyin.com/?p=296578907243 ) to something more bearable. Thanks to this tip! [...]
August 31st, 2006 at 5:25 am
[...] [...]
August 31st, 2006 at 10:00 am
@Cem
Yes it was. Thanks.
September 4th, 2006 at 7:49 pm
[...] I’ve made a couple of other small changes to the site as well; The article and page links have been altered to a more aesthetically pleasing format using Angusman’s Advice posted here and I’ve added a link exchange section to the sidebar with a link to Matt’s Blog ‘Abort. Retry. Fail?‘. Matt is the author of the Article on how to remove the Sony Ericsson file manager I linked to in my last post and his stuff is well worth a read. [...]
September 11th, 2006 at 9:44 am
I still can’t get the friendly permalinks to work. I am on win 2003, IIS 6, PHP 5. I have a dedicated server.
I tried all tricks you saif here but it still printing “no input file specified”.
If anyone know how to get it to work, please let me know!
Thanks,
Stephane
September 12th, 2006 at 4:13 pm
Finally, I got it to work on IIS 6 and win 2k3 with this:
http://www.nathanm.com/2006/07/02/wordpress_permalinks_removing_indexphp_in_iis.html
The plugin is here:
http://www.nathanm.com/wordpress-plugins/
Stephane
October 14th, 2006 at 5:58 am
[...] This reference from Cem via http://blog.taragana.com/index.php/archive/wordpress-tip-on-permalink-options/ [...]
October 30th, 2006 at 2:43 am
[...] XDForum (example: Anaconda Forum) is a nice basic forum software which works seamlessly with WordPress blogs (download our free theme and plugins). Unfortunately it works out-of-the-box with default permalinks only. Most site today use nice permalinks. This mini-tutorial will teach you how to use XDForum with nice permalinks (how to enable; tips and more). [...]
December 18th, 2006 at 5:32 am
I am trying to get some sort of friendly article names to work on my site http://www.fancyacar.co.uk at the moment. I have already made the rewrite rules in .htaccess file but i cant find a way to deal with duplicate post titles. Maybe i could just append a number to the post like http://www.fancyacar.co.uk/hello-world and http://www.fancyacar.co.uk/hello-world-2 ?? ? ? This will ensure that no post titles are the same, wouldnt it? What do you guys think?
April 5th, 2007 at 10:23 am
Wordpress adds the number by default in URLs to duplicate post name
April 11th, 2007 at 5:21 am
I had started my blog with Default format and then changed to Date and Name based.
But now it is custom format %category%/%postname% which I think is good in terms of search engine.
Not very sure!!
May 29th, 2007 at 5:33 am
Thanks for this great info. I have changed the settings of my permalink and hopefully it will attract more search engine to come…
Thanks…
June 5th, 2007 at 1:42 am
Thanks for the information - very helpful when changing my permalink structure. A caution for beginners however: be careful about using %category% unless you are sure you will not change your categories, as doing so will break some of your permalinks. I wrote about this in my blog: http://www.scratch99.com/2007/06/wordpress-permalink-customisation-caution-for-beginners/
As you can see I no longer use category
July 17th, 2007 at 5:01 am
I prefer to have only postname after domain name.fellow webmasters like short urls to link to and i am as a visitor much fond of short urls.
July 25th, 2007 at 9:58 pm
I look at dates in the URL when reading search results to find articles that are most recent.
August 27th, 2007 at 12:18 pm
I used your advice a year ago when I first set up WordPress on our Compulabel site and everything worked fine. The categories of the blog worked with the extra php.ini files to my blog root folder.
However, recently my hosting company updated their version of PHP on the server from PHP5.1.1 to PHP5.2.3. The category pages no longer display properly.
If you visit a category in our blog, like…
Compulabel Labels you’ll see (as of this date), you’ll get an error message…
CGI Error
The specified CGI application misbehaved by not returning a complete set of HTTP headers.
If tried everything, including uploading the entire latest version of Wordpress 2.2 and that hasn’t resolved the problem.
Does anyone have a solution to this problem, short of transferring our site to another server that has the older version of PHP software installed on it (which I don’t want to do)? Thanks
August 27th, 2007 at 1:56 pm
Try updating your permalinks in Options->Permalink
Then look at your .htaccess file to see if something is screwed up.
August 27th, 2007 at 1:57 pm
Also you can try creating a php.ini at my domain root with the following configuration:
cgi.fix_pathinfo = 1
cgi.force_redirect = 0
August 29th, 2007 at 10:13 pm
Thanks for the feedback, but the PHP.ini is correct.
I forgot to mention that I have my version of Wordpress hosted on a shared hosting company and it runs on a Windows IIS. So I’m not able to access the .htaccess file.
I’ve tried UPDATING the permalinks files and some become corrected and others don’t.
It seems Wordpress add /category/ or /archive/ to some of the Permalinks and it’s not always the same. Especially for the PREVIOUS links when a page is too full.
Also, when you create a new CATEGORY, and add a post to it. And click on the new Category link, it doesn’t seem to find the category or the link.
Feel free to explore the blog at
Compulabel and you’ll see my frustration.
Do you think the PHP incompatibility issue could be the issue? It seems like a long-shot but that was upgraded right around the same time the perma links started going bad.
Any other suggestions would be appreciated.
Thanks
October 27th, 2007 at 6:58 am
Its workking…Great tip for wordpress and seo begineers…
November 26th, 2007 at 11:06 am
hi , Thanks i was fighting with this Ugly Permalink problem of my blog http://www.shankerbakshi.com . 。 Thanks i got the solution here. Thanks again, you can’t imagine how happy i am to see permalink working on my blog
December 16th, 2007 at 6:46 am
Seconding Shanker Bakshi’s sentiments, I also was battling the permalink problem for about two evenings, on and off.. reloading probably 50 times, and slipping the php.ini code definitely saved my sanity, so thanks for making my day!
December 18th, 2007 at 12:57 pm
I DO NOT LIKE INDEX.PHP WUWUWUWU….
December 23rd, 2007 at 7:54 am
The new Wordpress has features built in to do that sort of stuff, what I find works well is /%postmonth%/%postname%.html , or similar
January 3rd, 2008 at 6:42 pm
Well, since everyone else seems to be sh!tting all over your post, I\’m going to go ahead and congratulate you, as it has helped me alot and I\’ve now got my blog working the way I want it. Thank you very much!
January 12th, 2008 at 6:19 pm
Thank you for this post! I have been really dragging my feet about changing my URL structure, I followed your directions here and it was almost too easy!
Thanks again
February 17th, 2008 at 3:50 am
Thank you. Very beatiful post.
February 27th, 2008 at 5:05 pm
Damn, good stuff… That helped and took me a while
February 29th, 2008 at 12:16 pm
Worked great - thanks so much! After several failed attempts with some plugins, this was the exact simple, effective fix we needed.
March 29th, 2008 at 11:29 pm
The PHP.ini trick stopped working with WordPress 2.5. Any suggestions?
April 13th, 2008 at 6:04 pm
Anyone home?
May 11th, 2008 at 2:40 pm
Awesome this worked for me. Thank you to people who share and respond.
cgi.fix_pathinfo = 1
cgi.force_redirect = 0
in php.ini file.
Wordpress shuld detect this in their next version.!
May 21st, 2008 at 4:20 pm
Thanks, this worked out fine!
May 22nd, 2008 at 3:37 pm
Using WP v2.5 and it worked out fine…Keep up the good work!