[TYPO3-english] fluidcontent_bootstrap based extension: mandatory fields problem
Federico Bernardin
typo3list at bernardin.it
Thu Jun 6 08:54:30 CEST 2013
Hi Nicola, I suggest you to open an issue into github (https://github.com/FluidTYPO3/flux), so Claus can resolve the problem.
Cheers
Federico
Il giorno 05/giu/2013, alle ore 21:08, Nicola Cerchiari <nicola.cerchiari at gmail.com> ha scritto:
> Yeah, i found it out myself, unfortunately on documentation it's clearly
> written about the required attribute; I find more annoying the mandatory
> signal on wrong sheets and/or fields though.
>
> Anyways, thanks to your suggestions I solved my issues.
>
> Thank you very much Federico.
>
> Bests,
> Nicola
> Il giorno 05/giu/2013 20:35, "Federico Bernardin" <typo3list at bernardin.it>
> ha scritto:
>
>> Hi Nicola,
>> I have just seen that flux doesn't support required attribute, if you want
>> to render a field compulsory you can set eval="required" as attribute. If
>> you want this behavior for file field you can set minitem > 0.
>> Try it, for me it works.
>>
>> Ciao
>> Federico
>>
>> Il giorno 05/giu/2013, alle ore 10:57, Nicola Cerchiari <
>> nicola.cerchiari at gmail.com> ha scritto:
>>
>>> [UPDATE]: After Federico wise suggestion i tried some more tests and this
>>> is what I found out:
>>>
>>>
>>> 1. If I set *on any configuration sheet* a field with minItems > 0 then
>>> the first field of the first sheet becomes marked as mandatory too
>>> 2. It seems that the required attribute is ignored: to cross check my
>>> first supposition I set required="TRUE" on a field.input in the second
>>> sheet of a configuration but no field or sheet becomes marked as
>> mandatory.
>>>
>>> Is there any solution to this or am I doing something wrong?
>>>
>>> Nicola
>>>
>>>
>>>
>>> 2013/6/5 Nicola Cerchiari <nicola.cerchiari at gmail.com>
>>>
>>>> Ciao Federico,
>>>> you are right and I realized I forgot to mention it.
>>>> The mandatory warning in on the first field of every sheet (if any).
>>>>
>>>> The matter is that however I set the fields the situation does not
>> change,
>>>> i even tried to copy&paste a configuration section from another fce but
>>>> situation remains the same.
>>>>
>>>> I tried to remove that field too but was and is not pointing out that
>> field
>>>> as mandatory (what makes me puzzled is that yesterday that fce was
>> working
>>>> flawlessly)... I tihnk i'm going nuts :-) !
>>>>
>>>> Thanks for help,
>>>> N
>>>>
>>>>
>>>>
>>>>
>>>> 2013/6/5 Federico Bernardin <typo3list at bernardin.it>
>>>>
>>>>> Hi Nicola,
>>>>> you set required into image field, are you sure warnings are not
>> related
>>>>> to this field? Can you try to remove file field and verify again?
>>>>>
>>>>> regards
>>>>> Federico
>>>>>
>>>>> Il giorno 05/giu/2013, alle ore 09:36, Nicola Cerchiari <
>>>>> nicola.cerchiari at gmail.com> ha scritto:
>>>>>
>>>>>> Hi everybody,
>>>>>> I just started to develop some new FCEs on a TYPO3 6.1.1 basing my
>> work
>>>>> on
>>>>>> fluidpages, fluidcontent and fluidcontent_bootstrap.
>>>>>>
>>>>>> Everything was going fine until I started developing my third FCE:
>> "all
>>>>> of
>>>>>> a sudden" anytime I try to insert in a page one of my FCEs TYPO3
>>>> backend
>>>>> is
>>>>>> complaing about some mandatory field not filled in, but I did not set
>>>> any
>>>>>> specification about this in my flexforms.
>>>>>>
>>>>>> I tried any configuration that came to my mind reading through
>>>>>> fedext.netbut nothing seems to work.
>>>>>> This is an example of one of my flexform configuration block:
>>>>>>
>>>>>> <f:section name="Configuration">
>>>>>> <flux:flexform wizardTab="XXX" id="XXX"
>>>>>> icon="{v:extension.path.resources(path: 'Icons/icon-XXX.png')}">
>>>>>> <flux:flexform.field.input name="title" label="Block Title"/>
>>>>>> <flux:flexform.field.input name="link" label="Block link">
>>>>>> <flux:flexform.field.wizard.link activeTab="url"/>
>>>>>> </flux:flexform.field.input>
>>>>>> <flux:flexform.field.file name="image" label="Image" required="1"
>>>>>> validate="trim" size="1" minItems="1" maxItems="1" showThumbs="1"
>>>>>> internalType="file" allowed="jpg,png,gif"/>
>>>>>> </flux:flexform>
>>>>>> </f:section>
>>>>>>
>>>>>> Has anyone any idea on why this is happening? Just ot give oyu a
>>>> further
>>>>>> datail the flexform posted here was working without problems till
>>>>> yesterday
>>>>>> and I did not work on this one but on another but even removing any
>>>> trace
>>>>>> of the last one from my extension didn't solve the problem.
>>>>>>
>>>>>> What am I so blind not to see?
>>>>>>
>>>>>> Thanks in advance
>>>>>> --
>>>>>> *Nicola Cerchiari*
>>>>>> _______________________________________________
>>>>>> TYPO3-english mailing list
>>>>>> TYPO3-english at lists.typo3.org
>>>>>> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
>>>>>
>>>>> _______________________________________________
>>>>> TYPO3-english mailing list
>>>>> TYPO3-english at lists.typo3.org
>>>>> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> *Nicola Cerchiari*
>>>> _______________________________________________
>>>> TYPO3-english mailing list
>>>> TYPO3-english at lists.typo3.org
>>>> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
>>>>
>>>
>>>
>>>
>>> --
>>> *Nicola Cerchiari*
>>> _______________________________________________
>>> TYPO3-english mailing list
>>> TYPO3-english at lists.typo3.org
>>> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
>>
>> _______________________________________________
>> TYPO3-english mailing list
>> TYPO3-english at lists.typo3.org
>> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
>>
> _______________________________________________
> TYPO3-english mailing list
> TYPO3-english at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
More information about the TYPO3-english
mailing list