Quote:
Originally Posted by Tim Cullis
Similar problems with Chrome and Firefox...
Can't log in with Chrome. Cleared cache and restarted browser, same result. Tried again, same result.
Tried with Firefox. Same result.
Dusted IE8 off and this works (hence able to post). Went back to Chrome whilst still logged in with IE8 and I can now log in.
_________________________
Logged out of Chrome and IE8, then started Chrome by itself and I can now log in OK.
BTW Grant, you should put another way for people to contact you on the yellow header otherwise people who can't find a workaround to logging in won't be able to let you know!
Tim
|
Good idea! Done - added a link to webmaster feedback
Quote:
Originally Posted by markharf
I use Firefox, Mac OS10.x
I can no longer click the titles of the categories on the left side of my screen ("About Us," "Forums," etc.) to collapse the lists below each title. That means I need to scroll down to find "Posts Last 24 Hours" each time I open the site. I don't like scrolling down; I'm growing old quickly and don't have the time to spare anymore.
Plus: the giant yellow box hurts my head. It would be just as effective if it were a quarter the size.
I'm not seeing what's been gained, but I trust it's significant.
Mark
|
VERY significant - not just a point upgrade but a major version of Drupal to Drupal 6, and now the latest version of vBulletin 3.x, tied together with Drupalvb, which is how we have single-sign-on for all of the site. The old software tying them together was a deadend, and the old version of Drupal was ancient with limited functionality and no one wanted to even work on it.
For the techies: We're not on Drupal 7 yet - this winter is a possibility, but maybe the following winter. The upgrade we've done now will make it much easier - not easy to got to Drupal 7, but for now Drupal 7 isn't ready for us - there's too many modules we use that aren't fully baked yet. We aren't going to vBulletin 4 for two reasons - it's still too flaky, and the connection to Drupal 6/7 isn't there. Hopefully by winter Drupal 7, vBulletin 4, and the connector - Drupalvb - will all be ready. If not it's not critical - there's LOTS we can do with Drupal 6.
In the meantime, there are immediately a few new features, primarily in the user options area, such as a photo album, messaging etc. Also there is now a "like" link to say you like this post, and a "Share" link to post on de.licio.us, technorati, digg and twitter.
We'll also be able to add more stuff over the fall and winter easily.
Yellow box - sorry - but even with that some people were wondering what was going on...
No need to scroll - just use the "New Posts" link on the blue bar above the posts - then you can choose over exactly what period you'd like new posts from.
Collapsing the lists - hmm, hadn't even noticed that was gone! Will see what I can do.
Quote:
Originally Posted by Tim Cullis
The above was on Windows XP notebook PC. Just tried on my Windows 7 notebook with Chrome and Safari (not Firefox) with EXACTLY the same result, it wasn't until I used the hated IE8 to log in that Chrome would do the same.
From the warning in the yellow box there's obviously some recognition that there might be a problem logging on, perhaps if the underlying problem was explained it might make it easier for people to work out how to solve their environment.
|
Notes added to hopefully make it more clear - we were hoping to get it all solved perfectly quickly, but that didn't happen. Despite a LOT of testing, on some 20 computers/operating systems/browser combinations, it seems not everything is perfect. (understatement...)
THE cure is clearly a full flush of the COOKIES - so far as we can tell it's primarily a cookie issue. We ran into this problem frequently in testing, and a flush always cured it for us.
There is an issue with logging in where you look like you're logged in according to the "Who's online" list, but the welcome box isn't there, just the login box - we're NOT sure what's happening there, and I'll be working on it over the weekend but have little hope of nailing it - it's beyond my technical expertise - but I hope to be able to clearly document the issue so we can track it down with our guru on Monday. He wanted the weekend off for some weird reason...
In the meantime the workaround I've figured out is to logout using the logout link I've put in the yellow box, then login again - and that seems to do it fine.
If anyone can come up with a clear "what they did" to make that issue happen - and can reproduce it consistently - I'd greatly appreciate it!
In the meantime, thanks for your patience and help while we sort it out - website upgrades are always fraught and flaky till it's sorted out, and we THOUGHT we had it nailed - a hundred hours of testing on two different servers in the process of getting it here and it's still not right is frustrating! BUT we're getting there!
thanks!