Hi Jim,

thanx for your investigation, I have moved all problematic to another newly created page so it should migrate smoothly now, when is the next cycle?

thx,
Martin

On Aug 31, 2009, at 19:19, Jim Grisanzio wrote:

Jim Grisanzio wrote:
Martin Man wrote:
Additionally this page was not migrated at all

http://www.opensolaris.org/os/project/czosug/events/

hey, Martin.

This page was not supposed to come over. See the site feature mappings under the special features section. Certain pages are not being migrated, so if you want the content you have to pull it out and create a new page outside of the app-produced pages (events, announcements, etc).

http://opensolaris.org/os/community/web/restructuring/site_features/

However, I see the two child pages under the events page did came over. Let me do a little test during the migration later today to see about this. Will get back to you.



Ok, this is what I did: I took your top level events page and put it in Advocacy as a test, but I renamed it with an _live at the end (which sort of juxtaposes with your events_archive page):

http://opensolaris.org/os/community/advocacy/events_live/

Then I put the two child pages under events_live:

http://opensolaris.org/os/community/advocacy/events_live/OpenSolarisTrainingAtMUNI/
http://opensolaris.org/os/community/advocacy/events_live/training-2008-11/

Anyway, it all migrated together just fine in Advocacy. So, to get that top level events page -- which is not part of the migration -- create a new page with a new name and move the two child pages under it and that will solve that problem. You don`t have to create new child pages, though. You can just reassign them to the new parent page via the drop down menus at the bottom of their content edit boxes in edit mode.

Jim






_______________________________________________
website-discuss mailing list
[email protected]

Reply via email to