My mistake, I meant "Hosting Provider", the company that hosts the web pages, where I have the elgg code.
A lot of the GET requests that have been failing are for the simple cache (caches static content including some CSS and JavaScript files).
An example GET request is for
https://xxxx.com/elggtestsite/cache/1742376112/default/elgg/menus/dropdown.mjs
Is this request something the web server can serve without invoking another process, or does it create a process for each of these, and that's why "entry process" gets maxed out quickly? Does each of these requests force php to be run?
In elgg, going to a typical page (e.g. groups) typically causes 15 to 25 such requests. Things get worse if there are two or three users! Should the web server queue up the requests if the number of "entry process" is maxed out, or is the only solution to have a high entry process maximum?
Does anyone know some answers to the previous post (I'll quote it here as well)?
A lot of the GET requests that have been failing are for the simple cache (caches static content including some CSS and JavaScript files).
An example GET request is for
https://xxxx.com/elggtestsite/cache/1742376112/default/elgg/menus/dropdown.mjsIs this request something the web server can serve without invoking another process, or does it create a process for each of these, and that's why "entry process" gets maxed out quickly? Does each of these requests force php to be run?
In elgg, going to a typical page (e.g. groups) typically causes 15 to 25 such requests. Things get worse if there are two or three users! Should the web server queue up the requests if the number of "entry process" is maxed out, or is the only solution to have a high entry process maximum?
1 - What errors are displayed in your browser's developer console aka Inspector ? (Ctrl+Shift+I)
2 - What's in the server error log?
Turn on 'Debugging and Logging - Log level: Log errors and warning' option (Dashboard -> Site settings) on /admin/site_settings
3 - You can activate 'Developer Tools' plugin and then 'Enable error log' option on /admin/plugin_settings/developers if you don't have access to the server.
Then check for errors here /admin/develop_tools/error_log
But after testing, disable this plugin or just this option to avoid loading your server.
'views' => [
'default' => [
'assets/' => elgg_get_data_path() . 'assets/',
],
],
/mod/my_plugin/views/default/assets/topbar_logo.png
Awesome! It works like a charm now. Thank you for the update.
Since I already created the assets folder, I chose to add the "views" bit to my elgg-plugin.
A beautifully styled little logo can make quite the difference for the layout. :)
Added a new plugin with this feature
Without code it's difficult to understand what's happening.
No code means no help.
If the code is large, place it on GitHub, GitLab and publish the link here so other developers can see your project.
Also one of the common development pitfalls is caching. Make sure eighter caching is disabled or after you create a new view, class or add a language string invalidate the cache.
Hello Nikolai,
FYI:
I cannot manually verify a user who is an admin. It gives the following error message:
"The page you are trying to view does not exist or you do not have permissions to view it."
The setting "Verify user when making him an admin" didn't make a difference either.
When I took away the admin rights, I could verify the user manually, and then I made him admin again, so he is a verified admin now nonetheless.
Just wanted to report that maybe there is something not working as intended regarding admins.
Regards,
elggnoob
Thanks for reporting!
I'll fix this issue in the next release.
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.