Publisher does not support the Fluid field type. Please do not contact asking when support will be available.
If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.
Ticket: Possible to Import from another Database?
| Status | Resolved |
| Add-on / Version | Publisher |
| Severity | Trivial |
| EE Version |
Tiffany Taunton
Aug 05, 2013The site I’m working on already has 6 translations of 65+ pages in a custom CMS. We have DB access to the old site but are at a loss at how to map it to the EE/publisher tables. Has this been done before? Can you provide any insight of what’s entered and where for each entry’s translation?
BoldMinded (Brian)
Importing translations is a large undertaking. I intentionally didn’t include it in Publisher b/c it could easily be an entirely separate module. I’ve done this before, and the first time it took me about 200 hours just to create an import/export module for a translation service. It did text comparisons to find new text since last export etc.
If you look at the tables, exp_publisher_titles is nearly identical to exp_channel_titles, but just has a few extra columns in there. Same thing with exp_publisher_data, which mimics exp_channel_data. If you’re dealing with categories, exp_publisher_category_posts might be necessary to update. If you use Matrix, Playa, or Assets you have to update those tables too :/
If you’re doing an import, everything should be assigned the “open” status in the publisher_status columns, and publisher_lang_id needs the proper language ID.
I hope this helps, but I have a feeling I’m just scratching the surface. Importing of content like this isn’t usually a straightforward task, but if you know SQL pretty well you can probably pull it off.