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.

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

OrchardCoreCmsWeb Only runs one time, second run giving page not found error #16289

Closed
Fusion-Priyakant opened this issue Jun 11, 2024 · 11 comments · Fixed by #16324
Closed

OrchardCoreCmsWeb Only runs one time, second run giving page not found error #16289

Fusion-Priyakant opened this issue Jun 11, 2024 · 11 comments · Fixed by #16324
Labels
Milestone

Comments

@Fusion-Priyakant
Copy link

Navigate to ./OrchardCore/src/OrchardCore.Cms.Web.
Run dotnet run.
Open the http://localhost:5000 URL in your browser.
Stop the App

Again Run the application a second time and browse the URL "http://localhost:5000", it will show a page not found error.

Copy link
Contributor

Thank you for submitting your first issue, awesome! 🚀 We're thrilled to receive your input. If you haven't completed the template yet, please take a moment to do so. This ensures that we fully understand your feature request or bug report. A core team member will review your issue and get back to you.

If you like Orchard Core, please star our repo and join our community channels.

@Piedone
Copy link
Member

Piedone commented Jun 11, 2024

I can reproduce this with a fresh clone of the latest main (3d3f172) under Windows (you need to actually run dotnet run --framework net8.0).

@Fusion-Priyakant
Copy link
Author

Fusion-Priyakant commented Jun 11, 2024 via email

@Piedone
Copy link
Member

Piedone commented Jun 11, 2024

I said I can reproduce it, it's a valid bug.

@Fusion-Priyakant
Copy link
Author

Fusion-Priyakant commented Jun 11, 2024 via email

Copy link
Contributor

We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues).

This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here.

@sebastienros sebastienros modified the milestones: 2.x, 2.0 Jun 13, 2024
Copy link
Contributor

We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues).

This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here.

@gvkries
Copy link
Contributor

gvkries commented Jun 14, 2024

Looks like this is caused by #15793. I'll have a look.

@Piedone
Copy link
Member

Piedone commented Jun 14, 2024

Thank you!

@gvkries
Copy link
Contributor

gvkries commented Jun 14, 2024

Thank you!

I broke it, so I'm trying to fix it 🙈😇 Hopefully this is the last mistake of this kind...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants