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: No languages on MSM extra sites

Status Resolved
Add-on / Version Publisher 2.8.3
Severity
EE Version 4.3.2

AdriaanSnoeren.com

Jul 20, 2018

Description:
Upgraded EE from 2 to 4 and now have the latest Publisher running on http://www.consmema.nl.
It’s a multi-site environment so http://www.ktb-machinery.nl and rothi.nl are the extra sites.
Only ktb-machinery.nl also has different languages but they are not visible in the language picker. Same code as consmema.nl, settings in Publisher > Languages correct and consmema.nl just works fine.

The EE 2 site had the language control plugin installed that we are not using anymore. I believe this shouldn’t be an issue but who know.

 

#1

BoldMinded (Brian)

Did you try re-saving each language and re-selecting the sites in which they appear? I don’t have an MSM instance setup right now, but below “Dev” is where the additional sites would be. https://screenshots.firefox.com/JBgEsbzbmGY30dT8/ee400.vm

#2

AdriaanSnoeren.com

Yes, I did re-save the languages. The sites appear as they should in the settings.

#3

BoldMinded (Brian)

And you don’t have the Language Control extension installed? The only issue you’re reporting is the language selector on the entry edit page doesn’t show all the languages for each site, right? Does this happen for all users or just some? Did you check the “Can change languages” setting in the Approval Settings page? Are all members checked?

#4

AdriaanSnoeren.com

No, it’s in the front-end. The {exp:publisher:languages} tag is working on the main site which is consmema.nl. The other two sites don’t display languages from this tag. Sorry if that wasn’t clear. The language selector in the back-end works just fine. And just to be clear, the Language Control extension WAS installed on the EE2 installation but didn’t get transferred to EE4.

#5

BoldMinded (Brian)

Can you share the full template code you’re using for that tag including parameters?

#6

AdriaanSnoeren.com

This is on the site that’s working:

<a href="#%22class=%22flag" title="{long_name}" class="flag flag-{publisher:current_language_code} current active"></a>
 {exp:publisher:languages show_current="no"}
  <a href="http://{translated_url}%22class=%22flag" title="{long_name}" class="flag flag-{short_name} choice inactive"></a>
 {/exp:publisher:languages}

And the one that isn’t working:

<a href="#%22class=%22flag" title="{long_name}" class="flag flag-{publisher:current_language_code} current active"></a>
 {exp:publisher:languages show_current="no"}
  <a href="http://{translated_url}%22class=%22flag" title="{long_name}" class="flag flag-{short_name} choice inactive"></a>
 {/exp:publisher:languages}
#7

BoldMinded (Brian)

What happens if you remove the show_current param?

#8

AdriaanSnoeren.com

Nothing, not even the default one comes into play.

#9

BoldMinded (Brian)

Also make sure that your cache is cleared and you have entered phrases for each language.

#10

BoldMinded (Brian)

Can you provide the CP login so I can take a look?

#11

BoldMinded (Brian)

Reminder don’t add login details in a comment, edit the ticket and add them in the fields provided. Thanks.

#12

AdriaanSnoeren.com

Comment has been marked private.

#13

BoldMinded (Brian)

I usually don’t like logging into live environments either, but I won’t edit anything, just want to take a look at the config (it may be quicker than this back and forth) if that is OK with you. Make a temp super admin account, you can delete it in a couple hours when I’m done.

#14

AdriaanSnoeren.com

Comment has been marked private.

#15

BoldMinded (Brian)

I think I see the issue. Do you have a dev/local/staging environment to test a new build in? Build link will be in the next private comment.

#16

BoldMinded (Brian)

Comment has been marked private.

#17

AdriaanSnoeren.com

The package you sent fixed the problem. Languages appear as they should now. Thanks!

Login to reply