PHP Fatal error: Class 'views_handler_filter_many_to_one_content' not found

Thanks for this report!
I fixed the naming and I moved the content_taxonomy.views.inc file into the includes folder (not related to this bug report, just wanted to get some order in the content taxonomy folder ;) ). So when updating don't forget to delete the old file and clear your views cache

I have the same problem. I downloaded your new version but don't know exactly what "old file" to remove...

Thanks Rainer

The fix is currently only in the dev-version, not in the beta3.
If you download the dev version you will see that the content_taxonomy.views.inc has moved into the /includes folder (inside the content taxonomy folder)

I've installed your -dev version now but still getting "Fatal error: Class 'content_handler_filter_many_to_one' not found in sites\all\modules\content_taxonomy\includes\content_taxonomy.views.inc on line 9"

I get this message as soon as I activate the "views.module V RC1".

So, where is the class content_handler_filter_many_to_one supposed to be?

Thanks for all your work!
Rainer

Can someone please state the requisite versions of all three modules as required at this date?

Just a quick report-help on this issue to anyone experiencing

to date 10/9/08

- install the latest cck.module RC7
- install content_taxonomy 6.x-1.x-dev instead of the 'stable'
- install Views.module 6.x-1.x-dev instead of the 'stable'
\ don't forget the delete the ones on your server!
- run the update.php (it will update 2 cck tables)
- visit your modules that some related modules might be might be disabled somehow -activate them back.

and this combi works -so far-

except... after all updates, new dev directions, fixes -if you have the link.module on you site, you will only have this new issue
http://drupal.org/node/304267

so many moving parts!
-------------------------
-Drupal development like water pipes each and many module developers holding one -small or big pipe and working hard to the whole plumbing works -and works better.

but its not all the time - in tandem.

While they do they move the parts around to make it better, by-product of this ongoing process time to time moving pipe parts don't fit together to complete the circuit,
as result it -leaks...

- until all joints fit back together again, to keep the community plumbing frame-work :)

That worked for me, thanks ica!
A few hours after installing the dev modules you mentioned, Views 6.x-2.0-rc2 was released. Can I upgrade from Views.module 6.x-1.x-dev or will it crash again because of Content Taxonomy?

Hi there,

I believe that I am having an issue with this, but am not sure and can't find any other leads. The problem is that I am not getting a clear error message like the one above.

I went through the whole Views/CCK/Link and now Content Taxonomy update process today and now I can't put Content Taxonomy fields into a View filter. I get the following error:

Error: handler for node_data_field_sup_or_issue > field_sup_or_issue_value doesn't exist!

Before doing these upgrades I had a view that used these fields and afterward this message was part of the Filter Definition :-(

I am on the following versions:

Core: 6.4
CCK:6.x-2.0-rc7
Views:6.x-2.0-rc2
Content Taxonomy:6.x-1.x-dev (2008-Aug-30)

Does anyone know why this might be happening?

Thanks,
scott

Moonshine,

Sorry I should have mentioned that before. The field is definately a Content Taxonomy field that was valid just before the upgrade. In addition, I even revalidated that the field works in existing nodes and for adding to new nodes (several times because I thought I was going insane! :-p ). Plus I validated that the database has values in it for the field (by viewing the node and by viewing the db tables).

[Edited to add this later]BTW, this is affecting every Content Taxonomy field that I have. I have tried adding three different fields to the Filter, all with the same error message. However, there is no problem adding the Content Taxonomy fields as an argument or a sort parameter. I even tried removing the content_taxonomy.views.inc for the one filter to see if it was causing problems - same error.

The strange thing is that even after removing the invalid stuff from my view filter and trying to readd the field, it is available as a selection in the Fields to Filter list, but when I choose it and select update to get the configuration part, I get that error message.

I'll be attacking the issue again this evening with a fresh mind, but man is it frustrating :-(

Appreciate any help you can give.

Thanks,
scott

Seems like Content Taxonomy needs some updates to be compatible with the new CCK and Views RC.
I try to take a look at this as soon as I have time (hopefully tomorrow or thursday)

thanks for the link.

I made the changes and the Content Taxonomy Module should work now with CCK RC7 and Views RC2/3.
Changes committed to the dev branch - dev snapshot will need a refresh to include the changes.

Keep in mind, that the folders have changed again! Now: content_taxonomy/includes/views. And don't forget to clear your views cache.