Hi admin

I'm unable to get the following to work:
"User can view only it's content, even if it is not published (combine with 'publish' wizard)".

When I set the publish wizard and the necessary fields I have to set permissions to allowed for "Edit state" for the user to be able to see his own unpublished data, however this will allow anyone to edit/delete the content. If I set it to not allowed then the user will not be able to see his own unpublished data.

The rest of the authoring system is working like a charm!

Cheers
Alexander

Configure "view own" and "edit own" for the concerned group. (instead of 'edit state')

"Edit state" ACL should be reserved to admins or publishers because with this ACL, you can see unpublished items.
(Edit state is dedicated for publish/unpublish)

The combination author + publish is interessant because if you don't choose 'publish' wizard, the 'view own' ACL does not have really sense because the contents are directly published.

Ok, so far I'm loving it! Works differently than I expected but I am coming to terms with it.

My only issue is with fully understanding the ACL's in relation to Published state.

If I Configure "allow" View Own, and Edit Own, the user cannot Add. So, I add 'Create' to the list, seems ok, but keep getting Error Messages: You are not authorised to view this resource. Or Not authorised to delete.
So it gets confusing.

This is how I 'think' it works: (please correct me if I have missed anything)

1. In J-Cook component Table - Add the Author wizard.

2. It creates a Field for me 'Author' in the Table.

3. In my FrontEnd Collection and Item I have ensured that the Publish field in present and 'Published' (1) by default. Otherwise record wont show. (Obviously - as not published).

4. Download Component.

5. Install Component in my J2.5 instance.

6. Select Components: 'my component name'.

7. Click on Options / Permissions.

8. For the required Group (I use Registered as a default) change Settings to (as required) View Own, Edit Own, Delete Own. (What about Create?) As example (of mine) Any new clients that Register then Sign On will be in the Registered Group.
Only they can Add a Quote, Edit their own quote, and Delete their own quote (as well as View only their quotes).

9. Create my Menu Item to Link to the Front End view - Collection (i.e. My Quotes).

10. This should then allow the Registered user to A) View, Add, C) Edit, and D) Delete their own Quotes.

At least that's what I think anyway, a little tired today. Please clarify Yes or No to above steps, and if No then what have I missed in relation to getting Error messages on ACLs. (No permissions to Edit, Delete..)

Lastly, but not least - Odd: My Rich Text fields x 2 have 'lost' their WYSIWYG Editor ability, just get an outlined box and it ignores JCE which was working.

Thank you Jocelyn!

Edward.

Hi Admin

I've set "Edit own", "View own", and "Delete own" all to allowed, but the user is not able to see his own unpublished data, nor is the user able to change from published to unpublished.

Do I miss something?

Cheers
Alexander

Arrrh, I should write a little tuto....

'create' should always be allowed if you want the user to submit content.

For everybody :
When you are in sandbox, please use the little icon (key) next the user to read the current ACL's that are in use for selected user.
Because sometime you allow an ACL, but another ACL forbid it, so it is confusing. (This is Joomla params only)

I'm probably too tired from testing this new great future to explain my problem

'creat', 'edit own', 'delete own', 'view own' are all set to allowed, the rest to not allowed for this group. If I set the default value for publishing to 1 (published), then the user is able to see the content, but not able to change the status. If the default is 'not published', then they cannot see the content (I can see the content with super user).

The user can easy create, edit, delete his own content that is working like a charm, but the user can't change the status of his own content.

I feel the same way.. have been playing with it for 8 hours now! My findings are exactly the same as yours Alexander.

In addition: In the sandbox I can see the Publish field, but locally I can not - it is not even visible. Odd.

Edward.

Please.. we know you have been working very hard and are very tired, but when you can.. A little Tutorial would be very helpful indeed.

Thanks again Jocelyn.

Edward.

This functionality is not available.
It should be 'core.edit.state.own'

Do you need this ?

To clarify, are you asking if we need the ability for Author to change their own record Publish status?
Good question; Should a User/Author be allowed to change the Published field? So, one minute the record is visible (Published), the it vanishes (Not Published). true?

Edward.

Exactly.

I can do this. It will add an ACL.

Ok, I can see some uses for this functionality. But don't let the decision be based on my own.

P.S. Dumb question of the day please.
With the introduction of this amazing (Thank you again!) Authoring, does that make the Table Data Type 'Joomla User' useless - Or is this still valid in conjunction with Authoring.

Thank you,

Edward.

Author MUST be a Joomla User datatype.

If you already instancied a Joomla user, you can reuse it for the Authoring wizard, but 'Joomla user' is not useless.

In your project, you still can, for any kind of situation, need to link an element to a user in a different context than authoring

I think it should be possible for the user to publish/unpublish his own data

Well it works quite well. Created three test components to see how it works, and it was cool. Now i'm trying again with some other idea, but registred users can now see everybody's content, even if then can only edit theirs... Sure i forgot something, but what am i missing.......