Can you post or pm a link to your blog?

The blog i'm having problem with is in the Intranet. No internet access. :-/

Can you at least post the error message?
Once you renamed blog2/ to blog/ you should only edit the $baseurl in basic_config.php, nothing else.

$baseurl in _basic_config.php is now http://domain.com/blog when blog2 was renamed to blog.

When trying to access the blog, it displays a blank page.

Here's the error from log file:

[Wed Aug 12 10:22:44 2009] [error] [client 10.x.x.x] PHP Warning:  require_once
(/path/to/blog2/conf/_config.php) [<a href='function.require-once
'>function.require-once</a>]: failed to open stream: No such file or directory in /path/to/blog2/index.php on line 25
[Wed Aug 12 10:22:44 2009] [error] [client 10.x.x.x] PHP Fatal error:  require_
once() [<a href='function.require'>function.require</a>]: Failed opening required '/path/to/blog2/conf/_config.php' (include_path='.:/usr/share/p
ear:/usr/share/php') in /path/to/blog2/index.php on line 25

Blog2 doesn't exist anymore after renaming but the error log shows that it's trying to open index.php from blog2. Is it cached somewhere? I've tried to refresh my browser and even tried to access the blog from a different PC. Same blank page and same error.

Here's the error when trying to access backoffice:

[Wed Aug 12 10:23:02 2009] [error] [client 10.x.x.x] PHP Warning:  require_once
(/path/to/blog2/conf/_config.php) [<a href='function.require-once
'>function.require-once</a>]: failed to open stream: No such file or directory in /path/to/blog2/admin.php on line 44

.htaccess problem?

¥

I thought about that... .htaccess for both are identical.

I have fixed the problem by workaround solution: temporarily assigned a domain to this blog, access the blog, and from backoffice > tools > Delete pre-renderered item cache. Then removed the domain and access the blog as per usual.

$baseurl in _basic_config.php needs to be updated temporarily to make it work. Then change it back afterwards.

I will follow upgrade procedure from now on! :)

Just suggestion to b2evo team, perhaps the upgrade procedure should be reviewed? It's currently applied directly to production system and I don't want visitors to see error messages like database is not up to date and click the installation link while I'm doing it. Of course a more proper way is to schedule doing it at off-peak hours... :roll: (Or there's already something in place but I've overlooked?)