Former Member
inherit
guest@proboards.com
195316
0
May 1, 2024 7:49:48 GMT -8
Former Member
0
January 1970
Former Member
|
Post by Former Member on Jun 26, 2014 23:40:15 GMT -8
Forum URL: thecreativepen.proboards.comI cannot edit any posts/threads on my forum It gives this error when I click on the edit button and then click on the BBCode button when trying to to edit a post JS Error: There was an error while trying to load the BBCode editor. Using Google Chrome - latest Version - I tried closing the browser and restarting again and still have the same issue With the error popup it shows below. I also get the error when clicking to delete a post EDIT: When I use Firefox it gives this error when I try to edit a post Invalid request token / possible request forgery (error 4). If you received this message in error, please go back, refresh, and try again. I'm also having a problem with new posted threads when I click on the reply button it says The thread you are trying to access could not be foundSteve
|
|
inherit
172462
0
Jun 25, 2023 5:27:46 GMT -8
mariannemarlow
200
October 2011
mariannemarlow
|
Post by mariannemarlow on Jun 27, 2014 0:31:54 GMT -8
Someone just messaged me with the same error on my forum: Invalid request token / possible request forgery (error 4). If you received this message in error, please go back, refresh, and try again.
|
|
Former Member
inherit
guest@proboards.com
195316
0
May 1, 2024 7:49:48 GMT -8
Former Member
0
January 1970
Former Member
|
Post by Former Member on Jun 27, 2014 3:44:47 GMT -8
ALL SEEMS TO BE WORKING CORRECTLY FOR ME NOW - I'M NOT GETTING ANY JS ERROR AND CAN NOW EDIT POSTS USING THE BBCode BUTTON.. If proboards staff was working to fix the issue - A BIG THANK YOU If was just a blip - for me for the moment it seems to have fixed itself I can post/edit without any problem Steve
|
|
inherit
The Great Cinnamon Roll
191518
0
Oct 19, 2016 22:17:44 GMT -8
David Clark
Care for some tai chi with your chai tea?
17,602
March 2013
davidlinc1
|
Post by David Clark on Jun 27, 2014 8:11:35 GMT -8
Apologies for the inconvenience - this should no longer be an issue, as our sysadmins addressed the problem overnight.
|
|