Developed with love by KnpLabs Hire us for your project!


by kaliop-uk

This bundle makes it easy to handle eZPlatform / eZPublish5 content upgrades/migrations

Kaliop eZ-Migration Bundle

This bundle makes it easy to programmatically deploy changes to eZPlatform / eZPublish 5 database structure and contents.

It is inspired by the DoctrineMigrationsBundle

You can think of it as the grandson of the legacy ezxmlinstaller extension.


  • PHP 5.6 or later.

  • eZPlatform or eZPublish Enterprise 5.4 or eZPublish Community 2014.11 or later.


In either require or require-dev at the end of the bundle list in the composer.json file add:

"kaliop/ezmigrationbundle": "^5.0"

Save it and run

composer update --dev kaliop/ezmigrationbundle

This will install the bundle and all its dependencies.

Please make sure that you have the bundle registered in the kernel as well. Check app/appKernel.php (for eZPublish ezpublish/EzPublishKernel.php)

The registerBundles method should look similar to:

public function registerBundles()
    $bundles = array(
        ... more stuff here ...
        new \Kaliop\eZMigrationBundle\EzMigrationBundle()

Checking that the bundle is installed correctly

If you run php bin/console (for eZPublish php ezpublish/console) you should see the following new commands in the list:


This indicates that the bundle has been installed and registered correctly.

Note: the command kaliop:migration:update is kept around for compatibility, and will be removed in future versions.

Updating the bundle

To get the latest version, you can update the bundle to the latest available version by using composer

composer update kaliop/ezmigrationbundle

Upgrading from version 4.x to version 5

  • Make sure you read carefully all the BC notes in the release notes

  • Nothing else is required, unless you have one of the following:

    • code which extends the migration bundle code/apis
    • old migrations, that you want to play again with the updated bundle, which have text values which include the string '[reference:xxx]' where 'xxx' stands for any sequence of characters

    For both cases, the fix is to apply manual changes to your code / migrations.

Upgrading from version 3.x to version 4

  • Make sure you read carefully all the BC notes in the release notes

  • Nothing else is required, unless you have one of the following:

    • code which extends the migration bundle code/apis
    • code which depends on parsing the output of the migrate command and relies on its exact format

    For both cases, the fix is to apply manual changes to your code.

Upgrading from version 2.x to version 3

  • Make sure you read carefully all the BC notes in the release notes

  • Nothing else is required, unless you have one of the following:

    • migrations definitions generated using extension versions 1.x or 2.x, yet to be applied
    • code which extends the migration bundle code/apis

    For both cases, the fix is to apply manual changes to your code/migrations.

Upgrading from version 1.x to version 2

Please read the dedicated documentation page

Getting started

All commands accept the standard Symfony/eZPublish 5 options, although some of them might not have any effect on the
command's execution.

Generating a new, empty migration definition file

The bundle provides a command to easily generate a new blank migration definition file, stored in a specific bundle.

For example:

php ezpublish/console kaliop:migration:generate --format=yml MyProjectBundle

The above command will place a new yml skeleton file in the MigrationVersions directory of the MyProjectBundle bundle.

If the directory does not exist then the command will create it for you, as long as the bundle does exist and is registered.
If the command is successful it will create a new yml file named with the following pattern: YYYYMMDDHHMMSS_placeholder.yml.
You are encouraged to rename the file and change the placeholder part to something more meaningful, but please keep
the timestamp part and underscore, as well as the extension.

(the contents of the skeleton Yaml file are stored as twig template)

Listing all migrations and their status

To see all the migrations definitions available in the system and whether they have been applied or not simply run the
status command in your eZPublish 5 root directory:

php ezpublish/console kaliop:migration:status

The list of migrations which have been already applied is stored in the database, in a table named kaliop_migrations.
The bundle will automatically create the table if needed.
In case you need to use a different name for that table, you can change the Symfony parameter ez_migration_bundle.table_name.

Applying migrations

To apply all available migrations run the migrate command in your eZPublish 5 root directory:

 php ezpublish/console kaliop:migration:migrate

NB: if you just executed the above command and got an error message because the migration definition file that you had
just generated is invalid, do not worry - that is by design. Head on to the next paragraph...

NB: migrations execute by the default as the admin user with ID 14. Without this user account in the database, you must
specify the use of another admin account by passing the -a flag.

Applying a single migration file

To apply a single migration run the migrate command passing it the path to its definition, as follows:

php ezpublish/console kaliop:migration:migrate --path=src/MyNamespace/MyBundle/MigrationVersions/20160803193400_a_migration.yml

NB: you can specify as well a folder with the --path flag, in which case all the migration definitions contained in that
folder will be executed.

Editing migration files

So far so good, but what kind of actions can be actually done using a migration?

Each migration definition consists of a series of steps, where each step defines an action.

A simple example of a migration to create a 'folder' content is:

    mode: create
    type: content
    content_type: folder
    parent_location: 2
        name: hello world

In a Yaml migration, you can define the following types of actions:
- creation, update and deletion of Contents
- creation, update and deletion of ContentTypes
- creation, update and deletion of ContentTypeGroups
- deletion of Content Versions
- creation and deletion of Languages
- creation, update and deletion of Locations
- creation, update and deletion of ObjectStates
- creation, update and deletion of ObjectStateGroups
- creation, update and deletion of Roles
- creation, update and deletion of Sections
- creation and deletion of Tags (from the Netgen Tags Bundle)
- creation, update and deletion of Users
- creation, update and deletion of UserGroups
- purging and recovering Contents from the Trash
- creation, appending, copy, renaming and deletion of files
- execution of SQL queries
- execution of command-line scripts
- execution of methods of symfony services
- execution of http calls
- sending of email
- canceling, snoozing or suspending the migration itself

The docs describing all supported parameters are in the DSL Language description

Custom migrations

For more specific needs, you can also use 2 other types of migrations:
- SQL migrations
- PHP migrations

SQL migrations

Example command to generate an SQL migration definition:

 php ezpublish/console kaliop:migration:generate MyBundle create-new-table --format=sql

This will create the following file, which you are free to edit:


NB if you rename the sql file, keep in mind that the type of database to which it is supposed to apply is the part
of the filename between the first and second underscore characters.
If you later try to execute that migration on an eZPublish installation running on, say, PostgreSQL, the migration
will fail. You are of course free to create a specific SQL migration for a different database type.

The Migration bundle itself imposes no limitations on the type of databases supported, but as it is based on the
Doctrine DBAL, it will only work on the databases that Doctrine supports.

NB if the SQL command (or commands) in your migration is too long, the migration might fail or be only partially
applied, in some cases (such as when using MySQL) without even reporting an error. If you need to execute multiple, long
queries, you are better off splitting them, either in many .sql migrations, or in a single .yml migration with sql steps.

PHP migrations

If the type of manipulation that you need to do is too complex for either YML or SQL, you can use a php class as
migration definition. To generate a PHP migration definition, execute:

 php ezpublish/console kaliop:migration:generate MyBundle AMigrationClass --format=php

This will create the following file, which you are free to edit:


As you can see in the generated definition, the php class to be used for a migration needs to implement a specific
interface. The Symfony DIC container is passed to the migration class so that it can access from it all the services,
parameters and other thing that it needs.

For a more detailed example of a migration definition done in PHP, look in the MigrationVersions folder of this very bundle.

NB if you rename the php file, keep in mind that the filename and the name of the class it contains are tied - the
standard autoloading mechanism of the application does not apply when loading the migration definition. This is also
the reason why the php classes used as migrations should not use namespaces.

NB since version 4.5, it is also possible to run any method of any existing Symfony service just by declaring it as
migration step in a yaml migration. See the relevant DSL for details.

Re-executing failed migrations

The easiest way to re-execute a migration in 'failed' status, is to remove it from the migrations table:

php ezpublish/console kaliop:migration:migration migration_name --delete

After removing the information about the migration form the migrations table, running the migrate command will execute it again.

Usage of transactions / rolling back changes

By default the bundle runs each migration in a database transaction.
This means that if a step fails, all the previous steps get rolled back, and the database is left in its original state.
This is a safety feature built in by design;
* if you prefer the migration steps to be executed in separate transactions the easiest way is to create a separate
migration file for each step
* you can use the command-line flag -u to disable usage of transactions by the migrate command

Note also that by default the migrate command stops on the 1st failed migration, but it can be executed with a flag
to allow it to continue and execute all available migrations even in case of failures.

As for rolling back changes: given the nature of the eZPublish API, rolling back changes to Content is not an easy feat.
As such, the bundle does not provide built-in support for rolling back the database to the version it had before
applying a given migration. We recommend always taking a database snapshot before applying migrations, and use it in
case you need to roll back your changes. Another approach consists in writing a separate migration to undo the changes.

Customizing the migration logic via Event Listeners

An easy way to hook up custom logic to the execution of migrations - without having to implement your own customized
action executors - is to use Event Listeners.

Two events are fired for each step during execution of migrations:

* ez_migration.before_execution => listeners receive a BeforeStepExecutionEvent event instance
* ez_migration.step_executed => listeners receive a StepExecutedEvent event instance

An event is fired only in case a migration fails because a step throws a specific migration abort exception:

* ez_migration.migration_aborted => listeners receive a MigrationAbortedEvent event instance

An event is fired when a migration is being generated using the kaliop:migration:generate command, allowing to alter
the data that will be serialized as migration steps:

* ez_migration.migration_generated => listeners receive a MigrationGeneratedEvent event instance

In order to act on those events, you will need to declare tagged services, such as for ex:

    class: my\helper\StepExecutedListener
        - { name: kernel.event_listener, event: ez_migration.step_executed, method: onStepExecuted }

and the corresponding php class:

use Kaliop\eZMigrationBundle\API\Event\StepExecutedEvent;

class StepExecutedListener
    public function onStepExecuted(StepExecutedEvent $event)
        // do something...

Known Issues and limitations

  • unlike the Doctrine Migrations Bundle, this bundle does not support rollback of changes. Read above for the reason.

  • if you are using the Doctrine Migrations Bundle to manage your schema, you will get spurious sql created to handle the
    database tables belonging to Kaliop Migrations Bundle.
    For the moment, the best work around is to use the filter-expression parameter on the command-line when running
    doctrine:migrations:diff and friends, with a value of kaliop_migrations_*

  • if you get fatal errors when running a migration stating that a node or object has not been found, it is most likely
    related to how the dual-kernel works in eZPublish, and the fact that the legacy and Symfony kernels use a separate
    connection to the database. Since the migration bundle by default wraps all database changes for a migration in a
    database transaction, when the Slots are fired which allow the legacy kernel to clear its caches, the legacy kernel
    cannot see the database changes applied by the Symfony kernel, and, depending on the specific Slot in use, might
    fail with a fatal error.
    The simplest workaround is to disable usage of transactions by passing the -u flag to the migrate command.

  • similar symptoms can manifest themselves when you are using the Solr Search Engine Bundle.
    In this case the problem is compounded the fact that, even if a node or object is sent to Solr from within a database
    transaction, the Solr search index might be configured to only commit received data within a short time delay.
    A known workaround involve:

    • separate your migration steps into separate migrations
    • running the migrations each in its own transaction (and process) by using the -p flag to the migrate command
    • adding sleep migration steps to migrations 2 .. N
    • and/or configuring Solr to always commit changes to the index immediately (eg. disable commitwithin)
  • when using SOLR in multi-core configurations and getting a java.lang.NegativeArraySizeException error, you will have
    to set a lower value than the default 2147483647 for parameter ez_migration_bundle.query_limit

  • if you get fatal errors without any error message when running a migration which involves a lot of content changes,
    such as f.e. altering a contentType with many contents, it might be that you are running out of memory for your
    php process.
    Known workarounds involve:

    • increase the maximum amount of memory allowed for the php script by running it with option '-d memory_limit=-1'
    • execute the migration command using a Symfony environment which has reduced logging and kernel debug disabled: the default configuration for the dev environment is known to leak memory
  • if you get fatal errors with the message 'You cannot create a service ("request") of an inactive scope ("request")',
    take a look at the following issue for a possible explanation and ideas for workarounds:

  • if you are using eZPublish versions prior to 2015.9, you will not be able to create/update Role definitions that
    contain policies with limitations for custom modules/functions. The known workaround is to take over the
    RoleService and alter its constructor to inject into it the desired limitations

  • when updating a Role, you have to specify in the migration all the policies for it. Any existing policies that are not
    in the yml file will be removed.
    To make it easy to create a migration for updating a role, please use the migration:generate command using the --type=role flag

  • take care when creating content types: the eZPublish API, used internally by the migration bundle, will let you use dash
    characters in the content type identifiers, even if the resulting content types will then be unusable, eg.

    Example of an invalid definition:

        type: ezstring
        name: Topbar-hover-color
        identifier: topbar-hover-color

Frequently asked questions

How can I update a specific content which has a different Id on dev, test and prod environments?

A: use the 'reference/set' migration step to define a reference for the desired content Id, and use a Symfony parameter
to store a different value for each Symfony environment. For example:

    type: reference
    mode: set
    identifier: content_id_ref
    value: ''

    type: content
    mode: update
        content_id: "reference:content_id_ref"
    etc: ...

How to update an existing Role to change its policies?

When using a migration to update a Role, you must define ALL its policies. Any not defined will be removed.
The safest and simplest way to make sure that you do not forget any of the existing policies is to first generate an
update migration that has the complete specification of the role as it currently is defined, and then edit manually.

Example command to create such a migration:

php ezpublish/console kaliop:migration:generate --type=role --mode=update --match-type=identifier --match-value=Anonymous bundleName

When dumping a Content into a yml migration via the generate command, the list of attributes is empty

A: this is most likely due to using a bad language configuration

Extending the bundle

Supporting custom migrations

The bundle has been designed to be easily extended in many ways, such as:
* adding support for custom/complex field-types
* adding support for completely new actions in the Yml definitions
* adding support for a new file format for storing migration definitions
* adding support for a new resolver for the custom references in the migration definitions
* taking over the way that the migrations definitions are loaded from the filesystem or stored in the database
* etc...

Following Symfony best practices, for the first 4 options in the list above all you need to do is to create a service
and give it an appropriate tag (the class implementing service should of course implement an appropriate interface).

To find out the names of the tags that you need to implement, as well as for all the other services which you can
override, take a look at the services.yml file.

Running tests

The bundle uses PHPUnit to run functional tests.

Running tests in a working eZPublish / eZPlatform installation

To run the tests:

export KERNEL_DIR=ezpublish (or 'app' for ezplatform setups)
export SYMFONY_ENV=behat (or whatever your environment is)

bin/phpunit --stderr -c vendor/kaliop/ezmigrationbundle/phpunit.xml.dist

NB the tests do not mock interaction with the database, but create/modify/delete many types of data in it.
As such, there are good chances that running tests will leave stale/broken data.
It is recommended to run the tests suite using a dedicated eZPublish installation or at least a dedicated database.

Setting up a dedicated test environment for the bundle

A safer choice to run the tests of the bundle is to set up a dedicated environment, similar to the one used when the test
suite is run on Travis.
The advantages are multiple: on one hand you can start with any version of eZPublish you want; on the other you will
be more confident that the tests will still pass on Travis.
The disadvantages are that you will need Docker and Docker-compose, and that the environment you will use will look
quite unlike a standard eZPublish setup!

Steps to set up a dedicated test environment and run the tests in it:

# if you have a github auth token, it is a good idea to copy it now to Tests/docker/data/.composer/auth.json
./Tests/ build
./Tests/ runtests
./Tests/ stop

In case you want to run manual commands, eg. the symfony console:

./Tests/ exec php vendor/ezsystems/ezplatform/bin/console cache:clear

Note: this will take some time the 1st time your run it, but it will be quicker on subsequent runs.
Note: make sure to have enough disk space available.
Note: the tests in the Docker container run against the version of eZPlatform kernel specified in the file .env.
If you want to test against another version, feel free to modify it and rebuild the containers.

Latest Stable Version
Total Downloads

Build Status
Scrutinizer Code Quality
Code Coverage

Version 2, June 1991

Copyright (C) 1989, 1991 Free Software Foundation, Inc., <>
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.


The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Lesser General Public License instead.) You can apply it to
your programs, too.

When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their

We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.

Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.

Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.

The precise terms and conditions for copying, distribution and
modification follow.


0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.

1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.

You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:

a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.

b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.

c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.

In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.

3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:

a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,

b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,

c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.

If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.

4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.

5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.

6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.

7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other

It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.

This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.

8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.

9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.

Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software

10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.




  • WIP testing docker improvements
    By gggeek, 6 months ago
  • WIP testing docker stack improvements
    By gggeek, 6 months ago
  • improve
    By gggeek, 6 months ago
  • improve
    By gggeek, 6 months ago
  • WIP better compat with solr-search-engine-bundle
    By gggeek, 6 months ago
  • wip docker stack for testing
    By gggeek, 6 months ago
  • docs
    By gggeek, 6 months ago
  • travis
    By gggeek, 6 months ago
  • travis
    By gggeek, 6 months ago
  • bump min versions of packages in travis matrix to speed up composer
    By gggeek, 6 months ago
  • try a travis fix
    By gggeek, 6 months ago
  • improve docker env 4 tests
    By gggeek, 6 months ago
  • Merge branch 'master' of
    By gggeek, 6 months ago
  • make travis_wait wait longer for setup
    By gggeek, 6 months ago
  • revamp test setup to bring it in line with the version used in the v3 branch
    By gggeek, 6 months ago
  • Merge pull request #231 from Ternovtsiiendry/master
    By web-flow, 6 months ago
  • docs
    By gggeek, 6 months ago
  • Fix issue #232
    By gggeek, 6 months ago
  • Fix compiling error
    By web-flow, 8 months ago
  • fix issue #216, improve tests
    By gggeek, 1 year ago
  • readme
    By gggeek, 1 year ago
  • add unassign to role updates; fix for query limit
    By gggeek, 1 year ago
  • test fixes; allow usage of solr multicore
    By gggeek, 1 year ago
  • test fixes
    By gggeek, 1 year ago
  • test fixes
    By gggeek, 1 year ago
  • more testing, fixes
    By gggeek, 1 year ago
  • more testing
    By gggeek, 1 year ago
  • more detailed error message if we can not find the desired user to be logged in into repo; fixup
    By gggeek, 1 year ago
  • more detailed error message if we can not find the desired user to be logged in into repo
    By gggeek, 1 year ago
  • improve wording for password usage in migrations
    By gggeek, 1 year ago