I redesigned the favicons to take advantage of tiki's theme management. So anywhere a theme specific kind of file can be overridden, the favicons can be as well. To tell you the truth, I'm not sure where all those places are. I know there is a lot of them.
- .tiki.org isn't a very good example, as they all use the default favicons! The tiki ones. From a designers perspective, they currently throw custom .tpl, CSS and images into the themes directory. Why not favicons? That is where everything else is put.
If we're going to do something other than that the documentation needs to reflect that. So instructions on how to change the favicons need to be tested and re-written etc.
I am a +1 for Bernard's suggestion. Even when/if this directory structure revamp happens, and there is another option for placement, it does not change that they can also be theme specific. And currently that is how we're managing them, so it makes all the sense for right now to do that. Additionally, all it means is making some empty directories. That's less work than this conversation thread.
> On Oct 11, 2018, at 7:37 AM, Gary Cunningham-Lee <firstname.lastname@example.org> wrote:
> As I understand it, the purpose of the _custom directory is just as you say, to avoid spreading website content over several directories. So instead of mixing Tiki package files and uploaded files such as in the themes directory, everything uploaded for a site would go in the _custom directory. Then just one directory needs to be archived or copied and it only contains custom content, not a mix of custom and package files. I understand that in this scenario, custom themes, fonts, etc. wouldn't be put in the themes directory any more; they'd go to _custom. See https://dev.tiki.org/File%20and%20directory%20structure%20revamp . I don't know what the timeline for this revamp is.
> About your original question, it doesn't seem to me that there's necessarily a relationship between favicons and themes except that they can be user-uploaded. At tiki.org for example, several themes are used but only one favicon (or one set of favicons) is used. The favicon doesn't change as the theme changes, although this could be the case. So I think it would be good to handle favicons like icons or custom CSS and either put them in one location so they're used no matter what theme is used, or put them in a theme's directory so they're used only with that theme. Maybe that's how they work now but I haven't tested it.
> — Gary
> This was discussed at TikiFest Japan in October 2017
> On 10/11/2018 6:57 PM, Bsfez Tiki wrote:
>> Thanks Gary for your comment.
>> (_custom directory https://doc.tiki.org/Path-structure)
>> Short answer:
>> The actual "Favicons" feature work that way and is using themes/themeName/favicons.
>> I'm not suggesting any change of the existing way things work.
>> I propose we avoid an extra step (creating the folder) by having one ready to be used (like we have fonts, icons, images, etc).
>>> As far as putting it in themes/themeName, favicons aren't particularly related to themes, are they?
>> I think favicons and themes are related from the user / customer point of view.
>> It will be for the same reason and generally by the same person (graphic) that both, themes and favicons will be created, added or modified.
>> If we can have fonts and icons there is no reason favicons would go somewhere else.
>> Practically, I don't see any interest we would have to make website designers to use several folders spreads over a Tiki.
>> I see very convenient to give ftp access to a single folder (the theme folder) to a external people or team (designers).
>>> On 11 Oct 2018, at 12:06 , Gary Cunningham-Lee <email@example.com <mailto:firstname.lastname@example.org>> wrote:
>>> The _custom directory was added to contain user content like favicons and even themes, I think. The idea is to have everything that's added for a Tiki instance all in one directory for easy portability, etc. I haven't heard much about this lately, though.
>>> As far as putting it in themes/themeName, favicons aren't particularly related to themes, are they? Or are you also thinking in terms of custom stuff being in one place?
>>> — Gary
>>> On 10/11/2018 3:18 PM, Bsfez Tiki wrote:
>>>> We have in Tiki since Tiki17 a Favicons preference / feature to ease the use and set favicons for the different device that reads it.
>>>> Beside doing what it says, It helps to have all the extra files and customisation enclosed inside the theme folder.
>>>> I think it would good to promote it (having more visible).
>>>> As we have : themes/themeName/fonts
>>>> I think it would be ok to have : themes/themeName/favicons
>>>> Good timing to add it for Tiki19 ?
>>>> TikiWiki-devel mailing list
>>>> TikiWiki-devel at lists.sourceforge.net <mailto:TikiWikiemail@example.com>
>>> TikiWiki-devel mailing list
>>> TikiWiki-devel at lists.sourceforge.net <mailto:TikiWikifirstname.lastname@example.org>
>> TikiWiki-devel mailing list
>> TikiWiki-devel at lists.sourceforge.net
> TikiWiki-devel mailing list
> TikiWiki-devel at lists.sourceforge.net