Interesting. We don't have a tag like that because there's no special processing for the preview. We actually save the page in a transaction, capture the rendering, raise an exception and rollback the transaction.
Perhaps we could handle URLs in the preview in a way that will be exactly the published page URL...? On Fri, Feb 15, 2013 at 12:58 PM, Drew Neil <[email protected]> wrote: > I've just run into this issue with my Disqus comments: > > http://help.disqus.com/customer/portal/articles/662547-why-are-the-same-comments-showing-up-on-multiple-pages- > > In the Radiant admin, if I hit the 'preview' button on an unpublished page > it will automatically load in disqus comments from an existing page. When I > publish the new page, it continues to show comments from the pre-existing > page, even though both pages have unique `disqus_identifier` values. > > The Disqus help page above recommends disabling comments when using a > preview feature. Is there an <r:unless_preview/> radius tag, or some other > way of suppressing content when rendering a preview? > > Thanks, > Drew > > -- > > --- > You received this message because you are subscribed to the Google Groups > "Radiant CMS" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > -- Write intention revealing code #=> http://www.clean-ruby.com Jim Gay Saturn Flyer LLC 571-403-0338 -- --- You received this message because you are subscribed to the Google Groups "Radiant CMS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
