The plugin generated 345 characters of unexpected output during activation.

Hi,

Can you make a screen capture ? the problem i know during activation is when a user test polylang before and didn’t remove it completly.

A key need to be set in the config.php and generally user don’t set it.

This is the case for you ?

i’m thinking about putting the language definition in another way to skip this problem

Stéphane

thank you for the speedy reply Stephane. Let me tell you about the strange thing about it:

I had tested Falang on a test website, where I did use Polylang before, and the error was not there (and I also updated todays release). I have now installed on the brand new production site and the error appears. No need for a screenshot, it’s just a WP default red message alert saying “The plugin generated 345 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.“

I have unistalled and tried again, same result.

By the way, your plugin has now put my dashboard in English, thought the installation language was Italian, meaning that the default language now is stuck into English!

Hi,

The problem is fixed for the next update.

The default language show in falang is the language you write your content in WP. It’s your site language but you can have a different dashboard language , you can set it in your user settings.

It’s something i use a lot when i make support.

Stéphane

The default language show in falang is the language you write your content in WP. It’s your site language

hi again, sorry but Falang insists on making up its own default language. It starts in English with a message “the site language (in Settings > General) is not the same set by Falang as predefined. You must modify your default language in Worpress settings” , I do change it but Falang still keeps the english and the error message-

UPDATE: I had to click to make the black star appear

• This reply was modified 6 months, 1 week ago by devsaredead.

It’s something fixed in the next release , i putlish it monday , the star is for the default language it seem it was not set correctly in your case

Stéphane

The 1.3.55 version published today fix the problem

thank you for the excellent support. I shall test it and will let you know if anything goes wrong ??

Thanks, i have tested it , on clean install on tastewp but of course you can have a look too

Stéphane