If you have a fatal, please tell me wich project. I will download it and check for you. But it must be setted as you said to propagate access.

Well, Joomla is not doing it natively. Or tell me where...

The wizards, when instancied normally (Authoring + Published) are simply limiting the accesses when you are browsing in the current table.

When thoses accesses applies on Categories for example, then when you are calling another model 'Items', you will see all items, even if they are contained in upublished or not accessibles categories for the user. Joomla is doing nothing to fix it. It must be called manually, or... now you can propagate accesses.
That the point.

Can you please explain better your problem.
Is the problem that the users cannot see/edit their items, or it is a problem of all users can see items.
Can you please tell me project / table / layout (P/T/L)

Question:Which Project?
Answer: I only have one project, and it only has one table. . Im a newbie The project is called prayer requests

Question: What Is The Problem?
Answer: The problem is that users can see other user's records. I don't want anyone to be able to see anyone else's records. Entries are private.

Question: What is the Fatal error?
Answer: The fatal error is not a problem anymore. I got a fatal error when I built the project after I checked propagate-access on two database fields. However, yesterday I deleted and re-added fields, cleaning up my project. I have tried to reproduce the error for you today but I cannot reproduce the error now.

Ok, no problem.

I saw your projects list, in facts...
Did you tried to set Published wizard with default value of published field to false. (+required = true eventually when you had prevous items. Anyways allways better)

Try now to create simple items lists that refers to your main table. (Title + FK to the main table)
If you do not activate the propagation, your sub items will all been seen whatever the accesses of the main table.

It is very complex stuff and has been reduced to the most simple for you.
When it will be working for you, try to dump the SQL query to see it. Try also to propagate multi-levels, it is amazing !

I hope it is working well, I have tested a lost and constructed in a clean way to do not raise issues.

Now I understand the idea.

You mentioned not publishing before, but I did not get it. I will try making all the records unpublished.

I am not able to set unpublished as the default.

I set unpublished as required with default value zero, however it did not work.

Even Mr.Guest can see the records created by Mr.Super

I attached an image. It shows how I tried to set unpublished as default.

I do not see the image in the post, even though I upload it. Can you see the image?

It shows the "Prayers" Table with the publish field dialog open.

Required = checked
Default Value = 0
Edit Check = 0

It is not working this way...
I should block you the possibility of propagate on Third tables (FK User, FK Access...)

Let's start from the begining :
You do not need to propagate any accesses for the moment.

Is it working without propagation ?


Only when the feature is working for you, then you can think about propagation :
When another table (For example "Questions") is referring to a "Request" For instance : FK Request.
On the properties of "FK Request", you set up the propagation.

The table "Questions" will be filtered trough the accesses of Requests (previously setted in the Requests table, using Wizards)

This feature works :
- for infinite number of Foreign Keys in "Questions"
- for infinite deep levels (When Another table "Calls" is propagating "FK Question")

Amazing, no ?

Well you might have issues because for example I never tried to propagate accesses on FK User, FK Access, ...
Now I will finish it well and write a documentation for that.

Monday you will get an upgrade I think.

I am not using propogate access.

I have only one table

I dragged "access" into the table

I dragged "access" into the grid

But it still does not work. It makes no difference.

Can you please tell me what I am doing wrong.

I will wait for the update, then try again

Upgrade is coming right now.

Also to check for you is the ACL configuration of your component.
You must attrib "Edit Own" to Allowed for the User group of your choice "Registered" or "Author"

In the coming upgrade, It fixes an issue with published 0 false per default

Hi @collins

On the contrary, there is an option there.... 'View Own' is what you're looking for

Gez