| 1 |
; $Id: README.txt,v 1.2 2008/08/09 14:45:33 alexb Exp $
|
| 2 |
|
| 3 |
PORT MODULE
|
| 4 |
|
| 5 |
A framework for importing and exporting structure (and content?) from a
|
| 6 |
Drupal application.
|
| 7 |
|
| 8 |
|
| 9 |
REQUIREMENTS
|
| 10 |
|
| 11 |
Drupal 5.x
|
| 12 |
|
| 13 |
|
| 14 |
USAGE
|
| 15 |
|
| 16 |
Install on source site and on target site (site you would like to export from
|
| 17 |
and site you would like to import to).
|
| 18 |
|
| 19 |
On source site, go to admin/build/export and export the elements of your
|
| 20 |
choice. Grab export data, go to admin/build/import on target site, paste export
|
| 21 |
data and hit submit.
|
| 22 |
|
| 23 |
Alternatively, choose 'Output as PHP functions' to export callable PHP function
|
| 24 |
definitions that you can copy and paste into your code. This can be useful
|
| 25 |
e. g. for building installer profiles.
|
| 26 |
|
| 27 |
|
| 28 |
SUPPORTED PORTS
|
| 29 |
|
| 30 |
* Menus
|
| 31 |
* Enabled modules
|
| 32 |
* Drupal variables (settings)
|
| 33 |
* User roles and permissions
|
| 34 |
* Content type definitions
|
| 35 |
* Image cache settings
|
| 36 |
* Node profile settings
|
| 37 |
* Spaces definitions
|
| 38 |
|
| 39 |
|
| 40 |
WRITE YOUR OWN PORTS = IMPORT/EXPORT FUNCTIONS
|
| 41 |
|
| 42 |
A. Define an export / import function pair where import() accepts the output of
|
| 43 |
export().
|
| 44 |
B. Expose them to port module through hook_ports(). See contrib/ or core/
|
| 45 |
directory in port module for examples.
|
| 46 |
|
| 47 |
|
| 48 |
DISCLAIMER
|
| 49 |
|
| 50 |
This is a proof of concept for a symmetrical import/export API.
|
| 51 |
|
| 52 |
Known problems
|
| 53 |
|
| 54 |
* Menu import/export doesn't update existing menus.
|
| 55 |
|
| 56 |
|
| 57 |
CREDITS
|
| 58 |
|
| 59 |
crud.inc is copied from the install_profile_api module.
|