What's causing browser problems ?

JoleneP

1st, there's nothing showing an error in the log files

2nd, Desktop users are complaining that when they post there's an error saying to refresh the page and try again. But doing this does NOT fix their error.

3rd, I was able to duplicate it on Chrome and Firefox. The problem is intermittent... Clearing the cache does not seem to fix the problem.

Any ideas ?

huseyinfiliz

JoleneP This should normally show up in the Flarum log file. Since you're not using a database queue, it looks like an extension that listens to the post publishing event is trying to run something in the background and failing.

You can try disabling the extensions you suspect one by one to narrow it down. Also, it’s worth checking the browser console (F12) to see if any errors appear there.

JoleneP

huseyinfiliz

It looks like I'm back to hunting ghosts and I have no more hair to pull out.

There's nothing in the log file. (I've checked it several times)
I've disabled every extension and the error is still there.
There's no errors in teb browser console.

huseyinfiliz

JoleneP I hope we can help you resolve this issue as soon as possible. You might have already tried some of these, but here are a few things to check:

Try enabling debug mode and reproducing the same error. A debug button should appear alongside the error, giving you more detailed information.

Check your file permissions.

If you have access, try clearing the cache and running asset publish commands via SSH to see if any errors occur.

Inspect the database to make sure no core columns or tables are missing.

Check server resources such as disk space and other statistics.

Look through Nginx/Apache logs to see if anything relevant appears.

Check the network tab in the developer console to see if there are any API errors.

KBExit

huseyinfiliz I do want to caution that debug mode risks throwing database credentials and such to be publicly available. Not recommended in a production environment...
If they have no logs, they might have permissions issues with their directory and cannot produce it. Alongside that, if they have permission issues, this is essentially a pandoras box of why they're constantly "pulling their hair."

luceos

JoleneP send me the url to your community via email and I'll try to identify the issue without diving too far into things, free of charge obviously.

My email is in my bio/profile.

ps. it's time to get things resolved for you ❤️‍🩹

JoleneP

luceos
Well I checked every single log available... I checked browsers... I checked everything that I could think of.

So on a lark I ONCE AGAIN did a recursive chown command to give the administrative user account ownership over everything in the install directory.

I can no longer replicate the problem so I'm guessing it's gone.... An no one seems to be complaining about it anymore.

ernestdefoe

JoleneP sounds like something is changing permissions.