update.php?op=do_update_nojs breaks with an error:
node_get_types() in /var/www/drupalfixme/database/updates.inc on line 278
Which is obvious, since taht one no longer exists. We thus need a wrapper for this function in updates.inc, i'd say,
Or else the older updates will break.

Comments

Bèr Kessels’s picture

Version: 4.6.3 » 4.7.0-beta1
Bèr Kessels’s picture

update: I was condufes the change was the other way round, node_get_typesis the new one.

The bug is related to the following:
* On tuesdays HEAD, I was developing a module for 4.7. This one was broken, because it still uses 4.6 functions.
* After the upgrade somehow, it held all modules from loading.
* its name is clipper, so all modules with a name after C were not loaded.

This is a rather critical issue. After I poked around in the database all modules are back.

I am not yet sure about this, though, still invesitgating.

Bèr Kessels’s picture

another update: first of all; I was confused, not condufes :)

Anyway, It was not the broken module that kept all others from loading. But an error in the system table.
It seems that table got a database change.
But since, after upgrading the codebase, that change was not yet performed (I still had to run update.php), all modules were removed from the table. resulting in a drupal with no modules present.
Poking around in the database fixed this, slightly.

I have no clue how we can fix this. But it definately is critical.

chx’s picture

Status: Active » Closed (won't fix)

There is nothing to fix here. The system table updates are performed well, if there is a contrib module which behaves erraticly , well contribs to be disabled during update.

Bèr Kessels’s picture

Project: Drupal core » Documentation
Component: database system » Misc
Status: Closed (won't fix) » Active

well
contribs to be disabled during update.

Says who? Is that big-red-bold-lettered stated anywhere? No.

Tresler’s picture

Assigned: Unassigned » Tresler
Priority: Critical » Normal
Status: Active » Postponed (maintainer needs more info)

How is this documentation?

Is this even still an issue?

What action should be taken?

No matter what, I doubt its 'critical' as no action in over a year. Assigned to me for tracking... will won't fix if no response in adequate time.

Tresler’s picture

Status: Postponed (maintainer needs more info) » Closed (won't fix)

told you I'd do it.

anschinsan’s picture

Project: Documentation » Drupal core
Version: 4.7.0-beta1 » 7.x-dev
Component: Misc » documentation