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您也可以想讀 |



Add to Technorati Favorites 
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
I think you would be better of including index.php in your path like this blog.
January 5th, 2006 at 8:34 am
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!