Allowing users to make their assets live

(Richard Crompton) #1

Hi

 

We have some site functionality that allows registered users to create articles and specify where on the site it will be displayed.

 

Because we don't have the resources to approve the content of the articles, we arn't going to use workflow.

 

With the use of triggers to change the status of the asset, their article management screen allows them to preview, edit, publish and archive the articles.

 

In order for them to publish their article, I've set the trigger to ignore permissions (as a sys admin user needs permission to do this), but am not happy with this solution.

 

Can you suggest another way to do this?

 

Thanks

(Nic Hubbard) #2

In order for them to publish their article, I've set the trigger to ignore permissions (as a sys admin user needs permission to do this), but am not happy with this solution.

 

Can you suggest another way to do this?

 

Why aren't you happy with this solution?

 

You can give the users write permission to the articles, that way they will have the permissions to make the status change. They could do this in simple edit or using that same trigger.

(Richard Crompton) #3

Hi Nic

 

The write permission won't allow the users to change the status of thier assets to Live or Archived.

 

I've allowed the user to have admin permission on their assets only and seems to have solved this issue.

(Richard Crompton) #4

Hi Nic

 

I am encountered a wierd issue with the triggers though.

There are 2 (both very similar):

  • Archived into Under Construction
  • Live into Under Construction

The Live one works everytime, but the Archive one only works intermitently - I get these errors when it fails:

[1024:mysource notice][R] (/core/include/locale_manager.inc:547) - Trigger Action: trigger_action_set_status Failed [CORE0135] [512:mysource warning][R] (/core/include/locale_manager.inc:547) - FAILURE: Trigger "Archived Into Under Construction" (Trigger# 64), Event "trigger_event_enter_simple_edit" broadcast by "Test Article by JD" (Id# 32979) [CORE0127]

 

Any ideas?
 

(Nic Hubbard) #5

Hi Nic

 

The write permission won't allow the users to change the status of thier assets to Live or Archived.

 

I've allowed the user to have admin permission on their assets only and seems to have solved this issue.

 

Sorry. Yes, you are right. You need Admin permissions to make a status change.

(Nic Hubbard) #6

The Live one works everytime, but the Archive one only works intermittently - I get these errors when it fails:

[1024:mysource notice][R] (/core/include/locale_manager.inc:547) - Trigger Action: trigger_action_set_status Failed [CORE0135] [512:mysource warning][R] (/core/include/locale_manager.inc:547) - FAILURE: Trigger "Archived Into Under Construction" (Trigger# 64), Event "trigger_event_enter_simple_edit" broadcast by "Test Article by JD" (Id# 32979) [CORE0127]

 

Any ideas?
 

 

Hmmm. No workflow is at play here? Are the assets that fail and the assets at work with the trigger in the same root node?

(Richard Crompton) #7

Hi Nic

 

Yes they are and workflow isn't applied to this root folder or cascaded assets

(Richard Crompton) #8

So to provide more details on this.

 

This happens most of the time, regardless of action, i.e. update an article using a simple edit layout.

 

First the HIPO herder appears briefly then the above error message.

Is this because the HIPO herder has started and finished before it can find it?

 

Is there a way to stop the HIPO herder from appearing?