[BUGFIX] Use compatible
flowpack/behat dependency to fix installation¶
Current composer installation breaks due to incompatible dependencies
caused by a dependency on
now only supports Flow 3.x
- Commit: 593c703
[TASK] Revert composer manifest to dev versions¶
- Commit: 3832366
[TASK] Update references in documentation¶
- Commit: 53b0f72
[BUGFIX] Flush content cache of source collection when moving content¶
Fixes a node being duplicated when cutting from one content collection and pasting into another one. This happens since the content cache for the previous collection isn’t cleared when the node is moved.
- Commit: 66cfaa1
contentElementWrapping processor is executed last¶
In some cases where integrators add their own
@process rules to
contentElementWrapping process is not executed last
potentially causing the wrapping to be added to a wrong wrapper element.
This is solved by setting the position of the processor to:
@position = 'end 999999999'
- Commit: f92f50d
[BUGFIX] Reload structure tree after adding new nodes¶
When nodes were changed in the structure tree the tree would only reflect the current page after having navigated to another document for the second time.
This was caused by a fix added with https://review.typo3.org/26158 and which is no longer needed, since the observer on pageNodePath is not triggered if the same page is reloaded.
- Commit: cc88b4d
[TASK] Clean up Release Notes and ChangeLogs¶
The 1.0 release notes are merely links to the Changelogs. The >=1.1 release notes could be useful even when they are for older versions of the docs. So, this archives <1.0 and keeps >1.0.
This also updates the ChangeLogs so that they don’t loose all of the formatting fixes that were added in later branches. Now that this is the only copy of those ChangeLogs, they need to be as usable as possible.
- Commit: 65a449c
[TASK] Remove ChangeLogs for other branches from documentation¶
Having the ChangeLogs of all previous branches only balloons the documentation without a real gain.
- Commit: 24ceaba
[BUGFIX] Return backend user even if security context is uninitialized¶
If the security context has not yet been initialized the user service would return NULL instead of initializing the security context and then check if there was a backend user. Instead of only returning it if it’s already initialized, it checks if it’s possible to initialize or not.
- Commit: 3f15433
[TASK] Move Doc Config from DocTools package¶
This moves the doc configuration from the DocTools package to the Neos package so that it can be changed per branch. To see the DocTools change, refer to I9b56df70f6b5140b41b41893a8fb6f516b8f1843
- Commit: a76c4e3
[TASK] Make PHP the default language for code blocks¶
The documentation now uses PHP as default language for code blocks, so that even when using just two colons to start a code-block it is highlighted.
- Commit: 4477fed
[TASK] Add support for sphinx-autobuild¶
This adds support for sphinx-autobuild, which watches the Documentation directory and automatically re-renders docs on change. This allows for a livepreview while editing the docs.
To use it, install `sphinx-autobuild`_:
pip install sphinx-autobuild
To use livepreview just run
make livehtml instead of
Then, visit http://127.0.0.1:8000 to see the livereload version of the
docs. Note, this builds the docs in
_build/livehtml instead of
- Commit: 9b422c1
[TASK] Make PHP highlighting work for snippets¶
This adds the “official” hack to turn on startinline for all php codeblocks whether they’re a snippet or a full file.
Sphinx and docutils don’t support setting the startinline option for pygments. That means that snippets of PHP code that don’t have “<?php ?>” don’t get highlighted. The hack was documented here: http://mbless.de/blog/2015/03/02/php-syntax-highlighting-in-sphinx.html https://github.com/fabpot/sphinx-php
- Commit: cf34288
[TASK] BeforeNodeMove & AfterNodeMove signals¶
Backports two signals for node moving needed to solve a bug with content cache flushing.
- Commit: ca5d770
[BUGFIX] UnpublishedNodes includes root node in PublishingService¶
The getUnpublishedNodes method in the PublishingService shouldn’t include the root node, since it’s not publishable.
Besides that the getUnpublishedNodes() method now returns 0 if it’s called for the live workspace as this workspace will never have unpublished nodes.
- Commit: 5d8d7bf