The availability check didn't work on foreign sites – Make sure that on both sites, local and foreign, the same Version of the flatmgr ist installed.
The availability check didn't work on multiple foreign sites – the URL's must be entered in flexform field without newline and use a “;” as separator
I get a XML response error – there are illegal characters in the response (check the error message). You can either switch your TYPO3 to utf-8 encoding in the installtool and set the correct page.config.locale_all. I tested with utf-8 and iso8859-1. The extension works fine when TYPO3 is set to [BE][forceCharset] = utf-8.
XML-response error in the availability check – make sure you have set the page.config.locale_all right in the TS page setup. XAJAX of the flatmgr uses the page.config.locale_all to switch to the desired encoding. Here is an example of utf-8 setting.
page {
...
config.metaCharset = utf-8
config.additionalHeaders = Content-Type:text/html;charset=utf-8
config.locale_all = de_DE.utf8
....
}
For iso charset you can set
page.config.locale_all = de_DE.ISO8859-15
You get warning about an inactive backend user when trying to save a modified data record..
You have to be logged in the backend to get the history tables updated when you change a data record.
I use for this purpose the modified extension dkd_feuser_belogin.
The modifications are made in the file ext_tables.php of the the extension dkd_feuser_belogin.
"foreign_table" => "be_users",
//"foreign_table_where" => "AND be_users.pid=###SITEROOT### ORDER BY be_users.uid",
"foreign_table_where" => "AND be_users.pid=0 ORDER BY be_users.uid",
I also tried to use for the backend login the extension simulatebe. It seems that the backend user created by simulatbe is not instantiated correctly. So I can't manage to get the history tables work correct with simulatebe.
