× Please submit new Bug Reports on GitHub: github.com/Jensen-Technologies/component-creator-issues/issues

Debate: handling unpublished items

9 jaren 6 maanden geleden - 9 jaren 6 maanden geleden #786 door Jonas Fagnastøl Henriksen
Debate: handling unpublished items werd gestart door Jonas Fagnastøl Henriksen
My view: 
There is a bug in component-creator that allows an unprivileged user access to items that are unpublished and trashed, through the direct link ( similar to http://mysite.no?option=com_mycomponent&view=myview&id=15 ). I regard this a serious issue, and has reported the bug to component-creator. However, Victor, handling the bug report at component-creator, means that the item should be available through the direct link, but not listed in category-listing or similar. He suggested I post the dispute to the forum, so here we are.

It should be noted that all core components in joomla deny unprivileged users to access unpublished and trashed items. 

Everyone in support of not allowing any users to view your trashed or unpublished items, raise your hands!
Laatst bewerkt 9 jaren 6 maanden geleden door Jonas Fagnastøl Henriksen.

Gelieve Inloggen of een account aanmaken om deel te nemen aan het gesprek.

9 jaren 6 maanden geleden #787 door Andres Maeso
Beantwoord door Andres Maeso in topic Bug handling unpublished items
Hi Jonas!

Should I move to the Feature requests forum? I think it will get more traction. And instead of bug, I would write "Debate", so everybody understand their opinion is required.

Let me know and I will do it asap.

Andrés Maeso
Customer relations manager at Joomla Component Creator.

Dit e-mailadres wordt beveiligd tegen spambots. JavaScript dient ingeschakeld te zijn om het te bekijken.

Gelieve Inloggen of een account aanmaken om deel te nemen aan het gesprek.

9 jaren 6 maanden geleden #795 door Randy Carey
Beantwoord door Randy Carey in topic Bug handling unpublished items
I know CC wants to build their components to be aligned with how core components do it.  

It is my understanding that (in core components) the front-end model will not serve up an article if it is not either published or archived.  Here is code from the article model that builds the SQL for retrieving the requested article:
if (is_numeric($published)) {
       $query->where('(a.state = ' . (int) $published . ' OR a.state =' . (int) $archived . ')');
}
Obviously, if a person has permission to edit, delete, or change state on this item, then this person should be able to see the item (at least backend, perhaps front-end as well).  But it seems to me that if an item is not either published or archived, then any front-end link to this item should not display the article (unless it is for the user to edit it), and the model should return an error message similar to how that core components do: 
if (empty($data)) {
     return JError::raiseError(404, JText::_('COM_CONTENT_ERROR_ARTICLE_NOT_FOUND'));
 }
De volgende gebruiker (s) zei dank u: Andres Maeso

Gelieve Inloggen of een account aanmaken om deel te nemen aan het gesprek.

Tijd voor maken pagina: 0.052 seconden
Gemaakt door Kunena

We use cookies so that you can place orders and we can provide a better service. You can control the use of cookies at the individual browser level. If you reject cookies, you may still use our website, but your ability to use some features or areas of our website may be limited.