Can we have more details on this issue? Why do we need this change? What does it imply? Do themes and plugins developers need to know about this change?
Can we have more details on this issue? Why do we need this change? What does it imply? Do themes and plugins developers need to know about this change?
<!-- github-comment-id:407322701 -->
The comment_derivative_params template variable is used on the comments
page in the core default theme.
The commit from sep 2017 broke it (variable was set in the template using
{include})
The comment_derivative_params template variable is used on the comments
page in the core default theme.
The commit from sep 2017 broke it (variable was set in the template using
{include})
>
<!-- github-comment-id:407325331 -->
OK @modus75 but at the beginning, @flop25 what does this issue tries to fix? Is there a problem with the {include} directive in Smarty? (I have no idea, I'm trying to understand the origin of this issue)
OK @modus75 but at the beginning, @flop25 what does this issue tries to fix? Is there a problem with the `{include}` directive in Smarty? (I have no idea, I'm trying to understand the origin of this issue)
<!-- github-comment-id:407328726 -->
OK @modus75 https://github.com/modus75 but at the beginning, @flop25 https://github.com/flop25 what does this issue tries to fix? Is there a
problem with the {include} directive in Smarty? (I have no idea, I'm
trying to understand the origin of this issue)
Hi Thx modus
Plg: Check the comment of my commit
Le mar. 24 juil. 2018 à 15:40, Pierrick Le Gall <notifications@github.com>
a écrit :
> OK @modus75 <https://github.com/modus75> but at the beginning, @flop25
> <https://github.com/flop25> what does this issue tries to fix? Is there a
> problem with the {include} directive in Smarty? (I have no idea, I'm
> trying to understand the origin of this issue)
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/Piwigo/Piwigo/issues/603#issuecomment-407328726>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AAs-jSWuult9JumMg9mGsmRn-pi7-2Zmks5uJt2XgaJpZM4LiLS9>
> .
>
<!-- github-comment-id:407353976 -->
Thank you for your hard work Have a good summer
Le mar. 24 juil. 2018 à 18:47, Pierrick Le Gall <notifications@github.com>
a écrit :
> OK, I get it :-)
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/Piwigo/Piwigo/issues/603#issuecomment-407377668>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AAs-jYf-sKrW9COvzbduOmO1PCt-yuevks5uJwljgaJpZM4LiLS9>
> .
>
<!-- github-comment-id:407377908 -->
I close this issue, it will be available starting with Piwigo 2.10.0. This change is detailed on documentation for theme developpers https://piwigo.org/doc/doku.php?id=dev:changes_in_2.10
<!-- github-comment-id:506373070 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
so comment_list can be replaced via template extension or extensions
No HTML changes just tpl and php
I have assigned this to 2.10 since the tpl code changed a bit
awaiting CP
Can we have more details on this issue? Why do we need this change? What does it imply? Do themes and plugins developers need to know about this change?
The comment_derivative_params template variable is used on the comments
page in the core default theme.
The commit from sep 2017 broke it (variable was set in the template using
{include})
OK @modus75 but at the beginning, @flop25 what does this issue tries to fix? Is there a problem with the
{include}directive in Smarty? (I have no idea, I'm trying to understand the origin of this issue)Hi Thx modus
Plg: Check the comment of my commit
Le mar. 24 juil. 2018 à 15:40, Pierrick Le Gall notifications@github.com
a écrit :
OK, I get it :-)
Thank you for your hard work Have a good summer
Le mar. 24 juil. 2018 à 18:47, Pierrick Le Gall notifications@github.com
a écrit :
I close this issue, it will be available starting with Piwigo 2.10.0. This change is detailed on documentation for theme developpers https://piwigo.org/doc/doku.php?id=dev:changes_in_2.10