Please consider support for non-multisite installation

Resolved cichy
(@cichy)

9 years, 1 month ago

Hi Team,

First of all splitting language versions into separate site instances is a great idea and I also think, as a user, that this is the natural way of handling the case of multilingual sites.

However, would it be possible for you to consider adding support for non-multisite installations? So, for example, the main language is on domain http://www.example.com which is a single installation and then another language English is on another single installation http://www.example.com/en/.

It could be beneficial in case one would like to use a plugin which is not compatible with multisite or when multisite is only a premium option. Regarding the latter, it is not that I don’t want to pay for premium plugins it is just that sometimes you need to decide whether you want to invest in one premium plugin or another. Regarding the former, if you have one plugin which is not compatible with multisite and you use it in your every project then MultilingualPress would be always rejected.

Best regards,
Przemek

Viewing 3 replies - 1 through 3 (of 3 total)

Thorsten Frommen
(@tfrommen)

9 years ago

Hi Przemek,

although I understand your reasoning, this is not something we will do.

MultilingualPress is 100 % based on the multisite feature of WordPress, for several reasons. Changing this would mean at least three things: a lot of work (for an unknown and yet assumed to be very small amount of people), changes ot the inner workings of the plugin (meaning almost the whole architecture as well as data structures), and last but not least loss of quite a lot functionality.

Currently, you can not only display translations of a post on the front end, but really manage all your multilingual content in a single installation (even on a single page!). Having MLP work with two completely separate WordPress installations would either mean you cannot do this any longer, or we would have to rebuild the whole infrastructure (or at least the part we are using) to allow for something like translating a post into multiple languages on one page on the fly.

If you don’t want (or cannot) use multisite for a project, then MLP is not for you – and this is OK.

However, there isn’t really any good reason for a plugin not being multisite compatible. Whatever the plugin does and for whatever reason it currently is not working properly in multisite, this should be fixable in almost no amount of time.

So, maybe you want to contact the authors and suggest making the plugin work in multisite…? 🙂

Cheers,
Thorsten

Thread Starter cichy
(@cichy)

9 years ago

Hi Thorsten,

Thank you for taking the time to reply to my inquiry.

MultilingualPress is 100 % based on the multisite feature of WordPress, for several reasons. Changing this would mean at least three things: a lot of work (for an unknown and yet assumed to be very small amount of people), changes ot the inner workings of the plugin (meaning almost the whole architecture as well as data structures), and last but not least loss of quite a lot functionality.

Understood. I only thought that it could be done as an addition to the core functionality, however, if this would mean rebuilding the whole architecture of the plugin then it is clear it cannot be done just like that. Perhaps this is an area for a different plugin then.

Thanks,
Przemek

Thread Starter cichy
(@cichy)

9 years ago

marking as resolved.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Please consider support for non-multisite installation’ is closed to new replies.