Gaetano Giunta
Gaetano Giunta
By default updateserachindex solr output is all mixed up and duplicated when run via ezpublish/console. This PR fixes that
- fixes script not working with centos 6.3 - adds support for /etc/sysconfig - more checks for when path to ez is incorrect - gives better output msg when the...
It would be a sensible strategy to start warning end users which keep using elements that will be dropped at some point in time in the future... We probably have...
It is currently possible to achieve an `upsert` (insert-or-update) via a 3-step process: - step 1: content/load, match via ..., set reference to count - step 2: content/create, if count...
This can be useful when handling text of unknown source and some weird recursive cases (eg. in migration generation)
A bit of docs could go a long way
Common scenario: - add a new Doctrine ORM entity via code + annotations - want to have the sql for creating the table added to your migrations It is not...
Add support for ETL scenarios: dump a full ez installation, transform it, reimport it somewhere else
In short: we could do a full ezp db dump, doing a breadth-first descent and making sure that user accounts are dumped 1st and contents 2nd. What would be missing...
This is similar to issue #57 , but it caters to a different usecase: content is edited on server A, and transferred to server B for display. This is generic...