David E Jones wrote:
...
>
That would leave us with just the page in the content manager to update
in order to be able to remove JPublish...
-David
I agree with David's comments and so I really think that getting rid of
the JPublish pages in the Content application should be an high priority
task now.
I could help with this in my spare time but since many of the Content's
screens are already broken or don't function properly, I'd love to get
some hints from the persons who have contributed to the component in the
past (e.g. Al and maybe Hans) about:
- the screens that are just an (incomplete) work in progress and can be
disabled (instead of migrated) for now
- the screens and other artifacts that are old or superseded or
misplaced or duplicated artifacts and can be removed (for example, there
is a services.xml file in the WEB-INF folder;
LookupPartyAndUserLoginAndPerson.ftl and LookupPerson.ftl in the content
folder; there are some files in the images folder that seems to me just
copies from the framework/images component; mysterious files such as
EditLayoutContent.ftl.multi in the layout folder etc. etc. etc...)
Thanks,
Jacopo
