Of course, this is why if you use the publish wizard, others users cannot see user private content.

Published means 'for everybody'.

Please give me a pillow, i feel so stupid i sould probably hide.....

Ok, so I am confused. I thought that in context a 'record' that is Published is 'visible' - however, I would assume that it is visible only to the Author.

So what you are saying is that regardless of Author, if a record is Published (via Publish Wizard) then it is globally visible to all? and so we should use a default of Not Published?

Sorry, very tired as well. Hope you understand.

Thanks,

Edward.

I have not tested yet this new expecting feature, I just read all the contributions of you gents.

According this

Published means 'for everybody'.

seems as a usefull functionality. It can work like sharing content.

Looks like you're right edward.
Three users : Admin, test1 and test2 : admin is super user, others are "registred"
With a published item, everybody sees it.
With an upublished item, only the creator and admin see it.

That's the point, and that's why publish wizard is very good used with authoring.

Still having ACL issues. Admin can rightly View, Edit, Create, Delete all when logged in.
User one can see records created by user one and two. But cannot Edit it's own record.
User two can see records created by user two and one. But cannot Edit it's own record.

New user Registrations are assigned to Group: Clients.
New records all have a Published record that is set to 0 (zero) false.

So close.. yet so far. I'm sure I'll get it right soon. Meanwhile, anyone have any ideas please?

Thank you,

Edward.

VeCrea wrote: Looks like you're right edward.
Three users : Admin, test1 and test2 : admin is super user, others are "registred"
With a published item, everybody sees it.
With an upublished item, only the creator and admin see it.

I'm facing the problem, that with an unpublished item, only the admin see it and NOT the creator, however it should work as you explained. Did you manage to create a component working that way or was your post just theoretical?

Best wishes
Alexander

I managed to get it work, and i don't have the problem edward is facing.
Let's go for explanations :
TABLES
1) Create a table.
2) 2 wizards : author and publish, then click on the little green + to get the two corresponding fields. The publish field has a default value of 0 (unpublished), which is set to prefill forms
3) I added a 3rd field, just to get a string value

PAGES
1) Create, for backend, a collection and a 1item
2) Create, for frontend, a collection and 2 1item
Why 2 x 1item ?Because on one you put a fly (display datas), and on the other one you put a form (to add a new data set)
3) Download the component.

INSTALL AND CONFIG THE COMPONENT
1) Install it (duhhh)
2) In the component, go to config
3) In Permissions, for "Registred", allow Create, View Own and Edit Own.

Try it with different users. Works here

@ahv, @edwardcox :

Please give me the ACL's of users that you speak about.
Because sometime you give access, BUT another ACL is forbidding the access, so when it is merged, you lost the ACL authorization.

Please always copy the list of ACL's for the users you speak about.
(And remember that for the moment in sandbox, the configuration is reseted when you regenerate)

In sandbox :
The current ACL is viewable in the tooltip icon, next to the virtual user selectbox.

In your localhost, or production, try to insert theses lines in the template file :
And let' see if you still have the problem.

One more precision : don't allow "edit state" for registred users, because they then will be able to see more than what they need to see

In facts, I thought about and I think is not a good idea. So I will not.

Publish state is really important. It should always been given to an Administrator to do the job.
On internet, contents are approved by moderator or admin.


So, maybe another wizard that is more about "Sharing"

To VeCrea: when we do not allow "Edit State" we will not able to use ordering functionality

I actually think, that the ACL is working as it is suppose to do - The publish/unpublish is not for the common user but for a moderator / admin. So the normal user will not be able to publish/unpublish own data?

In my component the user is only allowed to "create", "edit own", "delete own", "view own"

To etc :
I never use ordering... Maybe it with an example ?