Jørn Wildt

Yes, I know. This topic has been treated previously but I think is important. I think that a valuable improvement for Pagesetter will be the posibility of customize the editor page: hidden fields, add instructions and comments for users, etc... Specially, the fact that a normal user (not a publisher) must know to change the the approval state and the online checkbox.

Meanwhile, I have touch pubEditSpec.xml and now the approval state field is Preview. Is possible to set unckecked by default the online checkbox?

Next version will be with different layouts depending on who is editing the publication.



Could you please clarify that?



You can hack pnuserapi.php / pagesetter_userapi_getEmptyPub() with little or no effort.

But the idea was in fact that "normal" users should leave the publication in preview for another one (the editor - you?) to approve it. If you trust people to be able to write without your approval then I would expect them to be able to set the state to approved. Or?

I have change the order of the items:

- <field name="approvalState" title="_PGAPPROVALSTATE" type="select" mandatory="true">
<option title="_PGAPPROVALPREVIEW"></option>
<option title="_PGAPPROVALAPPROVED"></option>
<option title="_PGAPPROVALREJECTED"></option>

But I see that's nosense, changes in pagesetter_userapi_getEmptyPub() are enough. I have changed also the online checkbox.

Exactly, if I set Approval State as Preview and online unchecked the edit page is in the right way by default and normal users have not to change anything to submit a new article.

By the way, which is the filter expression to get in a block the list or articles waiting for approval?
</field>

Duh! That was a good question. I was expecting that I had to write a completely new "waiting" block, but of course it should be possible to use the standard block.

The only problem is although that it is pretty hardcoded that the publications should *not* show up in a list when they are either offline or in preview :-( So it's not possible.

Hmmm ... rethinking it.

It would be rather cool to be abe to use the standard block. But then the admin has to figure out how to parameterize the block for 1) standard lists, 2) wating content, and 3) old stories.

I'm getting confused here ... what's best - three different hardcoded, easy to use, blocks or one genereal purpose you parameterize. For myself I would prefer the last - with online documentation right at my hand.

I agree, the second option is better although the case of waiting content maybe specially consider.