http://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692018-07-25T16:04:38ZTYPO3 ForgeTYPO3 Core - Bug #85645: CMS Fluid has hidden dependency on CMS Backendhttp://forge.typo3.org/issues/85645?journal_id=3694032018-07-25T16:04:38ZClaus Dueclaus@phpmind.net
<ul><li><strong>Category</strong> set to <i>Fluid</i></li></ul> TYPO3 Core - Bug #85645: CMS Fluid has hidden dependency on CMS Backendhttp://forge.typo3.org/issues/85645?journal_id=3694392018-07-26T11:22:46ZChristian Kuhnlolli@schwarzbu.ch
<ul></ul><p>Well, I think we added only "hard" dependencies until now to composer.json in our core extensions. For instance, if your extensions primary job is a backend module for editors, but it also comes with a tiny frontend plugin, we until now only set cms-backend as dependency, cms-frontend could be a suggest then.</p>
<p>This is similar for typo3/cms-fluid: Only a couple of VH's really need cms-backend, "most" of cms-fluid works well in practice if cms-backend is not there. However, since cms-backend is a hard requirement for a full typo3 anyway, it does not matter much. Thus, I'd be fine to add cms-backend to the require section of composer.json in cms-fluid. And I'd guess same goes for cms-frontend (needs check). It simply does not make much sense to use cms-fluid if not at least one of the two is loaded. In a project that does not need cms-frontend and cms-backend, one would probably go with standalone typo3fluid/fluid only in the first place and not with the typo3 cms part on top, even if cms-core is loaded, which then would act as a library only. And in fact cms-core is evolving to a library more and more since most controllers are in cms-frontend and especially in cms-backend and we're also slowly trying to push this further.</p>
<p>The only thing we could argue is whether we set cms-backend and maybe cms-frontend as suggest instead of require. That could be an advantage for frontend nodes that don't install cms-backend, or backend nodes that don't install cms-frontend. However, I'm not sure if the system is far enough already to do this in a good way already. But if we set require to cms-backend right now, it may later be turned into a suggest only for that reason.</p> TYPO3 Core - Bug #85645: CMS Fluid has hidden dependency on CMS Backendhttp://forge.typo3.org/issues/85645?journal_id=3694582018-07-26T21:05:26ZGeorg Ringer
<ul></ul><p>IMO the VH in ext:fluid which are BE related must be moved to EXT:backend and everything is fine.</p> TYPO3 Core - Bug #85645: CMS Fluid has hidden dependency on CMS Backendhttp://forge.typo3.org/issues/85645?journal_id=3696532018-07-30T09:11:20ZMathias Brodalambrodala@pagemachine.de
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-5 priority-4 priority-default closed" href="/issues/85619">Task #85619</a>: Streamline package interdependencies</i> added</li></ul> TYPO3 Core - Bug #85645: CMS Fluid has hidden dependency on CMS Backendhttp://forge.typo3.org/issues/85645?journal_id=4153632020-02-15T16:08:11ZGeorg Ringer
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Accepted</i></li></ul> TYPO3 Core - Bug #85645: CMS Fluid has hidden dependency on CMS Backendhttp://forge.typo3.org/issues/85645?journal_id=4194622020-03-18T14:27:59ZGeorg Ringer
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-5 priority-4 priority-default closed" href="/issues/89519">Task #89519</a>: Add missing dependencies to composer.json of extbase</i> added</li></ul> TYPO3 Core - Bug #85645: CMS Fluid has hidden dependency on CMS Backendhttp://forge.typo3.org/issues/85645?journal_id=4194642020-03-18T14:28:30ZGeorg Ringer
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-5 priority-4 priority-default closed" href="/issues/87508">Bug #87508</a>: composer.json doesn't list all (soft-)mandatory PHP extensions</i> added</li></ul> TYPO3 Core - Bug #85645: CMS Fluid has hidden dependency on CMS Backendhttp://forge.typo3.org/issues/85645?journal_id=4717662022-07-20T12:25:44ZGeorg Ringer
<ul><li><strong>Status</strong> changed from <i>Accepted</i> to <i>Closed</i></li></ul><p>even though this issue is valid I am closing this issue after talking to lolli. just moving the VH itself around doesn't help much as there are far more dependencies inside the VHs to other extensions like extbase.</p>