Tiny Fixes That Saved the Build
Sometimes a project is not broken because of a giant disaster.
Sometimes it is broken because of one tiny thing sitting there like:
“Yes. I am the problem. No, I will not make myself obvious.”
This thread is for small fixes, weird discoveries, quick saves, one-line solutions, and those moments where the answer was embarrassingly simple.
No shame.
Every builder has lost two hours to a missing comma, wrong folder, cached file, or checkbox they definitely “already checked.”
They had not checked it.
What belongs here?
Post anything that might save another builder time.
Good examples:
- A tiny command that fixed your site
- A setting people often miss
- A browser/cache trick
- A hosting panel issue
- A DNS mistake
- A Flarum, Laravel, PHP, JS, CSS, MySQL, or CloudPanel fix
- A plugin/extension setting that caused weird behaviour
- A “don’t forget this” reminder
- A small bug and the exact fix
- A tool that made the job easier
- A mistake you made so others can avoid joining your suffering
This is not for massive tutorials.
This is for quick useful fixes.
The kind of fix that makes you whisper:
Are you serious?
Post your fix like this
Copy this format:
Problem:
Fix:
Why it happened:
Useful command/link:
Difficulty:
Example:
Problem:
Flarum changes were not showing after editing CSS.
Fix:
Cleared Flarum cache and published assets.
Useful command:
php flarum cache:clear
php flarum assets:publish
Why it happened:
Old compiled assets were still being used.
Difficulty:
Easy, but emotionally damaging.
Perfect. Clear. Useful. Slightly wounded.
Tiny fixes worth remembering
Here are some common ones.
1. CSS changed but nothing updates
Try:
php flarum cache:clear
php flarum assets:publish
Then hard refresh:
CTRL + F5
If that works, the problem was probably cache.
Cache is useful.
Cache is also a professional liar.
2. You are in the wrong folder
Before running commands:
pwd
List files:
ls -lah
If you do not see the files you expected, stop.
You may be about to confidently break the wrong thing.
3. Composer refuses to install something
Check why:
composer why-not vendor/package
For Flarum core conflicts:
composer why-not flarum/core 2.0.0
This usually gives a better answer than staring at the red text like it owes you money.
4. Site shows a 500 error
Check logs:
tail -n 100 storage/logs/*.log
For many PHP apps, the log knows the truth.
The browser says:
500 Internal Server Error
The log says:
Here is the exact file and line number, enjoy.
Always check the log.
5. Images do not show
Check:
- Is the image URL public?
- Does it open directly in the browser?
- Is it blocked by hotlink protection?
- Is the file path correct?
- Is the image first in the post if used for thumbnails?
- Did you clear cache?
- Is the image too slow or from an unreliable source?
For Fyrbloc thumbnails, put the image at the very top:
# Post title
The “before I panic” checklist
Before posting for help, try:
That last one hurts.
Many builders have edited settings beautifully and then closed the page without saving.
This is called advanced clown technology.
Quick fixes people can reply with
If you found a fix, reply with something like:
Tiny Fix:
Flarum thumbnail was not showing because the image was not the first image in the first post.
Fix:
Moved the markdown image to the very top.
Result:
Thumbnail appeared after clearing cache.
Or:
Tiny Fix:
Custom CSS looked broken on mobile.
Fix:
Added a media query for screens under 700px.
Result:
Mobile layout stopped acting possessed.
Or:
Tiny Fix:
Composer install failed.
Fix:
Removed the incompatible extension first, then updated with --with-all-dependencies.
Result:
Install completed.
Do not post secrets
Even for tiny fixes, hide private info.
Do not post:
- Passwords
- API keys
- SMTP passwords
- Database credentials
- Private tokens
- Full
.env files
- Customer/user data
Safe version:
DB_PASSWORD=hidden
MAIL_PASSWORD=removed
API_KEY=redacted
Good builders redact.
Bad builders accidentally publish their life.
Why this thread matters
Small fixes stack up.
One tiny fix might save another builder:
- 10 minutes
- 2 hours
- A broken deploy
- A panic reinstall
- A dramatic message to support
- A suspicious conversation with their keyboard
So post the small stuff.
The fix that felt obvious after you found it might be exactly what someone else needs.
Final rule
If a tiny fix saved your build, share it.
No ego.
No pretending you knew it all along.
No “I meant to do that.”
Just the fix.
Build. Break. Notice the tiny thing. Fix. Launch.
