At some #TYPO3 barcamp (was it #T3CMD23?), I attended a session on data anonymization (names, email addresses, IP addresses) while keeping the relational integrity of the data intact. I don't remember the name of the tool, though, and would be grateful for any pointers.
Frontenders often use <f:debug> to see available properties but then they can’t find the get/has/is functions that Fluid supports as properties. I’m experimenting with adding these to debugger output. Good idea?
@danielsiepmann@jigal@cybersmog After posting I thought about those protected/private properties and added a check to show if they are accessible in fluid (through a getter).
I deliberately left the non public properties in because it might be necessary to change the model to make them accessible.
I’ll check out your code!
@sixtus it’s pretty complicated to forbid a political party. Because only the current government can start the procedure (in DE the Regierung/Bundestag, in NL the public prosecutor which is part of the Ministry of Justice) judges are careful not to let it become a tool for a dominant party to remove other parties.
Judges also like to let the democratic process take care of removing anti-democratic parties and expect people not to vote for them (I’m less hopeful in this regard).
Teil zwei des Talks von Nikita Hovratov zum Thema Content Blocks in #TYPO3. Heute geht es noch weiter in die Tiefe.
Die Slides von gestern und heute sind hier:
@cybersmog Oh no, not more yaml! Everything needs to end up in php arrays and the core already uses json, xml, typoscript and yaml to store that data. Now a flexform (xml!) will be stored in yaml?
Why not use typoscript syntax more? It has a pretty intuitive syntax with support for comments, mixins (copy and reference operators), constants, conditions, and there is a built in editor and parser which can show the resulting configuration.