Unable to load main_above template

[recce101]

I've done several successful test installations of SMF 2.0 RC3 over the past week, using webinstall.php, but today each time I finish the installation and try to connect to the new forum, I get an "unable to load the main_above template" error message. Running repair_settings.php has not resolved the problem, and the required files seem to be there using FTP.

During the installation process I'm also getting an error message "installer has detected another version of SMF already installed with the specified information," but that is not the case. I have one other SMF 2.0 RC3 forum running from another directory using a different database. Any idea what could be happening?

[gbsothere]

I've done several successful test installations of SMF 2.0 RC3 over the past week, using webinstall.php, but today each time I finish the installation and try to connect to the new forum, I get an "unable to load the main_above template" error message. Running repair_settings.php has not resolved the problem, and the required files seem to be there using FTP.

During the installation process I'm also getting an error message "installer has detected another version of SMF already installed with the specified information," but that is not the case. I have one other SMF 2.0 RC3 forum running from another directory using a different database. Any idea what could be happening?

Even though you have all the files present, you might try reuploading a fresh index.template.php from your RC3 zip to .../Themes/default.  It's possible the the file became corrupted during the overwrite. 

As to the installer finding another version of SMF, I wonder if it's possible, if you've used this same browser with each of your several installations, if the old database information became "cached" and that's what the installer is picking up?  What happens if you try to install after a cache dump or, better still, using a different browser?  (Stranger things have happened.)   

[recce101]

I wonder if it's possible, if you've used this same browser with each of your several installations, if the old database information became "cached" and that's what the installer is picking up?

I thought of that too, and verified that my Firefox is set to dump the cache every time it's shut down, which I did before each try. But who knows, and maybe I'll bring out IE7 for a shot at it today.

Last night I was able to successfully install SMF and hook it to a copy of another database which I've been using on my current server. The installation I'm having trouble with is intended to hook to a database which I backed up from another site. I've been partially successful with that, and at the completion of installation all of the messages are available for viewing to a "visitor" (though none of the avatars are visible) but any attempt to login or register brings up either a database error message or a blank screen with the "unable to load the main_above template" statement. I'm thinking the database I'm trying to connect to is corrupted and need to figure out how to check that out. Being new to MySQL I don't yet know how to go about that. I know how to view the table info with phpMyAdmin, but that's about it. Any ideas there?

Thanks for your help.

[gbsothere]

Are you wanting to clone an existing RC3 forum, complete with all its mods, boards, posts, etc., or start fresh with this RC3 that you're installing?  I've been out and about and just returned and I need to get on the same page with you.   

The procedure is a bit different, depending on which  you want to do.

[recce101]

gbsothere:

I'm a volunteer with a nonprofit organization that has an active forum using SMF 2.0 RC1.1. Their site is working okay at the moment, but they're getting ready to move to another hosting company and I want to have an offsite backup in case something goes wrong during the transfer. I have admin privileges at their site, but I defer to others for configuation changes and use my access mainly for moderator-type duties and to download daily backups of the database using Maintenance > Forum Maintenance > Database > Backup Database (with all 3 boxes checked). The resulting sql.gz file is about 10MB.

Right now I don't need to have an exact clone of their forum, but would be happy with just the basic RC3 using the default theme running the latest database backup, so in the event their site goes down during the transfer (or later) all of the messages up to the last backup will be available and members can be redirected to my site (I'll deal with resulting bandwidth issues if and when that happens). In the interim, one of the other administrators and I can use my site to experiment with mods and themes.

I've created a new mySQL database on my shared HostGator server and imported the backup file to there. It completes after a couple of minutes with no errors displayed and 63 tables showing on phpMyAdmin. After running webinstall.php, I also upload and run repair_settings.php to change some incorrect paths, then the site will come up in "visitor" mode, e.g., the boards and messages all available (but no avatars) and the menu at the top limited to Home - Help - Search - Login - Register. Clicking Register brings up the message "Database Error. Please try again. If you come back to this error screen, report the error to an administrator." Trying to login with my valid username and password results either in a "Password incorrect" message or a blank screen with "Unable to load the 'main_above' template." I've tried this on two successive days with different database backups.

I've successfully created a duplicate of another SMF forum which has been on my site for a while, using the same procedures, and they both run fine. I'm therefore suspecting that the database I'm having trouble with is corrupted in some way, and that's where I am at the present time. Thanks for your help,

Ned

[gbsothere]

I'd try using an ftp application like Filezilla.  (Mac users generally use Fetch or Cyberducky.)  Webinstall doesn't always ....  well, there's not always "joy", so I'll be kind.   

I think, if they're running 2.0 RC1.1 and that's the version of your database backup, I would first copy all that forum's files from the present location to your new location.  Then I would go ahead and do a fresh database import into the new site.  After that, I would download the RC3 LARGE upgrade zip, open the zip, then open the folder inside. I would move all those files over to their proper directories in your forum's location on your server, then make them writable (permissions 755 for folders and 644 for files).  Then I would upload the upgrade.php and all the .sql files in the zip's main folder to the forum's root and point your browser to upgrade.php and follow the instructions to upgrade.  It's important to not miss any files, when moving them from the zip to the server.

Running upgrade.php will, of course, update your database to RC3 and should sort any URLs and paths.

(Now, after typing all that, I'm going to glean back over your post one more time and make sure I understood everything you said.)   



EDIT:  reading back over this, yes, you could just have fresh RC3 files...  I doubt if there are any mods, themes, etc., from the old forum that would survive the overwrite, so it's probably not worth the bother of copying their files over, first.

[recce101]

I doubt if there are any mods, themes, etc., from the old forum that would survive the overwrite, so it's probably not worth the bother of copying their files over, first.

Also, I don't have root access to their server at the present time, just admin privileges to the forum through the SMF software. But I'll try downloading the RC3 archive and doing a "manual" install (I use AceFTP, not Filezilla).

While you were writing your response I ran the mySQL Databases check and repain utilities available on my HostGator cpanel with no errors noted, but I still suspect a problem with the database.

Ned

[gbsothere]

Also, I don't have root access to their server at the present time, just admin privileges to the forum through the SMF software. But I'll try downloading the RC3 archive and doing a "manual" install (I use AceFTP, not Filezilla).

While you were writing your response I ran the mySQL Databases check and repain utilities available on my HostGator cpanel with no errors noted, but I still suspect a problem with the database.

Ned

Well.... the thing is that you mentioned using Webinstall which is to install a fresh SMF forum.  But you're working with a database that is 2.0 RC1.1, so you'd need to upload the files, then import that database and then, you'd need to download that RC3 LARGE upgrade zip and use the upgrade.php and the included .sql files located inside its folder (move them to your forum's root and point your browser to upgrade.php) to upgrade that 2.0 RC1.1 database to a RC3 database.  If you have RC3 files but a 2.0 RC1.1 database, you're going to have database errors.  So, after importing, you wouldn't use Webinstall, you'd use the upgrade.php file (in the RC3 zip).  You wouldn't have found errors running your database check, because it's a healthy database; it's just not an RC3 database.  The upgrade has to happen for it to work with RC3 files.

Or have I managed to murky this up, even more?   


Little edit:  you'll save yourself some hassle during the upgrade.php if you first make all the folders and files writable (755 folders/644 files).

[recce101]

If you have RC3 files but a 2.0 RC1.1 database, you're going to have database errors.

Then that must be my problem! Probably the best thing to accomplish my objective is to install 2.0 RC1.1 and use that, not bothering to upgrade to RC3 until the main site does. I believe I saw an archive of old installation files, so I'll look there for RC1.1, unless you have a good link off the top of your head.

Ned

[gbsothere]

Then that must be my problem! Probably the best thing to accomplish my objective is to install 2.0 RC1.1 and use that, not bothering to upgrade to RC3 until the main site does. I believe I saw an archive of old installation files, so I'll look there for RC1.1, unless you have a good link off the top of your head.

Ned

Here ya go! 

http://download.simplemachines.org/?archive;version=47

If you have RC3 files there, now, you may want to completely remove all of them, instead of trying to overwrite them with older files, since some may not overwrite and you'd still have errors.  If you want to stay at 2.0 RC1.1, then I'd go with all fresh (the files in the full install pack) and not have any rogue RC3 files in the mix.   

If you unzip this and move them over, you can just use the repair_settings.php file, instead of install.php, since your backed up database is already in place.

[recce101]

I installed RC1.1 to a clean directory.  But I still got the same main_above template error message after running repair_settings.php, although a check of my Settings.php indicated everything was correct there. Next I'll try a clean install of RC1.1 with an empty database and get that working and backed up before trying to import the database in question. Would you happen to have an old 1.1 database backup lying around that you know is good that I could use for a test? If so I can PM you an email address.

Ned

[gbsothere]

I installed RC1.1 to a clean directory.  But I still got the same main_above template error message after running repair_settings.php, although a check of my Settings.php indicated everything was correct there. Next I'll try a clean install of RC1.1 with an empty database and get that working and backed up before trying to import the database in question. Would you happen to have an old 1.1 database backup lying around that you know is good that I could use for a test? If so I can PM you an email address.

Ned

That is just odd.....   

Before I did anything, I'd go to into phpMyAdmin and select all the tables in that database and choose "Check Tables" from the drop down and see if any are crashed.  It seems odd that you're getting that same error message no matter how many times you upload fresh files.   

If you find any that need repair, you can repair them, then see if you can access your forum.  That may be all you need to do.  Hopefully.  I seriously doubt it's the files, since they're all fresh out of the zip...

*thinking*

Can I get a link to your new forum, that you just installed?  I have a little bit of a hunch about the theme.


(I forgot to answer your question:  I no longer have any older database backups, unfortunately.)


EDIT:  Let me add a bit here, in case I miss you and tell you what I think may be going on.  Since this is a database from the active forum you're trying to back up, I think it's possible that they have a custom theme set as default (not SMF default) and, of course, in the smf_themes table in the database, it would reflect this.  If you've uploaded all new files, then that custom theme's files aren't there, but the database has it chosen as the default theme.  If you can access your database and browse the smf_themes table (or whatever prefix you've assigned to your tables), you should see these columns:

ID_Theme, variable, value

ID_Theme for the forum default will be "1". Under "Value" you should see "SMF Default Theme - Core". In the other rows, you should see the theme URL, images URL and theme directory path.  For default, the Theme URL should end in smf (or whatever your forum folder is called)/Themes/default.  Add /images for the Images URL and, of course, your path should correspond.

All this is a hunch, as I said. 

[gbsothere]

Ned, in case I miss you, read my last post again.  I've edited it.   

[recce101]

If you find any that need repair, you can repair them, then see if you can access your forum.

I anticipated that and did check the database with phpMyAdmin, and all 63 tables checked okay. That was with a fresh backup that I made from the main site today, but it still crashed my 1.1 installation. I have three SMF installations running now, and will have a fourth later:

http://wvpress.com/smf/test01 [nofollow] and .../test02 are RC3 installations.

http://wvpress.com/smf/test03 [nofollow] is the RC1.1 installation with a new database that I just now installed but haven't populated with messages yet, which replaces the 1.1 installation that crashed with the database I'm concerned about. A fourth installation will let me trade backups back and forth, and if there's no problem there, then I still think the backup from the other site has issues of some sort.

I just saw your edit, and I'll check that after dinner.

I really appreciate your help on this!

[gbsothere]

If you find any that need repair, you can repair them, then see if you can access your forum.

I anticipated that and did check the database with phpMyAdmin, and all 63 tables checked okay. That was with a fresh backup that I made from the main site today, but it still crashed my 1.1 installation. I have three SMF installations running now, and will have a fourth later:

http://wvpress.com/smf/test01 and .../test02 are RC3 installations.

http://wvpress.com/smf/test03 is the RC1.1 installation with a new database that I just now installed but haven't populated with messages yet, which replaces the 1.1 installation that crashed with the database I'm concerned about. A fourth installation will let me trade backups back and forth, and if there's no problem there, then I still think the backup from the other site has issues of some sort.

I just saw your edit, and I'll check that after dinner.

I really appreciate your help on this!

All those links are pulling up just fine for me, so I'm not getting the "main_above template" error.  Hmm..  (Oh, wait... these are fresh databases.)

Well, Ned, old man that I am, I'm shuffling off to bed, but I'll check back, bright and early and see how things have progressed.  In the meantime, I'm confident others will glance in and maybe weigh in with suggestions.   

Good luck with it! 

[gbsothere]

Just stopping back by on my way to bed to let you know that I got the PM and answered back.  They're using a custom theme, so if you edit your smf_themes table to set the default as "SMF Default Theme - Core" (and your URLs and paths reflect this) you should be able to get in.   

[recce101]

Got your PM — I think we're getting there. Thanks much,

Ned

[recce101]

Well, sorry to say, that didn't work either. The smf_themes table was already set to SMF Default Theme - Core (strange, since their SMF admin panel shows smFox as the current theme), and the three paths were fixed by the repair_settings.php routine, but it still didn't work. Same blank screen and message about the main_above template. However, I've been able to backup and interchange the newly created databases of the two RC1-1 installations easily (.../test03 and .../test04). I wonder if the conflict between what their database thinks is the current theme and what it really is has something to do with my problem?

Maybe I should post a request for somebody's old RC1-1 database backup and see if I can get that to work.

Ned

[gbsothere]

Good morning, Ned.  Well, that's a disappointment; I thought surely, when I saw their forum, that it was just a matter of editing the themes table.

I know you said you don't presently have access to their server but do you suppose someone who does would zip up the custom theme folder they're using (the one on the server that they've edited) and email it to you?  If so, you may be able to just upload that to .../Themes and get rid of the "main_above template" error that way.

It's odd... I've run across two other "main_above template" errors the past two days.  One member had a simple piece of code deleted from his index.template.php so, in his case, it was the files.  That wouldn't apply to you, since you're uploading all fresh files from the zip.  The other case was a member installing an RC3 theme on a 1.1.11 forum, crashing it, and then having to go into his themes table and edit it so that his forum would come back up.  You've tried that.  (I'm assuming that where you saw "SMF Default Theme - Core" in the table, it was associated with ID_THEME "1"?)

The only other thing I can think of is to provide the custom theme files that are missing, if they'll get you that folder. 

This is a poser, but watch someone else stroll through here with something so simple, I'll toss my laptop into the nearest wall.   

[recce101]

This gets a little involved, so read it when you have the time:

I know you said you don't presently have access to their server but do you suppose someone who does would zip up the custom theme folder they're using (the one on the server that they've edited) and email it to you?  If so, you may be able to just upload that to .../Themes and get rid of the "main_above template" error that way.

Another volunteer administrator is expecting to get server access, and I've set aside some FTP space for him to store the entire directory structure.

I think it's possible that they have a custom theme set as default (not SMF default) and, of course, in the smf_themes table in the database, it would reflect this.  If you've uploaded all new files, then that custom theme's files aren't there, but the database has it chosen as the default theme.

I thought we were onto something here, but now I'm not so sure. I rechecked the admin panel of the site in question, and confirmed that the overall forum default is "smFox - Rediscover SMF." That theme is listed as compatible with SMF 1.1 RC2, not the 2.0 RC1-1 that they're running, and they must have applied some tweaks, because it looks terrible (tabs all squished together, etc.) running "as is" on my Test 03 SMF 2.0 RC1-1 installation — see what I mean at:

http://wvpress.com/smf/test03 [nofollow]

and compare it to .../test04, which is also RC1-1 but running the original "SMF Default Theme - Core."

Next I checked the latest database backup from their site, and the smf_themes table shows id_theme 1 as "SMF Default Theme - Core" and towards the bottom of the table id_theme 2 is "Classic YaBB SE Theme" and id_theme 3 is "Babylon Theme." These are all part of the original RC1-1 installation package, and the current overall forum default theme "smFox - Rediscover SMF" is listed nowhere in the table!

I initially thought this might be the problem, so decided to check the database of my Test 01 installation which is successfully running RC3 with a Halloweenish "ProCurve" theme as the overall forum default. But when I looked at that database, I was surprised to find no mention of "ProCurve" in the smf_themes table, but id_theme 1 listed as "SMF Default Theme - Curve" and id_theme 2 as "Core Theme," again part of the original RC3 installation package. So unless I'm missing something, even a properly functioning database doesn't have any entries for the theme that's actually running on the site.!!??!!

Another thing I hadn't realized, though I guess it's standard and should have realized, is that the avatar images are stored in an "attachments" directory in the site file structure, not in the database, and although they're referenced in the database, the avatars wouldn't be included in a database backup. My Test 01 has one avatar, stored in the .../test01/attachments directory; Test 02 is running from a backup of the Test 01 database, and while the same avatar shows up in its messages, the .../test02/attachments directory is still essentially empty, and the images are pulled from the .../test01/attachments directory.

The same pattern holds with the RC1-1 installations, Test 03 and 04. Test 04, running from a backup of the Test 03 database, shows the same two avatars as Test 03, but they are pulled from the .../test03/attachments directory and were not copied into the attachments directory of Test 04.

So, back to my basic problem, I wonder if the fact that I'm missing the attachments directory of the site I'm trying to semi-mirror, but the backup database is looking for them in an inaccessible location, is causing a glitch?

Meanwhile, I'll email the other administrator and see if he has server access yet.

Ned