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 with MSM
| Status | Resolved |
| Add-on / Version | Publisher 1.6.3 |
| Severity | |
| EE Version | 2.10.1 |
Linus Design
May 28, 2015Hi
I’m just about to start my first Publisher site, and am trying to understand how it might work with MSM (which I’ve also not used before!).
My client wants separate domain names (example.com, example.co.uk, example.de etc), and to have pretty much the same content on all of them, but translated into each language. The templates will be exactly the same for all sites. I guess the only way to do this is with MSM?
If so, would they still be able to have one entry for each piece of content (with Publisher handling translations within that entry) or would then need to publish to each site separately?
And if they then want to post, say, a news story to just their German site, is there a way to do that? Or if they want to post an entry to all but one site (say they don’t have the german translation ready), is that possible? I see that turning off persistent entries in Publisher is “currently experimental”, but does it being an MSM site make this easier to do in any way?
And finally, would it make any of this easier if they don’t go for separate domains and instead go with example.com/uk/, example.com/de/ etc?
Apologies if these questions are more about MSM – but I’m not sure yet how it all fits together!
Thanks, Frank
BoldMinded (Brian)
Hi there!
Based on this statement “have pretty much the same content on all of them, but translated into each language” it sounds like you don’t want to use MSM. This is exactly what Publisher is built to do… manage entries/content and enter translations for each entry, and use the same templates for all languages. Definitely sounds like MSM will complicate things. You may need this companion add-on I wrote to handle the different TLDs.
https://devot-ee.com/add-ons/publisher-domain-control
You’ll need to setup all those domains at your host registrar to point to the same IP, and your web host configuration needs to point all the domains to the same installation of EE. From there Publisher Domain Control and Publisher should be able to sort it out and load the language based on the TLD.
The Persistent Entries feature is probably not experimental anymore. I’ve had a few customers use it pretty well, however, the 1.6.4 release that will be out in a few days does fix a minor bug with it. If you want to publish an entry just in the German site, then you’ll want to turn off Persistent Entries, otherwise the entry will try to display in your English and UK sites too.
Hope this helps
Linus Design
Thanks for the super fast reply! And that’s very encouraging – I’ll grab a copy of Publisher Domain Control and have a play with it.
This is probably more of a hosting question, but do you know whether doing it this way would work with bog-standard shared hosting? Or would I need a VPS or dedicated server to use this set up?
Thanks again for you help!
BoldMinded (Brian)
It should work with any hosting setup. It just needs to be setup so the virtual hosts all point to the same set of files, e.g. /var/www/html or wherever the EE files are located.
Linus Design
Great, thanks – looking forward to getting to know this module better!
BoldMinded (Brian)
Good luck. Just create new tickets if you have any other questions. Look out for the 1.6.4 build sometime next week that fixes an issue with the persistent entries.