Schlagwort-Archive: DBAL

TYPO3 visibility and Doctrine DBAL a.k.a. Restrictions

Updated 2016-06-03
Details for restrictions.

When it comes to visibility (e.g. flags like „hidden“, „starttime“ or „deleted“) TYPO3 implements a lot of magic, that works differently in the Frontend and in the Backend. Imagine a list view for example. In the Backend list all records flagged with „hidden“ are shown while in the Frontend list they are hidden. In the past (before the change to the Doctrine DBAL facade that I mentioned in my earlier post [1]) that was archieved by the function ContentObjectRenderer->enableFields().

And now this will change again. Once change 48049 [2] is merged into the master, this will simplify things drastically. So, what you are reading right now is brand new stuff, stuff that is even only in code review at the moment of writing. Please be aware of this and forgive me for any misinformation that might be in this post.

TYPO3 visibility and Doctrine DBAL a.k.a. Restrictions weiterlesen

Migrate from the TYPO3 database wrapper to the Doctrine DBAL syntax

Last updated: 2016-06-06 13:00

With the TYPO3 8.1 release, the Doctrine Database Abstraction Layer (DBAL) will be introduced into the TYPO3 core. Sooner or later the old TYPO3 database wrapper (together with the old dbal and adodb extensions) will be removed. So if you’re an extension developer creating extensions for TYPO3 8.1 or above, it could come in handy to migrate all of your database calls to the new syntax. If your extension just relies on Extbase Repository stuff, then you are fine. The migration of Extbase will be done by the core itself so your magic functions will also work in the future. But in case you still have this dusty exec_SELECTgetRows somewhere in your extension, I’ll try to give you some help to come to the light side.

Migrate from the TYPO3 database wrapper to the Doctrine DBAL syntax weiterlesen