New Forum! (Known Issues)
This new look is GREAT. Good work to all that made it happened.
There is only one function that I miss. In the previous one it was very easy to select only postings that was not read yet. I do not see it on this one.
Having said that, great work.
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...
- Sometimes while posting, the forum will say your reply didn't post when it really did. The only known workaround, right now, is to copy your post and reload the page to check if it posted. Most times it did but, if it didn't, then you can just paste it in again and click 'Post Reply'.
- I have a theory that this is related to some of the "behind the scenes" tasks being run when you post. Emails being sent, etc. If anything there fails, it tends to squawk.
- Only likely to be fixed by the Flarum development team themselves when they release their next beta.
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.