http://coffee2code.com/archives/2010/01/05/hide-broken-shortcodes-v1-1/ pro-gram-mer: n. a person who converts coffee into code Tue, 07 Feb 2012 05:56:04 +0000 hourly 1 http://coffee2code.com/archives/2010/01/05/hide-broken-shortcodes-v1-1/comment-page-1/#comment-460126 Coffee2Code Releases Updates for WordPress 2.9 | Blogging, WordPress, Social Media, Web Publishing - WordCast Thu, 06 Jan 2011 11:00:27 +0000 http://coffee2code.com/?p=494#comment-460126 [...] Hide Broken Shortcodes prevents broken shortcodes from appearing in posts and pages. [...] [...] Hide Broken Shortcodes prevents broken shortcodes from appearing in posts and pages. [...]

]]> http://coffee2code.com/archives/2010/01/05/hide-broken-shortcodes-v1-1/comment-page-1/#comment-451612 Morten Skogly Mon, 22 Mar 2010 13:18:12 +0000 http://coffee2code.com/?p=494#comment-451612 Hi, have you come across a method for replacing the shortcode permanently with the content it generates? I've used tantan flickr that "caches" the generated content as a customfield, but I have a case where I want to pull inn an article from and old publishing system and simply replace the shortcode with this content, and thats it. I thought that would be a nice function for others as well, for instance if you wanted to "retire" a wordpress blog, and archive it. To minimize the risk of shortcode content dying you could pull it in and store it as part of the post content. Hi, have you come across a method for replacing the shortcode permanently with the content it generates? I’ve used tantan flickr that “caches” the generated content as a customfield, but I have a case where I want to pull inn an article from and old publishing system and simply replace the shortcode with this content, and thats it. I thought that would be a nice function for others as well, for instance if you wanted to “retire” a wordpress blog, and archive it. To minimize the risk of shortcode content dying you could pull it in and store it as part of the post content.

]]>