Item "as category"

That would be just great!!
We can make reviews "component" with powerful Relation field.

Hello,
benefit of solution is that it will be "clean" and also allow multiple type of relations of each Content Type.

Nevertheless a complete implementation will require some more work
e.g. item's manager support of listing the related items,
and other we may have not anticipated now

This will be added in a timely manner ...

Regards

Hello ggppdk!

ggppdk wrote: Hello,

Micker's suggestion
might work in display your data, but
- You need backend access to create one category per product, and is bit cumbersome to maintain. You could create a link to "review submit that includes the category id", but how do you get this category id?
and even after you get it how do you create the link to the item form that is product review? Furthermore some changes to item form might be needed

I didn't had time to make some serious test, but yes, I came to the same conclusion

ggppdk wrote: Before saying anything further, i need to ask your reviews are complex? , i mean are they more than just a single Text ?

Yes, my reviews are complex. They'll have some combobox fields, some text fields and 5 different ratings (for 5 different properties (plus the relations I've said in my first post). The products are complex too. They'll have the relations (as stated before), images, text fields, radio images etc.

Let me mention also some other "advanced" features/fields:
1. The site'll have multiple languages, so the Products will have multiple languages too. Reviewers will post reviews in their preferred language. If they'll want to, they'll be able to translate their own reviews.
2. The reviews should be "base" or "advanced". The base, simpler review is meant for casual users, while the advanced review is for expert/professional users, who exactly know how to review every single feature.
3. A product in it's information should show it's rating. The rating is calculated by averaging the ratings from all the reviews (in all languages). Obviously, if a review is translated in e.g. 2 languages, it should count as one review, not as two.

This is my ideal site, I don't know if everything is possible, I just wanted to explain to you everything, so you have the whole picture of my idea.

Let me show you a practical example (from a well known review site) of something similar. I have a page with a list of products: www.ciao.co.uk/nf/Mice_Trackball ... 3-mouse~o3
The list could be ordered by rating, reviewer, date added, alphabetically etc. In this list I can see the average rating of the product.

When I click on a particular product I get this: www.ciao.co.uk/Logitech_MX_Mouse__6462472
Product's page with it's features (included average rating), and in the lower part of the page all the related reviews, which could be ordered in different manners (by rating, reviewer, reviewer "reputation" etc.).

Sorry to bother you again, I read this post multiple times:

ggppdk wrote: The idea in little words (a little as i can) is:

e.g.
1. You have 2 Content Types:
- products, reviews

2. You have a relation field assigned to "product" Content Type, which is called "Review"
-- this will list the related reviews in the item view of product item

3. BUT : (here is the change/enhancement)
the relation field besides listing the reviews VIA THE RELATION FIELD "Review" (list can show any field of them, description, etc,)
it will also present a link called:
Add new "Review"
(inside quotes is the label of relation field)

4. This link will have a URL variable e.g.

&relation_field=field_id&relation_item=item_id
(id of relation field and the item id of the product)

and it will open item form of Review and on Save of new "Review" Type item, ... it will update also update the value of "Review" field of the product[/b]

This can be done by adding code to "Relation Reverse" Field that we will assign to "Review" Content Type

Is this already possible, or were you talking about a future functionality? Also, assigning a Relation field to the Product item instead of assigning it to the Review would force me to add a Review, then go to the Product, and edit the relation field by adding the newly added Review. Shouldn't the Relation field be in the Review, and the Inverse relation in the Product?

After forum discussion the idea of what is useful / possible and best way to do it, matures.

The above is for future implementation,

currently we have resources for
- bug fixing
- bug fixing with related minor additions (that require little time), that is tricky to describe ...
- finishing J3.x support
- Installable Content Kits
- Paid projects (... but still supporting FC and enhancing it, is eating up some time now, but well OK, this will be more balanced in time)

In your case you need the functionality now, so i would suggest, finding a component/CCK or even other CMS that supports your needs.

If you have a budget for it and at least one month, i can discuss implementing it now.

FLEXIcontent is great component, it is FREE, has free BUG support (other support should be free but ... anyway) but it does not do everything.

Regards