Download the PHP package basilicom/pimcore-plugin-migration-toolkit without Composer

On this page you can find all versions of the php package basilicom/pimcore-plugin-migration-toolkit. 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?

Example code of basilicom/pimcore-plugin-migration-toolkit

Informations about the package pimcore-plugin-migration-toolkit

Pimcore Plugin Migration Toolkit

License: GPL v3

Version information

Bundle Version PHP Pimcore
^4.0 ^7.4 ^6.8
^4.0 ^8.0 ^10.0
^5.0 ^8.1 ^11.0

Why?

In every project we have migrations for the same things. Like Thumbnails, Classes, etc.

This plugin provides you with the migration helpers and further tools.

Usage Migration Helpers

For all migrations extend them from the class .

Migration Data

If a migration needs data it needs to be located in the following folder:

System Settings

System Settings can be set via config.yaml.

Example:

Language Settings

Language Settings are part of the System Settings and can be set via config.yaml.

Example:

Website Settings

Example: Up

Example: Down

Static Routes

Example: Up

Example: Down

User Roles

There is no way to remove the workspaces (dataobjects, documents or assets).

Even when deleting a user role in the pimcore backend the workspace data stays in the database.

Example: Up

Example: Down

Bundle / Extension

It is not possible to enable and install one bundle in one migration!

You need to make two migrations one with enable (disable) and one with install (uninstall) and then run it with the command Migrate in separate process. Otherwise it would not find the newly enabled bundle for the installation.

Example: Up

Example: Down

Class Definitions

Example: Up

Example: Down

Objectbricks

Example: Up

Example: Down

Fieldcollection

Example: Up

Example: Down

Classification Store

Classification Stores cannot be created with given ID.

But the ID is needed for the store field in a class.

Therefore using the name is needed.

But the name is not unique, so always use a unique name.

So be aware of that.

Example: Up

Example: Down

FieldDefinition Examples

Custom Layouts

Custom Layouts will get the id like "lower()".

Example: Up

Example: Down

Document (Page)

Example: Up

Example: Down

Object (Folder)

Example: Up

Example: Down

Asset (File)

Example: Up

Example: Down

Asset (Folder)

Example: Up

Example: Down

QuantityValue Unit

Example: Up

Example: Down

MySQL Helper

Example: Up

to load and execute a large sql file, do the following:

all sql files should be stored in the sql subdirectory within the migration's data directory:

Example: Down

please keep in mind the changed path in case of down migrations:

Translation Helper

to add the translations into the pimcore shared/admin translations. default domain is 'messages' (shared translations). but you can change it to any domain, also 'admin' (admin translations).

Example: Up

Example: Down

Commands

Migrate in separate process

Executes the same migrations as the command, but each one is run in a separate process, to prevent problems with PHP classes that changed during the runtime.

You're also able to migrate only specific bundles using the bundle prefix.

In some cases you might run migrations on large datasets. Therefor 120s of timeout per migration won't be enough. To adapt the timeout just pass the --timeout option. To unset the timeout at all, pass 0.

Import Translations

To import a csv file, like the exported shared translations from pimcore. To Pimcore shared translations. Or to Pimcore admin translations.

Ideas

All versions of pimcore-plugin-migration-toolkit with dependencies

PHP Build Version
Package Version
Requires php Version ^8.0
pimcore/pimcore Version ^10.0 || ^11.0
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 basilicom/pimcore-plugin-migration-toolkit contains the following files

Loading the files please wait ....