AJaySi
[BUG] On boarding not working.
🐛 Bug Description
A clear and concise description of what the bug is.
🔄 Steps to Reproduce
Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
✅ Expected Behavior
A clear and concise description of what you expected to happen.
❌ Actual Behavior
A clear and concise description of what actually happened.
📸 Screenshots
If applicable, add screenshots to help explain your problem.
🖥️ Environment
Desktop (please complete the following information):
- OS: [e.g. Windows 10, macOS 12.0, Ubuntu 20.04]
- Browser: [e.g. Chrome 91, Firefox 89, Safari 14]
- ALwrity Version: [e.g. v1.2.3]
Mobile (please complete the following information):
- Device: [e.g. iPhone 12, Samsung Galaxy S21]
- OS: [e.g. iOS 14.6, Android 11]
- Browser: [e.g. Safari, Chrome Mobile]
📋 Additional Context
Add any other context about the problem here.
🔍 Error Logs
If applicable, paste any error logs or console output here:
Paste error logs here
13:22:43 | ERROR | services.seo_tools.sitemap_service:analyze_sitemap_for_onboarding:366 - Error in onboarding sitemap analysis: Failed to parse sitemap XML: not well-formed (invalid token): line 18, column 36
13:22:43 | ERROR | api.onboarding_utils.step3_routes:analyze_sitemap_for_onboarding:429 - Sitemap analysis failed: Failed to parse sitemap XML: not well-formed (invalid token): line 18, column 36
🏷️ Component/Feature
Which component or feature is affected?
- [ ] Blog Writer
- [ ] SEO Dashboard
- [ ] Content Planning
- [ ] Facebook Writer
- [ ] LinkedIn Writer
- [ ] Onboarding
- [ ] Authentication
- [ ] API
- [ ] Other: _______________
🎯 Priority
- [ ] Critical (blocks core functionality)
- [ ] High (major impact on user experience)
- [ ] Medium (minor impact)
- [ ] Low (cosmetic issue)
I think the onboarding pipeline is too strict to the results of the steps inside.
I am not only facing to above error, but also below:
i just think the onboarding are too complicated. not a good product design.
@doncat99
Hmmm, there is heuristic to get the sitemap with different combinations.
-
Also, even if sitemap analysis fails, the competitor analysis results should have been presented. I will need to do better exception handling.
-
As part of the exception handling, I will also provide an input for manually providing the sitemap, when we fail to get the sitemap.
"i just think the onboarding are too complicated. not a good product design."
- I agree. Can you help make it better ? Thanks.
"i just think the onboarding are too complicated. not a good product design."
- I agree. Can you help make it better ? Thanks.
Ummm... business flow and data flow are not designed reasonably. You should first draw your desired business flow and clearly declare it.
In my opinion, the onboarding process should be a summit and result-oriented interaction; there is no need to break it down into multiple steps, since you don't need users to verify the sub-step outcome. Thus a one-step onboard interaction would be a best practice, and you can do the re-generate in the result onboarding result page.