Replying to Avatar TravelTelly

I try now to fix an admin page error nostr:npub1jvnpg4c6ljadf5t6ry0w9q0rnm4mksde87kglkrc993z46c39axsgq89sc I get this:

To Fix Your Admin Access:

✅ Use the working deployment:

* Admin Panel: https://npub1nr80d06jql93hwx2dtqxr8epchgyhwkvuarerj5sx0ufuxcjpqlq90pkwk.nostrdeploy.com/admin

* Basic Test: https://npub1nr80d06jql93hwx2dtqxr8epchgyhwkvuarerj5sx0ufuxcjpqlq90pkwk.nostrdeploy.com/admin-basic

* Debug Info: https://npub1nr80d06jql93hwx2dtqxr8epchgyhwkvuarerj5sx0ufuxcjpqlq90pkwk.nostrdeploy.com/admin-debug

❌ The shakespeare.to URL will continue to show 404 until you deploy the updated code to that hosting service.

Next Steps:

1. Test the admin panel on the working URL (nostrdeploy.com)

2. If it works there, then the issue is just that the shakespeare.to deployment needs to be updated

3. If you want to keep using shakespeare.to, you'll need to deploy the updated code to that hosting service

The admin panel should work perfectly on the nostrdeploy.com URL when you're logged in as the Traveltelly admin npub. Try it and let me know if it works!

Any idea👇 nostr:npub1jvnpg4c6ljadf5t6ry0w9q0rnm4mksde87kglkrc993z46c39axsgq89sc and nostr:npub1scvyzz02ayma34hesz62pdrd5nhsmxp74hjq8msmfs9khh3r3drsnw68d8 !?

nostr:nevent1qqs8t83w7l4tzvxjcvxgjat7wkpf0geerxp850tv38jlsr8jfgv5xesrhfcpw

Reply to this note

Please Login to reply.

Discussion

Pardon, was looking into some of this earlier but I wasn't able to follow up until now. Do you have the current shakespeare.to project URL that is shown in the UI?

It's hard to see the current behavior via nostrdeploy.com, as it likely is a context-sensitive item that would require modifying the npub it's checking to test locally.

Perfect! I'll take a look once I have a moment. 🙂

Thanks you are amazing! 🙏

Finally got a chance to look at this! The behavior in this case (likely from an earlier debugging effort) was the creation of a parallel routing file; changes being made to the route (such as adding /admin) were not live as they were being applied to the routing file rather than the custom one. To resolve this locally, I updated the application to use the routing logic:

https://gitlab.com/soapbox-pub/reviewstr-fork/-/commit/5b595113b60f3608168de9865fba2d3d73e0dcbc

You're welcome to try to have Shakespeare introduce the above change, or import the following project with the above commit:

https://gitlab.com/soapbox-pub/reviewstr-fork

Thank you for your patience - hope that helps somewhat!

Thank you! You make really #shakespeare word trying because now the projects envolves🙏 I hope you guys nostr:npub1jvnpg4c6ljadf5t6ry0w9q0rnm4mksde87kglkrc993z46c39axsgq89sc nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424 nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6 know how good work Chad is doing. Without his help I would already stop using it and now I only get more energy to build 🙏☀️🤙 #grownostr

Chad is a legend.

For sure 🙏