BoldMinded

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: Publisher retrofit, Structure support

Status Resolved
Add-on / Version Publisher
Severity Trivial
EE Version

David Stewart

Dec 10, 2012

Hi, I am considering Publisher for an existing multilingual site which has outgrown the ‘one MSM site per language’ approach. Some questions:

1. Because I am imploding an MSM site (absolute nightmare) so entries from language specific sites are moved into the master site, how practical will it be to associate these existing entries with their corresponding other language entries? This could be done manually, but we would need some means of associating entries without resorting to copy/paste between nemerous fields in each entry.

2. How does Publisher work with Structure? Does Structure display separate menu trees for each language, with the ‘tree switch’ tabs above the menu tree? The site has some entries missing for some languages and some language-specific entries in others, so is this supported?

3. How will native Assets support work and what are the implications of using Assets without native support?

Thanks…

#1

BoldMinded (Brian)

  1. Publisher doesn’t create multiple entries per language. It saves the language data in an external table. Honestly your best bet if you want to avoid a lot of copy/paste is to consider using Transcribe as it creates an entry for each translation.

  2. 1 Tree. If the entry does not exist for a language, it will default to the English version.

  3. It will support Assets 2 natively when it is released.

Publisher is designed for a single tree site, meaning every piece of content has a translation. If some of your translations are not present for some languages, meaning the sitemap is different across languages, then you may want to consider Transcribe.

#2

David Stewart

Thanks for the speedy reply… I have already been testing Transcribe, but after spending a while hacking new features into it and then fighting with content migration scripts, I needed to check out Publisher just in case some sanity could be restored.

I think you are correct though - our need for different menu trees between languages is a determining factor.

The main issue here is that if there is an existing multilingual scheme in place, migrating existing content into either ML add-on is a major issue.

Login to reply