Views 1.7 pre-req #2: Write new vocabulary fetcher

On it.

I think these functions need to be re-implemented:

taxonomy_views_node_get_terms
taxonomy_views_node_get_terms_by_vocabulary
taxonomy_get_vocabularies

(Correction to above: taxonomy_node_get_terms and taxonomy_node_get_terms_by_vocabulary need to be reimplemented and I used the names given above in their reimplementation.)

This patch should do it, if I understood the problem correctly.

Thanks webchick for making Earl's requests into issues!

^{benjamin, Agaric Design Collective}

By intentionally avoiding db_rewrite_sql(), then isn't Views providing a potential mechanism for access elevation if a site is using some kind of taxonomy access control module?

I haven't looked at the patch but in contemplating this and the problem aclight raises in #3 I though perhaps a new permission that should perhaps be setup to specifically grant this permission to roles intentionally. I haven't investigated enough to say this is the right way to go.

The reason to avoid db_rewrite_sql here is that rebuilding the cache is completely unrelated to the user who's actually doing it. It's *not* per user. THe cache is supposed to be the total cache of all information that's available.

The actual view that gets run later is still run through db_rewrite_sql, so theoretically taxonomy_access or similar modules should then go ahead and put in their restrictions, thus limiting what is available.

Thanks, Benjamin! I'll look at this more closely later today, after I've had some coffee.

http://drupal.org/node/83490 is duplicate of this.

I tried the patch, but I'm still having the same problem.

I'm using Drupal 5.6

Cheers for this patch, it resloved the issues I was having with some views becoming corrupt and a MySQL error in the log.

Details about my issue here: http://drupal.org/node/312138

Drupal 5.12, Views 5.x-1.6, MySQL database 5.0.51a, PHP 5.2.4-2ubuntu5.3...

The patch appeared to work for us, and would for a period of time with exposed filters, however after a time memory would fill (presumably from cache) and our site would go down. We ended up removing the patch and backing off using exposed filters on our calendar view.

We are also using Taxonomy Access Control, the exposed filter was using a calendar category on Calendar (5.x-2.5) View

Subscribing. Patch working so far.

I just downloaded 1.7 and it looks like this patch never made it.

Patch against 1.7 attached.

1.7 was released due to the security issue. I'm not actually maintaining Views 1, except that I kind of had to do that. The actual 1.7 maintainer has kind of bailed on it. So I dunno if anyone will ever look at this.

No problem, I am actually upgrading all my modules in preparation for a move to D6.

At this time, only security fixes will be made to the 5.x version of Views.