Finally, after two weeks of non-stop work, I have finally released version 3.1 of CJ File Browser, my image/file manager that can be used as a tinyMCE plug-in or be used in stand-alone mode. To anyone that downloaded the previous couple of versions, let me apologize to you.
Since the very first release of my ColdFusion File Manager, I have always tried to make it simple and easy for people to figure out how to use it. When I converted the code to make it a tinyMCE plug-in, it added a layer of complexity that I never really had time to deal with. The result of that led me down the path of releasing a bunch of sub-par projects to the public.
A few weeks ago, I decided I was going to re-write some of the code and try to clean things up a little bit. I quickly released version 3.0, found some little bugs and released version 3.0.1. Well, I got to be honest with you. That one was pure crap. And for that, I apologize.
One of the main features of CJ File Browser is the capability to use various server technologies besides ColdFusion, to handle all the server calls. In order to do this, you may need to create your own plug-in for the new Handler Engine System. This guide will provide you with the layout, required functions and function responses that are needed in order to do this.
Unfortunately, in order for you to create your own Handler Engine plug-in, you are going to need at least some basic knowledge of programming language. There's just to much going on on the functions to effectively explain it all here. You are going to need to be able to open up one of the existing handler engine plug-ins to get a grasp of what it's doing. If any of this is not making sense, then don't hesitate to ask a question. I'm more than happy to provide any insight into making these!
How's that for a teaser. Stay tuned!
My entire morning was wasted on a perplexing little problem I was having trying to get TinyMCE to embed YouTube videos for one of my clients. I must have tried a gazillion different little hacks, mods and anything I could think of, but each time I hit the submit button, it seems as if the
<embed> tags were being converted to
<InvalidTag>. No matter what settings I used in the TinyMCE init script, it still was converting these tags. Guess what? It wasn't TinyMCE at all. It was ColdFusion all along! Go figure.