<?xml version="1.0" encoding="utf-8"?>
			
			<rss version="2.0">
			<channel>
			<title>James Allen&apos;s Coldfusion and Internet Technology Blog - BlogCFC</title>
			<link>http://jamesallen.name/index.cfm</link>
			<description>Adventures in Coldfusion and Internet development.</description>
			<language>en-us</language>
			<pubDate>Wed, 08 Sep 2010 17:47:33 +0100</pubDate>
			<lastBuildDate>Mon, 19 Nov 2007 21:10:00 +0100</lastBuildDate>
			<generator>BlogCFC</generator>
			<docs>http://blogs.law.harvard.edu/tech/rss</docs>
			<managingEditor>slingshotuk@googlemail.com</managingEditor>
			<webMaster>slingshotuk@googlemail.com</webMaster>
			
			
			
			
			
			<item>
				<title>Fixing &lt; code &gt; blocks when using TinyMCE in BlogCFC</title>
				<link>http://jamesallen.name/index.cfm/2007/11/19/Fixing-code-blocks-when-using-TinyMCE-in-BlogCFC</link>
				<description>
				
				&lt;p&gt;While working on setting up and integrating the superb BlogCFC with my own custom template, I discovered that the admin section does not utilise a richtext editor (Ray is hardcore :). However, Ray has been very helpful by splitting out the textarea HTML used on the blog entry input page which makes it very easy to plug in a suitable rich text editor.&lt;/p&gt;
&lt;p&gt;The one I have chosen is TinyMCE. It&apos;s very nice to configure (incredibly easy - easy is good) and pretty lightweight. Nick Tong over at succor.co.uk blogged about adding TinyMCE to BlogCFC last year and it&apos;s a nice clear guide to anyone who wants to do this. Check out his blog post &lt;a class=&quot;null&quot; href=&quot;http://www.succor.co.uk/index.cfm/2006/10/10/Adding-TinyMCE-to-blogCFC-admin-area&quot; target=&quot;_blank&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Now, while it&apos;s a pretty trivial job to get TinyMCE working with BlogCFC there are a number of initial problems that break some functionality. These are to do with the custom tags which you can use to embed certain formatting / features into a blog post. As the tags are HTML style TinyMCE decides to nuke them from the source code view and escapes them in visual mode - not good.&lt;/p&gt;
&lt;p&gt;The first of these is the &lt;strong&gt;&amp;lt;more/&amp;gt;&lt;/strong&gt; tag which allows you to break up a blog post so that on the index page you only see a summary and then click &apos;more&apos; to view the entire post. A fix to this is to modify BlogCFC to support [ more/ ] instead. Nick Tong has again blogged about making the changes &lt;a class=&quot;null&quot; href=&quot;http://www.succor.co.uk/index.cfm/2006/10/10/Changes-to-more-tag-in-blogCFC-for-rich-text-editors&quot; target=&quot;_blank&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The second problem is in including a nicely colour coded scrolling code box which you can use to include Coldfusion code samples on your blost posts. Out of the box, the way to do this is to enclose the code sample with &lt;strong&gt;&amp;lt;code&amp;gt;&lt;/strong&gt; &lt;strong&gt;&amp;lt;/code&amp;gt;&lt;/strong&gt; tags. As above, this is a no no with TinyMCE as it doesn&apos;t recognise the tags as valid HTML and so removes them. If you try including them in the visual mode (which is what I wanted) it escapes the characters and breaks the functionality.&lt;/p&gt;
&lt;p&gt;I spent a couple of hours looking into this and have come up with a modification which allows the code output functionality to work in visual editing mode, but using &lt;strong&gt;{ code }&lt;/strong&gt; and &lt;strong&gt;{ /code }&lt;/strong&gt; tags instead (&lt;em&gt;without the spaces - I am having to do that to avoid my mod kicking in and showing &apos;and&apos; in code display&lt;/em&gt; :).&lt;/p&gt;
&lt;p&gt;
				 [More]
				</description>
						
				
				<category>BlogCFC</category>				
				
				<pubDate>Mon, 19 Nov 2007 21:10:00 +0100</pubDate>
				<guid>http://jamesallen.name/index.cfm/2007/11/19/Fixing-code-blocks-when-using-TinyMCE-in-BlogCFC</guid>
				
			</item>
			
		 	
			
			
			<item>
				<title>Firefox bug when using TinyMCE with BlogCFC - [ Exception NS_ERROR _NOT_AVAILABLE ]</title>
				<link>http://jamesallen.name/index.cfm/2007/11/19/Firefox-bug-when-using-TinyMCE-with-BlogCFC--Exception-NSERRORNOTAVAILABLE</link>
				<description>
				
				&lt;p&gt;I&apos;ve just discovered that when &lt;a class=&quot;null&quot; href=&quot;http://www.succor.co.uk/index.cfm/2006/10/10/Adding-TinyMCE-to-blogCFC-admin-area&quot; target=&quot;_blank&quot;&gt;using TinyMCE with BlogCFC&lt;/a&gt; an exception is generated in Firefox 2 which means you can&apos;t use the editor component.&lt;/p&gt;
&lt;p&gt;I have worked out a fix, which is due to the BlogCFC post entry page initially setting the main div (tabber) to &apos;display:none&apos;:&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;admin/entry.cfm - line 246 (in BlogCFC 5.9):&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;{code}&lt;br /&gt;&amp;lt;script type=&quot;text/javascript&quot;&amp;gt;&lt;br /&gt;//Used to hide tabber flash&lt;br /&gt;&lt;br /&gt;document.write(&apos;&amp;lt;style type=&quot;text/css&quot;&amp;gt;.tabber{display:none;}&amp;lt;\/style&amp;gt;&apos;);&lt;br /&gt;&amp;lt;/script&amp;gt;&lt;br /&gt;{/code}&lt;/p&gt;
&lt;p&gt;To fix, simply remove this style:&lt;/p&gt;
&lt;p&gt;{code}&lt;br /&gt;&amp;lt;script type=&quot;text/javascript&quot;&amp;gt;&lt;br /&gt;//Used to hide tabber flash&lt;br /&gt;&lt;br /&gt;document.write(&apos;&amp;lt;style type=&quot;text/css&quot;&amp;gt;.tabber{}&amp;lt;\/style&amp;gt;&apos;);&lt;br /&gt;&amp;lt;/script&amp;gt;&lt;br /&gt;{/code}&lt;/p&gt;
&lt;p&gt;I thought this might affect the operation of the tab switching but it seems to have no visible effect, so all is well.&lt;/p&gt;
&lt;p&gt;Let me know if anyone get&apos;s an issue with this.&lt;/p&gt;
				
				</description>
						
				
				<category>BlogCFC</category>				
				
				<pubDate>Mon, 19 Nov 2007 21:00:00 +0100</pubDate>
				<guid>http://jamesallen.name/index.cfm/2007/11/19/Firefox-bug-when-using-TinyMCE-with-BlogCFC--Exception-NSERRORNOTAVAILABLE</guid>
				
			</item>
			
		 	
			</channel></rss>