Closed (fixed)
Project:
Views (for Drupal 7)
Version:
7.x-3.0
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
23 Dec 2011 at 20:05 UTC
Updated:
29 Apr 2013 at 11:42 UTC
Jump to comment: Most recent file
Comments
Comment #1
dawehnerWhat about "never was or will be"? I'm not native so it's hard to say, but in fact it was intended to use was here as well.
Comment #2
mrtoner commentedSure! Actually, it's probably better as "...so update 6013 never was nor will be run." 'Nor' is the proper negation here.
Comment #3
dawehnerDo you want to create a patch for it? Otherwise i will probably do it in some days.
Comment #4
mrtoner commentedYes, I can do a patch, although it'll be the old style. Odd. Does update.php pull the description from the comments in the .install file?
Comment #5
dawehnerYes that's what update.php does, quite fancy...
Comment #6
mrtoner commentedWell, let's give this a shot, then.
Comment #7
dawehnerYou provided a reversed patch. Anyway, committed the patch.
Comment #8
mrtoner commentedDarn! I really hate working on the command line. I got me Gitbox, but haven't learned how to use it yet.
Comment #10
quiethero commentedI am quite confused. If 7300 has to do with human_name field in views_view table and when I go to check the table "human_name" is there already; now what do I do? This will not allow me to update.php and I have literally racked my brains out to find the solution in Drupal 7.21. I cannot update my database.
My Patch will not properly work and I really have no idea what to do in Mysql so since it was already there I left it alone. Is there a line of code I can put somewhere in the views_view and end this madness?
Comment #10.0
quiethero commentedYet another typo fixed.