You are here

Home » API reference » Node export 5.2

README.txt in Node export 5.2

Same filename and directory in other branches
  1. 8 README.txt
  2. 5 README.txt
  3. 6.3 README.txt
  4. 6 README.txt
  5. 6.2 README.txt
  6. 7.3 README.txt
README file for the export module for Drupal 5.x.

The export module allows users to export a node and then import it to another 
website. The authorship is set to the current user, the menu and url aliases 
are reset.

Users with the "export node" permission can utilize this functionality. A new
tab will appear on node pages with the word "export".

This module makes reasonable checks on access permissions.  A user cannot export 
a node unless they can use the input format of that node, and unless they have
permission to create new nodes of that type based on a call to node_access().

Settings can be accessed at admin/settings/export.  On this page you can
set whether the publishing options are reset when making a export of a node.  
This is set for each node type individually.

This module seems to work with common node types, however YMMV, especially with
nodes that have any sort of image or file  attachments.   In all cases, but 
especially if you are using a complex (CCK) or custom node type, you should 
evaluate this module on a test site with a copy of your database before 
attempting to use it on a live site.

To install this module, copy the folder with all the files to the
/sites/all/modules  OR /sites/default/modules directory of your Drupal 
installation and enable it at /admin/build/modules.  New permissions are 
available, but there are no changes to the database structure.

Security Warning: Users with the permission "use PHP to import nodes"
will be able to change nodes as they see fit before an import, as well as 
being able to execute PHP scripts on the server.  It is advisable not to
give this permission to a typical node author, only the administrator or
developer should use this feature.  You may even like to turn this module
off when it is no longer required.

Note: this module was originally built upon code from the node_clone module
maintained by Peter Wolanin (pwolanin@drupal) at 
http://drupal.org/project/node_clone which was derived from code posted by 
Steve Ringwood (nevets@drupal) at http://drupal.org/node/73381#comment-137714

File

README.txt
View source 
  1. 

  2. README file for the export module for Drupal 5.x.

  3. 

  4. The export module allows users to export a node and then import it to another 

  5. website. The authorship is set to the current user, the menu and url aliases 

  6. are reset.

  7. 

  8. Users with the "export node" permission can utilize this functionality. A new

  9. tab will appear on node pages with the word "export".

  10. 

  11. This module makes reasonable checks on access permissions.  A user cannot export 

  12. a node unless they can use the input format of that node, and unless they have

  13. permission to create new nodes of that type based on a call to node_access().

  14. 

  15. Settings can be accessed at admin/settings/export.  On this page you can

  16. set whether the publishing options are reset when making a export of a node.  

  17. This is set for each node type individually.

  18. 

  19. This module seems to work with common node types, however YMMV, especially with

  20. nodes that have any sort of image or file  attachments.   In all cases, but 

  21. especially if you are using a complex (CCK) or custom node type, you should 

  22. evaluate this module on a test site with a copy of your database before 

  23. attempting to use it on a live site.

  24. 

  25. To install this module, copy the folder with all the files to the

  26. /sites/all/modules  OR /sites/default/modules directory of your Drupal 

  27. installation and enable it at /admin/build/modules.  New permissions are 

  28. available, but there are no changes to the database structure.

  29. 

  30. Security Warning: Users with the permission "use PHP to import nodes"

  31. will be able to change nodes as they see fit before an import, as well as 

  32. being able to execute PHP scripts on the server.  It is advisable not to

  33. give this permission to a typical node author, only the administrator or

  34. developer should use this feature.  You may even like to turn this module

  35. off when it is no longer required.

  36. 

  37. Note: this module was originally built upon code from the node_clone module

  38. maintained by Peter Wolanin (pwolanin@drupal) at 

  39. http://drupal.org/project/node_clone which was derived from code posted by 

  40. Steve Ringwood (nevets@drupal) at http://drupal.org/node/73381#comment-137714