I still have a bunch of Manila sites I keep running, and for that I keep a copy of Frontier running on one of my servers. My life would be a lot simpler if I had Manila running in the OPML Editor environment. So this blog post are my notes on the process of getting that to work.
1. I downloaded the Frontier trial product from userland.com, and copied manila.root into the Tools folder of my OPML Editor installation. It’s in the same place as in Frontier, Guest Databases/apps. (Note: The manila.root I’m using has a creation date of June 6, 2005.)
2. I relaunched the OPML Editor. manilaThread.script runs, and it initializes config.manila.
3. I added a #changes table to the top level of manila.root, so that my WebEdit check-ins are tracked. This is just for documentation.
4. There’s no menu in manilaSuite, so there’s no Manila menu in the Tools menu. This is because manila.root predates the Tools feature. So I grabbed a copy of mainresponder.menu and put it in manilaSuite.menu. Change the title of the menu from Server to Manila. (Later I will release this as a part to update manila.root. No doubt some of the commands in this menu don’t belong in the Manila menu.)
5. I mapped a few test domains to my EC2 server: tmp1, tmp2, tmp3, tmp4, tmp5.smallpicture.com.
6. I copied one of my Manila sites, twoWayWeb.root, into my www folder. Open the file. Put the cursor on the top item. Choose Install Site from the Manila sub-menu of the Tools menu. Enter http://tmp2.smallpicture.com/. The first few times I tried to get to the home page of the site it seemed to hang, but after going away and coming back, it worked. So it appears that the OPML Editor is a good hosting environment for Manila.
7. Now let’s see if the editorial features are working. I logged in through the Members box. The Editors Only menu appeared. Clicked around, everything worked except Prefs, it wanted “prefsSuite.” I’m going to put it at the top level of manila.root, since it’s the only code I have now that’s dependent on it. If another app shows up, we can move it into system.verbs.builtins. That settled that. It works.
8. Go to the Control Panel for the server, and follow the instructions on the Static Rendering faq. It’s pretty simple to render the whole site, just go to the Admin page, and scroll down, and click the Render Whole Site button. It gives you a list of all the pages.
- http://scripting.com/manila/tmp2/2005/12/01.html
- http://scripting.com/manila/tmp2/
- http://scripting.com/manila/tmp2/
- http://scripting.com/manila/tmp2/2000.html
- http://scripting.com/manila/tmp2/2000/12/25.html
- http://scripting.com/manila/tmp2/2005.html
- http://scripting.com/manila/tmp2/2005/02/22.html
- http://scripting.com/manila/tmp2/2005/02/26.html
- http://scripting.com/manila/tmp2/2005/02/28.html
- http://scripting.com/manila/tmp2/2005/03/01.html
- http://scripting.com/manila/tmp2/2005/03/02.html
- http://scripting.com/manila/tmp2/2005/03/04.html
- http://scripting.com/manila/tmp2/2005/03/07.html
- http://scripting.com/manila/tmp2/2005/03/08.html
- http://scripting.com/manila/tmp2/2005/03/09.html
- http://scripting.com/manila/tmp2/2005/03/10.html
- http://scripting.com/manila/tmp2/2005/03/15.html
- http://scripting.com/manila/tmp2/2005/03/18.html
- http://scripting.com/manila/tmp2/2005/04/04.html
- http://scripting.com/manila/tmp2/2005/04/21.html
- http://scripting.com/manila/tmp2/2005/05/23.html
- http://scripting.com/manila/tmp2/2005/06/04.html
- http://scripting.com/manila/tmp2/2005/06/13.html
- http://scripting.com/manila/tmp2/2005/07/23.html
- http://scripting.com/manila/tmp2/2005/09/14.html
- http://scripting.com/manila/tmp2/2005/09/21.html
- http://scripting.com/manila/tmp2/2005/09/29.html
- http://scripting.com/manila/tmp2/2005/10/11.html
- http://scripting.com/manila/tmp2/2005/10/12.html
- http://scripting.com/manila/tmp2/2005/10/21.html
- http://scripting.com/manila/tmp2/2005/12/01.html
- http://scripting.com/manila/tmp2/macintoshnews.html
- http://scripting.com/manila/tmp2/p2pnews.html
- http://scripting.com/manila/tmp2/dotcomnews.html
- http://scripting.com/manila/tmp2/musicnews.html
- http://scripting.com/manila/tmp2/soapmeetsrss.html
- http://scripting.com/manila/tmp2/xmlnews.html
- http://scripting.com/manila/tmp2/patentnews.html
- http://scripting.com/manila/tmp2/mindbombnews.html
- http://scripting.com/manila/tmp2/the2xinternet.html
- http://scripting.com/manila/tmp2/payloadsforrss.html
- http://scripting.com/manila/tmp2/desktopwebsites.html
- http://scripting.com/manila/tmp2/commercialcategories.html
- http://scripting.com/manila/tmp2/davidstromonweblogs.html
- http://scripting.com/manila/tmp2/thexmlfiles.html
- http://scripting.com/manila/tmp2/speechandweblogs.html
- http://scripting.com/manila/tmp2/about.html
- http://scripting.com/manila/tmp2/editorial/
- http://scripting.com/manila/tmp2/editorial/turningpointforweb.html
- http://scripting.com/manila/tmp2/turningpointforweb.html
Posted by Er hat es geschafft – Der Schockwellenreiter on January 20, 2010 at 1:00 am
[...] Winer hat Manila im OPML-Editor zum Laufen bekommen. Eine Beispielsite ist online. Als nächstes will er all seine Manila-Sites statisch herausrendern. [...]
Posted by Converting a dynamic Manila site into a static site « Frontier News on January 20, 2010 at 6:54 am
[...] About « Getting Manila to run in the OPML Editor [...]