이 플러그인은 최근 3개의 주요 워드프레스 출시와 시험 되지 않았습니다. 워드프레스의 좀 더 최근 버전으로 이용할 때 더 이상 관리되지 않고 지원되지 않고 호환성 문제가 있을 수 있습니다.

Enhanced Custom Permalinks

설명

This plugin is a fork of the Custom-Permalinks plugin. It has some expanded bug patches AND is able to interoperate with the WP-no-category-base plugin.

This plugin will allow you to set permalinks in a more precise way – in short you can include sub-folders. A page could have the permalink http://www.example.com/aFolder/anotherFolder/page.html without having to create the intermediate pages or categories aFolder/anotherFolder/.

Be warned: This plugin is not a replacement for WordPress’s built-in permalink system. Check your WordPress
administration’s “Permalinks” settings page first, to make sure that this doesn’t already meet your needs.

This plugin is only useful for assigning custom permalinks for individual posts, pages, tags or categories.
It will not apply whole permalink structures, or automatically apply a category’s custom permalink to the posts
within that category.

설치

  1. Unzip the package, and upload enhanced-custom-permalinks to the /wp-content/plugins/ directory
  2. Activate the plugin through the ‘Plugins’ menu in WordPress
  3. Edit any post, page, tag or category to set a custom permalink.

후기

2016년 9월 3일
this plugin destroys the wordpress admin area, it uses deprecated code. also the author does not seem to use the DEBUG=true setting for plugin development, what is a sign for very bad quality. Do no use, will kill your site!
2016년 9월 3일
Works great on simple templates, but if you change the permalink of a page using a custom query template with a paged parameter, it returns a 404 error on page/2, page/3, etc.
모든 14 평가 읽기

기여자 & 개발자

“Enhanced Custom Permalinks”(은)는 오픈 소스 소프트웨어입니다. 다음의 사람들이 이 플러그인에 기여하였습니다.

기여자

자국어로 “Enhanced Custom Permalinks”(을)를 번역하세요.

개발에 관심이 있으십니까?

코드 탐색하기는, SVN 저장소를 확인하시거나, 개발 기록RSS로 구독하세요.

변경이력

0.1.0 Initial Release

0.1.1 Patch
Updates to allow the plugin to work with newer versions of php w/o warnings by removing calls to mysql_real_escape_string and replacing them with prepared statements.