As stated in this thread can you check the mentioned solution:
It should still work if you are using Without Sharing, but it's challenging.
For input fields, you will need to add the new ignoreEditPermissionForRendering attribute on apex:inputField. This will allow you to override entity the lack of edit permission for the guest user. However, it doesn't ...
I'm not sure I got what you're trying to do but if users have no license and you don't want to violate SF terms here's something you can do, unless you really need to use SF Public site :
create a connected app
create a page/minisite outside Salesforce, ie. on a LAMP server or any kind you like
authenticate your page users the way you like (custom, SSO, ...
My 2 cents:
We are familiar that Site page come with a guest user profile, but,
can we implement a custom login that reads unique ID data from a
Not recommended. you can look at authenticated high volume community
or site users license. By building a custom login functionality you
are violating the Salesforce MSA and if they find this out on ...
This is a recent security enforcement part of the Spring 21 release. You can read more about this here.
Salesforce is removing the View All, Modify All, edit, and delete object permissions on all objects for guest users in new and existing orgs. These permissions are removed for custom objects and standard objects. Guest users can only have read and create ...
To have the permission to Edit a field with apex:inputField, we have to put the ignoreEditPermissionForRendering attribute (https://trailblazer.salesforce.com/issues_view?id=a1p3A000001YpKGQA0)
Even if this is resolved, a new error appear
I can't update an object with DML "update" in User Site Guest..
I have the message "core.apexpages....