Please see:
http://blog.4lancer.net
There is no place to possibly log in, going directly to the admin page gives me Access Denied, kinda pissed.
Did the default (since 4.5 release) selection on the database update.
Did just solve one problem though: Links to recent comments started with http://localhost because in the settings.php file http://localhost is the default base URL, when it should be just localhost whoever did that is a dink. So now the page doesn't look like crap. Well, the front page anyway, the Access Denied page still looks like crap. Even
http://blog.4lancer.net/user/1
Gives an Access Denied.
Did just find a link to Login, but the Login page is not found:
http://blog.4lancer.net/user/node/user
And on top of that, URLs are going to crap as well:
http://blog.4lancer.net/node/blog/comment/reply/comment/reply/306
Rediculous. Would like any and all help ASAP.
Thanks
Jake Stichler
Search4Lancer
Comments
Log in
You can log in at http://blog.4lancer.net/user/. Once logged on, double check your settings.
Note that the format of the settings file changed. See the release announcement for details.
Page not found.
Page not found.
Scratch that, was defaulting
Scratch that, was defaulting to /user/1
Your $base_url is wrong as well
Your $base_url should be 'http://blog.4lancer.net' not 'http://localhost'.
And I also said it shouldn't
And I also said it shouldn't be 'http://localhost' but rather 'localhost' works just the same, as is evident from the recent comment URLs.
Scratch that, apparently
Scratch that, apparently localhost works some places and not others. Rather odd.
Comments
Well, you have to be more descriptive. Saying it looks like crap is not descriptive enough. Even crap comes in various shapes and colors you know.
Anyway, try going to http://example.com/user
You should get a login screen. Login and see if that works.
--
Consulting: 2bits.com
Personal: Baheyeldin.com
--
Drupal performance tuning and optimization, hosting, development, and consulting: 2bits.com, Inc. and Twitter at: @2bits
Personal blog: Ba
And you could have seen the
And you could have seen the crap for yourself at one of the many links I provided.
No guarantees
I must say your tone is a bit too negative for me. Drupal is free software, it comes with no guarantees. We all worked hard to ensure 4.6 is as bug free as we can make it.
Situations like yours still happen, but when they do it's best to see it as an opportunity to improve Drupal rather than to come here being pissed off at people who are trying to help you in their spare time.
To me it looks like you didn't take into account that the settings file moved, as described in the announcement. You could also be dealing with outdated contributed modules and/or themes which you should have disabled before upgrading, as the instructions say.
As far as $base_url goes, it should definitely be an absolute URL with http:// .
--
If you have a problem, please search before posting a question.
You have a backup, don't you?
Before you upgrade a production site, you should always test it first, e.g. locally on a test computer.
Of course I have a backup.
Of course I have a backup. However, I don't have a system suitable for testing.
Just upgraded with no major issues
Drupal 4.6 was released to the world today.
I did a test upgrade on my test machine from 4.5 using a copy of the database that I backup from the live sites.
There were no major issues. The ones I encountered were contributed module specific. The only core issue I saw was one duplicate menu item in the Navigation block, which I disabled.
Perhaps I will find the time to write a detailed report once I am done.
--
Consulting: 2bits.com
Personal: Baheyeldin.com
--
Drupal performance tuning and optimization, hosting, development, and consulting: 2bits.com, Inc. and Twitter at: @2bits
Personal blog: Ba