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: Switching languages add multiple prefix

Status Resolved
Add-on / Version Publisher 1.6.12
Severity
EE Version 2.10

Rein

Jul 14, 2016

Hi brain,

if you go to this site: http://huisfeest.reinos-test.nl/en/home and switch to the language “dutch”, you see you get this url “http://huisfeest.reinos-test.nl/nl/en/home”. Switching to german, you get this url “http://huisfeest.reinos-test.nl/de/nl/en/home”

Before the update, it was working correctly.

I use the default template tag for switching.

{exp:publisher:languages}
                    <li>
                        <a href="{switch_language_url}">
                            <img alt="{long_name}" src="/assets/images/lang-{short_name}.png"/>
                        </a>
                    </li>
                    {/exp:publisher:languages}

Any idea?

Best,
Rein

#1

BoldMinded (Brian)

The CP login you provided does not work.

#2

BoldMinded (Brian)

Did you see the change log for 1.6.12? https://boldminded.com/add-ons/publisher/change-log

You said this is a new issue when upgrading, but the only major thing changed in 1.6.12 is the security fixed for the host lookup value. What version did you have installed before 1.6.12? Make sure your site_url is properly set.

#3

BoldMinded (Brian)

Appears to be an issue already fixed in the next 1.6.13 release.

Login to reply