Elxis 4 and conversion

[xmanhattan]

Hello all,

While testing (locally) the possibilty of converting to Elxis 4 I would like to ask a few questions.
I did a conversion and noticed that it did not carry over the Greek content. 

I installed a copy of my current Elxis 2009 site and Elxis 4 but only in English under c:\wamp\www\bman and c:\wamp\www\nautilus respectively.

When the conversion ran it displayed the pages with Greek content and asked if there were pages that they were translated from, I simply clicked on proceed.

Was this the way it should work or should I have assigned the additional language to Elxis 4 before proceeding with the conversion?

Another question I wanted to ask but never did is, what method does Elxis 4 use with regard to mobile?
Is it css based or program based with something like http://mobiledetect.net/ ?

Very nice job with the converter!

[datahell]

The Converter has an option if you want to convert all content or not. If you select Yes (convert all content) you will get a mix of all language items in the final site. I dont recommend this option. To get a really multi-lingual output do the following:

1. Both sites should have the same default language, this is VERY important.
2. Convert all content: No
3. Run the converter and at the end you will be asked to convert the multilingual content. There you can assign content in other than the default language to Elxis 4.x translation items for the converted articles or menu items.

Example.
Page in English (default): Contact us is converted to Contact Us
Page in Greek: Επικοινωνία set it as a translation for Contact us
Page in French:  Contactez-nous set it as a translation for Contact us
etc..

Regarding your second question:

Elxis 4.x detects mobile devices and tablets and generates a lighter output. Then the template makes a mobile friendly layout that might be responsive or not. This I believe is a better solution as the pages are lighter and load faster on mobile devices. Only responsive solutions have the negative that the all content is always get loaded (so pages are heavier) and the template just hides or re-arranges the content in order to become mobile friendly. More information in Elxis Docs.

[xmanhattan]

First Datahell, I want to say thank you for all of the work you do to create a fantastic piece of software.

After running the converter again and seeing the results, I think that its a good idea to reorganize my website first and then convert it.  After that it is going to take some time to feel comfortable with all the features and power of the new program.

[datahell]

Thanks Peter, I believe this tool was highly needed. The converter, as in your case, is also a good opportunity to remove garbage items that have been left forgotten on the old site for a long time, and clean it. Old sites have unused articles and categories, unpublished menus, duplicated modules assigned to nowhere, etc. The new site you will be much more organized and clean.

The key to a good conversion is to work a little on the converted site after the converter finish its job. Don't leave it as is. The converter transfers the data and makes them compatible, it doesn't build the layout and style of the web site. After the conversion install and configure modules, improve menus and content, etc. I released Elxis Converter v1.1 yesterday which fixes a few issues I noticed mostly on IOS Reservations conversion. I run the converter on 2 online sites with, I believe, very good to excellent results.