Re: [Tiki-devel] Asking for feedback: Tiki code organisation reorg, take ... 3?

On mardi 25 avril 2023 01 h 16 min 57 s EDT Bernard Sfez wrote:
> Thank you Benoit for improving Tiki.
> 
> I have a more end-user/consultant point of view than a coder one.
> I understand the reasons behind the organization proposed and may be there
> is no room here for a end-user interfering with the plan 🥴 but still this
> is my thoughts.
> 
> 
> I would like to point that it should be easy, easier or at least not harder
> 😉 to backup admin changes and users content added to a Tiki.
> 
> By those I mean the files I have to backup/copy/restore from time to time on
> a Tiki:

The idea is that they would ALL be in private/* and public/storage/* now, and nowhere 
else (unless custom paths are set for some features).

> Themes
> - Custom theme directory with favicons, fonts, icons, images, js, options,
> sass, templates (is there more ?):
> https://themes.tiki.org/How+To+Add+a+New+Theme - Custom template directory

As documented, they will go in public/storage/themes
 
> (/themes/templates) - (the advantage of using this is to have custom
> templates available for all the themes) - (I couldn’t find documentation
> about it)

That will remain, but go in private/template_overrides/
 
> Languages
> - The custom languages (lang/fr/custom.php for example) - couldn’t find a
> documentation about this:
> https://dev.tiki.org/item485-Custom-language-translation 🤭

Indeed, it seems undocumented I didn't know about it.  It would go in private/
lang_overrides , added to the paths, but someone should probably document that 
feature.

> Files
> - File gallery and other files (storage) - (outside Tiki root for security -
> or is it old school now ?):
> https://doc.tiki.org/File-Storage#Storing_files_in_a_directory

The webserver root won't move to public/ till the very end of the process.  But when it 
does the default location for all these will be outside the root.
 
> Config files
> - The .user.ini file: https://doc.tiki.org/php.ini#user.ini

That's not a tiki feature at all:  https://www.php.net/manual/en/configuration.file.per-user.php[1] , we have no control on where it's read, it's a cascade from the document root.

> - The system configuration file (tiki.ini.php file):
> https://doc.tiki.org/System-Configuration#Activate_the_system_configuration

There's no path for it in the code (maybe there should be), it's read in whatever is set in 
system_configuration_file.  And there is no real local.ini.php.example.  But logically one 
would put it in private/conf/tiki.ini.php

> - The robot.txt file

Like user.ini, it has to be at the document root, unless we generate it from php, but that's 
really out of scope.

-- 
Benoit Grégoire

--------
[1] https://www.php.net/manual/en/configuration.file.per-user.php

_______________________________________________
TikiWiki-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel