Activity
From 2014-04-22 to 2014-05-21
2014-05-21
-
15:43 Bug #58972 (Closed): DateViewHelper property "forceLocale" not passed as boolean
- Carsten Bleicker wrote:
> Can you close this issue?
Yes, thanks for the feedback ;) -
15:33 Bug #58972: DateViewHelper property "forceLocale" not passed as boolean
- Thank you bastian!
It works:
<f:format.date forceLocale="{true}" localeFormatType="date">{dateTime}</f:format.date>... -
10:20 Bug #58972 (Needs Feedback): DateViewHelper property "forceLocale" not passed as boolean
- Because the "forceLocale" argument is of type "mixed" there is no type conversion taking place (one reason why we sho...
-
10:00 Bug #58983 (New): format.date does not respect linebreaks and throws exception
- This one works:...
2014-05-20
-
22:19 Bug #58972: DateViewHelper property "forceLocale" not passed as boolean
- Results in:
"true" is not a valid locale identifier. (20140520201641f4700c) -
22:19 Bug #58972 (Closed): DateViewHelper property "forceLocale" not passed as boolean
- As far as i understand this should check localisationService.
<f:format.date forceLocale="true">{document.dateTime}<...
2014-05-19
-
15:29 Bug #58921: f:form.* VHs crash if NOT inside f:form but followed by f:form
- Adrian Föder made me try ...
-
14:38 Bug #58921: f:form.* VHs crash if NOT inside f:form but followed by f:form
- Fun fact: if you reverse the two like so:...
-
14:32 Bug #58921: f:form.* VHs crash if NOT inside f:form but followed by f:form
- Here's my backtrace as requested, should be the same for everyone who uses the provided snipped above...
-
14:28 Bug #58921 (New): f:form.* VHs crash if NOT inside f:form but followed by f:form
- The f:form.* ViewHelpers work inside of forms and standalone, but they crash if used standalone and they are followed...
2014-05-16
-
13:03 Bug #58862: FormViewHelper doesn't accept NULL as value for $arguments
- Bastian Waidelich wrote:
> The patch is not needed, but if you could quickly test whether this really fixes the issu... -
12:40 Bug #58862: FormViewHelper doesn't accept NULL as value for $arguments
- Kevin Fischer wrote:
> Let me know if I should submit another patch that moves the argument definitions to initial... -
12:30 Bug #58862: FormViewHelper doesn't accept NULL as value for $arguments
- Bastian Waidelich wrote:
> I agree. But we usually try to avoid *mixed* types as they're really error prone. So I'd ... -
12:06 Bug #58862: FormViewHelper doesn't accept NULL as value for $arguments
- Kevin Fischer wrote:
> I think it'd be good to have the arguments working streamlined across the standard ViewHelp... -
11:58 Bug #58862: FormViewHelper doesn't accept NULL as value for $arguments
- Hi Bastian,
I think it'd be good to have the arguments working streamlined across the standard ViewHelpers; and th... -
11:52 Bug #58862 (Needs Feedback): FormViewHelper doesn't accept NULL as value for $arguments
- Hi Kevin,
just for clarification: Why would you want that? -
11:47 Bug #58862 (Needs Feedback): FormViewHelper doesn't accept NULL as value for $arguments
- Unlike other ViewHelpers like the ActionViewHelpers, the FormViewHelper doesn't accept NULL as value for the $argumen...
-
11:29 Bug #28283 (Under Review): Paginate Widget does not highlight current page
2014-05-15
-
15:34 Feature #58557 (Rejected): Define Namespaces in Configuration File
- Aimo Künkel wrote:
> {typo3.neos:helper(foo: 'bar')} feels quite handy and i'd like to see it in the fluid core!
... -
15:01 Feature #58557: Define Namespaces in Configuration File
- Hi Bastian,
Thanks for your thoughts and update about your technical discussion.
{typo3.neos:helper(foo: 'bar')... -
15:33 Feature #58829 (Closed): Register package namespaces automatically
- Currently when using ViewHelpers from 3rd party packages the package namespace has to be registered:...
2014-05-14
-
19:31 Bug #28283: Paginate Widget does not highlight current page
- Bastian Waidelich wrote:
> Thanks for the feedback, I'll look into this asap
*cough* sorry, I lost track of thi... -
19:29 Revision dee12aa6: [BUGFIX] Paginate Widget: Correctly highlight current page
- With #28283 the current page is correctly highlighted most of the
time. But if a non-existing page is requested (for ... -
13:26 Revision 5c3f697c: [BUGFIX] Make required work on Textfield and Textarea VH
- The way required was checked any non-null value would mark a field as
required - including FALSE, which is not expect... -
11:36 Revision 1e3536d1: [BUGFIX] Make required work on Textfield and Textarea VH
- The way required was checked any non-null value would mark a field as
required - including FALSE, which is not expect...
2014-05-13
-
16:23 Feature #58557: Define Namespaces in Configuration File
- Hi guys,
as promised, we discussed that topic in our "Technical Meeting" today (see http://wiki.typo3.org/TYPO3_Ne...
2014-05-08
-
09:48 Feature #44572: Format.Case ViewHelper in order to change the case of string values
- Thx for your reply. Created ticket #58621. Since this is resolved in Fluid I change back done to 100%.
2014-05-07
-
14:44 Feature #44572 (Resolved): Format.Case ViewHelper in order to change the case of string values
- Robert, Michael and Bjoern: could you please, if any, open an issue at http://forge.typo3.org/projects/typo3v4-fluid ...
2014-05-06
-
15:21 Feature #58557: Define Namespaces in Configuration File
- Ok, I added the topic to the agenda of our upcoming technical meeting (see http://wiki.typo3.org/TYPO3_Neos-Discussio...
-
15:13 Feature #58557: Define Namespaces in Configuration File
- I like the idea of namespaces specified in configuration.
-
12:22 Feature #58557: Define Namespaces in Configuration File
- Thanks for your update, i can understand your point with the advantages of fluid templates being self-contained.
S... -
12:00 Feature #58557: Define Namespaces in Configuration File
- Hi Bastian,
I understand your (and Sebastians) arguments; but for the sake of consistency, the f: namespace should... -
11:28 Feature #58557 (Needs Feedback): Define Namespaces in Configuration File
- Aimo Künkel wrote:
Hi Aimo,
this topic comes up from time to time but we didn't make namespace prefixes configu... -
11:08 Feature #58557 (Rejected): Define Namespaces in Configuration File
- It would be nice if one could define the namespaces via configuration file, additionally to the existing way inside t...
Also available in: Atom