KimP

@felix: I haven't used twig in this project as much as I’d liked to do. For now we only implemented it for the parts that needed to be rendered both client and server side. The overview of shows is rendered server-side (we want the overview page to be indexable by search engines), but to generate the shopping cart, we needed to have the same chunk of code generated in javascipt (the data for this is fetched cross-domain from our backend system). So for that we used twigjs. I wanted to replace all php-templates with twig-templates so we could extend templates and so, but didn’t had the time Same goes for the data providers. They are only used for the twig templates and there for not used that much. I hope to refactor some of this to make proper use of both modules. When we do, we’ll post it here somewhere!

Very nice! Thx. Should have searched better before asking

Hi, Topic is a bit misleading but didn’t know how to describe it in 1 sentence. Say i have a page which represents an event. This event is hosted at different moments in time. For every time it’s hosted, i’d like te have a new page, with the event itself as parent. EventTime 1 Time 2 Time 3 Etc. This would generate urls like /event/time_1, /event/time_2 and so on. Because most content on the page is the same (can differ a bit but not much), google probably sees it as duplicate content, so i set canonical tags in the header of every subpage witch point to /event. So far so good. But now, when you go to the /event page i’d like to show the content of the next upcoming time (say, Time 2). I could solve this with a redirect to /event/time_2, but the seo guys prefer i keep at /event. Any suggestions on how to achieve this? I overriding $this->page and $page as first lines in my template doesn’t feel like the right way Grz, Kim

Hi Adrian, Thx, and thx for the quick reply. I've created an issue on github for this. Have a few minutes to check i out now, so i hope i find something. If so, i'll submit a pull request. Gr, Kim

Hi, As said in the title, when a field is set to be locked or hidden it'll be empty after saving the page. This only happens when you set te visibility of the field via the template. When setting te visibility on the field itself, it works just fine. Only happens in 2.5, not in 2.4. When i've time i'll try to fix it. In the meanwhile, if anyone has the solution for this, i'm happy to hear it Kind regards, Kim