docs: add troubleshooting note for missing assets#224
Conversation
|
@OdinakaDico : Thanks for the contribution and for providing the setup evidence references. After reviewing the content, we have some concerns that make us hesitant to merge this as-is. The suggested causes don't match the symptom Base URL misconfiguration and Pretty URL setup issues are unlikely to produce 404s specifically for CSS/JavaScript/asset files. Those problems typically manifest as page-level routing failures, not missing static files, because HumHub's published assets under The steps confirm problems rather than fix them The "Check the following points" list tells users what to verify but doesn't tell them what to do about it. Troubleshooting documentation is most useful when it closes the loop: symptom → likely cause → concrete resolution. Asset 404s are not a common support issue for us To be honest, we rarely receive support requests specifically about 404 errors on CSS/JS assets. This makes us wonder whether this entry is addressing a fairly isolated setup situation rather than a broadly recurring problem. The referenced evidence (S2-I04, S3-I02) isn't publicly accessible to us, so we can't assess how representative those cases are. If this was triggered by a specific environment (e.g. a non-standard XAMPP or Windows setup, a subdirectory installation with a misconfigured web root), it might be worth narrowing the entry to that specific scenario with a concrete fix, rather than a general checklist. We're happy to revisit if you can provide more context on the root cause and the fix that actually resolved it. |
2 participants
Summary
Adds a small HumHub-focused troubleshooting entry for cases where HumHub loads without styling/scripts or where browser developer tools show 404 errors for CSS, JavaScript, or asset files.
Scope
This is focused on HumHub installation/setup troubleshooting. It does not add general XAMPP, PHP, Apache, Windows, MySQL, or Composer troubleshooting.
Changed file
Related setup evidence