“Page Builder by SiteOrigin” work in “Polylang”
because there is created for each language has its own page.
@vadym Volos
WPGlobus works with all languages in just a single admin page
@vadym Volos
In current version WPGLobus don’t works with Page Builder by SiteOrigin
@alex Gor
I see what is not working. 🙂
You want feedback?
If you do not need help, tell me and I will not give feedback.
@vadim Volos
Do you have specific suggestions to improve WPGlobus?
one language = one page
1. There will be no problems with the plugins
2. If the WPGlobus will disable all pages will be available on the same links
3. If the pages will be available on their links will not have problems with the SEO, repost in social networks, with paid advertising.
@vadym Volos
ok, let’s get “one language = one page”.
As I understand, you like “Polylang” and want to get some similar functionality from WPGlobus?
@alex Gor
It is important that links remain the same if the plugin WPGlobus will be disabled. Because it will be a lot of problems with all the pages on the site. Besides links, it is important that the content of each page to remain the same as before.
@vadym Volos
Let’s look for multiple languages at eCommerce sites. The fun starts with thousands of products. Would you like to have every product multiplied in your database?
I think it’s better if every product will be multiplied in the database. Better than when something happens, all my products will no longer be available on the links. In two or three times more products is not so much. But it is much more reliable.
Think. Do not hurry. Consult. Weigh the pros and cons.
Hi Vadim,
– WPGlobus and Polylang are different, and so are qT, WPML, etc. Each one has pros and cons. We are not goong to change the way our plugin works, but we will continue improving it constantly.
– You are right, if you deactivate WPGlobus, the site will look terrible. We are planning to write a utility that will allow removing all languages except the main one. That should be a descent solution for cleaning up.
– You are also right about the Composer. There are many of them, and we believe that soon they all will support WPGlobus. We are more than happy to cooperate with all plugin and theme authors.
Thanks again for your feedback. We appreciate your support!
1.
Please do not close the topic, so as not to mislead people. Topic Title: Page Builder by SiteOrigin – only works for one language. When this plugin will work, then we can say that the issue is “resolved”.
2.
We are planning to write a utility that will allow removing all languages except the main one. That should be a descent solution for cleaning up.
Bad idea. If the plugin is disabled all languages have to work! Why remove them? The plugin can be disconnected for various reasons (such as maintenance or error), but when he turned off all the references and all pages in all languages should be available.
3.
Thanks again for your help. I appreciate your support!
Vadim,
The question you asked about Page Builder has been answered. At the moment, WPGlobus does not support it, as well as many other third party plugins. We do not have any specific plans on that. Nothing to add here.
The rest of the discussion, while is very interesting and productive, is off-topic. And again, there is nothing to add: WPGlobus will not duplicate pages, and the site will stop being multilingual once WPGlobus is deactivated.
Thanks again Vadim
