{"action":"created","issue":{"url":"https://api.github.com/repos/qtranslate/qtranslate-xt/issues/605","repository_url":"https://api.github.com/repos/qtranslate/qtranslate-xt","labels_url":"https://api.github.com/repos/qtranslate/qtranslate-xt/issues/605/labels{/name}","comments_url":"https://api.github.com/repos/qtranslate/qtranslate-xt/issues/605/comments","events_url":"https://api.github.com/repos/qtranslate/qtranslate-xt/issues/605/events","html_url":"https://github.com/qtranslate/qtranslate-xt/issues/605","id":356462584,"node_id":"MDU6SXNzdWUzNTY0NjI1ODQ=","number":605,"title":"Gutenberg support","user":{"login":"GasimGasimzada","id":807231,"node_id":"MDQ6VXNlcjgwNzIzMQ==","avatar_url":"https://avatars1.githubusercontent.com/u/807231?v=4","gravatar_id":"","url":"https://api.github.com/users/GasimGasimzada","html_url":"https://github.com/GasimGasimzada","followers_url":"https://api.github.com/users/GasimGasimzada/followers","following_url":"https://api.github.com/users/GasimGasimzada/following{/other_user}","gists_url":"https://api.github.com/users/GasimGasimzada/gists{/gist_id}","starred_url":"https://api.github.com/users/GasimGasimzada/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/GasimGasimzada/subscriptions","organizations_url":"https://api.github.com/users/GasimGasimzada/orgs","repos_url":"https://api.github.com/users/GasimGasimzada/repos","events_url":"https://api.github.com/users/GasimGasimzada/events{/privacy}","received_events_url":"https://api.github.com/users/GasimGasimzada/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-09-03T11:14:02Z","updated_at":"2018-09-03T14:03:49Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"I am opening this issue; so, we can discuss all Gutenberg development here if it is okay with you guys. I am willing to implement this feature but I need some feedback on this regarding how to proceed. Here is the problem that I am facing with this. Plugins such as WPML create separate posts for each language instead of using one post and doing string interpolation. That's why, implementing Gutenberg on that is much easier since every language post is separately stored in the database.\r\n\r\nWhen checking Gutenberg database record, it looks something like this:\r\n\r\n```\r\n<!-- wp:paragraph -->\r\n<p>Some paragraph</p>\r\n<!-- /wp:paragraph -->\r\n```\r\n\r\nOn the other hand, qTranslate-X adds the following syntax for database records. `[:en]...[:de]...`. \r\n\r\nIs there a way to know if there is a chance for these boxes to clash? I can do a big database change to separate these texts into a separate table with columns such as:\r\n\r\npost_id, language, title, content, date_published\r\n\r\nAs a result, this will also increase page performance because we will be able to select much less data from the database. Writing a migration tool will also be easy but the whole thing is going to take some time. If everyone agrees and approves this idea, I can work on it and get it running in a week or two with my limited availability.\r\n\r\nMoreover, there are two problems that arise from qTranslate implementation:\r\n\r\n1. qTranslate uses tinymceInit function and if we use Gutenberg, the function does not exists, meaning we get an error and nothing is saved. I will investigate this and try to fix and make qTranslate not dependent on tinymce when using gutenberg.\r\n\r\n2. Gutenberg editor takes up the entire space for the content editor and as far as I can tell, there is no way to add content above the editor. So, my suggestion is that we add language selectors to the \"top bar\" (the black bar that is always on top in the admin page). This can also give a better and cleaner UI that will look nice with WP design language.\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/qtranslate/qtranslate-xt/issues/comments/418124902","html_url":"https://github.com/qtranslate/qtranslate-xt/issues/605#issuecomment-418124902","issue_url":"https://api.github.com/repos/qtranslate/qtranslate-xt/issues/605","id":418124902,"node_id":"MDEyOklzc3VlQ29tbWVudDQxODEyNDkwMg==","user":{"login":"dschmidtke","id":11058383,"node_id":"MDQ6VXNlcjExMDU4Mzgz","avatar_url":"https://avatars1.githubusercontent.com/u/11058383?v=4","gravatar_id":"","url":"https://api.github.com/users/dschmidtke","html_url":"https://github.com/dschmidtke","followers_url":"https://api.github.com/users/dschmidtke/followers","following_url":"https://api.github.com/users/dschmidtke/following{/other_user}","gists_url":"https://api.github.com/users/dschmidtke/gists{/gist_id}","starred_url":"https://api.github.com/users/dschmidtke/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dschmidtke/subscriptions","organizations_url":"https://api.github.com/users/dschmidtke/orgs","repos_url":"https://api.github.com/users/dschmidtke/repos","events_url":"https://api.github.com/users/dschmidtke/events{/privacy}","received_events_url":"https://api.github.com/users/dschmidtke/received_events","type":"User","site_admin":false},"created_at":"2018-09-03T14:03:49Z","updated_at":"2018-09-03T14:03:49Z","author_association":"NONE","body":"Thanks for making a first step to Gutenberg support. I must admit that I did not study this as much as you already did. However, I think a design principle of qTranslate was to put everything into the wp_posts table instead of opening additional tables for posts by language. I would prefer to stick to the old principle and I don't see a reason why the language tags of qTranslate might not play nice with the Gutenberg comments. As I see it, the retrieval of a post goes like that: 1. Pull the post from the database; 2. Extract the content for the requested language; 3. Feed that to Gutenberg and let it do its block magic."}}
{"actor":{"display_login":"dschmidtke"}}