Note that there are some explanatory texts on larger screens.

plurals
  1. POGetting data out of Typo3
    primarykey
    data
    text
    <p>We have a site we're taking over and porting from typo3 to Orchard. As of right now, all we have is the database and none of the site files. I have the database setup on mysql and can query the data. I don't currently know what version of typo3 it's using. If necessary, I might be able to find out, but as I said, right now all I have is the database.</p> <p>I need to get the data out in a usable form so that I can massage it into the xml needed to import into Orchard. The problem is, I can't find any documentation on how typo3's database is setup, so I've not been able to get at the content...thus far, the only useful table I've found is the "pages" table, but that really seems to just store the instance of a page, minus the content. Here are the things I need:</p> <pre><code>Page Title Parent Page (for hierarchical concerns) Content for a page </code></pre> <p>Can someone shed some light onto what tables I need to look for to pull this content out?</p> <ul> <li>Edit * I was able to get something working using:</li> </ul> <p>What I did was gather the data using this query:</p> <pre><code>select p.Uid PageId, p.pid ParentId, Title, c.BodyText, concat('index.php?id=',p.Uid) OriginalUrl, p.deleted, c.deleted from pages p left join tt_content c on p.Uid = c.Pid where p.deleted = 0 and c.deleted = 0 </code></pre> <p>And then going through each of the tt_content records and concatenating them together to flatten and form somewhat coherent HTML for a page...this is better than nothing. I haven't done anything with the plugins yet, but I do see tx_ tables in there...regardless, this is a start... order by PageId, c.pid</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

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