First, there is an important readme in ./convert/readme.txt:
Readme
Conversion
------------------------
Each module has its own convert directory
base/convert/modules/blog
base/convert/modules/block
Make sure to check each for a "readme" file.
None of the convert modules copy files from the previous version. It
is up to you to move images and documents to your new installation.
If there is a problem with your conversion, I recommend that you
do not continue with other mods until you can fix it.
If you have perform the conversion more than once, you must clear the
tables and drop the sequence tables. All the conversions assume you
are starting from scratch and you haven't enter ANY content.
Go slow, backup your data, and test heavily before going live.
When you are satified with the results, you may want to move the
convert directory elsewhere, remove read priviledges, or delete it
entirely.
Call convert
(remember: //your.domain/convert/)
Login is required before, or will be prompted.
Connecting to the database
The situation now is, you are logged on in your (destination/receiving) new site and the questions about the database connect are about the (source/sending) older site. For conversion, the actions will work with two databases. Regarding this condition, the answers should given carfully. If the database resides at the same server, localhost is the best host name. If not, the url of the database server is required.
If a non standard tcp port is used for the dbserver, that port has to be specified also. And, you have to know if the database server is remotly callable (is configured to receive requests from the net) - many dbserver react only as localhost for security reasons. If the dbserver is not reachable remotely, there is no chance for the convert utility.
Select data to convert
Regard, there is not a module to convert, but the modules data. The respective new module itself just runs at the new site.
1.4.1.Convert WebPages
If webPages (pagemaster pages) are to convert, the question follows:
eZine
