migrating .shtml to .page

Is there a tool or process that automates the migration of .shtml to .page? Our client has 80,000+ pages that they want to migrate ASAP.

Find more posts tagged with

Comments

nipper

learn perl. Smiley Very Happy

There is no tool to do that. You need to write a script to do so.

catownsley

I need to know how the file contents change for compatibility. Have you converted the file types, other than a simple file extension change? If so, what type of performance issues arise out of pushing static content to a a dynamic content server, such as Tomcat.

nipper

That depends on what you are doing.

Obviously if the file extension is changing, links to it need to change. Minor detail.

Also, typically you would remove the header/footer/left nav and replace them with SP components. So yes the file contents will change.

catownsley

So the .shtml does not have to be converted to the .page xml format? Also, have you made this conversion before?

nipper

in the process of doing it now

Currnetly stripping out navigation, header & footer. Then will need to remap internal URLs and rename files. Not certain of the final format, I am waiting for SP guy to give me the final structure. but it will be the HTML (maybe in a wrapper)

catownsley

Also, all of our .shtml is templated and backed by DCRs.

nipper

Then it would probably be easier to make a tpl that generates the .page

tanguyr

I would suggest that you don't generate too many individual .page files in a single site, or performance will suffer when editing pages. We learned this the hard way (and we have less than 2k .page files): when you edit a component on a .page, SitePublisher will visit all the other pages in the site, which can take a loooong time. On top of this, if the user performing the edit doesn't have read privs on every folder under the site directory you will get an error - we booked this with support, bug number is LST-5194

catownsley

we researched the issue you describe with Interwoven and this was their reponse:

"When a user is in the SitePublisher interface in edit mode and clicks on a component to edit the data/properties of that instance of the component it does not visit all other pages.
Perhaps that post from the Belgium user was referring to the "Get Latest Components" function when is used when you update a component and wish to update all instances of that component on all pages. In this case then all pages are examined but this is not a regular user doing this and this is when the default functionality of a component is changed not just the individual instance of a component on a page."

tanguyr

we researched the issue you describe with Interwoven and this was their reponse:

"When a user is in the SitePublisher interface in edit mode and clicks on a component to edit the data/properties of that instance of the component it does not visit all other pages.
Perhaps that post from the Belgium user was referring to the "Get Latest Components" function when is used when you update a component and wish to update all instances of that component on all pages. In this case then all pages are examined but this is not a regular user doing this and this is when the default functionality of a component is changed not just the individual instance of a component on a page."

Here below the instructions i sent them to recreate the issue (00774540 is the case number) (NOTE: i'm on Solaris, change paths and commands as appropriate for your environment):

1) create TeamSite groups "SUPERGROUP_00774540", "SUBGROUP_ONE_00774540" and "SUBGROUP_TWO_00774540"


iwgroup create SUPERGROUP_00774540
iwgroup create SUBGROUP_ONE_00774540
iwgroup create SUBGROUP_TWO_00774540

2) add "SUBGROUP_ONE_00774540" and "SUBGROUP_TWO_00774540" to "SUPERGROUP_00774540"


iwgroup add-included-groups SUPERGROUP_00774540 SUBGROUP_ONE_00774540 SUBGROUP_TWO_00774540

3) create a branch


iwmkbr /default/main BR00774540 'branch created for illustration of support case 00774540' INITIAL

4) create a workarea on this branch


iwmkwa /default/main/BR00774540 myWA "testing WA" INITIAL

5) assign this workarea to SUPERGROUP_00774540


iwaccess set-group /default/main/BR00774540/WORKAREA/myWA "SUPERGROUP_00774540"

6) create a site in this branch

These are my options:
Create From: None
Name*: BR00774540
Description: site for illustration of support case 00774540
Workarea: default: /main/BR00774540: myWA
Site Addresses: www.br00774540.com
Directory: br00774540

7) create two folders in this site: "FOLDER_ONE" and "FOLDER_TWO"


mkdir /default/main/BR00774540/WORKAREA/myWA/sites/BR00774540/FOLDER_ONE
mkdir /default/main/BR00774540/WORKAREA/myWA/sites/BR00774540/FOLDER_TWO

8) assign "FOLDER_ONE" to "SUBGROUP_ONE_00774540" and "FOLDER_TWO" to "SUBGROUP_TWO_00774540"

 
iwaccess set-group /default/main/BR00774540/WORKAREA/myWA/sites/BR00774540/FOLDER_ONE SUBGROUP_ONE_00774540
iwaccess set-group /default/main/BR00774540/WORKAREA/myWA/sites/BR00774540/FOLDER_TWO SUBGROUP_TWO_00774540

9) assign permissions to "FOLDER_ONE" and "FOLDER_TWO":


iwaccess set-unix-permission /default/main/BR00774540/WORKAREA/myWA/sites/BR00774540/FOLDER_ONE "rwxrwx---"
iwaccess set-unix-permission /default/main/BR00774540/WORKAREA/myWA/sites/BR00774540/FOLDER_TWO "rwxrwx---"

10) add a user into each of the two subgroups


iwgroup add-users SUBGROUP_ONE_00774540 wuserone
iwgroup add-users SUBGROUP_TWO_00774540 wusertwo

11) Grant a role to SUPERGROUP_00774540 that allows users to create and edit pages (we have a modified author role, as explained in Case 00774515)


iwaccess add-permission-entry /default/main/BR00774540 -group SUPERGROUP_00774540 -role author

12) Create a page

Log in with the test account that is a member of SUBGROUP_ONE_00774540
Navigate to FOLDER_ONE
create a page with a single component (any component will do)
double click on the component in design view, you will get the following window:
[screenshot of of edit component window with the "throbber" running]
and you will be stuck on this window until your browser times out (no error message is shown to the user).

If you look in servletd_out.log, you will see that the system threw an error:


2008-12-08 14:00:39,441 ERROR com.interwoven.livesite.common.business.BusinessException - level [-1]
Failed to get Page
com.interwoven.cssdk.access.CSAuthorizationException: //bewcmi01/default/main/BR00774540/WORKAREA/myWA/sites/BR00774540/FOLDER_TWO(Permission denied)

Note that i am not trying to create a page in FOLDER_TWO, but rather in FOLDER_ONE, so i don't see why the system is trying to access FOLDER_TWO

-- END INSTRUCTIONS --

Take it from me: the more .page files you have, the slower it gets for users to edit a component on any one page.

/t