I’ve just found and started to use the plug-in. It’s mostly working nicely and really helps out when deploying a site to a live location.

I however have one issue: When changing to short codes I cannot get the pictures to appear in the visual editor. Everything works fine when you view the page but in the visual editor I just get a broken link icon instead of the picture.

Does anyone have any insight into this?

(I’m using WordPress 3.2.1)

Reply from Peter: I don’t know of an easy solution to that, but perhaps someone else can share their findings!

<a href= "[posturl]">{KEYWORD}</a>

…now turned the new post with my chosen keyword to

<a href= "[posturl]">Test Post Code</a>

…and on my actual blog the keyword now has an internal permalink structure linking to its own post.

Thanks for this great shortcode!

Is it possible to use your shortcode plugin to auto generate the NEW post URL vs having to put in an ID# for some other random post? For example, I use CPMage by Greg Jacobs. It’s a plugin that generates articles from various directories, etc… and i use their keyword tag to generate the post and the content {KEYWORD}. Is it possible to use your code to ensure that when a NEW post is generated it will know to pull the URL of that NEW POST? Here’s the use of your code, and wondering if it would work for my needs? See below:

<a href= "[posturl]">{KEYWORD}</a>

Reply from Peter: I’m not sure if I completely understand the use case, but I’m guessing that my plugin is not what you are looking for. The “posturl” shortcode as implemented is only for the article in which it is placed. You’d have to write your own custom logic to have it based on anything other than the current post.

Reply from Peter: Thanks for pointing that out. The plugin has a setting for that to be hard-coded near the bottom of the file, but I should probably have a smarter automatic fallback in a subsequent plugin release.

Also, hope you can check if this is compatible with WP 3.1. Thank you.

Reply from Peter: Thanks for the feedback. It is compatible with WordPress 3.1. It uses get_bloginfo( ‘template_url’ ) (which you can change near the top of the plugin file). However, you are right that I should add [childtemplateurl] (and have that output stylesheet_directory) as well. I’ve now released that with version 0.3.

Reply from Peter: I just released version 0.2 with the shortcode [templateurl]

PS: more preciserl, for example when I insert an image or other item from media library, I need to change in HTML to avcoid the absolute path reference and use shortcodes. Any way to avoid that?

Reply from Peter: You can use [blogurl] in the TinyMCE view. Also, in the image properties box, you can also use [blogurl] in the “Link URL” field, as well as in the “Source” field in the “Advanced Settings” tab. I haven’t looked into how to affect the default-generated URLs nor to create a completely new button and new dialog / properties box behavior.

Great plugin — have you made any progress with updating the plugin to support using this with WordPress in a subdirectory as mentioned by Mario above?

If it would be possible to provide more details on what to edit in the plugin code that would be great — I think your plugin has some great potential for people who install WordPress in subdirectory for development and then use the Move your wordpress directory steps (http://codex.wordpress.org/Giving_WordPress_Its_Own_Directory ) to make it live at the root url of the site. This keeps any hardcoded links from being broken when the permalink structure changes for launch

Thanks again

Nathan

TO

$blogurl_settings['siteurl'] = get_option(‘home’);

That works for the [blogurl] do I need to change anything for uploads?

Reply from Peter: I’ve released an updated version that will differentiate [blogurl] from [blogurl wordpress]