Closed (fixed)
Project:
Views (for Drupal 7)
Version:
7.x-3.1
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
29 Mar 2011 at 06:20 UTC
Updated:
29 Feb 2012 at 19:00 UTC
Jump to comment: Most recent file
Comments
Comment #1
dawehnerWhy would core run views_update_6000(), this really confused me.
Did you jumped from drupal5 to drupal7?
In general this seems to be a duplicate of #765364: views module Update field .views_display
There the update functions will get updated/removed because we don't need them here anymore.
Comment #2
slimandslam commentedThe database is an updated D6 so it might have some old stuff in it, but, if I ever had the views module installed before, it must have been years ago. I don't know why the D7 views module is updating anything.
Comment #3
slimandslam commentedComment #4
slimandslam commentedI don't see that this is a duplicate of the indicated issue. Please address THIS error message.
You call a function, _drupal_initialize_schema(), that does not exist anywhere in Drupal 7.
Comment #5
bojanz commented@dereine
Before upgrading to D7, you need to have the latest version of D6 + contrib modules, right?
So why are we even keeping the D6 code in there?
Comment #6
dawehnerI'm not sure anymore but afaik we wanted to require 6.x-2.x-11/12 before the update so we can remove a bunch of update functions.
Comment #7
merlinofchaos commentedIf you never had Views installed on D6, you don't need the update code to run. I recommend you skip the update.php stuff, disable the views module, uninstall it using the modules admin, and then re-enable it. That should get rid of all of the update issues for you.
Comment #9
wardv commentedThis bug should not have been closed, it still exists.
The comment in #7 does not help if you ever had views enabled in D5 or D6. In that case, you really need to run the updates.
I've attached a patch that removes the problematic updates (only) for people in this situation. It fixed the problems for us.
Comment #10
dawehnerYou know posting a patch somehow should use the rules of drupal codestyle etc. Sorry but these are sort of required.
Here is a proper patch for this issue.
Comment #11
dawehnerJust committed that patch