Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>The datebase structure is pretty simple. You have the pages table which has a uid and a pid. The pid allways defines on which page a record is created. </p> <pre><code>Page Title =&gt; pages.title Parent Page (for hierarchical concerns) =&gt; pages.pid Content for a page =&gt; tt_content.* where pid = pages.pid order by sorting </code></pre> <p>There are different types of pages, some of them are just folders which holds records, but the page does not exist in the menu.</p> <p>The same is with tt_content. There are a lot of different Content Elements (like Text, Image, Text/Image, Headers etc.). Have a look at tt_content.CType for that. It can happen, that you have an image defined, but someone changed the content element to TEXT only, so the image will not be rendered in TYPO3. You need to have a look at colPos too. This field indicates in which column the content will be shown. colPos = 0 is usally the normal column, colPos = 1 left, colPos = 2 right etc. But it depends. Within these columns you can use sorting to get the correct order.</p> <p>Beside tt_content there are "plugins" or "extensions" which ships with additional tables. The usually start with tx_ or tt_. So, they will hold records too.</p> <p>It would be possible to render the XML you need for each page with TYPO3 - without any template. The database would be enough. But for that you need to understand TypoScript and the TYPO3 database scheme. I guess, you will be fine with getting the pure data.</p> <p>There are some additional fields, but imho the important ones are pretty easy to understand: deleted = 0/1, hidden = 0/1, starttime, endtime, uid, pid.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload