You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
tried to use wagtail-transfer to move some data between my servers. Stumbled upon a very weird CircularDependencyException: the resolution path is [create revision id # 114, create page id # 13] and current operation is create revision id # 114. Looks like it followed the page link from revision and then latest_revision link back to Page, and errored out? I'm not sure what's going on, this seems like a normal situation that the code can't handle.
I do load data into pages with my management commands with the following snippet:
Again, this looks correct to me, but perhaps I'm subtly messing something up. Could you help me out?
P.S. I've also gotten another CircularDependencyException, but that was a more reasonable one - my site root page has a StreamField which links back to it. A bummer, but understandable; seems like I'll have to special-case it.
The text was updated successfully, but these errors were encountered:
Hello,
tried to use wagtail-transfer to move some data between my servers. Stumbled upon a very weird CircularDependencyException: the resolution path is
[create revision id # 114, create page id # 13]
and current operation iscreate revision id # 114
. Looks like it followed the page link from revision and then latest_revision link back to Page, and errored out? I'm not sure what's going on, this seems like a normal situation that the code can't handle.I do load data into pages with my management commands with the following snippet:
Again, this looks correct to me, but perhaps I'm subtly messing something up. Could you help me out?
P.S. I've also gotten another CircularDependencyException, but that was a more reasonable one - my site root page has a StreamField which links back to it. A bummer, but understandable; seems like I'll have to special-case it.
The text was updated successfully, but these errors were encountered: