Dear Nikolai,
Many thanks for your message and the links you provided.
This was really helpful and after several attempts, I finally succeed with the extend method.
I have another question :
How can I replace the text logo by an image logo ?
Thanks again.
Have a nice day.
Thierry
The links below are for previous Elgg versions but should work for the current release as well:
https://elgg.org/discussion/view/2804746/logo-in-default-theme-in-all-stable-elgg-version
https://elgg.org/discussion/view/2849336/how-to-change-the-logo-from-text-to-image
I forgot to mention that the easiest way to extend engine/theme.php is to use a hook in elgg_plugin.php instead of class:
'theme' => [ 'body-background-color' => '#000', 'anchor-color' => '#000000', ],
Not sure what "Loop and Dynamic pointer" is supposed to be.
My guess is that the loss of the connection to your database is due to my.cnf settings with regard to the number of max connections and the keep-alive time of connections. Especially, if you are on a (cheap) shared server or "cloud server" hosting plan the coniguration of max connections is quite low and maybe most MySQL settings are kept on the default values even if they make not much sense. And you probably can't even make the necessary changes in my.cnf to stop the connection issues.
My advice: get in contact with the support of your webhoster to help you out optimizing the my.cnf settings (general advice is difficult because it depends also on things like memory available). And if you are not on a VPS or similar hosting plan you probably need to switch (and pay more...) to be able to make the necessary improvements.
I never understood why I should use composer as an end-"user" either. It might have advantages to use it for development but I had never experienced any advantage in trying to maintain a site (together with all plugins!) as opposed to make use of the "traditional" way of using zip files (regardless where to fetch them from). My "version control" is the version of Elgg / the plugin the zip is supposed to contain and any differences in files can be figured out using some diff tool.
The elgg-cli commands have NEVER worked for me either! And I don't understand under which conditions they are supposed to work. I would have to execute the commands as root to get them working at all and I can't advice anyone to do that. Security aside, any files and folders created by root can't very likely not be read by the webserver just to name one other problem.
If you have a test server you might want to give composer / elgg-cli another try. You could try to get accustomed to it and then make use on your production server. Otherwise, the old fashioned way of using zip files and the browser-based installation still works (and works perfectly fine if you ask me).
As for the Elgg documentation of making use of composer I would also say that it's not really helpful. And searching the Internet (or making use of the composer docs) is not much better either because I see totally different target groups in the usual users of composer and Elgg users (admins). Just because you want to use Elgg does not mean that you are necessarily a coder. But maybe a coder does not understand that non-coders might have some trouble understanding the composer docs...
Still struggling through the same thing, but i am not asking anymore questions. I will eventually give up on it anyway, and that will be the end of it.
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by Raül Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.