David Molineus
David Molineus
> This won't really be usable for us at least, as we often have multi-domain setups and thus also need different domains in our local development environments for example. You...
> I think the concept can work, not sure its easier to use than https://github.com/contao/contao/pull/4077, but it has the advantage of being configuration and not DB stuff. I honestly missed...
Would be great if the prev/next links could be added again. To solve the issue with multiple modules with pagination on a page, the feature could be optional in the...
Finde ich gut so. Bearbeitet man ein Inhaltselement, das bereits ein "Anzeigen ab" Datum hat, welches in der Vergangenheit liegt, müsste man dies dann jedes Mal mit anpassen.
> @dmolineus Gemeint ist wohl, das wenn ich 'ab' 03.01.2018 eintrage und 'bis' 28.02.2018, das sich das logisch nicht verträgt. Sorry, hatte ich anders verstanden. War wohl noch zu früh...
The difference is that for the regular use case (using content element in an article) the `getContentElement` method is triggered. Same for frontend modules in the regular page. https://github.com/contao/core/blob/9ca7b0d03b522622ce4bd2b00ad4fc34efbf28f6/system/modules/core/modules/ModuleArticle.php#L213 https://github.com/contao/core/blob/9ca7b0d03b522622ce4bd2b00ad4fc34efbf28f6/system/modules/core/pages/PageRegular.php#L133-L137...
> But in these cases, the getContentElement or getFrontendModule hooks are triggered. Then the getForm hook would be triggered additionally, wouldn't it? Sorry, missed that question up to now. No,...
> Moving the hook would be a BC break because it might not be expected that the hook is called for every form. Also it might not be expected that...
>> Would be fine with me. > > Could you update the PR accordingly then? That should fix the issue, right? Hm, had a look in the code again. My...
Here an screenshot to illustrate what I mean; 