I want the default profile to be "Person"
Hi all
I need the default profile for account creation to be a person profile. Then, if the user wants, they can create other profiles (person or organization).
With the following configuration, I can initially achieve what I need. However, if the user doesn't complete the form (create-person-profile) and clicks on any other link on the page, then when they try to complete the profile because the system requires it, two options appear (People and Orgs).
What I want is for them to only be able to complete the "Person" form.
Is it possible to modify the "Please create a profile to start using the site" link so that it leads to the "Person" form?
Specifically, I don't want someone to be able to create an Orgs profile without first creating a People profile.
Thank you very much.
-
- · PavelS
- ·
I think it would go like this. Go to Navigation-Items-System-Add Profile
Hide Orgs(visible for) or turn them off completely
-
-
·
LeonidS
- ·
Hello @Claudio Acosta !
You may close the Create Org action for the necessary level. But if you need definitely to disable this option in the Profiler Switcher then you may add the RAW block in the Studio->Pages->System->Account ->My Profiles page, put it to the end of all blocks and add there the following code:
<script> $(".bx-menu-object-sys_add_profile li:odd").hide(); </script>then limit visibility of this block for the certain membership levels like Account, Unconfirmed etc
-
·
LeonidS
-
- · Claudio Acosta
- ·
@Hi @PavelS @LeonidS
I suppose I didn't explain myself clearly.
I need it to be a requirement that a person has a People profile before creating an Orgs profile.
Is this possible through configuration, or does it require programming changes?
Thanks.
-
- · Claudio Acosta
- ·
Hi @LeonidS
If you could tell me about this, I would appreciate it.
I need to know if this is possible to move forward with my project.
Thank you very much.
-
-
·
LeonidS
- ·
UPDATE: the solution works but dear @Claudio Acosta has troubles to insert it to the RAW block due to hosting security settings.
-
·
LeonidS
-
- · Claudio Acosta
- ·
Hi @LeonidS
I want to confirm that the solution you offered works, thank you very much.
To create the raw block with the code you provided, I had to disable a rule in mod_security.
First I checked the log in my control panel and sent it to Gemini. The result was that my server log indicated that the web application firewall (WAF) had blocked a legitimate request (false positive) after detecting a pattern it mistook for a Cross-Site Scripting (XSS) attack.
Alert Analysis
Affected File: /studio/builder_page.php [Log].
Triggered Rule: COMODO WAF ID 212620 (07_XSS_XSS.conf) [Log].
Cause: The content field of a POST request contained JavaScript code (<script>$(".bx-menu...").hide();</script>) [Log]. ModSecurity detected the <script> tag and blocked the action with a 403 Forbidden error for security reasons.
Context: This appears to be a legitimate action by a page builder on your website attempting to save changes that include scripts.
One of the solutions recommended by Gemini was the one I used: disabling a rule in ModSecurity.
However, I need to find another alternative that allows me to disable the rule only for that specific application.
Regards.