IOW, is there a painless (relative) upgrade path. How does modETP fit
into the mix? Will it be possible to migrate current content into
modETP and then to ETP2?

Thanks,

modETP is a modification of ETP1.0 without upgrade scripts.  I don't actively maintain it anymore although some parts will be moved to ETP2.  ETP2 is the real successor.  modETP was a wack a code solution for a marketing/sales need.  Although modETP was good enough to be used for some production or soon to be production sites.

If you have time I would encourage you to help out Dave for ETP2 as I am unable to.  DaveB is alone on this one as I think Luke P is also busy.

I have a need for a simple CMS where I can set up simple templates that indicate where blocks of text and images are to go, then allow the site admin to upload their text and images.  It doesn't have to be easy to specify the templates, since I'll be doing that, but it does have to be easy from the user's point of view.

ETP doesn't seem to do this;  it just lets me upload one block of text per page.  Do any of the others?  Or am I missing some feature of ETP?

I still would like to see a short-and-sweet description of how ETP, ETP2, modETP and CMS differ, if there is anyone out there who has tried them all?

It's hard to tell by looking if dev.openacs.org does what I need or not.  Let me try to describe it better.  This is my ideal setup; I'm fairly sure nothing like this exists today (except maybe CMS which isn't working on PG as of last night's checkout), so don't think I expect to get exactly this.  I just need to know how close I can come to perfection. :)

Site admin is ready to post some content to a couple of pages.  He goes to the CMS admin page, where he chooses the first page he wishes to update.  He is presented with a page that lets him upload 2 images and 3 blocks of text.  The system knows, because I have set it up this way, that this particular page requires (or allows) those particular pieces.  He hits a Preview button, likes what he sees, and submits the new page.  Page is now live.

He then goes back to the CMS admin page, where he chooses another page to update.  This one is 1 image and 2 blocks of text.  Etc, etc

So I need an admin interface that lets me create a page, telling it what ADP to use and what content blocks that page requires.  Then I need another admin interface that lets the user upload content as above.

I understand what you're saying about having an ADP that pulls from various ETP sections, but I don't think it's going to do enough to simplify uploading of new content, especially images.  Or am I wrong about that?

We should probably take this offline, but maybe I can help you with ETP2?  How far along is it?

Dave, I am willing to help with ETP2 - just let me know what needs doing.  But not until after I get the 4.6 release page done! :)

For what it's worth, I put together a 3.2.5 module that does a number of the ETP functions, but in particular uses some ideas and code from the Musea content management system for handling images in the text. It organizes pages into topics, scopes to groups or site-wide deployment, and lets authors control various other aspects of the page (but doesn't do revision control like ETP does). I've enabled the module in the Bay Area OACS User Group area; if you're interested go to http://www.epimetrics.com, register (Talli, you've already done that, long ago), add yourself to that group, and have a look. I've given regular group members page editing permissions so you'll have access to all the editing/admin pages for the group.

I'd offer to port this across to 4.5 but that seems superfluous given all the great work in ETP. Ah well, I hope to be able to give back to the community with 4.5 development soon, now that various 3.2.5 projects have stabilized.

The code for images is mostly from the Musea example, though I wrote some stuff that parses the page as it's delivered and substitutes the real image tags for the pseudo tags page authors use. I'd be happy to bundle the whole module together if there's interest; I just assumed that it would need to be ported to v4x first.

So when you added yourself, you got put in a role without those permissions. Now fixed. I just "became you" and confirmed that you get the admin links now. Sorry.

I am working on fixing some bugs and cleaning up ETP 1 to release ETP 1.1 this week for beta testing.

After that we can coordinate on futher work.

So mainly we need someone to make sure the data model and pl/sql procs are aligned with the postgresql versions and working and to test the queries.

My previous post seem to sound that ETP will never be ported, sorry.