01:37:34 <mneuhaus> @NamelessCoder ^^ hmm, year php array could be ok as well i guess, although i like the slimliness of yaml :)
02:33:50 <bottoni> Good morning, I FluidTYPO3 page template with nested <flux:form.object/> not working when exceeding a certain object limit. Only the other flux fields get saved into tx_fed_page_flexform, the xml structure remains valid though. Does anyone know this problem or does anyone spot an error in my template: https://gist.github.com/boettner-it/6f29fd2e5c9d66705f84
05:05:58 <NamelessCoder> bottoni raise max_input_vars. See bottom of Flux's README.md file
05:36:44 <bottoni> Thanks NamelessCoder, I missed the README. Sounds like the solution. Unfortunately the customers privider (1&1 in Germany pfff...) offers no reasonable methods to change PHP settings. Means one php.ini file in every directory involved in the processing. I´ll discuss a move to another provider. This point is just another one on the list for moving but the customer has refused to so far.
05:45:26 <mneuhaus> aside from managed/root servers 1&1 is quite shitty
05:48:58 <mneuhaus> yea, probably plenty more our there that are decent
05:49:57 <bottoni> being more flexible than 1&1 is not too hard. Discounter will always be discounter
05:50:01 <mneuhaus> but usually i have the feeling there's 10-15% good ones, 30-40% "ok" ones and the rest is pure stupid, non-flexible, no-real-knowledge-support crap
05:50:44 <mneuhaus> had a customer once, who provided me the passwords, etc for their hosting.
05:50:56 <mneuhaus> after a quick check: no php, no database, 30mb webspace