I saw this mentioned in another issue, but I wanted to give it its own so that people could more easily follow it. Are there any plans to make this module look at multiple content types when determining percent complete and have it displayed in one block? For example, if I have 3 content types being used by content profile to create a user's profile I would like to be able to select fields (as it is set up now) to determine when their profile is complete, but instead of one block and percentage for each content type it would be better to have all three tallied so that the profile is seen as a whole even though it is three seperate content types.

Comments

pvhee’s picture

pvhee commented

Currently this is not possible, but with the ongoing views integration (see #376273: Taxonomy/Views Support and #536406: Cache Content Complete values) this will become possible in the next version of this module.

scalp’s picture

scalp commented

Cool! I look forward to trying it out.

felipe’s picture

felipe commented

Subscribing.

pvhee’s picture

pvhee commented
Status: Active » Fixed

Version 1.2 of the module has been released.

Note that using views you can combine the completeness of various nodes and then display them as you want.

Status: Fixed » Closed (fixed)

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

Arkrep’s picture

Arkrep commented
Status: Closed (fixed) » Active

Would it be possible to give some quick instruction on how to do this?

Arkrep’s picture

Arkrep commented
Status: Active » Fixed

I managed to figure this out.

I ended up using the dev build, not sure if I missed something in the latest stable build, but anyway here's how I achieved it.

I was using the content complete with the content profile module.

Filter: Content Complete: Content type = true

Arguments: UID (basic validation)

Fields: Content Complete: Completeness & Content Complete: Completeness Data

Style: Content Complete ( Grouping field = Completeness)

Status: Fixed » Closed (fixed)

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