04-17-2016, 03:53 PM
The tabdata.php file that comes with coreBOS has it, so if the migration isn't working with that file it is because it is regenerated with the information in your 5.2.1 database.
That means that the code is incorrect, it shouldn't be counting on having the module active to get the tabid, it should go directly to the database.
I can fix that but I'm afraid there is going to be a lot more of those errors present. Can you activate those modules in your 5.2.1 and do the migration with them active and then deactivate them again once on coreBOS?
That means that the code is incorrect, it shouldn't be counting on having the module active to get the tabid, it should go directly to the database.
I can fix that but I'm afraid there is going to be a lot more of those errors present. Can you activate those modules in your 5.2.1 and do the migration with them active and then deactivate them again once on coreBOS?
Joe
TSolucio
TSolucio