Download the PHP package muensmedia/partial-content-export without Composer

On this page you can find all versions of the php package muensmedia/partial-content-export. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package partial-content-export

Muensmedia.PartialContentExport

Export and import partial content instead of an entire site

With this package, you can export partial content - page trees and even individual content elements from one Neos instance into another. Think of it as a more flexible version of the built-in site export and import.

Muensmedia.PartialContentExport uses Neos' built-in Site Export / Import Service with an extended command line interface to make more of its capabilities available. If you have ever needed to manually copy content you prepared on a staging instance to your live instance, and exporting the entire site is not an option, than this is the package for you!

Features

Author

This package is developed by MÜNSMEDIA GmbH from Magdeburg.

Installation

Run this composer command to install the package

and then update composer: composer update

Usage

The command line interface is heavily inspired by the original site:export and site:import commands.

Export content

Example: Exporting a page or content element using its identifier.

This will export the node identified by 16e80b43-393b-42c6-8e1a-2f280640fbf0 into a file easter-campaign.xml within Muensmedia.Site/Resources/Private/Content directory. Additionally, a Resources directory containing all resources used in the exported content will be created.

Option Example Explanation
source 16e80b43-393b-42c6-8e1a-2f280640fbf0
or
/sites/site/node-fwrkqocrc01hp/node-v76vwg2cymq7u		 The page or content element to export. Can be either a node identifier or a node path.
package-key Muensmedia.Site Optional. The package to write the exported content xml into. If no package key is given, --filename must be an absolute path.
filename easter-campaign.xml Optional. The file name for the exported xml. Must be an absolute path if --package-key is not given.
site-name site Optional. The site to export from. Only needed if a node identifier is given in --source.
tidy 0 Optional. Exports formatted xml (to be more easily readable). Defaults to true
node-type-filter !Neos.Neos:Page,Neos.Neos:Text Optional. Allows limiting the export to certain node types. See the documentation for the original site:export command for more details.
detect-extensions 0 Optional. Checks installed composer packages to find compatible extension data that can be included in the export. Defaults to true
extension sitegeist/taxonomy Optional. Includes data from the given extension into the export. Can be set multiple times to include data from multiple extensions.

Import content

Example: Simply importing content to the same location in the content tree that it was exported from.

The original location of the exported content is stored in the xml file. If no other location is specified, the content will be imported at the same location. Content already existing at that location will be merged with the new one.

Option Example Explanation
package-key Muensmedia.Site Optional. The package to fetch the exported content xml from. If no package key is given, --filename must be an absolute path.
filename easter-campaign.xml Optional. The file name for the exported xml. Must be an absolute path if --package-key is not given.
target-path 16e80b43-393b-42c6-8e1a-2f280640fbf0
or
/sites/site/node-fwrkqocrc01hp/node-v76vwg2cymq7u		 Optional. The page or content item to import into (i.e. the parent node new content will be inserted into.) If the root node of the imported content already exists, it is also valid to specify its node identifier or path instead of its parent's.

Supported extensions

The Partial Content Exporter can import/export additional data from extensions that is not directly attached to the content repository node tree.

When exporting content, we will scan for compatible extensions and ask you if you want to include their data. You can disable the automatic scan using --detect-extensions 0. You can also directly specify the extensions you would like to export using --extension <package name>, for example --extension sitegeist/taxonomy.

When importing data, all included extension data is imported as well. If the required package is not installed in the target Neos instance, the import will fail with an error message. If the package is installed in a different version (no matter if it's higher or lower), a warning will be displayed but you have the option to import the data anyway.

Currently, only the package Sitegeist.Taxonomy is supported.

Extension Name Remarks
Sitegeist.Taxonomy sitegeist/taxonomy Includes all taxonomy data of all sites in your Neos instance (not just the taxonomies used in the given exported node subtree) into the export.

Current limitations

This package currently cannot be used to duplicate or move content (either to the same or a different site within the same installation). This means that you cannot re-import existing content to a different path to move it or create a duplicate. As doing so would cause various problems within your Neos site, we added some basic sanity checks to prevent this condition.

Contributions

If you find any issues with this package or have ideas for future developments, please create an issue. We will also gladly review and accept pull requests to improve this package.

License

See License

All versions of partial-content-export with dependencies

PHP Build Version
Package Version
Requires php Version >=7.4
neos/neos Version ^7.0 || ^8.0
ext-xmlwriter Version *
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package muensmedia/partial-content-export contains the following files

Loading the files please wait ....