Currently the .info file identifies tagadelic as a dependency, meaning you have to install it to use community_tags. While I can see that most sites would want to use both modules, and that the tag cloud block obviously need tagadelic, it seems like I should be able to install community_tags on its own.

As long as we're nitpicking, it probably SHOULD list taxonomy as a dependency.

Comments

dropcube’s picture

Assigned: Unassigned » dropcube
Category: bug » feature

I fully agree. Tagadelic is used for tags visualization, but I think that would be good to consider removing the Tagadelic dependency, and provide an alternative visualization if Tagadelic is not enabled.

geodaniel’s picture

I closed #412940: Tagadelic Dependence? as a dup of this.

entrigan’s picture

I think this is an obvious need. I committed views integration, so it is possible that views could provide the alternate visualization.

It may not be trivial to allow for both, since they have different data gathering methods.

coltrane’s picture

Removing tagadelic is proposed in this issue for a 2.x branch #649818: Community Tags 2.0.

Though I'd be OK with the requirement being dropped in the 1.x branch

entrigan’s picture

the reason why I would put it in 2.0 is because in it's current incarnation the Tagadelic display is one of the key features of the module, and I do not want to cause anyone issues when upgrading between minor releases.

chaps2’s picture

Version: 5.x-1.x-dev » 6.x-1.0-beta4
Status: Active » Fixed

Fixed in 6.x-1.0-beta4. If Tagadelic is installed then CT will use it by default but it is not required. Other display options can be selected on the configuration page - currently "none" and "links".

Status: Fixed » Closed (fixed)

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