Linux 软件免费装

Hikari Internal Links

开发者 shidouhikari
更新时间 2010年7月6日 02:39
捐献地址: 去捐款
PHP版本: 2.8.0 及以上
WordPress版本: 3.0

标签

feed Post posts page categories shortcode tag permalink taxonomy link category RSS slug custom type p2p Post to Post wpdberror ID

下载

0.06.03

详情介绍:

Don't worry anymore of linking a post or a category, to later change its title or slug, or changing your posts permalinks, and creating invalid links to your own site pages. Hikari Internal Links provides a shortcode that dynamically generates links to most Wordpress resources. You can query these resources based on their ID or slug, and these links are generated dynamically. Therefore if you change a resource's title or permalink, its links will be updated automatically. Features Available Resources This plugin is a fork from Michael Toppa's Post-to-Post Links II.

安装:

Hikari Internal Links requires at least Wordpress 2.8 and PHP5 to work. You can use the built in installer and upgrader, or you can install the plugin manually.
  1. Download the zip file, upload it to your server and extract all its content to your /wp-content/plugins folder. Make sure the plugin has its own folder (for exemple /wp-content/plugins/hikari-internal-links/).
  2. Activate the plugin through the 'Plugins' menu in WordPress admin page.
  3. Now you can start using the shortcode to build internal links to your site
Upgrading If you have to upgrade manually, simply delete hikari-internal-links folder and follow installation steps again. Uninstalling Hikari Internal Links doesn't store configs in database. You can freely deactivate it or simply delete its files and it will be fully uninstalled.

升级注意事项:

0.06 and above If you have to upgrade manually, simply delete hikari-internal-links folder and follow installation steps again.

常见问题:

Where can I see a list of all shortcode parameters and exemples of it being used?

For a full description of its shortcode parameters, please refere to Hikari Internal Links � Exemples.

What happens if I build a link based on slug and later change that resource's slug?

Most resources can be queried by ID or slug, this feature is provided to offer flexibility on its use. When a resource is queried, the value used to query must refere to a existing resource. If you query using ID and change the resource ID, then there's no way to find what it used to refere to... same thing goes for using slug and later changing the slug. I suggest using ID always when possible and never change resources IDs, that's not needed at all and could only be done editing directly the database.

Where's the options page?

There's none, currently I see no need to set options. Just use the shortcode anywhere you want :)

更新日志:

0.06