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.

Sign up for GitHub

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

Jump to bottom

account for translations_api returning WP_Error #105

Closed
herrvigg opened this issue Jun 21, 2018 · 2 comments
Closed

account for translations_api returning WP_Error #105

herrvigg opened this issue Jun 21, 2018 · 2 comments
Labels
legacy PR Legacy PR imported from original repo

Comments

@herrvigg
Copy link
Collaborator

herrvigg commented Jun 21, 2018 •
edited
Loading

Issue by entr
Friday Mar 27, 2015 at 12:45 GMT
Originally opened as qTranslate-Team/qtranslate-x#105

entr included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/105/commits
@herrvigg herrvigg added bug Something isn't working, reproducible legacy issue Legacy issue imported from original repo labels Jun 21, 2018
@herrvigg herrvigg mentioned this issue Jun 21, 2018
Closed
@herrvigg herrvigg changed the title IE 10 and up: Language Switching Buttons do not change content in TinyMCE fields account for translations_api returning WP_Error Jun 23, 2018
@herrvigg herrvigg reopened this Jun 23, 2018
@herrvigg herrvigg added legacy PR Legacy PR imported from original repo and removed bug Something isn't working, reproducible legacy issue Legacy issue imported from original repo labels Jun 23, 2018
@herrvigg
Copy link
Collaborator Author

Comment by johnclause
Friday Mar 27, 2015 at 16:28 GMT

Michel (@mweimerskirch), could you comment on this, since I believe that was in your patch?

@herrvigg
Copy link
Collaborator Author

Comment by mweimerskirch
Thursday Apr 02, 2015 at 11:38 GMT

Good idea @entr. It works great.
I wrote an additional patch that displays the error message in the admin interface (#113), so the user knows what went wrong (e.g. timeout, SSL error, etc?)

@herrvigg herrvigg mentioned this issue Jun 23, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
legacy PR Legacy PR imported from original repo
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@herrvigg