Closed CMSworker closed 2 years ago
Hm, I could not reproduce. With only the following present in the composer.json
:
{
"name": "contao/managed-edition",
"type": "project",
"require": {
"contao/conflicts": "@dev",
"contao/core-bundle": "^4.12",
"contao/manager-bundle": "4.12.*",
"contao/news-bundle": "^4.12",
"inspiredminds/contao-sibling-navigation": "^1.3"
},
"extra": {
"contao-component-dir": "assets"
},
"scripts": {
"post-install-cmd": [
"@php vendor/bin/contao-setup"
],
"post-update-cmd": [
"@php vendor/bin/contao-setup"
]
}
}
the module News sibling navigation is available for selection in the back end.
Tried it with a new installation, same problem. Maybe it's related to the order of installing everything with Contao Manager? Here more detailed step-by-step:
It is also not visible when you create a test news archive and some test news entries.
The composer.json is looking like this after installation as described:
{
"type": "project",
"require": {
"contao/conflicts": "*@dev",
"contao/manager-bundle": "4.12.*",
"contao/news-bundle": "4.12.*",
"inspiredminds/contao-sibling-navigation": "^1.3"
},
"extra": {
"contao-component-dir": "assets"
},
"scripts": {
"post-install-cmd": [
"@php vendor/bin/contao-setup"
],
"post-update-cmd": [
"@php vendor/bin/contao-setup"
]
}
}
Please test dev-master
, may be that will fix it.
Yes that seems to fix it.
Before I also made a test with installing Contao full and than removing Calendar etc. and adding the siblings extension (1.3.1), this way the module is also not selectable in the dropdown list (probably not relevant anymore after the fix)
Thank you for the extension and your support!
Just repeated my first test (install Contao minimal, add news, than add siblings extension), but with siblings "dev-master". It works, the module is available in the module select list in backend.
Released as 1.3.2
.
Problem description: When the calendar extension is not installed you can't create a siblings module for news.
First test (base):
Second test:
Third test: