I installed elgg on a local machine and everything works fine. I installed it on a shared online hosting platform (where I host my web pages) and get a lot of cache errors and other errors.
- Layout was forced before the page was fully loaded. If stylesheets are not yet loaded this may cause a flash of unstyled content.
- 14:47:57.853 Loading failed for the module with source “https://xxx.com/cache/0/default/elgg/lightbox.mjs”.
I get this "Loading failed" message on a bunch of other .mjs files as well
I disabled the caches and flushed the elgg cache. Also flushed cache on Firefox browser.
The net effect is a lot of javascript code doesn't work, pressing the compacted menu button doesn't work, sometimes tabs don't work, etc; and often, jpg and other images don't show up. When I clear caches, the images show up first time I refresh the page, and don't show up if I refresh again.
Any ideas what things to look for?
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.
Thanks, it turns out I did have a copy of the elgg .htaccess in my elgg directory. It has
but none of the other ones:
I'm now also getting net::ERR_ABORTED 508 (Loop Detected) on some .mjs files.
I wonder if it's a race condition, since the ISP is much slower than my local server. I can try to throttle my local server to see if similar problems show up.
If all else fails, I'll install another instance of elgg again in a different subdirectory.
I'll see if my ISP can come up with some insights, and will update here in case it helps anyone else!
Looks like the problem was with the ISP, maxed out on number of "entry processes" (the number of processes the web server can spawn).
But also seems something else was causing this to happen. They fixed it, but haven't told me what they changed. I will ask again, and if I find out, I will update here.
Just going to the "create group" page on elgg caused over 10 entry processes. Sounds like something is misconfigured!
ISP or hosting provider?
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)?
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.
- Previous
- 1
- 2
- Next
You must log in to post replies.