Realm imports crashing

[Acenoid]

So is there any way, when I have a 254 build and no server access, to go back to 253? I have made plenty of changes on 254, but it seems that the import / export works better on the older version?

The 254 build fixed 2 issues:
1. Corresponding pins / node targets missing on smart images - could be very annoying potentially
2. import structure export, replacing structure elements - Iam not sure of the implications and if this can be worked around somehow in 253?

 

[Acenoid]

Iam on 254 currently, and trying to import data into a realm.
Like the OP I first imported the full export of another realm.
After doing a few changes (moving categories around) some topics were corrupt and I attempted a partial export of another realm, which ends in the error OP described.

The major issue I have now is, that I cannot revert to 253 since my DB is now on the newer version. ...

Anyone found another solution how to revert to 253 if all available databases are already on 254?

 

[JustinThomason]

I had to delete my local DB, install 253, and then do a full sync down from the LW server. Worked fine - just took some time. Just make sure you're fully up to date with your syncing before doing any of this.

 

[Acenoid]

I cannot do that. Server subscription expired and it is not up to date since may last year. I have some backups theoretically which should be on 253 but I have made many changes since then, since 254 worked fine.

Or do you mean if I would get server synch enabled again (not possible atm - I had no need for a credit card for more than a year) sync up, downgrade to 253, and then sync down again?

 

[Acenoid]

By importing the data to anohter realm and then import again to the original destination, it is possible to add further topics. However I had some duplicate categories, so it is not only an emergency workaround. Maybe it still works with preserve ownership, not sure.

Let's hope LWD finds some time to revise this import / export situation in the future.

It would be super cool if the application would just abort the import if a problem arises instead of crashing with the error.

 

[Farling]

By importing the data to anohter realm and then import again to the original destination, it is possible to add further topics.

This is usually the route to disaster, export and import should only be used one-way between realms.

 

[Acenoid]

To clear up the instructions:

originating Realm A
target: B

1st Import A->B works
2dn (partial) Import A->B crashes

workaround for 2nd import:
Import A-> C -> B

So the imports have the same direction.

 

[nightpanda2810]

256 released recently does NOT fix import/export issues referenced in this thread.

256 release also removed cloud access to 253, the only working version, making it basically completely useless if you do any kind of importing.

 

[SteveT]

Hi everyone, rather than responding in all the various related threads related to the last few RW builds 253-256, I've opened a new thread which I intend to be a central place for me to respond to these issues and provide information:

https://forums.wolflair.com/showthread.php?t=65964

An important note discussed in more detail in that thread is that we've now reduced the required build to access the server back down to 253 (with caveats). Also, if you experienced import/export issues in builds 255-256 that were not present in build 253, please take a look at the instructions there. Thank you!