Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[com_fields] com_contact: field is disabled within a field group if you extend the Formular #13753

Closed
ufuk-avcu opened this issue Jan 25, 2017 · 11 comments

Comments

@ufuk-avcu
Copy link

ufuk-avcu commented Jan 25, 2017

Steps to reproduce the issue

Install a clean Joomla 3.7 Alhpa 2
Go to Joomla Backend -> com_contact -> Fields -> Choose "Mail" (left from the search) -> New -> Choose Type "Text" -> Title e.g. "Test input field"
If you do this steps correctly, then everything works a excepted and you have an additional field in your Contact Form(please don't forget to fill out the Mail Field, to see the Contact Form in the Frontend).

If you now Create a Field Group with in com_contact and Assign my Field "Test input field" to this new Group, then the Additional input field is disabled and you can't type your text in this field in the frontend anymore.

fireshot capture 10 - kontakt - http___projekte joomla-agentur de_37_en_kontakt

System

Joomla 3.7 Alpha 2
PHP 7.0.9
MariaDB

@ufuk-avcu ufuk-avcu changed the title [com_fields] [com_fields] > com_contact > field is disabled within a field group if you extend the Formular Jan 25, 2017
@Bakual
Copy link
Contributor

Bakual commented Jan 26, 2017

This should already be fixed with #13676. Can you try with a current staging?

@laoneo
Copy link
Member

laoneo commented Jan 27, 2017

@ufuk-avcu is this fixed with the pr #13676? Can you please test it again with the latest staging. Thanks.

@ghost
Copy link

ghost commented Jan 27, 2017

Tested with latest staging and master, Issue isn't fixed.

@Bakual
Copy link
Contributor

Bakual commented Jan 27, 2017

Looks fine to me:
mail

Make sure to create new groups and fields. Don't test with existing ones as the asset entry may be borked there.

@ghost
Copy link

ghost commented Jan 27, 2017

My fault: Permissions "Public > Edit Custom Field Value" was Default on "Not Allowed". Changing on "Allowed" now works.

@ufuk-avcu
Copy link
Author

Tested it again with the staging from today. After i changed the Permissions like @franz-wohlkoenig suggested, the frontend submission works now. Maybe we should consider, to change this default setting...

@laoneo
Copy link
Member

laoneo commented Jan 28, 2017

In DPFields I'v defaulted it to allowed. Don't know if this behavior should be done for the core as well?

@Bakual
Copy link
Contributor

Bakual commented Jan 28, 2017

ACL settings always have to default to disallow if not explicitely allowed.
By default, fields rightfully should not be allowed to be changed in most cases. At least for public.
You will want it only for the mail in com_contact and in the registration of users. In all other cases, there should be at least a registered user or even higher (eg author).
But then, you can't even set com_contact to allow it for public, because you don't want that for the contacts itself, only for the mail.
Good luck trying to set sane default values for that. 😄

@ghost
Copy link

ghost commented Feb 5, 2017

There are now Issues about "field not editable" by experienced two People. Expecting more after 3.7-Release default should be allowed.

@joomla-cms-bot joomla-cms-bot changed the title [com_fields] > com_contact > field is disabled within a field group if you extend the Formular [com_fields] Mar 30, 2017
@laoneo
Copy link
Member

laoneo commented Apr 1, 2017

Can we close this issue as it looks like it is fixed, or?

@joomla-cms-bot
Copy link

Set to "closed" on behalf of @franz-wohlkoenig by The JTracker Application at issues.joomla.org/joomla-cms/13753

@joomla-cms-bot joomla-cms-bot changed the title [com_fields] [com_fields] com_contact: field is disabled within a field group if you extend the Formular Apr 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants