Hi there!
Sorry, I have problems to follow you?
If you mean the installation, it went sooooo good and easy. The only problem was the fields import. As Alex said, there needs to be more work done, I thought it would be most important to inform the difficulties.
Do you have problems? It would be interesting to share and exchange. BTW, I read the browser problem. For your information, Alex loves explorer and so the best is to use it also.
If you mean parts that I could import Links, NO, I could solve it only in a bad way.
What really happened is that, I beleive, that the first import of a application would go through correct, with some basic problems. The big problem may start with the second application. Since the second time the community table will be once again put to comparision for the import, it would be a big conflict to ressolve as to how to get the second application fields match with the comms and import them too. The most complicated task would be then the third.
The GT application has different field names, values and field properties and thats the problem.
I suggested Alex to bring out a new version of each application first as a conversion "BEFORE" going to the comms concept. By this way, of converting the application first into a modified tables would not destroy anything i.e. data. With this step, some of the fields will be shifted into different tables. Then remains in the user tables only those fields that are set. They willl all be the same in each application, which is also what is happening finally.
In my suggestion of doing a pre-screening is to have some fields in thee applications itself. What is happening is that many fields that should belong to one specific application gets in to the comms table, thereby increasing the fields data.
Comm table needs to actually have only universal values or fields that are not specific JUST for a one application. Hence preferences of one particular application needs to go into the table application_prefs for each one. Like Forum prefs and Gmail prefs are coming into the comms, that could be avoided.
It is possible that I am making a mistake or not following something.