I'm stumped. I've been trying to upgrade views 6.2.11 to 6.x-3.0-alpha3, mostly because of the better exposed filters handling and the reset button. Using 6.19 core. No matter what I do it keeps telling me that I'm using 6.2.11. I've tried disabling and uninstalling the views module with no success. My system table is reporting the below error, and I think that is a key somehow, but I'm not sure how to fix it. I can't find any stray Views directories with 6.2.11 code. Any help would be appreciated!

('sites/all/modules/viewsCAUSEDERRORS/views.module', 'views', 'module', '', 1, 0, 0, 6009, 10, 'a:10:{s:4:"name";s:5:"Views";s:11:"description";s:55:"Create customized lists and queries from your database.";s:7:"package";s:5:"Views";s:4:"core";s:3:"6.x";s:7:"version";s:8:"6.x-2.11";s:7:"project";s:5:"views";s:9:"datestamp";s:10:"1276743614";s:12:"dependencies";a:0:{}s:10:"dependents";a:0:{}s:3:"php";s:5:"4.3.5";}'),
('sites/all/modules/viewsCAUSEDERRORS/views_export/views_export.module', 'views_export', 'module', '', 1, 0, 0, 0, 0, 'a:10:{s:4:"name";s:14:"Views exporter";s:11:"description";s:40:"Allows exporting multiple views at once.";s:7:"package";s:5:"Views";s:12:"dependencies";a:1:{i:0;s:5:"views";}s:4:"core";s:3:"6.x";s:7:"version";s:8:"6.x-2.11";s:7:"project";s:5:"views";s:9:"datestamp";s:10:"1276743614";s:10:"dependents";a:0:{}s:3:"php";s:5:"4.3.5";}'),
('sites/all/modules/viewsCAUSEDERRORS/views_ui.module', 'views_ui', 'module', '', 1, 0, 0, 0, 0, 'a:10:{s:4:"name";s:8:"Views UI";s:11:"description";s:93:"Administrative interface to views. Without this module, you cannot create or edit your views.";s:7:"package";s:5:"Views";s:4:"core";s:3:"6.x";s:12:"dependencies";a:1:{i:0;s:5:"views";}s:7:"version";s:8:"6.x-2.11";s:7:"project";s:5:"views";s:9:"datestamp";s:10:"1276743614";s:10:"dependents";a:0:{}s:3:"php";s:5:"4.3.5";}'),

Comments

Letharion’s picture

Assigned: Unassigned » esmerel

While waiting for more sophisticated answer, I suggest reverting to a backup, trying again, and describing in greater detail how you perform the upgrade :)

merlinofchaos’s picture

Status: Active » Fixed

sites/all/modules/viewsCAUSEDERRORS/views.module'

I'm going to make a couple of guesses based upon this filename.

Instead of deleting yoru views directory, you moved it to viewsCAUSEDERRORS. Do you still have a sites/all/modules/views directory as well?

Drupal is only capable of seeing one of these modules within any of its various modules directories. The first one it sees is the one that it accepts. You must make sure you have no other copies of views within any modules directory. If you want to back it up, move it outside of your Drupal installation. That should ensure that it only sees the newest one.

esmerel’s picture

Assigned: esmerel » Unassigned
styledata@yahoo.com’s picture

I do have a sites/all/modules/views directory, and it has the 6.x-3.0-alpha3 module in it. I have scoured elsewhere to make sure there are no other views directories, and I don't see any. Is it possible that when there was a foulup a couple months back, that the CAUSEDERRORS statement was written to the database and has never been resolved? Can I modify those statements to be correct, and if so, how might that read?
Thank you

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.