I've Run Into A Problem While trying to Upload A picture
"Oops! Something went wrong. Please reload the page and try again."
is what i keep getting
Its A Jpeg File Of 50kb large so not a File Size issue
using Chrome On window 10
I've Run Into A Problem While trying to Upload A picture
"Oops! Something went wrong. Please reload the page and try again."
is what i keep getting
Its A Jpeg File Of 50kb large so not a File Size issue
using Chrome On window 10
@V8 @PeteM I'm adding the issue you guys discussed in the challenge thread...
Okay... easy enough to post twice and delete one of them if both come up.
Haven't been on in months! Looks awesome, but I'm a but retarded when it actually comes round to using this new format. LOL!
Here's one : I was trying to necro-bump this thread : https://community.guitartalk.co.za/d/17983-movies-about-music-musicians/34
And I just keep on getting the "ooppss something went wrong, please try again" message - no matter how many times I try and post it.
What am I doing wrong? ?
V8 Awesome! Thanks for finding this bug. Turns out that it was a SQL error caused during the import. Specifically to do with the number_index
column on the discussions table.
I fixed it for that discussion and tested it by doing a test reply. It worked. I deleted my reply so you can go ahead and play there again ?
I then fixed it for all other discussions. So we shouldn't see that exact bug again.
Thanks again for spotting this one!
V8 Nope that was definitely different. This was a SQL index issue. So the post never got inserted. What you guys experienced was that the post got inserted but something else caused an error message, making it look like the post never got inserted.
That's a logic flaw in Flarum. Essentially, their code is saying: If there's any error at all during the posting process, then return an error. (So even a notification email not being sent for a reply, constitutes an error.)
Hopefully they'll fix that in the next major release.
domhatch i try to log off and receive essentially the same message.
Thanks @domhatch! Any chance you can get me a screenshot or a video of that.
To do a video is super easy. Just use UseLoom.com right in your browser.
Here's a quick one I did right now, showing you how to record your screen super-fast:
https://www.useloom.com/share/b91f2f9bd9494df4a0a98b9f59ed950f
NorioDS hey there. so, murphy intervened. my logout (perfectly recorded by useloom which is a smashing tool by the way, big ups for the linkup!), went off without a hitch.
i have a feeling the error message i receive comes along when i've been idle in here for a while and then try to log out. i'll try to recreate that situation and post the recording if i receive the error message.
hope i'm not wasting yer time
dh|
domhatch i have a feeling the error message i receive comes along when i've been idle in here for a while and then try to log out. i'll try to recreate that situation and post the recording if i receive the error message.
Hmmm good theory. I've had that happen before with Laravel where the CSRF token expires if I leave a form open and then try use it later. Could very well be what's happening.
I'd appreciate if you could replicate the issue and confirm if that's what's happening. It'll be something I'll pass on to the Flarum dev team to fix. I think they're releasing a new beta in a month or 3.