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: Copying an Entire Language
| Status | Resolved |
| Add-on / Version | Publisher NA |
| Severity | Trivial |
| EE Version | NA |
Christian Maloney
Jan 10, 2014We are using publisher for country localization not just switching the language, so we will have multiple “languages” that are really just the same language. US and UK are both english but with slight tweaks for example.
So, we have about 10 languages setup, and some of them will be basically the same with minor tweaks. But, these aren’t necessarily the default language. Is it possible to make a “copy” of a language without having to go through each entry and re-saving?
For example:
English is the default language and I have Spanish translated for Spain, but I want to create a Spanish language for Mexico? Is there are relatively simple way of copying everything for Spain to Mexico?
BoldMinded (Brian)
Hi, Christian. There isn’t anything built in to accomplish this, but you can certainly do it the hard/manual way… which probably isn’t that hard. You just need to find the rows in the exp_publisher_titles and exp_publisher_data tables, copy them, and then change the lang_id of the copied rows. Or you can write a script to do this.
If you’re having to make minor changes you still have to edit the entry and save it, right?
Christian Maloney
Yea we will have to go in and edit a bit, some will be tweaked more then others. So, if I just copied the data in those tables it “should” work? I wasn’t expecting a built in function, but if there aren’t any issues you can think of doing in the database that seems much better then doing via the EE backend for ~2000 entries.
Thanks!
BoldMinded (Brian)
Shouldn’t be issues with copying, just make sure you know which rows should have their lang_id changed. The primary keys are entry_id, channel_id, site_id, lang_id, and status. The id column in each table isn’t really used.