gProximity incompatible with default views

Ryan Palmer - February 9, 2009 - 18:04
Project:gProximity
Version:5.x-1.x-dev
Component:Code
Category:bug report
Priority:normal
Assigned:Unassigned
Status:won't fix
Description

I have some gProximity views that I exported so that they may be stored in code as per the following tutorial:
http://shellmultimedia.com/articles/managing-your-views-code

This seems to work well with every other kind of view, but breaks with gProximity. I get the following error when trying to access the view:

This View's fields have been changed or just created. Please go here and update/add fields for this gProximity view.

It seems that gproximity relies heavily on the contents of {view_view} table which does not contain info on default views stored in code, and cached in {cache_views} table.

The only work-around I can think of involves the following:

  • Change the gpid to be the name of the view instead of the vid, because default views don't have a vid, only a name. This impacts just about everything else, it would seem (admin menu paths, etc).
  • Pull in views configuration data from the cache_views table instead of view_view table. There are 4 direct queries to the {view_view} table in the module.

This refactoring sounds quite complex, which is fine, but I would want refactor in consultation with the module maintainer(s). Thoughts?

#1

greenSkin - August 13, 2009 - 17:13
Status:active» fixed

Sorry, inadvertently changed status to 'fixed'.

#2

greenSkin - August 13, 2009 - 17:13
Status:fixed» won't fix

Won't fix for this version of gProximity.

 
 

Drupal is a registered trademark of Dries Buytaert.