In the way you have defined the view with the newer views dev releases there are some issues.

moved the default view function into model.views_default.inc

and it is missing the key when it is added to the views array. namely $views[$view->name] = $view;

small issues i had getting this example going.

PS: thanks saved a fair amount of head ache!

CommentFileSizeAuthor
#3 model-views_bug-1277016-3.patch885 byteswesleydv
#2 model-Fixed_view_name-1277016-2.patch685 bytesDaniel_KM

Comments

dqd’s picture

dqd
Location London | N.Y.C | Paris | Hamburg | Berlin
commented

since views is under heavy development I would suggest you to make the changes by yourself. It will not be possible for a busy maintainer to follow that in every step since views arrives finally.

Daniel_KM’s picture

Daniel_KM commented
Status: Active » Reviewed & tested by the community
StatusFileSize
new model-Fixed_view_name-1277016-2.patch685 bytes

Hi,

Here is the little patch for the view bug to allow the use of two modules based on Model simultaneously.

Sincerely,

Daniel Berthereau
Infodoc & Knowledge management

wesleydv’s picture

wesleydv commented
Status: Reviewed & tested by the community » Needs review
StatusFileSize
new model-views_bug-1277016-3.patch885 bytes

I created a new patch, updating a bit more to be compliant with views 3.0.
Most importantly it removes:

  $views = array();

As this piece of code removes all other views defined in code by other modules.

jackfoust’s picture

jackfoust commented

I wish I would have found this issue 2 hours ago! I was also bitten by using two copies of modified model module where only the last enabled module had its view installed!

ronald_istos’s picture

ronald_istos commented
Issue summary: View changes
Status: Needs review » Fixed

Fixed in related issue #1383916: "Model" view not imported when multiple Models enabled

Status: Fixed » Closed (fixed)

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