karpadiem
CanAccessPanel logic causing 403 error for livewire.update on Tenant Registration Form
Access to particular tenant is controlled elsewhere right? This is just if the user can access the particular panel or not? I did it this way because besides the two user types above (member of an company and employees of the Saas [admins]) there is a third user type and panel of customer.
Based on your feedback, sounds like i have three options?
- Leave it as is with the livewire.update route override (assuming this is not security risk)
- Move my tenant (company) registration outside of the company panel
- Remove the check for accessing the company panel and handle rerouting "customers" a different way.
Does that sound right?
18 replies
CanAccessPanel logic causing 403 error for livewire.update on Tenant Registration Form
After lots of trial and error. It's failing when the route is a livewire.update request orignating from the company panel when the user is not yet associated with a company (my tenant model).
This bit of code added to anAccessCompanyPanel() fixes it, but I worry that's not the approprate way to handle it. Does this present a security risk?
18 replies
CanAccessPanel logic causing 403 error for livewire.update on Tenant Registration Form
The only thing i can think to do to fix it (and it does) is add
But i worry that will create some sort of security issue.
Am i missing something obvious?
18 replies
CanAccessPanel logic causing 403 error for livewire.update on Tenant Registration Form
This allowed the user to access these pages. However, shortly after accessing the page, the first livewire.update request happens and a 403 error is thrown.
18 replies
Table Column Relationship Sum, Avg, Max, Min, ext being ignored
@Dennis Koch I’m definitely reading in the documentation that your suggestion should be correct. I guess I’m worried something else is wrong since dropping the “_sum” made it work.
11 replies
Creating new entries for multiple recourses in a single form
Follow up question, ContactResource::formShcema()) has a repeater for email addresses. It's using the Contact Model's email_addresses relationship. This works properly on the Contact Creation page, edit page, view page, as well as the employee view page and edit page. However, the values of the repeater seem to be trashed in this create employee wizard. Are repeaters nested in a relationship supported when creating a new entry, or am i doing something else wrong?
13 replies
Creating new entries for multiple recourses in a single form
Ok, I seem to be getting closer. I think i was expecting to have the full data show in the dd(data) of handleRecordCreation(array $data) and was debugging that way. I see how that the employee record would be created first, and then the contact record.
13 replies
Creating new entries for multiple recourses in a single form
I guess this is where Im struggeling. How do I properly assign the relationship() to all fields in ->schema(ContactResource::formShcema()) ? Is it possible to assign a relationship to a Group, Fieldset, or Section?
13 replies
Creating new entries for multiple recourses in a single form
However, if add
dd($data);
to protected function handleRecordCreation(array $data):Model
None of the information from that part of the form is there.
However, if i make the whole step use ContactResource::formSchema()
it does pass the information i want, except not packaged in a array of 'contact.fields'. This option also keeps me from using a select that would allow the user to pick an existing contact.
13 replies