Isn't CCK a dependency of this module? (It doesn't state so)
If not, where the content_fields function should come from?

Comments

jpetso’s picture

jpetso commented

Good point. CCK is not supposed to be a dependency, maybe I have to take additional care to call CCK functions only conditionally.

arhak’s picture

arhak commented

please, don't forget to document which advantage this module takes when CCK is enabled

jpetso’s picture

jpetso commented
Status: Active » Fixed

I removed the CCK dependency in the new 6.x-1.0-rc1 release, thanks for the notice (and sorry for the late fix).

As for additional functionality with CCK, it's like this:
Value Providers needs modules to supply providers ("Views info and the associated parse functions") in their respective hook_value_provider_info() implementations, and those providers can then be used to programmatically access Views results. This module supplies a basic set of providers (more should be added, but I haven't written more yet) and all of the default providers, currently, are for CCK fields.

Therefore, if you use Value Providers without any add-ons *and* with CCK disabled, there won't be any values to access, and the module is useless. However, even without CCK, modules can still supply their own providers, so it does makes sense to remove the CCK dependency. (After all, Value Providers is a developer's module anyways so the developers should get to choose whether they want CCK or not.)

Status: Fixed » Closed (fixed)

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