Getting Manila to run in the OPML Editor

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.

  1. http://scripting.com/manila/tmp2/2005/12/01.html

  2. http://scripting.com/manila/tmp2/

  3. http://scripting.com/manila/tmp2/

  4. http://scripting.com/manila/tmp2/2000.html

  5. http://scripting.com/manila/tmp2/2000/12/25.html

  6. http://scripting.com/manila/tmp2/2005.html

  7. http://scripting.com/manila/tmp2/2005/02/22.html

  8. http://scripting.com/manila/tmp2/2005/02/26.html

  9. http://scripting.com/manila/tmp2/2005/02/28.html

  10. http://scripting.com/manila/tmp2/2005/03/01.html

  11. http://scripting.com/manila/tmp2/2005/03/02.html

  12. http://scripting.com/manila/tmp2/2005/03/04.html

  13. http://scripting.com/manila/tmp2/2005/03/07.html

  14. http://scripting.com/manila/tmp2/2005/03/08.html

  15. http://scripting.com/manila/tmp2/2005/03/09.html

  16. http://scripting.com/manila/tmp2/2005/03/10.html

  17. http://scripting.com/manila/tmp2/2005/03/15.html

  18. http://scripting.com/manila/tmp2/2005/03/18.html

  19. http://scripting.com/manila/tmp2/2005/04/04.html

  20. http://scripting.com/manila/tmp2/2005/04/21.html

  21. http://scripting.com/manila/tmp2/2005/05/23.html

  22. http://scripting.com/manila/tmp2/2005/06/04.html

  23. http://scripting.com/manila/tmp2/2005/06/13.html

  24. http://scripting.com/manila/tmp2/2005/07/23.html

  25. http://scripting.com/manila/tmp2/2005/09/14.html

  26. http://scripting.com/manila/tmp2/2005/09/21.html

  27. http://scripting.com/manila/tmp2/2005/09/29.html

  28. http://scripting.com/manila/tmp2/2005/10/11.html

  29. http://scripting.com/manila/tmp2/2005/10/12.html

  30. http://scripting.com/manila/tmp2/2005/10/21.html

  31. http://scripting.com/manila/tmp2/2005/12/01.html

  32. http://scripting.com/manila/tmp2/macintoshnews.html

  33. http://scripting.com/manila/tmp2/p2pnews.html

  34. http://scripting.com/manila/tmp2/dotcomnews.html

  35. http://scripting.com/manila/tmp2/musicnews.html

  36. http://scripting.com/manila/tmp2/soapmeetsrss.html

  37. http://scripting.com/manila/tmp2/xmlnews.html

  38. http://scripting.com/manila/tmp2/patentnews.html

  39. http://scripting.com/manila/tmp2/mindbombnews.html

  40. http://scripting.com/manila/tmp2/the2xinternet.html

  41. http://scripting.com/manila/tmp2/payloadsforrss.html

  42. http://scripting.com/manila/tmp2/desktopwebsites.html

  43. http://scripting.com/manila/tmp2/commercialcategories.html

  44. http://scripting.com/manila/tmp2/davidstromonweblogs.html

  45. http://scripting.com/manila/tmp2/thexmlfiles.html

  46. http://scripting.com/manila/tmp2/speechandweblogs.html

  47. http://scripting.com/manila/tmp2/about.html

  48. http://scripting.com/manila/tmp2/editorial/

  49. http://scripting.com/manila/tmp2/editorial/turningpointforweb.html

  50. http://scripting.com/manila/tmp2/turningpointforweb.html

2 responses to this post.

  1. […] Winer hat Manila im OPML-Editor zum Laufen bekommen. Eine Beispielsite ist online. Als nächstes will er all seine Manila-Sites statisch herausrendern. […]

    Reply

  2. […] About « Getting Manila to run in the OPML Editor […]

    Reply

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: