-
☆ A M B ☆
- 120 Posts
I got an enquiry from someone with an existing multi-lingual MODX site. The site was built by using separate MODX installations for each separate language! The whole thing is then pulled together into sub-domains (ie. www.mycompany.com/en/, www.mycompany.com/de/ etc.) Each country site is then maintained separately within it's own MODX installation.
However, the client wants to have only a single English-language "Our People" version so that they only have to maintain these pages in one place. Trying to figure out the best way to achieve this across multiple MODX installations and can only see this as being done through iframes? But as they are being deprecated, I wonder if there is a much better MODX solution that I have overlooked?
At the moment, I am still waiting to hear whether it's a Revo or Evo site but it was only built last year, so probably more likely to be Revo? Ideas for both options would be highly appreciated!
Thanks.
-
☆ A M B ☆
- 3,141 Posts
If Revo, I would try to sell them on migrating all the different sites into one MODX installation, so you can just use symlinks or something similar. It will also make it easier to manage as everyone logs in to the same site and you can share logins, content and extras.
If that's not an option, or they run evo, you can also use curl / file_get_contents or the likes in a simple snippet to get it from whatever source.
-
☆ A M B ☆
- 120 Posts
Thanks for your quick reply, Mark! The client actually isn't sure whether it's Evo or Revo, so will have to wait and see if he wants us to do the job and then get access. But I think it's more likely to be Evo going by his description of the Manager.
Will look into the curl bit - thanks!
It sounds like you're going to be doing some migrating.
As Mark suggests, you'll probably be happier if you move everything into one MODX Revolution site using either symlinks or contexts. That way you'll have just one MODX core to upgrade, though the migration may be a pain if it's an Evolution site, especially an older version. You may be able to use Provisioner to help with the migration.
BTW, the version of MODX should appear at the upper-left of the Manager.
------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone:
http://bobsguides.com/modx.html
-
☆ A M B ☆
- 120 Posts
Unfortunately, migration is not an option due to costs. This is not a site that I built or have any access to at the moment, only got an enquiry in to take over a few development bits. The potential client is a brand consultant who used a different developer to create the site last year for one of his own clients but this developer is no longer available. No budget there whatsoever to do major structural changes, so we would have to work with what we have, I'm afraid.
This is only at the quotation stage from my end, hence I rely on him for version info which he was not sure of during our conversation. Could therefore only go by his description of the backend (which he also did not have access to during our conversation but it sounds like Evo to me). Not straightforward! Was just trying to think of creative solutions to the issues in order to be able to estimate time required at lowest cost.
Thanks so much for your suggestions though - will relay that to the client but I don't think it's an option.
I understand completely. Migration is a major undertaking, especially for what is likely an older Evolution site. It's also very difficult to quote because it's hard to know what you might run into.
------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone:
http://bobsguides.com/modx.html
