Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with non translatable field #448

Open
ridom opened this issue Oct 28, 2016 · 0 comments
Open

Issue with non translatable field #448

ridom opened this issue Oct 28, 2016 · 0 comments

Comments

@ridom
Copy link

ridom commented Oct 28, 2016

Hello qTX team, hello @johnclause

I am experiencing an issue, first I want to say that I am not totally sure that it comes from the qTx plugin but there are some points that make me think it is.
First, I show you the errors I get :

Warning: strpos() expects parameter 1 to be string, array given in .../wp-includes/shortcodes.php on line 205
Warning: preg_match_all() expects parameter 2 to be string, array given in .../wp-includes/shortcodes.php on line 213
Warning: array_intersect(): Argument #2 is not an array in .../wp-includes/shortcodes.php on line 214
Array

(the string Array is displayed with the others error lines)

So, there is a field in page options called “Custom titlebar content” which is not translatable but which was already filed before I install the plugin.
When I delete the textual content and I save the modification, I get the errors shown above. Sometimes, the string Array is displayed alone (I mean without the warning error lines) BUT it is prefixed with one of the 2 language names (I don’t know if it is linked but it is the wordpress install language).

In order to try to make the errors disappear, I came back to the first revision, reload front and it works… But the point is, as soon as I save it again (even not making any change), the errors are back : the 3 lines errors if I am not lucky, ‘(language) Array’ if I am displaying the original wp language or just ‘Array’ if I am in english language.
As it was not working, I decided to fill it with raw multilingual format, I saved it but coming back to the field, I realised that some brakets had been added with non-sense:
what I added : [:de]DE[:en]EN[:]
after saving : [:de][:de]DE[:en]EN[:][:en]DEENDE[:]

You can see an instance of the bug here (probably not available for a long time) :
http://test.designforthemes.com/skstore01/de/kontact/

Have you ever heard about that issue.
What could I do?
Thanks for helping!
ridom

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant