Importing from Siteframe 3.x
The Admin menu on Beaumont provides a mechanism for importing content from a Siteframe 3.x database. This page contains information you should be aware of if you are planning on importing from a 3.x website.
When importing, you can selectively import Users, Folders, and Documents. These options are really provided for testing (unless, for example, you want to convert a public site to a private one). When you finally perform the live import, you should import everything at once. This is because the script internally maintains references so that old values (user_id, folder_id) can be mapped to the new values in the new site. If you perform these functions separately, this data is no longer available and folders cannot be assigned to the correct users.
Dates
The creation dates of all imported objects will reflect the time of the import, and not the time the objects were created on the original system.
Templates
Templates are not imported from 3.x. There is no compatibility between the templates used in 3.x and in Beaumont. Your new site will use one of Beaumont's defined template sets.
Users and Passwords
The following information is imported for each user:
- Nickname (becomes user name in Beaumont)
- E-mail address
- First name
- Last name
- Password
If your 3.x site uses MD5() passwords instead of the more common SHA1() passwords, then users' passwords will not be available on the new site. If this is the case, the users will need to reset their password and assign a new one. If you prefer, you can set crypt_function=md5 in siteframe.ini, but you should do this before creating the site, since any passwords you create earlier (for example, for the administrative user) will use that password mechanism.
Users are imported in user_id sequence; this way, they will maintain the same sequence as in the old site.
If the user has a Nickname defined, it is used for the Beaumont user name. If not, then the first and last names are concatenated, and that is used. If there is a duplicate user name error, a random number is appended to the user name. Administrators should encourage their users to select a Nickname before the import, since user names cannot be changed in Beaumont once assigned.
Administrators, if you really want to change someone's user name, you can update the table using MySQL directly (UPDATE bpt_user_info SET user_name='newname' WHERE user_id=VALUE).
Folders
- In Beaumont, all pages are required to have a folder; if a document in 3.x does not exist in a folder, then the import will assign the document to the most-recently-created folder owned by the user.
- If the user has no folders, then a new folder is created to hold any user documents.
- No specialized types of folders are retained; instead, all folders are imported as simple folders under Beaumont.
- Folders are imported in folder_id sequence.
- If the destination website allows hierarchical folders, the import will attempt to keep the hierarchy intact; however, since folders are imported in folder_id sequence, any folder that has a higher-numbered folder as its parent will not be imported correctly.
Pages
Pages ("documents" in 3.x) are imported with some restrictions.
- Documents with embedded template language was supported under 3.x but not under Beaumont; these will display as bare template code (e.g., "{user_id}") in the imported site.
- "Link" documents become "Links" in Beaumont (not a Page)
- Articles become Pages
- Images and Files become Pages with attached Files.
- Bugs are not imported.
- Documents are imported in doc_id sequence.
Comments
- If "Documents" are selected for import, it will attempt to import comments as well.
- Import of threaded comments is not supported (i.e., the "reply-to" chain will not be maintained).
- Comments are imported in chronological sequence to attempt to retain some semblance of order.
Ratings
- Because of changes in the rating structure between 3.x and Beaumont, ratings are not imported.
