qTranslate-XT (eXTended) - reviving qTranslate-X multilingual plugin for WordPress. A new community-driven plugin soon. Built-in modules for WooCommerce, ACF, slugs and others.
License: GNU General Public License v2.0
Monday Jan 12, 2015 at 21:41 GMT
Originally opened as qTranslate-Team/qtranslate-x#4
Hi,
I noticed, that adding new Pages to a Menu breaks the translation.
Upon saving the now changed menu every old translation gets deleted.
Step 1: Create a new test menu /wp-admin/nav-menus.php
Step 2: Add some pages
https://www.dropbox.com/s/sltppu1khin1btc/Screenshot%202015-01-12%2022.29.12.png?dl=0
Step 3: Add more pages
https://www.dropbox.com/s/kr9uxyze44dtkc8/Screenshot%202015-01-12%2022.29.30.png?dl=0
https://www.dropbox.com/s/gkusl97zj1nmd7n/Screenshot%202015-01-12%2022.36.45.png?dl=0
Step 4: Save Menu
https://www.dropbox.com/s/8idafcrp1zvj39m/Screenshot%202015-01-12%2022.29.40.png?dl=0
As you can see only the default language (and the translations of the last item) are preserved.
I'm fine with the ... tags, but preserving these upon adding new items would be great 👍
Monday Feb 23, 2015 at 20:02 GMT
Originally opened as qTranslate-Team/qtranslate-x#30
I really like that qtranslate-x supports translating custom (meta) fields. However, it is not always clear, which fields are translatable, and which are not.
This could be improved upon by visually highlighting the translatable field. For example with a small flag icon in at the top right of each field. Like this maybe (option 1):
There are probably better ideas for highlighting the fields, but this is just a first idea. What do you think?
Saturday Feb 14, 2015 at 13:11 GMT
Originally opened as qTranslate-Team/qtranslate-x#19
getting latest changes
ddon included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/19/commits
Sunday Feb 15, 2015 at 11:03 GMT
Originally opened as qTranslate-Team/qtranslate-x#20
xhaleera included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/20/commits
Monday Jan 12, 2015 at 15:30 GMT
Originally opened as qTranslate-Team/qtranslate-x#3
qtranslate.pot catalog is too old.
I've started with .pot from the very good mqTranslate and most strings are the same, way more than original qtranslate.pot.
Please update .pot file so that we can keep up with the translations.
Great work by the way, hope this will be the future of qTranslate platform, with all childs merged into one :)
I'm very happy with this joint solution.
Best regards
Pedro Mendonça
Thursday Feb 26, 2015 at 18:17 GMT
Originally opened as qTranslate-Team/qtranslate-x#49
Hi, i'm pretty new to the higher functions of github, so i'm not sure if commenting to a closed issue reopens them. So to be sure that you see it, i paste my response here.
Please be free to delete this issue if you saw my response in the closed thread.
Hi again!
Sorry, that was a miscommunication. This is really about "Hide URL Information for Default language" and the fact that after going to the secondary language, visiting the site without language path gets you to the secondary language again.
Thank you for the clarification about your reasons to "get" the language in the order that it does. I see many things clearer now and i can understand the reasons.
I think the reason that so many "mqtranslate-to-qtranslate-x-switchers" like me have a problem with this is that its completely opposite to what we were used to from mqtranslate or qtranslate. mqtranslate didn't use cookies or Browser Redirection, so this is new to us and sometimes breaks functionality on existing websites.
Maybe we (you) can implement a compatibility function that uses my "fix" above if activated. It could be called "mqtranslate redirect compatibility" or something like this ;)
Happy Coding,
Kuchenundkakao
Saturday Feb 21, 2015 at 11:10 GMT
Originally opened as qTranslate-Team/qtranslate-x#29
In my "cleanup" patch I accidentally wrote code that's only compatible with PHP >= 5.4, but unfortunately, some people are still using 5.3.
mweimerskirch included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/29/commits
Sunday Jan 18, 2015 at 13:13 GMT
Originally opened as qTranslate-Team/qtranslate-x#8
Hello,
current version of plugin makes for me the wrong translation of URL.
I am switched to non-default language and trying to use search form produces wrong URL
the blog is not on home url, but on subpage: http://mypageblog/blog/
typing the query in search box produces wrong URL http://mypageblog/blog/pl/pl/?s=dsa
commenting out in function:
function qtranxf_fixSearchForm($form) {
//$form = preg_replace('#action="[^"]*"#','action="'.trailingslashit(qtranxf_convertURL(get_home_url())).'"',$form);
return $form;
}
fixes the problem, the URL is correct: http://mypageblog/blog/pl/?s=dsa
i guess there is some kind of problem in the qtranxf_convertURL function.
more info available upon request.
best regards,
Pawel
Tuesday Feb 24, 2015 at 12:11 GMT
Originally opened as qTranslate-Team/qtranslate-x#37
As the title says, if you try to use the "convert database" function, you get a lot of errors because no mysql connection is opened.
Please replace lines 81 and 97 in the admin/admin_utils.php with the following:
$wpdb->query($wpdb->prepare('UPDATE '.$wpdb->posts.' set post_content = %s, post_title=%s, post_excerpt=%s WHERE ID=%d',$content, $title, $excerpt, $post->ID));
Wednesday Feb 25, 2015 at 09:20 GMT
Originally opened as qTranslate-Team/qtranslate-x#41
The number of characters are trimmed accordingly at default EN page .
However, when I navigate to ZH page. The number of characters are trimmed wrongly with get_the_excerpt();
Friday Feb 20, 2015 at 21:36 GMT
Originally opened as qTranslate-Team/qtranslate-x#26
mweimerskirch included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/26/commits
Friday Feb 13, 2015 at 13:01 GMT
Originally opened as qTranslate-Team/qtranslate-x#18
Added textdomain to strings that had their textdomain cutted in some commits
Correction to .pot (should be checked the generatiing process so it don't happen again)
Portuguese language update
pedro-mendonca included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/18/commits
Tuesday Feb 24, 2015 at 11:57 GMT
Originally opened as qTranslate-Team/qtranslate-x#35
I just did a migration from mqtranslate to qtranslatex and get some errors – perhaps the given strings or data are not nice validated? Site seems to work.
require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), include('/themes/lucas/front-page.php'), get_footer, locate_template, load_template, require_once('/themes/lucas/footer.php'), wp_footer, do_action('wp_footer'), call_user_func_array, Debug_Bar->render, __, translate, apply_filters('gettext'), call_user_func_array, qtranxf_gettext, qtranxf_use, get_class
require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), include('/themes/lucas/front-page.php'), get_footer, locate_template, load_template, require_once('/themes/lucas/footer.php'), wp_footer, do_action('wp_footer'), call_user_func_array, wp_admin_bar_render, do_action_ref_array, call_user_func_array, wp_admin_bar_updates_menu, wp_get_update_data, wp_get_translation_updates, get_site_transient, get_site_option, get_option, apply_filters('option__site_transient_update_themes'), call_user_func_array, qtranxf_useCurrentLanguageIfNotFoundUseDefaultLanguage, qtranxf_use, qtranxf_use, get_class
require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), include('/themes/lucas/front-page.php'), get_footer, locate_template, load_template, require_once('/themes/lucas/footer.php'), wp_footer, do_action('wp_footer'), call_user_func_array, wp_admin_bar_render, do_action_ref_array, call_user_func_array, wp_admin_bar_updates_menu, wp_get_update_data, wp_get_translation_updates, get_site_transient, get_site_option, get_option, apply_filters('option__site_transient_update_core'), call_user_func_array, qtranxf_useCurrentLanguageIfNotFoundUseDefaultLanguage, qtranxf_use, qtranxf_use, qtranxf_use, qtranxf_use, qtranxf_use, get_class
require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), include('/themes/lucas/front-page.php'), get_footer, locate_template, load_template, require_once('/themes/lucas/footer.php'), wp_footer, do_action('wp_footer'), call_user_func_array, wp_admin_bar_render, do_action('wp_before_admin_bar_render'), call_user_func_array, wp_customize_support_script, home_url, get_home_url, apply_filters('home_url'), call_user_func_array, qtranxf_home_url, qtranxf_get_url_for_language, qtranxf_parseURL
require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), include('/themes/lucas/front-page.php'), get_footer, locate_template, load_template, require_once('/themes/lucas/footer.php'), wp_footer, do_action('wp_footer'), call_user_func_array, wp_admin_bar_render, do_action('wp_before_admin_bar_render'), call_user_func_array, wp_customize_support_script, home_url, get_home_url, apply_filters('home_url'), call_user_func_array, qtranxf_home_url, qtranxf_get_url_for_language, qtranxf_parseURL
require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), include('/themes/lucas/front-page.php'), get_footer, locate_template, load_template, require_once('/themes/lucas/footer.php'), wp_footer, do_action('wp_footer'), call_user_func_array, wp_admin_bar_render, do_action('wp_before_admin_bar_render'), call_user_func_array, wp_customize_support_script, home_url, get_home_url, apply_filters('home_url'), call_user_func_array, qtranxf_home_url, qtranxf_get_url_for_language, qtranxf_parseURL
require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), include('/themes/lucas/front-page.php'), get_footer, locate_template, load_template, require_once('/themes/lucas/footer.php'), wp_footer, do_action('wp_footer'), call_user_func_array, wp_admin_bar_render, do_action('wp_before_admin_bar_render'), call_user_func_array, wp_customize_support_script, home_url, get_home_url, apply_filters('home_url'), call_user_func_array, qtranxf_home_url, qtranxf_get_url_for_language, qtranxf_parseURL
require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), include('/themes/lucas/front-page.php'), get_footer, locate_template, load_template, require_once('/themes/lucas/footer.php'), wp_footer, do_action('wp_footer'), call_user_func_array, wp_admin_bar_render, do_action('wp_before_admin_bar_render'), call_user_func_array, wp_customize_support_script, home_url, get_home_url, apply_filters('home_url'), call_user_func_array, qtranxf_home_url, qtranxf_get_url_for_language, qtranxf_parseURL
require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), include('/themes/lucas/front-page.php'), get_footer, locate_template, load_template, require_once('/themes/lucas/footer.php'), wp_footer, do_action('wp_footer'), call_user_func_array, wp_admin_bar_render, do_action('wp_before_admin_bar_render'), call_user_func_array, wp_customize_support_script, home_url, get_home_url, apply_filters('home_url'), call_user_func_array, qtranxf_home_url, qtranxf_get_url_for_language, qtranxf_parseURL
require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), include('/themes/lucas/front-page.php'), get_footer, locate_template, load_template, require_once('/themes/lucas/footer.php'), wp_footer, do_action('wp_footer'), call_user_func_array, wp_admin_bar_render, do_action('wp_before_admin_bar_render'), call_user_func_array, wp_customize_support_script, home_url, get_home_url, apply_filters('home_url'), call_user_func_array, qtranxf_home_url, qtranxf_get_url_for_language, qtranxf_parseURL
require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), include('/themes/lucas/front-page.php'), get_footer, locate_template, load_template, require_once('/themes/lucas/footer.php'), wp_footer, do_action('wp_footer'), call_user_func_array, wp_admin_bar_render, do_action('wp_before_admin_bar_render'), call_user_func_array, wp_customize_support_script, home_url, get_home_url, apply_filters('home_url'), call_user_func_array, qtranxf_home_url, qtranxf_get_url_for_language, qtranxf_parseURL
Thursday Jan 29, 2015 at 09:46 GMT
Originally opened as qTranslate-Team/qtranslate-x#12
.pot catalog updated with new strings found.
Portuguese files updated also.
pedro-mendonca included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/12/commits
Wednesday Feb 25, 2015 at 14:43 GMT
Originally opened as qTranslate-Team/qtranslate-x#44
mweimerskirch included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/44/commits
Friday Feb 20, 2015 at 18:48 GMT
Originally opened as qTranslate-Team/qtranslate-x#24
Use core WordPress methods for the language file updates instead of probing the SVN directories (which does not always work). Another advantage of this approach is that the "admin" and "network-admin" translations are updated as well.
mweimerskirch included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/24/commits
Friday Feb 20, 2015 at 17:38 GMT
Originally opened as qTranslate-Team/qtranslate-x#23
I fixed a few translatable strings (the translation domain "qtranslate" was missing).
And I added a shell script that makes it much easier to update the language files. It just needs to be run in the "lang" folder. I noticed that the files in the "admin" directory are not included in the current pot/po files.
mweimerskirch included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/23/commits
Tuesday Feb 24, 2015 at 18:47 GMT
Originally opened as qTranslate-Team/qtranslate-x#39
get_terms will translate all terms (for example for the tag cloud)
term_description will translate the term description (for example for themes that show the WooCommerce product category description)
soft79 included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/39/commits
Saturday Jan 10, 2015 at 08:10 GMT
Originally opened as qTranslate-Team/qtranslate-x#1
Good morning John,
I just upgraded my blog to qTranslate-X 2.8. After doing that, none of my posts were reachable anymore - everything resulted in 404s. When I disabled qTranslate-slugs, my posts were reachable again, so there seems something in qTranslate-X 2.8 that breaks if slugs is also used.
This issue has made me rethink the current approach with qTranslate-X and qTranslate slugs. I think we're running into a fundamental issue here - as long as the two plugins are separate and are thus not always tested together, issues like these will keep cropping up. Of course, it'd be possible to try and fix slugs everytime qTX gets upgraded (or the other way round), but that would lead to a lot of uncertainty and frustration for users because it's not ensured that a working combination is installed.
So I'd like to discuss whether you think it makes sense to include the slugs functionality in qTranslate-X itself. If you agree (and also if @LC43 doesn't see a problem with that since it's his code) I would volunteer to include that functionality. What do you think?
Best regards,
Bastian
Monday Feb 23, 2015 at 22:38 GMT
Originally opened as qTranslate-Team/qtranslate-x#31
The following is a minor issue I noticed while digging through the code.
The original qtranslate used HTML comments as separation characters:
<!--:en-->.....<!--:-->
A big advantage of this notation was that if you happened to use this notation in the WYIWYG editor, it would be escaped automatically and saved correctly:
<!--:el-->.....<!--:-->
qtranslate-x uses the shorter versions:
[:en]......
When entered manually in the WYSIWYG editor (e.g. if you want to write an article about qtranslate-x), the codes disappear when saving, because they are not escaped.
On a related note, the original qtranslate codes disappear as well (which didn't happen with the original version). This might be because the "split_regex" handles both separators at the same time.
Thursday Feb 26, 2015 at 11:52 GMT
Originally opened as qTranslate-Team/qtranslate-x#48
Replaced mysql_real_escape_string with $wpdb->prepare to avoid errors happening under PHP 5.5
kuchenundkakao included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/48/commits
Monday Feb 09, 2015 at 20:50 GMT
Originally opened as qTranslate-Team/qtranslate-x#14
ddon included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/14/commits
Thursday Feb 19, 2015 at 18:31 GMT
Originally opened as qTranslate-Team/qtranslate-x#21
Hi qTranslateTeam,
First, thank you for your great work! Since I found that this plugin is actively developed, I'll try to do a feature request.
I would be very pleased to see an option in the admin panel to also show posts in the default language when a translation is not available. Currently, (if I'm correct) this is only possible for the title of the post.
Something like this would be perfect:
Sorry, this entry is only available in Language
to:
Sorry, this entry is only available in Language:
post in default language here
Thanks!
Friday Feb 20, 2015 at 15:16 GMT
Originally opened as qTranslate-Team/qtranslate-x#22
mweimerskirch included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/22/commits
Friday Feb 20, 2015 at 19:06 GMT
Originally opened as qTranslate-Team/qtranslate-x#25
Hi,
I wrote also in wp support. After migrating almost painless from mqTranslate I found out that Tags and Categories are not translated after the migration.
I have a bilingual site (English- Italian) and Italian tags/Categories are not present anymore. Clicking the language button only English version is available of both. Pages and Posts works correctly. If you visit http://www.norwayinteractive.biz/ changing language can see that About Us menu item changes because is a page title while other items not, they are tags and categories.
I wish you can find the fix because there's no error log in the php panel of server site
thanks
I tested with other themes too and tried to deactivate also some plugins but nothing changes and tags/categories are not available in Italian always English is shown.
Tuesday Jan 27, 2015 at 11:21 GMT
Originally opened as qTranslate-Team/qtranslate-x#11
pedro-mendonca included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/11/commits
Wednesday Feb 11, 2015 at 07:08 GMT
Originally opened as qTranslate-Team/qtranslate-x#16
Hello,
After I install the https://wordpress.org/plugins/qtranslate-x/ the latest version it disable the Add Media and Text option and I cannot post my content fine, so do you have any idea?
thanks
Monday Jan 12, 2015 at 13:55 GMT
Originally opened as qTranslate-Team/qtranslate-x#2
Changed hardcoded strings to translatable.
pedro-mendonca included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/2/commits
Wednesday Feb 25, 2015 at 09:00 GMT
Originally opened as qTranslate-Team/qtranslate-x#40
Trigger a custom event when addCustomContentHooks is called to allow themes and plugin developers to add their own custom content hooks.
Usage example:
jQuery(document).on('qTranslateX:addCustomContentHooks', function(event, qtx, form) {
jQuery('.acf-field-text .acf-input-wrap input').each(function() {
qtx.addContentHookById(this.id, form);
});
});funkjedi included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/40/commits
Wednesday Jan 14, 2015 at 11:36 GMT
Originally opened as qTranslate-Team/qtranslate-x#6
Joined "SEO friendly" string, because not in all languages make sense to translate SEO + 'friendly' (string).
pedro-mendonca included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/6/commits
Thursday Feb 26, 2015 at 11:39 GMT
Originally opened as qTranslate-Team/qtranslate-x#47
Hi,
Platform info:
Problem:
On a clean install + qtranslate-x I get the following error when editing a post (that has the visual tab active on load)
Uncaught TypeError: Cannot read property 'getNode' of undefined
Steps to reproduce:
This bug only occurs when "Visual tab" is the active one on load. If for example "Text" and I switch to "Visual" there is no error.
I have the feeling that it is trying to access an element in the DOM that at that point isn't loaded/ready yet. I need to find some time to investigate further.
Tuesday Feb 24, 2015 at 16:37 GMT
Originally opened as qTranslate-Team/qtranslate-x#38
After doing a security review of this plugin I found that site/blog-admins are able to include javascript tags and other HTML markup in text-fields that could allow the inclusion of malicious javascript on every page, e.g.
Language Name: English <script>alert(document.cookie);</script>
While site-admins might be trusted on single-site installations, on multi-site installations the owners/admins of individual sites cannot necessarily be trusted. This pull-request runs the user-inputs in the configuration screens through WP's built-in input-validation functions. For more information, see: http://codex.wordpress.org/Data_Validation#Input_Validation
adamfranco included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/38/commits
Tuesday Feb 24, 2015 at 11:45 GMT
Originally opened as qTranslate-Team/qtranslate-x#34
Regarding this discussion on the Wordpress forums.
Language toggle only affects the first field with a custom class defined.
Wednesday Feb 25, 2015 at 16:17 GMT
Originally opened as qTranslate-Team/qtranslate-x#45
Widget now passes validation.
acidicX included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/45/commits
Monday Feb 23, 2015 at 23:14 GMT
Originally opened as qTranslate-Team/qtranslate-x#32
I'm still trying to make the code more readable and easier to test and extend. IMHO the "xsplit" function can be removed. The function was necessary for qtranslate to be compatible with older browsers. Newer browser that implement ECMAScript 5 (this includes IE 9 in "standards mode") do not need this any longer. This would make the code a bit more readable, but IE 8 on the other hand would no longer be compatible. However, as WordPress displays a big warning when you use the admin area with IE 8 (or other old browsers), this should not be a problem.
mweimerskirch included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/32/commits
Tuesday Feb 24, 2015 at 09:17 GMT
Originally opened as qTranslate-Team/qtranslate-x#33
Hi Guys,
Seems like development is going on at a hectic pace for qtranslate-x, thought I would bring this post to your attention as it has a proposed solution included in post 25.
https://wordpress.org/support/topic/default-language-cant-be-chosen?replies=26
Friday Jan 23, 2015 at 09:47 GMT
Originally opened as qTranslate-Team/qtranslate-x#10
.pot Catalog is now up to date to verstion 3.0
found new string "Add to Menu"
Portuguese language files updated to this 3.0 .pot
pedro-mendonca included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/10/commits
Saturday Feb 21, 2015 at 09:52 GMT
Originally opened as qTranslate-Team/qtranslate-x#28
It should prevent many bugs for some users.
xhaleera included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/28/commits
Monday Feb 09, 2015 at 21:12 GMT
Originally opened as qTranslate-Team/qtranslate-x#15
Since I work here with many Estonian clients and I always install qTranslate-X on their blog, I have to manually add Estonian language every time I install this plugin. I hope we can add this language to default list if nobody minds.
ddon included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/15/commits
Thursday Feb 26, 2015 at 21:25 GMT
Originally opened as qTranslate-Team/qtranslate-x#50
Added '.' to end of string, corrected php and .pot
Updated portuguese language files
pedro-mendonca included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/50/commits
Wednesday Jan 14, 2015 at 02:16 GMT
Originally opened as qTranslate-Team/qtranslate-x#5
Theme: any, "Twenty Fifteen" would do.
Plugins: can be qTranslate-X only, I do not think it is a compatibility problem with other plugins.
At least two languages, for example, en and de, to be specific.
Steps to reproduce the problem:
<!--:en-->EN<!--:--><!--:de-->DE<!--:-->, which is normal.<!--:en--><p>EN</p><!--:--><!--:de-->DE<!--:-->, where EN was the active language at time of pressing "Update". This part is kind of explainable, TinyMCE embraced active text with <p></p>, although it does not do so, when plugin is deactivated.But then something really strange happens:
<!--:en--><p>EN</p><p> </p><!--:--><!--:de-->DE<!--:--><p><!--:en--><p>EN</p><p> </p><p><!--:--><!--:de-->DE<!--:--></p><p> and </p> do not match anymore.Further clicking “Update” does not modify this text anymore.
I have been printing various variables on java console, but those <p> did not show up anywhere I looked so far. I have no idea how they get into the database.
If people consistently keep editor at "Visual" mode, they apparently do not notice a problem. Nobody complained about this yet, but we'd better to clear it out before somebody does.
P. S. I first discovered this in the original qTranslate, and I thought that after cleaning the code, it will go away on its own, but it did not so far.
Thursday Feb 12, 2015 at 00:02 GMT
Originally opened as qTranslate-Team/qtranslate-x#17
This is a continuation of WP discussion https://wordpress.org/support/topic/the-latest-beta-from-github-is-good-for-testing-thank-you on the topic initiated by side777.
side777: I get a WordPress database error Unknown column 'wp_posts.post_content' in 'where clause' for query SELECT * FROM wp_comments [...] but only on some sites of my multisite network. still investigating.
side777: Unfortunately i could not reproduce the error with a clean 2015 - BUT get_comments() still returns an empty array! The 2015 recent comment widget DOES return the comments, but ALL, also for untranslated posts, though.
johnclause: I guess in some cases this query gets executed without wp_posts table included. What are those cases? Do we abort this function in such cases? Or do we force a reference to wp_posts in somehow?
side777: I think this is not a good approach anyway - in worst case you query 1000s of comments WITH the corresponding posts, PLUS filtering the post content - I wrote my own solution a while ago... I think it's way more effective to save the current language to a comment meta when the comment is saved. this way you can easily query comments by meta.
johnclause: Sure that would be much better. Unfortunately, qTranslate is not designed for big sites with many languages and huge content to begin with. It does have severe performance problems in many places, not just this one. My priority is to make it work in a minimal, but bug free way, so that people can continue to use it. Most of qTranslate* clients, I believe, are small bi-lingual (not multi-) sites and they are ok with this version of free translation framework. I would worry about the performance issues later, when time comes. For now we need to figure out how to fix this query issue as soon as possible, so that I could release 3.0. Then I will be happy to come back and redesign this piece as well as other places in a much more efficient way. And I believe that those missing if statements, which we need to figure out now, will be useful to know when we do optimization.
Tuesday Feb 24, 2015 at 12:06 GMT
Originally opened as qTranslate-Team/qtranslate-x#36
The language menu prints a-tags without href, the image flags have no alt attribute and the li-tags have no classes what language ist currently chosen or such. This makes it really difficult to style the language-menu
Thursday Jan 22, 2015 at 19:15 GMT
Originally opened as qTranslate-Team/qtranslate-x#9
Fix incorrect Pedro :)
pedro-mendonca included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/9/commits
Wednesday Feb 04, 2015 at 13:47 GMT
Originally opened as qTranslate-Team/qtranslate-x#13
pedro-mendonca included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/13/commits
Wednesday Jan 14, 2015 at 12:43 GMT
Originally opened as qTranslate-Team/qtranslate-x#7
...mprove performance -- see https://wordpress.org/support/topic/evidence-on-how-slow-and-inefficient-qtranslate-is-please-do-something.
janbernloehr included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/7/commits
Wednesday Feb 25, 2015 at 12:43 GMT
Originally opened as qTranslate-Team/qtranslate-x#43
The widget is not getting language files, shows english text.
Wednesday Feb 25, 2015 at 22:52 GMT
Originally opened as qTranslate-Team/qtranslate-x#46
otherwise the translations are not available inside the constructor.
Fixes #43
mweimerskirch included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/46/commits
Friday Feb 20, 2015 at 23:14 GMT
Originally opened as qTranslate-Team/qtranslate-x#27
Hi Michel (@mweimerskirch), I am wondering, since you seem pretty familiar with both codes, mq- and -x, could you take a look at the problem with WP Editor https://wordpress.org/plugins/wp-editor/? Users report, https://wordpress.org/support/topic/wp-edit-modifying-pages-in-visual-mode-not-working, it working in mq-, while it not working in -x. Would you be able and have time to look for a reason? I would not expect a fix to be easy, but at least understanding the reason why it does not work in -x would be a good start. Thanks a lot in any case for all your help.
Wednesday Feb 25, 2015 at 10:04 GMT
Originally opened as qTranslate-Team/qtranslate-x#42
This allows theme and plugin authors to more easily configure custom fields without having the user manually edit the configuration.
mweimerskirch included the following code: https://github.com/qTranslate-Team/qtranslate-x/pull/42/commits
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.