All add-ons currently require PHP 7.4 or greater.
On July 4th 2024 PHP 8.2 will be the new minimum requirement for all add-ons. Expect any add-on released after that date to require 8.2 or greater. Some releases may not immediately take advantage of 8.x specific features in PHP, which means you might, be able to continue using new releases in PHP 7.4, however, if you experience an error the first thing you should do is update to PHP 8.2 then create a support ticket if the error persists.
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: Multilingual Phrase Groups in MSM Sites
| Status | Resolved |
| Add-on / Version | Publisher 3.10.2 |
| Severity | |
| EE Version | 7.3.12 |
Eric Harth
Oct 09, 2023I hope this message finds you well. I would like to report a bug related to the usage of Phrase groups in our ExpressionEngine system, particularly in the context of Multi-Site Manager (MSM) integration.
Issue Description:
We operate a large-scale ExpressionEngine system where the primary site has been structured around the use of Phrase groups to facilitate multilingual support. Recently, we started updating several MSM sites to adopt this architecture. During this process, we encountered a critical bug: Phrase groups created in site_id = 1 are not automatically associated with any of the MSM sites. When creating a phrase group with the same key as an existing one within a Multi-Site Manager (MSM) site, all phrases within the duplicated group are displayed. However, the system does not provide an option to add translations to these phrases.
Observations:
Upon investigation, I examined the exp_publisher_phrase_groups table and noticed that a Phrase group, when created, is associated only with the site it originates from. This means that if we wish to make these Phrases available across all sites in our MSM setup, we must manually duplicate them for each site.
Proposed Solution:
To streamline this process and enhance the usability of the Publisher addon, I propose implementing a feature. Specifically, when editing a Phrase group, it would be highly beneficial to have the option to mark a checkbox that allows associated Phrases to be available across all sites within the MSM setup.
Feature Request:
Could you consider developing this feature and including it in an upcoming release? It would significantly improve our workflow and reduce the need for duplicating Phrases across multiple sites manually.
Current Workaround:
As of now, our workaround is to duplicate Phrases for each specific MSM site. However, this workaround incurs a considerable amount of additional work and complexity, which we believe could be greatly alleviated by the proposed feature.
Your attention to this matter is greatly appreciated, and we look forward to any updates or solutions that may arise. Please feel free to reach out if you require further clarification or if there are any additional details you would like to discuss.
Thank you for your continued support.
BoldMinded (Brian)
Eric, thanks for the suggestion. I reclassified this as a feature request because currently it’s working as expected. I’ll think about this, but I can’t provide any sort of timeline on when I could get around to this.
Eric Harth
Hi Brian
We’re fine to create the necessary phrases on a per-msm-site basis until multi-site phrase groups might be added. The issue is that we are running some global layouts that we use across the primary and MSM sites. This layout has phrases such as ‘Contact’ and ‘Shop’ etc. When we use the template on the MSM site those tags don’t render and show up as {phrase:Shop} as you’d expect for a site without the phrase defined.
So we thought we’d just recreate the phrase group and phrases necessary for the layout in the MSM site. When we added a new phrase group, that uses the same short name e.g. permalinks_and_footer as it is in the primary site, upon saving, we then see a list of all of the phrases in that group from the primary site. If you open one of those phrases for editing, no language input fields are available to add translations. The tag will no longer show as unparsed, but will have no content and be blank. I’ve added screenshots to the original ticket. If you add a new phrase to this group with a different key, it behaves as expected, offering the languages available on that MSM site.
Hope this helps. Cheers
BoldMinded (Brian)
Eric, I have a new build that might help with this. It lets you set a group to be global, e.g. shared across all MSM sites. Let me know if you want to test this.
Eric Harth
Thanks, we’ll definitely give this a test. Cheers
BoldMinded (Brian)
Comment has been marked private.
BoldMinded (Brian)
Eric, how has this been working out for you?
Eric Harth
Hi Brian, sorry I didn’t get chance to test this before Christmas (also no, we didn’t get a build when you initially mentioned it). I’ll schedule it for a team member ASAP.
Also, whenever I use the field on the support form to designate the email address to notify of updates, it always defaults to the account address. This is often why I initially miss your replies as that is a semi-monitored admin inbox for the team, rather than my primary inbox. Not sure if you were aware that happens.
Cheers
Eric Harth
Just noticed, this appears to be publisher lite, instead of the full version. Do you have a full version build to test?
Cheers
Eric Harth
Looks like you’ve got that update in 3.11.0, we’ll install and test that version. Also, good to see a fix for the bloq field being deleted as we’ve had that as a not so rare occurrence!