Feng Forum
Support => Feng Office 3 => : MiKonst February 25, 2015, 09:00:33 AM
-
In module workspace since upgrade to 3.0, there is a problem with the display when the workspaces are written in cyrilic.
Workspaces are no longer displayed.
In versions up to 3.0 was support for Cyrillic names without problem.
Can you solve this?
I have people from Russia and would like to have this support of Russian names in workspaces.
Thx
-
Hmm actually I have just tried cyrillic characters in our demo (demo.fengoffice.com) and it worked like a charm.
Can you please try there and let us know how it goes?
If it works, it could be a server setting on your side preventing from doing so.
Best regards,
Francisco
-
In module workspace since upgrade to 3.0, there is a problem with the display when the workspaces are written in cyrilic.
Workspaces are no longer displayed.
In versions up to 3.0 was support for Cyrillic names without problem.
Can you solve this?
I have people from Russia and would like to have this support of Russian names in workspaces.
Thx
Session "default" started at 2015-03-20T16:27:29+0000
#1 ERROR: Error: json_encode(): Invalid UTF-8 sequence in argument in 'E:\inetpub\wwwroot\xxxxxx\application\views\json.php' on line 1 (error code: 2)
Time since start: 0.23001289367676 seconds
-
In module workspace since upgrade to 3.0, there is a problem with the display when the workspaces are written in cyrilic.
Workspaces are no longer displayed.
In versions up to 3.0 was support for Cyrillic names without problem.
Can you solve this?
I have people from Russia and would like to have this support of Russian names in workspaces.
Thx
Session "default" started at 2015-03-20T16:27:29+0000
#1 ERROR: Error: json_encode(): Invalid UTF-8 sequence in argument in 'E:\inetpub\wwwroot\xxxxxx\application\views\json.php' on line 1 (error code: 2)
Time since start: 0.23001289367676 seconds
Hmm have you tried in our Demo (demo.fengoffice.com) so that we can start discarding different things causing this issue? If it is a server setting, its solution is quite different from a code change.
-
the settings in the server are ok. I have two versions running 2.7 and 3.3.1. version 2.7 running perfectly. So, entwedr the problem in code or in DB. Please, you have more experience, help
-
Hmm have you tried in our Demo (demo.fengoffice.com) so that we can start discarding different things causing this issue? If it is a server setting, its solution is quite different from a code change.
In demo version is a professional. I work with community version 3.1.2, which is clear do? If I have the pro version, I will not write here.
There is a problem with decode. I ask but take this issue seriously.
-
Sorry.. I do not get it... did you try in our demo or not? How did it go?
If it does not work there, a screenshot would be appreciated, because it worked out for me.
Thank you.
Best regards,
Francisco
-
Sorry.. I do not get it... did you try in our demo or not? How did it go?
If it does not work there, a screenshot would be appreciated, because it worked out for me.
Thank you.
Best regards,
Francisco
Francisco, Thank you for your work.
The error that I have written, does not occur in your demo version.
I suspect that is a lot of work of your colleagues with professional version of the program.
Unfortunately, the community version has bugs with utf8 decoding (see above).
I hope this will be fixed at some point, so my message is here!
And I very warmly necessarily please forward this information to developers, so the correction of these errors is actually not that complicated: the website for selection from the work area gets a value that can not decode.
Many kind regards, Konstantin
-
Hi Konstantin,
In our emails exchange we did not get to talk about this matter, but I rather have it in the Forums so in case someone else experiences they can follow up on it. :)
What I meant is that in our servers we are not experiencing issues with the Cyrillic characters.
The utf8 decoding is not related to the Community Edition, Professional Edition or Enterprise Edition... but it is the same for everyone. This means that it should be a server side issue with its settings.
If you were able to solve this matter, it would be great to know how so that other people can solve it in case they face it.
Otherwise.. you can always consider using our cloud or getting at least a Basic Support Plan to have our Technical Team looking into your server.
Best regards,
Francisco