error getting into admin - DEFAULT_THEME/templates is not a directory.

[sjbt]

I upgraded to 2.8 but can't log in to the admin panel.

Is this a new template directory structure? "DEFAULT_THEME/templates

I created those directories in the templates directory and it gave me this error -
public_html/templates/DEFAULT_THEME/templates/header.htt does not exist

I'm not aware that we need a header.htt in the template files either.

Can you point me to an explanation or fix for this?

Thanks!

[rabsaul]

Has no one answered this question? I have the same problem. I got the first message, then manually created a "templates" directory inside /templates/wb_theme/ , and now get the second message:

Template Error: filename: file [full path] .... /templates/wb_theme/templates/header.htt does not exist.
Halted.

Need help with this ASAP.

[rabsaul]

Nevermind. Apparently that directory hadn't uploaded. Weird that it happened to two of us.

[buuzta]

  For real that's weird. After upgrading from 2.7 to 2.8 I've got the same error.

[Luisehahne]

Do you run the upgrade-script.php?

Dietmar

[snerpton]

Did anyone manage to solve this? I upgraded from a working 2.7 installation to 2.8 and get the same error:

Code:

Template Error: filename: file /home/username/public_html/wb/templates/wb_theme/templates/login.htt does not exist.
Halted.

I successfully ran upgrade-script.php. Any help would be much appreciated.

Many thanks,

Chris

[doc]

Hi,

seems not all WB 2.8 files were transferred to the server.
Check via Ftp for a file called: "wb/templates/wb_theme/templates/login.htt".

If the file does not exist, the "upgrade" was not completed (maybe timeout of your FTP tool etc.).

Doc

[snerpton]

Thanks for the quick reply.

You were absolutely right, wb/templates/wb_theme/templates was empty. I re-uploaded and everything works just fine now.

Many thanks,

Chris

[pszilard]

Code:

/templates//templates is not a directory.

I am getting the above message and cannot log in to admin. Please note the double //

I have checked and all of the files have been successfully uploaded, and when I re-run the upgrade script, it ends with

Code:

Add default settings to database for news section_id= 185
Database data header added successfully
Database data post_loop added successfully
Database data footer added successfully
Database data post_header added successfully
Database data post_footer added successfully
Database data comments_header added successfully
Database data comments_loop added successfully
Database data comments_footer added successfully
Database data comments_page added successfully
Upgrade existings postfiles to new format

Template Error: set_root: /home2/remektek/public_html/_remektek/templates//templates is not a directory.
Halted.

As I am now completely stuffed, I would really love some one to help! Please.

[pszilard]

PLEEASE, any one to help?

[pszilard]

Well, I am disappointed that no-one had offered any help.

However I managed to fix the problem myself! I thought I'll share in case it helps someone else.

Recap of my situation
I had moved my site from a local ISP to Hostmonster (aka Bluehost), where it is defined as an Add-On domain. I had already moved 1/2 a dozen WB sites this way before. This time the migration went well too. until I decided to upgrade WB from 2.7 to 2.8.1, when all these problems started happening and I couldn't log in to the back end. The front was still working, however.

The solution
I was lucky in that I had a QNAP 109 Pro II single drive NAS device which has LAMP features built in. So I installed my site from the backup, to the local QNAP, which went without a hitch.

Then I did the upgrade. Got new error that it couldn't find DAFAULT_THEME/templates so I copied the "simple" template folder and renamed it to DEFAULT_THEME and ran the script again.

This now completed with no errors. I could operate the back end which confirmed v2.8.1, so I the ftp-ed the entire site up to the server, but still got the usual error on trying to log in.

Next I dumped the MySQL from the QNAP's upgraded site and dropped the server's tables and imported the converted data set from the QNAP. Bingo! All seems to work now!

Didn't track down the problem, but got a solution. It also looks like there is bug in the upgrade process re this DEFAULT_THEME.

[mjm4842]

Hi Paul,

I suspect that the setting for the backend theme may have got lost in the upgrade for some unknown reason. This value is the default_theme entry in the settings table of your sites database. Although your bandage solution worked, it did not resolve the problem. As such, it is very likely that you will experience issues again in the future if left unfixed.

The good news is that you should be able to fix this by completing the instructions below. For the benefit of everyone who might read this in the future, I have included both a solution for you and for those who still can't get into their admin backend site.

If your admin backend site is now working

1) Go into your WebsiteBaker Settings
2) Change the Backend-Theme in the Default Settings section to "classic_theme" or "wb_theme" and save.
3) You can then go and change it back to the argos_theme again.

One everything is working again, you should be able to safely delete your DEFAULT_THEME foder. Should this not work for you, I would recommend that you delete the contents of that folder and replace it with a copy of the classic_theme folder instead. The reason is that the "simple" template folder that you copied was a frontend template while the classic_theme folder is a backend template. Since this is a backend template issue, it makes more sense to have files for a backend theme in the DEFAULT_THEME directory.

If your backend admin site is NOT working

1) Start phpMyAdmin. How you get into phpMyAdmin will vary depending on your web hosting provider.

You may be prompted for a username and password depending on your hosting provider. If you are trying this out on a local copy using Server2Go (and possibly WebsiteBaker Portable Edition), by default the username is root and here is no password.

2) Select the name of your database in the left side column. If you don't know what it is, you can find it in the file called "config.php" located in the root of your website.

3) Click on the "settings" table in the left hand column.

4) Click the SQL tab near the top of the window.

5) Copy and paste the following code into the SQL query/queries on database field:

If you use the default backend theme, use this line:

  UPDATE `settings` SET `value` = 'wb_theme' WHERE `name` = 'default_theme'

If you use the Argos backend theme, us this line:

  UPDATE `settings` SET `value` = 'argos_theme' WHERE `name` = 'default_theme'

Click the Go button to run the SQL command. Be sure to check the green bar at the top after. It should say  "1 row(s) affected."

If you see a message that says "0 row(s) affected.", use the following SQL command instead:

INSERT into `settings` (`setting_id` ,`name` ,`value`) VALUES (NULL , 'default_theme', 'wb_theme');

Verifying the setting

You can verify the value associated with the default_theme field by clicking on the browse tab. Keep in mind when checking this name and value pair in the table that there are at least two screens of entries in the table and that the "default_theme" is likely on the second page. You can get to the second page by clicking on either the > or the >>[ buttons on this page.

Hopefully the above information will help resolve your issue so that you won't have problems upgrading in the future.

With best regards,

Michael Milette

[pszilard]

My backend theme was wb_theme. Anyway, I switched it, saved it and switched back again.

Thanks for your help.

[gaolin100]

You were absolutely right, wb/templates/wb_theme/templates was empty. I re-uploaded and everything works just fine now.

[ereemst]

Thx that did the trick BUT, now in the admin of wb i dont see the them anymore to explain
i see the frontend template and right onder there there should be the scroll screen that say WB theme or default theme i dont know but its empty and if i click the arrow next to it its empty?

See pic for more explanation