Alright. Now I've been doing some testing. I've been going trough most of my backups and finally I have found something that hopefully can give me some answers to why the import is not working like it should. The result of my testing is that the import process stops working after I have installed the add-on XenSocialize. This is pretty much where I stand now.
I will try disabling it from my very last backup and see what happens with the import. Should be an interesting test.I just looked at the code for that addon. It extends the thread datawriter which might be causing problems. Disabling that addon (as opposed to uninstalling it) should avoid any potential conflicts during the import.
Ha. It did the trick. Now the import worked like it should. I guess everything will be OK by enabling the add-on again once the import is completed. I still would like to know what's causing the import to fail. Maybe we will find out soonI will try disabling it from my very last backup and see what happens with the import. Should be an interesting test.
I just added a flag which will disable my extended class when the user is importing...Great news! I'm curious to hear what it was
Actually there was no 'interference'I see. So that extended class interfered with the import of the posts in som way?
That might be the reason... but not sure though... and still you don't want all the imported threads be posted on Facebook/Twitter, do you?I recall last time I did the import, at the beginning of july, the add-on was configured and enabled. And after the import, which worked fine, my Facebook group, for example, was populated with all the imported threads. This time xenSocialize was not configured with correct Facebook information, on purpose. Could that be a part of the explanation why it did not work at all this time? What do you think?
We use essential cookies to make this site work, and optional cookies to enhance your experience.