Judah Raine
Total posts: 332
26 Sep 2012 10:47

Hi there, just upgraded my site to Joomla 2.5 and installed Cobalt, and now creating... I intend using Joomla core for standard ïnformation type pages, and using Cobalt for my reviews section as I need authors/publishers to submit their books online and my reviewers to submit their reviews.

BUT, and this is my concern: Both sections (review requests and reviews) will obviously have the same categories, e.g. a review request will be submitted to category historical, and the final review will of necessity have to have the same category.

For review requests, the submissions are public, but only the reviewers may see and search these categories. For reviews only the reviewers may submit and the articles are for public viewing.

I do not want someone searching the review categories to find any links to review requests, i.e. i need to specify on the reviews page what section the readers may search.

Is this possible or will having the same categories confuse the issue? Would it be better to make some change to the category name, or will having a similar word, e.g. historical, in both section's categories be a problem. I'd appreciate your response as I would like to proceed with these, but don't want to go to all that work if I have to work in a different category name altogether.

It also occurs to me that I may in the future have overlapping categories between Joomla and Cobalt, i.e. with same/similar names. How will this affect the searches and permissions?

Many thanks, and please bear with me, I'm totally new to J25 and Cobalt.

Last Modified: 18 Sep 2021


Sergey
Total posts: 13,743
26 Sep 2012 21:19

For review requests, the submissions are public, but only the reviewers may see and search these categories. For reviews only the reviewers may submit and the articles are for public viewing.

I think you can make everything within one section and one type. When publiс try to submit this type it is request because he see only request field. But when reviewer edit it it have review fields. Thus request is transformed into review.

But what I would do, I would make books and reviews sections all Cobalt based. Then you have only one category structure. Reviews are not categorised any more. They are only children of books and inherit books category structure. YOu see list of the reviews right under he book description. Buttons to adв new review is also there. This will be ideal and easier to migrate later. And also book search will be much easier by different fields.


Judah Raine
Total posts: 332
26 Sep 2012 23:31

Thank you, I will try this and get back to you if I run into problems :)


Judah Raine
Total posts: 332
27 Sep 2012 01:06

So sorry, I'm a little confused.... I create a single category. To this public can add article (review request). At this point I need the reviewers only to access the article in the frontend, select a book and download (one download only allowed per book). It is critical that this step allows only registered, logged in reviewers to access the article. Once they have read the book, only reviewers can go in (frontend) and add the required information, i.e. review and rating. Once published, the article is then once again available to the public for viewing.

I have most likely missed something here and do apologise, but I'm not sure how to make it restricted during the review selection and creation stage. Will the search not reveal these to everyone when they search in the completed reviews? I thought that perhaps in the unpublished stage they would not show, but how do the reviewers then find the articles to do what they need to do?

I would greatly appreciate your help with this, thank you so much :)


Sergey
Total posts: 13,743
27 Sep 2012 19:59

I have most likely missed something here and do apologise, but I'm not sure how to make it restricted during the review selection and creation stage.

What I would do

  1. Create new user group name it reviewers.

  2. Creale new access level called reviewers and add this group to this access level.

  3. When create field upload for uploading book allow download(or even view) only for access level (AL) reviewers

  4. When create content type review the fields that contain review itself set AL reviewers

  5. When reviewer add review he have to change article ownership to him, so field author in form template parameters have to be set AL reviewers. And if not set Author can edit = no, and moderators AL reviewers. It is another way.

How to combine review request and review itself in one type.

You create one type. By default you set Who can view = AL reviewers. This wil make it so that after public created new article it is not visible by anyone but reviewers. When he create article he only see one textarea with default text in it.

Please, add a review for this article.

He can add some extra or just click submit.

Then reviewers come and see all requests. They download, read, edit review. When they edit they change authorship and AL to public. They have special fields to add review that are editable only by AL reviewers and visible to public.


Judah Raine
Total posts: 332
27 Sep 2012 22:43

Oh :) Sound so simple. Thank you once again, I will give this a try.


Judah Raine
Total posts: 332
20 Oct 2012 06:53

Hi there, I have been delayed with this project and now wanting to resume. I need to please clarify something... If I wish to have the review files uploaded and then downloaded by a reviewer, will I need to purchase a separate field module and which one, upload or download?? An urgent answer would be appreciated


Sergey
Total posts: 13,743
20 Oct 2012 22:23

Uregent answer on Sunday.

Yes you awill have to purchase uoloads field. It handle both download and upload process. But if you want to sell yorbdownloads you willl need pay to download foeld.

Powered by Cobalt