Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Content cloning fails if any pages have linked resources (js / css) #611

Open
JimKerslake opened this issue Nov 19, 2024 · 2 comments
Open

Content cloning fails if any pages have linked resources (js / css) #611

JimKerslake opened this issue Nov 19, 2024 · 2 comments
Assignees
@JimKerslake
Labels
bug

Comments

@JimKerslake
Copy link
Collaborator

The whole content cloning process keels over with an EF Core tracking exception.

image
@JimKerslake JimKerslake self-assigned this Nov 19, 2024
JimKerslake added a commit that referenced this issue Nov 19, 2024
@JimKerslake
#611 content cloning bug
94904a0
JimKerslake added a commit that referenced this issue Nov 19, 2024
@JimKerslake
Merge pull request #612 from cloudscribe/feature/611
5c45674 
#611 content cloning bug
@JimKerslake
Copy link
Collaborator Author

Bumped cloudscribe.SimpleContent.Storage.EFCore.Common to 8.0.3
Plus the 4 dependent Db-specific ones

@JimKerslake
Copy link
Collaborator Author

Debatably(?), the content cloning could (should?) collate any page errors but still carry on with subsequent pages, rather than stopping completely at the first error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JimKerslake JimKerslake

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@JimKerslake