Serious bug improt/export please fix!!

Scriptcase 8 Bugs
#1

This situation occurs…

Person 1 exports his project and logs out.
Person 2 makes changes to his own project and generates his apps. Then he exports his projects. In the export are therefore ALL public libraries.
Person 1 logs in and alters something to the public libraries and logs out.
Person 2 logs in and imports hit project NOW THE LIBRARIES ARE OVERWRITTEN BY OLDER LIBRARIES!!

This is a very serious bug!!

How can we prevent this behaviour???
It shouldnt be so that the public libs are also exported UNLESS specifically tagged.
The same goes for the scriptcase, public, project and user libs!!

I dont want to import old public libs!!
I want to be able to choose which to import and which not!!! Otherwise I can get old files back in my code…
So this doesnt work well with multiple developers!!

Please fix this properly or at least give options upon importing to not import certain libs (by type and name)!!

#2

I guess the same happens when you restore an old version of the application. I there are libs included then the old one replace the actual.

#3

Does the import work at all? I’m trying to import a recently exported project to work on as a sandbox. When I try to import the zip file it accepts the files but gives no feedback and does not import the file.

#4

Yes import does work but you import OVER your new code… Even if you think you just expoerted your projects you ALSO exported your libs. And thus overwrite your NEW libs with your old exprted libs… But it does work…

#5

@rr I’ll address this issue. Thanks for reporting in mate.

#6

Please pick this up. I have been reporting this several times before.