My site is gone away and nobody can help me?

By mdroste on 20 Apr 2006 at 16:10 UTC

I don't want to duplicate my post: http://drupal.org/node/59540
Please read my original thread. I really need help.

Thanks

meinolf

Comments

Re: Can't login after update to 4.7-rc 3

gdip commented 20 April 2006 at 16:16

I get access denied when trying to visit your site!

Try to register

mdroste commented 20 April 2006 at 16:33

Please, try to register with /user/register or simply click on a category at the top of the site and take a look at the result.

meinolf
--
go with us - learn php

--
mdwp*

Could register but it wouldn't let me log in. When I se the page listings I strongly believe there's something screwed up in your database. I got a similar result yesterday which turned out to be caused by my repair attemps of the .MYI files.
I have absolutely no clue to why Drupal got screwed up when I repaired the tables. I had to use the backup to fix it (and not attempting to repair it again!).

Does Drupal identify the correct update version for your database or do you have to choose it manually?

System module 133

mdroste commented 20 April 2006 at 17:42

Update.php says: "The version of Drupal you are updating from has been automatically detected. You can select a different version, but you should not need to."

and in the dropdown box "select version" there is a default value of 133.

Believe me the database is full of content. Over 2000 node and 300 users.
One can see the nodes and the pager at the bottom of the site.
But instead of content there is only "by Gast (anonymus) n/a".

I don't have any content on my site by anonymus users. Only registered users posted articles during the last year.

meinolf
--
go with us - learn php

--
mdwp*

Is it something wrong with

gdip commented 20 April 2006 at 19:39

Is it something wrong with your database backup?

What happens if you use your backup for the old (working) version of Drupal?
Do you get a working site then?

If you have a working old version of the site please make sure you don't overwrite that database with the backup!!!

I don't think so

mdroste commented 20 April 2006 at 19:50

Before I've updated to 4.7 rc3 yesterday I've make a dump with mysqldump.
I overwrite the original database of my site with update.php.

How can I upgrade to a newer version of Drupal without this?
And therefore we make backups of our original database.

Hm, but what - and it seems this happens to my site - when the backup not work?
I dont't know.

meinolf
--
go with us - learn php

--
mdwp*

I tried to login a couple of

gdip commented 20 April 2006 at 20:01

I tried to login a couple of minutes ago but it didn't work.
Can you upload a gzipped or zipped version somewhere so I can download it and test it on my server?

You can mail me the web address via my contact form.

Now I can login

mdroste commented 20 April 2006 at 21:08

After update from 128 I can login and have full access to administration.
But all nodes still don't show (or generate) their content.

meinolf
--
go with us - learn php

--
mdwp*

Try 128

heine commented 20 April 2006 at 19:54

Can you try updating from 128?

Can you tell a bit more about the upgrade history of this site?

--
Tips for posting to the forums.
When your problem is solved, please post a follow-up to the thread you started.

128?

mdroste commented 20 April 2006 at 20:03

Do you mean the system version in the dropdown box of the update.php page?

History:
I started with 4.5 last year, updates to all 4.6 versions follows.
And yesterday the update to 4.7rc3.

meinolf
--
go with us - learn php

--
mdwp*

4.6.6?

heine commented 20 April 2006 at 20:09

Yes the system version. In the other thread you wrote that you were updating from 4.63 to 4.7-rc3. Is that correct or should it be from 4.6.6 to 4.7-rc3?

--
Tips for posting to the forums.
When your problem is solved, please post a follow-up to the thread you started.

One step forward

mdroste commented 20 April 2006 at 20:13

Yes you mean this.

And - after updated from 128 I CAN LOGIN to my site.

But, at this moment there is still no content. Just empty nodes.

But I have full access to the administration. One big step.

And why this all happens?

meinolf
--
go with us - learn php

--
mdwp*

No idea

heine commented 20 April 2006 at 20:16

And you've got a nice warning:

Warning: Unknown column 'sid' in 'field list' query: INSERT INTO accesslog (title, path, url, hostname, uid, sid, timer, timestamp) values('', 'node', 'http://drupal.org/node/59599', '85.144.200.67', 0, 'effdd6d54824798fdc5c2f02fbd1a676', 108, 1145564052) in /home/htdocs/web0/html/includes/database.mysql.inc on line 120

Can you post all errors you got during / after the update? Post them between <code>-tags.

No added sid column, would mean that system_update_148() didn't happen.
--
Tips for posting to the forums.
When your problem is solved, please post a follow-up to the thread you started.

Since I was on 4.6.6 when I

sepeck commented 20 April 2006 at 20:36

Since I was on 4.6.6 when I updated, I manually slected update 131 and had no issues when I did that.

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
_{Drupal Best Practices Guide}

Nice warnings

mdroste commented 20 April 2006 at 20:37

Here are the most common errors:

Table 'usr_web0_1.node_revisions' doesn't exist query: SELECT n.nid, n.vid, n.type, n.status, n.created, n.changed, n.comment, n.promote, n.moderate, n.sticky, r.timestamp AS revision_timestamp, r.title, r.body, r.teaser, r.log, r.format, u.uid, u.name, u.picture, u.data FROM node n INNER JOIN users u ON u.uid = n.uid INNER JOIN node_revisions r ON r.vid = n.vid WHERE n.nid = 2139 in /home/htdocs/web0/html/includes/database.mysql.inc on line 120.

Unknown column 'theme' in 'where clause' query: SELECT * FROM blocks WHERE theme = 'lincolns_revenge' AND status = 1 ORDER BY region, weight, module in /home/htdocs/web0/html/includes/database.mysql.inc on line 120

meinolf
--
go with us - learn php

--
mdwp*

Be sure to follow the guidelines

heine commented 20 April 2006 at 21:17

Interesting I also saw:

Warning: Unknown column 'cache' in 'field list' query: INSERT INTO sessions (sid, uid, cache, hostname, session, timestamp) VALUES ('effdd6d54824798fdc5c2f02fbd1a676', 0, 0, '85.144.200.67', '', 1145567562) in /home/htdocs/web0/html/includes/database.mysql.inc on line 120

This may mean you experience similar issues as someone else: http://drupal.org/node/58215

1 Right now I'm mostly interested in errors you see during the update.
2 Also, what was the drupal version you are updating from (one thread says 4.6.6, other 4.6.3)
3 Please describe (in detail) what upgrade procedure you follow.

As to 3, make sure you login before deleting old files, switch back to bluemarine, delete all 4.6 files (except your own files).
--
Tips for posting to the forums.
When your problem is solved, please post a follow-up to the thread you started.

Looks better now

heine commented 20 April 2006 at 21:33

The site looks a lot better now: how did you solve the problem?
--
Tips for posting to the forums.
When your problem is solved, please post a follow-up to the thread you started.

131

mdroste commented 20 April 2006 at 21:48

Yes - step by step my site looks a little bit better.
I follow the tip of sepeck and use system module 131 for update.php.
But how can one know this? Should I try the next one?
Is this a try and error update? What are my errors?

In my opinion we've found a bug in the update.php.

Anyway - I still miss the content of my nodes.

And, of course thanks to all who help me upon this step.

meinolf
--
go with us - learn php

--
mdwp*

What's that

mdroste commented 20 April 2006 at 22:01

After I make the update with 131 the content of all nodes was still gone.

And now - without making anything else - the content is there!

Miraculix at work???

Lets talk about the update procedure (128 to ...) so that other users don't have this trouble.

And again, thanks to all!

meinolf
--
go with us - learn php

--
mdwp*

Here are the steps I used to

sepeck commented 20 April 2006 at 22:08

Here are the steps I used to identify the update I used
http://www.blkmtn.org/node/325

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
_{Drupal Best Practices Guide}

Other interesting things

mdroste commented 20 April 2006 at 22:18

What you can see at my site in the primary navigation, is not the state my site has before I update to 4.7 yesterday. Where does the items come from? In the middle of the last year that was my primary navigation. No joke!

meinolf
--
go with us - learn php

--
mdwp*

There are still strange things

mdroste commented 20 April 2006 at 22:44

Take a look at my site mission (yellow block at the top of the page). Very small size.
I've set the font-size in a inline style (no good practice - I know). So, I go to admin -- settings, change the inline style and save it. After that the german characters (Umlaute) are gone.

If I go back to the frontpage and make a reload - all just fine - but no changes are saved to the mission block.

Maybe this is a issue of my theme - it's a cutomized version of lincolns - not prepared for 4.7.

meinolf
--
go with us - learn php

--
mdwp*

Primary and secondary links

sepeck commented 20 April 2006 at 23:10

Primary and secondary links is not the same anymore.
Switch to Blue Marine as was suggested earlier.

Here are a list of some of the differences
http://drupal.org/node/57649

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
_{Drupal Best Practices Guide}

I know

mdroste commented 20 April 2006 at 23:31

As I said at the beginning of this thread I have good working versions of 4.7 beta at my sites:
www.swf-info.de
www.joblooker.de
www.learn-php.de

It's a multisite installation of Drupal. Until yesterday these sites runs with 4.7 beta.
Now with 4.7-rc3. The problems I describe in this thread only happens to my site
www.go-with-us.de

But where and why old items of my primary navigation (long, long ago) are stored in the database.
And rebuild with 4.7-rc3. I've found them all here: -- admin -- menu -- primary navigation.

meinolf
--
go with us - learn php

--
mdwp*

In the link I provided is

sepeck commented 20 April 2006 at 23:37

In the link I provided is this one
Primary/secondary links now part of the menu system or did I not understand something?

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
_{Drupal Best Practices Guide}

Sorry

mdroste commented 20 April 2006 at 23:56

for my bad english.
I know that primary and secondary navigation are now part of the menu system. And that is good.

In Drupal 4.6 I setup a primary navigation in admin/themes/settings. In the middle of last year I setup a navigation for my theme like this
"features", "help" , "faq" , "impressum", "sitemap", "feedback"

At the end of last year I change it to "Home", "FAQ", "Impressum".

At the end of this long day - after I'm able to recover my site I've updated to 4.7-rc3 -
the OLD items "features", "help" , "faq" , "impressum", "sitemap", "feedback" were shown as a part of the global menu system.

Where do they come from? I've deleted this items a few month ago.

meinolf
--
go with us - learn php

--
mdwp*

At a guess, and this is just

sepeck commented 21 April 2006 at 00:16

At a guess, and this is just a guess.... perhaps they were still listed in your xtemplate based themes? If they were still present though inactive then the script would have tried to migrate them for you.

That might be your explanation.

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
_{Drupal Best Practices Guide}

Wow

mdroste commented 21 April 2006 at 00:27

That's possible. I think one of my first themes was xtemplate based.
But if so - is this a good practice for a update script?

I'm a "believer" of Drupal, but I think some of these issues we've discused today are "no-goes" for many companies, specially for big enterprises.

meinolf
--
go with us - learn php

--
mdwp*

I disagree. The XTemplate

sepeck commented 21 April 2006 at 00:52

I disagree. The XTemplate was the default engine. The contrib template engine phptemplate handled links differently. There is only so much testing and automation that can happen by script. One of the first ideas was to just not migrate them and people would have to do so by hand. But hue and cry was raised and some migration scripts worked out, so it's a best effort automation. It worked for the most part on my sites with only minor tweaks needed.

That's why everyone should have a backup and migrate on a test site first. Also, if you have a custom theme, you are definitaly going to have to update it first if the look and feel of your site is important. Now if you are using PHPTemplate based theme's then there should be less to update but there are still changes.

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
_{Drupal Best Practices Guide}

Thread feedback - Information

heine commented 21 April 2006 at 07:08

Hi meinolf,

Some feedback: You've given almost no information to determine what might have been the problem; for example the exact version you're upgrading from is still not clear to me.

While your problem may be solved, this thread does nothing to solve the bigger problem (if it exists).
--
Tips for posting to the forums.
When your problem is solved, please post a follow-up to the thread you started.

How can I

mdroste commented 21 April 2006 at 08:54

I really like to give you the information you need to clarify the problems.
But how can I get the exact version of my last update - month ago.

That's one thing I've learned - make notes about your updates.

And I think the automatic version detection of the update.php failed. And if it is possible - as in my case -
that a site is unusable after that, than bigger problem exists.

So I really would like to help to solve it.

meinolf
--
go with us - learn php

--
mdwp*

Thanks

heine commented 23 April 2006 at 12:08

It took me some time to locate the thread again.

Thank you for your offer! Could you send me a stripped down version (most nodes removed, admin pwd removed) of your database together with the files from your drupal installation (zipped/7-zipped)? If you include a step by step description of your upgrade attempts, I can take a detailed look at it (provided I have sufficient time the coming week).

E-mail: h.deelstra@gmx.net

--
Tips for posting to the forums.
When your problem is solved, please post a follow-up to the thread you started.

I'll send you a mail in the middle of the week

mdroste commented 24 April 2006 at 07:35

meinolf
--
go with us - learn php

--
mdwp*

My site is gone away and nobody can help me?

Comments

New forum topics