[SOLVED] Fatal error on Step 18 of upgrade from 2.0.7

I got this exact error on my same upgrade install, here. We seem to have followed the same steps, too.
I'll be watching this thread with interest!

It's a bug in the upgrade script.  Until a patch is released, manual fix is as follows:

1.  Open install/upgrade20.php and go to line 168:

seriesreview($s['seriesid']);

2.  Replace that line with the following two:

$thisseries = $s['seriesid'];
include("includes/seriesreviews.php");

Then finish the upgrade STARTING at step 18.  DO NOT GO BACK.

After doing that, it did take me to the next step (where I have to delete things), but I saw this error on the top of the page:

Warning: main(includes/seriesreviews.php) [function.main]: failed to open stream: No such file or directory in /home/**/public_html/drfa/install/upgrade20.php on line 169

The same error repeats 16 times.

After deleting everything mentioned (except for the install folder, since I might need to go back to that step?), I opened a new window with my site in it (the old window with Step 18 "completed" page is still open), and on the index.php page, this error shows up:

Warning: main(timefunctions.php) [function.main]: failed to open stream: No such file or directory in /home/**/public_html/drfa/blocks/featauth/featauth.php on line 5

Warning: main(timefunctions.php) [function.main]: failed to open stream: No such file or directory in /home/**/public_html/drfa/blocks/featauth/featauth.php on line 5

Warning: main() [function.include]: Failed opening 'timefunctions.php' for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/**/public_html/drfa/blocks/featauth/featauth.php on line 5
A fatal MySQL error was encountered.
Query:
Error: (1054) Unknown column 'member' in 'field list'

Okay the second line of that fix should read:

include("../includes/seriesreviews.php");

The ../ was missing.

Your other problem is because the featured author block was a 2.0 block.  It's not one of the default blocks, and therefore wasn't upgraded.  You'll need to turn it off.

Okay, that fixed it (for the errors on the top of Step 18).
But as for turning off the featured author block, how can I do that if I can't even access the site (i.e. fatal error means the site won't load at all)? Do I just delete a particular file or folder that still exists? Or do I need to edit a file?

Also, what's the databasepath folder that we're supposed to delete in that final step? I see a "data" folder with the file dbconfig.php in it... is that it?

Yes. Whatever you named your data folder is the folder you want to delete.  For your featured author problem.  Open up the variables.php file for yor default skin (I think you chose CSSZen?).  Add:

$blocks['featauth']['status'] = 0;

That'll turn the block off for that skin, and you'll then be able to go into your admin settings and turn it off for the site.

Okay, adding that line of code worked. But is Featured Author not a block/module in 3.0? Or is there another way of disabling the  old one and enabling a new one? When the option is set to "Active", I get the error again.

No, that block wasn't part of 2.0 either.  It was one you downloaded from my site.  You're going to have to leave it disabled until someone updates it. 

Edit This summer I posted a version for 3.0 at my site, but I make no guarantees that it will work as we've gone through numerous changes and bug fixes since then.  You're welcome to try it though.  I would suggest though that you get everything else working before you start adding and modifying things.

Bump.  Is this solved now?  If the original poster doesn't reply back in a week, this thread will be closed.

Yes, it has been solved. Quick question about something mentioned in the last post though-- the featured author block was just a modified version of featured story, wasn't it? I know the 3.0 version released this summer wasn't up-to-date with the latest release (3.0.2), but if someone did want to do the featured author block again, would it be difficult to modify the featured story block, or are they totally different?

They're fairly similar.  The difference now would be in making sure it'll work for those who bridge to outside author tables.