I replied to an old thread below, but was unsure if
this was for the same thing.
The listings is a great module, but limited by it's
unstructured handling of listings content. If it were
possible to assign each individual listing to a fatcat
category, and therefore be able to browse listings by
these, it would be fantastic.
Insofar as the classes are concerned, perhaps the
administrator could control the presentation elements
of the "classes", but instead of it being a class it
would in fact be linked to a fatcat categories? So each
fatcat category within the listings would have its
unique presentation class as determined by the admins.
That is to say, for each category in the listings
module, the presentation elements could be administered
by Admins the same way they are now managed as classes.
Is this possible within the scope of the core and the
module's functionality?
The above would make this module so versatile! I have a
community of artists I am implementing a site for, and
this would allow the admin to create a set of fatcat
categories, and where appropriate assign listing's
presentational elements to each category so that each
artist could post their listings in a structured way
(their are some real estate guys that would like to be
able to create categories for property locations), as
well as manage their biographies etc - all of the
things that make this such a fantastic module! And to
top it off, their works would appear in what's related!
Logged In: YES
user_id=1293045
Update: I need to retract the comment regarding structure,
as this is handled by the classes already as I have just
discovered. This module is better than I though.
If only the classes could be linked to 1 or more fatcat
categories, and/or could be generated from a fatcat category
and linked automatically it would be almost heaven on a website!
Logged In: YES
user_id=1071236
I made a hack to assign categories to listings.
Download it here:
http://www.oosterhoff.nu/pws/index.php?
module=documents&JAS_DocumentManager_op=viewDocum
ent&JAS_Document_id=19