This thread is for our developers to comment on bugs that we have here at the forums - either new ones or known ones – that way we can let you know about the known ones so you don’t keep reporting them. We might be able to suggest workarounds, or you might have suggestions yourselves.
Please continue to report bugs by notifying me (or another staff member), but before you do so, check this thread to see if we are already aware of it.
1. bbcode for php unable to parse backslash (\).
Check that you have used backslashes in the right place. For eg,
// The \
in this instance will not render. Unfortunately, the parser
// doesn't tell you about syntax error.
echo \
.'hello world';
// This is the right syntax and the backslash will render
echo "\
Hello world";
2. Random misalignment of Ads.
The layout of ads might go haywire at times. We could not reproduce this at the moment but they seems to be related to flash ads. If the ads are stopping you from using the forum, let us know.
Here is an interesting one I believe it’s to do with that SEO plugin (Automatically parse links in text) by the looks of things…
Let’s assume I type in the following:
src=“http://www.sitepoint.com/forums/images/picture.jpg”
Outside of a code block for example: src=“http://www.sitepoint.com/forums/images/picture.jpg”
In some instances it inserts:
http://www.sitepoint.com/forums/images/picture.jpg
Infront of the text, which of course is wrong.
This is where I first noticed it happening: http://www.sitepoint.com/forums/graphics-8/graphics-wont-show-749890.html when I typed: src=“http://www.sitepoint.com/forums/images/picture%20001.jpg” it prefixed the SPF URL.
Obviously I edited it back out and unchecked the check-boxes to prevent it reoccurring in that post. I know how to prevent that happening but nevertheless it still occasionally happens.
EDIT: it has occurred in this post too; I just typed the SRC for that QUOTE block NOT the SPF URL part!
Obviously I didn’t type the SPF URL in that post above! I only used: src=“images/picture.jpg” and src=“images/picture%20001.jpg” the forum did the prefixing as you can see. 
If you PM a link to the announcement in the SEO forum ([noparse]http://www.sitepoint.com/forums/search-engine-optimization-3//announcements.html[/noparse]) the // get converted to a single / and then it doesn’t work anymore (gets redirected to the forum index).
thanks for reporting. agreed that the seo plugin is doing some weird things. the bug has been added to our to-do list.
I can click on this thread if I go to the page in CSS and click from there:
But from search I get a 404:
Bad Request
Your browser sent a request that this server could not understand.
Apache Server at SitePoint » Web Design, Web Development, Freelancing, Tech News and more Port 80
I suspect it has something to do with the weird accent mark that I don’t even seem to have on my computer.
I can reliably reproduce this. I go to Search and type in 62.5% as my search term, and it’s near the top:
Css font-size:62.5% not maintaining div´s with on IE7/8
by kickdog.
I get to it via CSS by going to page 11 (today anyway). Last post by Eric Watson on 31 March.
New user registration is broken on the iPhone or iPad , an error does not allow to get to the registration page past the agreement page
I am using FF 6.02
When I logout from SP I get the usual message saying I am being logged out and that all cookies have been cleared.
But when I close the browser, then reopen it and browse to http://www.sitepoint.com/forums/ how come I still see
Welcome, webdev1958
at the top of the browser window???
I remember Shaun of the Dead having that problem once. I think he had to tell Firefox to clear logins cache or something. The browser was still storing stuff it shouldn’t have.
Mine’s done it twice since the upgrade.
Thanks Stomme poes.
I tried it again just now without changing anything at all in FF and when I closed the browser and then reopened it and browsed to SP forums, the “Welcome” message was not there.
Most probably just a temporary or intermittent bug while the techies were doing something.
Anyone else have to log in for every single visit, or just me?
It does look like there is something slightly screwy going on with logging in, esp in FF. We are looking into it atm.
Ok, for those of you that are having issues logging in or out using FF, it looks like the browser is caching the results. So, if you are not logged in, you need to hard refresh the page after logging in and if you are already logged out, you need to hard refresh the page to see that you are really logged out (ie see the welcome message).
Don’t know about that. I just cleared the cache, restarted FF, and it still gives me the cached ‘new posts’ (“created 37 minutes ago”).
Edit: sorry, has nothing to do with login in/out. I mixed things up.
The problem with the “Welcome” message I posted earlier just happened again. It appears to be intermittent.
fwiw, I find it astonishing :headbang: these bugs were not found during the testing phase prior to going live with the upgrade.
When I was on the dev server, it was a “snapshot” (so lots of stuff was static from a certain date). Logging in issues, those seem to be new.
I think because, what they did was, they started with a default vBull4 setup, then changed the CSS to to current layout but nothing else, then launched as fast as they could (due to the servers dying apparently).
Now they’re adding plugins and whatnot back in, and writing new ones. The FF issue may have appeared after a plugin got added. A few other bugs were definitely caused by adding plugins.
^^ 100% correct. Many of us tested extensively and these issues didn’t come up. They are new and are as a result of the bug fixes and plugins that we are installing. This is a HUGE forum that has been evolving over more than a decade. The number of legacy hacks and plugins was astounding, so we are having to make a lot of changes on the fly. I realise that it’s frustrating, but please bear with us. We are working ridiculously hard to try and get things running smoothly for you.
My logging in bug seems to be fixed. fingers crossed
What problem do you have? It seems you can log in fine, otherwise you wouldn’t have been able to post that message (:
