Printable View
I have finally fallen to the dreaded double post. No message about leaving the page, nothing. Just bam! There it is. Also, having a tough time with thelackofspacesinareplytoanotherpost. I used to be able to get around it by going advanced but today my advanced was blank. Is that what you're talking about too, @rockco ? Then I figured out that if I chose the multi-quote button the spaces worked.
@GoJays , from the replies received, @dataiv concurs the following are errors:
- REPLY opens a blank page, going ADVANCED MODE also blank page
- Double Posts (forum is littered with many double posts)
This problem is new:
"thelackofspacesinareplytoanotherpost. Then I figured out that if I chose the multi-quote button the spaces worked
I cannot determine if @dataiv concurs we are all experiencing log-in problems, staying logged in while performing tasks and the constant need to confirm credentials at various steps of the editing process. Several forum members have commented on this behavior, but I'm not sure if the techs agree it's an issue.
@GoJays , from the replies received, @dataiv concurs the following are errors:
- REPLY opens a blank page, going ADVANCED MODE also blank page
- Double Posts (forum is littered with many double posts)
This problem is new:
"thelackofspacesinareplytoanotherpost. Then I figured out that if I chose the multi-quote button the spaces worked
I cannot determine if @dataiv concurs we are all experiencing log-in problems, staying logged in while performing tasks and the constant need to confirm credentials at various steps of the editing process. Several forum members have commented on this behavior, but I'm not sure if the techs agree it's an issue.
Quote:
Originally Posted by KelJo
Yeah the blank post is still my main issue too. My TL is looking fine now, but my WL thread is impossible to copy & paste over from my other thread (my initial attempt at resolving the issue: creating separate TL and WL threads) and some of the posts just lead me over to a blank form, which I haven't been able to get around. Been difficult to try to trade without a proper WL.Quote:
Originally Posted by GoJays
I probably shouldn't say this out loud because so far luck has been on my side with this issue, but I haven't had any problems with staying logged in. Yep, I just jinxed it.Quote:
Originally Posted by rockco
ihavethesamespacingproblemswhenusingchromewhenirep lywithquote..Quote:
Originally Posted by GoJays
it doesn't happen in firefox. and look at that! the second line of this post is properly spaced?!!
does anyone else get this when posting an image?
and then have the image appear twice in the post, once as an attachment.
Warning: preg_match(): Compilation failed: invalid range in character class at offset 23 in [path]/includes/class_wysiwygparser.php on line 458
what's going on?!!
everything was fine until about a week ago.
The Leafs are in the Playoffs!!!! :shrug::cheesygrin:
Quote:
Originally Posted by heartgirl99
Quote:
Originally Posted by GoodBoy
:lolsign:
Quote:
Originally Posted by heartgirl99
Yes, I mentioned this in a previous post--seen this error message several times today
argh! frustrating!Quote:
Originally Posted by KelJo
It happens to users with Firefox too, only seems to be on quotes.Quote:
Originally Posted by heartgirl99
Hitting enter or posting the reply above the quote seems to fix it though
@dataiv ??Quote:
Originally Posted by heartgirl99
All, the preg_match error should not happen now. I just made a change to the expression that should fix it. In regard to other things you are all experiencing, I personally haven't ever been logged out or requested to log back-in at any random time, but I do believe it happens to you.
I believe there is a plan to get an expert in VB's code to look into these issues mentioned along with an upgrade, as my experience isn't suited to me trying to solve CSS/AJAX/Cookie type issues. On the server side I see no errors when I try to edit a large post, so I am not sure what is going on there at all. I wish I could solve all the issues :) ...
And thank you for posting any PHP warnings or errors (like the preg_match one) or server errors that you see. If you post those, they are typically things I can look into, more so than the actual functionality of vBulletin (VB) as a whole. So please keep posting if you see errors or messages like that one.
*update: try editing large posts now, small change made to character encoding in filling the text box that may fix it.