From cb7e3d67c16c23a1cd879cc5631cb5a4a7e31d51 Mon Sep 17 00:00:00 2001 From: Alex Finnarn Date: Tue, 8 Oct 2019 16:43:07 -0400 Subject: [PATCH] Issues #56 and #54: Provide Troubleshooting Info For JSX and Authentication Errors --- README.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/README.md b/README.md index 4026fb7..95d41b8 100644 --- a/README.md +++ b/README.md @@ -56,3 +56,10 @@ This project is only possible thanks to the awesomeness of the following project ## :tm: License MIT + +## Migration Troubleshooting + +Since everyone has different content in their Medium blogs, you might encounter some issues that can't be fixed in a standardized way or aren't worth trying. These issues and potential workarounds will be posted below: + +- **JSX closing tag parsing error** - [Issue #56](https://github.com/mathieudutour/medium-to-own-blog/issues/56). You may have some self-closing, void tags in your blog posts. JSX requires all tags to be self-closed so even though the HTML break tag can be written as `
`, you will need to change the syntax to read `
` or go back later after running the migration and place the tags in a code block. +- **GitHub authentication errors** - [Issue #54](https://github.com/mathieudutour/medium-to-own-blog/issues/54). GitHub allows users to set up authentication several different ways. For instance, if you have two-factor authentication enabled, you have to provide a token in certain cases when cloning down repositories. Please check your authentication settings if you experience any issues related to authentication failures.