I've created a new project but I can not add files to it. The Tabs 'Summary', 'Files' and 'Support' generates an error page ""hoops, we can't find that page.". Other tabs work.
https://sourceforge.net/p/mediatagging/admin/ -> success https://sourceforge.net/p/mediatagging/blog/ -> success https://sourceforge.net/p/mediatagging/discussion/ -> success https://sourceforge.net/p/mediatagging/wiki/Home/ -> success https://sourceforge.net/p/mediatagging/tickets/ -> success https://sourceforge.net/p/mediatagging/code/ref/main/ -> success https://sourceforge.net/projects/mediatagging/support -> failed https://sourceforge.net/projects/mediatagging/reviews/ -> failed https://sourceforge.net/projects/mediatagging/files/ -> failed https://sourceforge.net/projects/mediatagging/ -> failed
The project appears to be provisioned only in the modern '/p/' namespace. All legacy '/projects/' routes resolve to "Whoops, we can't find that page".
This suggests incomplete mapping between legacy project UI endpoints and the new project backend.
These URLs are not manually constructed. They are generated by SourceForge UI itself.
The project appears to be partially provisioned across two routing namespaces:
This results in internal navigation links pointing to non-existent pages.
Hello,
Is this still an issue? Our team has been working on your report and we would like to have your feedback.
Sincerely, SourceForge Support
Hi, I joined this moring (MEST) and wow, it's back working. Thanks for your support.
Hi,
Thank you for your feedback With your issue resolved, this ticket will be closed.
Log in to post a comment.
https://sourceforge.net/p/mediatagging/admin/ -> success
https://sourceforge.net/p/mediatagging/blog/ -> success
https://sourceforge.net/p/mediatagging/discussion/ -> success
https://sourceforge.net/p/mediatagging/wiki/Home/ -> success
https://sourceforge.net/p/mediatagging/tickets/ -> success
https://sourceforge.net/p/mediatagging/code/ref/main/ -> success
https://sourceforge.net/projects/mediatagging/support -> failed
https://sourceforge.net/projects/mediatagging/reviews/ -> failed
https://sourceforge.net/projects/mediatagging/files/ -> failed
https://sourceforge.net/projects/mediatagging/ -> failed
The project appears to be provisioned only in the modern '/p/' namespace.
All legacy '/projects/' routes resolve to "Whoops, we can't find that page".
This suggests incomplete mapping between legacy project UI endpoints and the new project backend.
These URLs are not manually constructed. They are generated by SourceForge UI itself.
The project appears to be partially provisioned across two routing namespaces:
This results in internal navigation links pointing to non-existent pages.
Hello,
Is this still an issue?
Our team has been working on your report and we would like to have your feedback.
Sincerely,
SourceForge Support
Hi,
I joined this moring (MEST) and wow, it's back working.
Thanks for your support.
Hi,
Thank you for your feedback
With your issue resolved, this ticket will be closed.
Sincerely,
SourceForge Support