Ciao Roberto,

first of all I have to say that this module really rocks! Great work!

I installed it on a fresh 4.7.5 and made the patches by hand (I still don't know how to do this professionally) and it works very well.

When I click on "create translation" I get an error message:

warning: strtr() [function.strtr]: The second argument is not an array. in /home/www/doc/11111/homepage.com/www/includes/common.inc on line 629.

I ignored it and it seems that everything works though.

I just wanted to let you know of this, maybe you know what it is...

Thank you again for your work, it's wonderful. I'm an ex-i18n user and your module is something like a release to me :-)

Comments

funana’s picture

funana commented

Hmmm. I read your Changelog and there you say "No patches are more necessary to core files.". In the Readme.txt you wrote "Apply the patches under the subdirectory patches."...

*confused

I will take the original core modules again and see how it works.

spooky69’s picture

spooky69 commented
Version: 4.7.x-2.0 » 5.x-1.x-dev

Same problem as above. It seems to be that the problem occurs when I have the localizer node module activated. Are there patches that need to be applied or should I assume that the latest release should have all required patches applied?

funana’s picture

funana commented

Hmmm. I use the patched core modules again and I could not reproduce the error... strange strange...

Roberto Gerola’s picture

Roberto Gerola commented

> warning: strtr() [function.strtr]: The second argument is not an array
Yes. It is already fixed.
Thanks.

Roberto Gerola’s picture

Roberto Gerola commented

> Hmmm. I read your Changelog and there you say "No patches are more necessary to core files.". In the Readme.txt you wrote "Apply the > patches under the subdirectory patches."...

> *confused

You are right.
During the evolution of the module, patching has been reintroduced.
I'll fix the Changelog.

Thanks.

Roberto Gerola’s picture

Roberto Gerola commented

>Same problem as above. It seems to be that the problem occurs when I have the
>localizer node module activated. Are there patches that need to be applied or should I
>assume that the latest release should have all required patches applied?

No. I've simply changed the syntax of the function localizer_t and I've missed to update
a call. Already fixed. A new version will be released in the next hours.

Thanks.

Roberto Gerola’s picture

Roberto Gerola commented
Assigned: Unassigned » Roberto Gerola
Status: Active » Fixed

Fixed in 5.1.4 version

Roberto Gerola’s picture

Roberto Gerola commented
Status: Fixed » Closed (fixed)