Replying to Avatar chad

No problem, happy building!

As for the latter item, it would likely be an issue that is only caught at browser runtime (i.e., the developer console). To investigate further, I'd try opening your site externally and opening the browser console via the following guide (these steps are roughly the same between browsers):

https://developer.chrome.com/docs/devtools/console/reference#open

See if any red error logs appear. If so, you can likely right click, select 'Copy Message' (or the equivalent available option), and paste the error directly into Shakespeare. The agent should be able to understand where to look based on that context and attempt to resolve the issue. You might have to repeat this process a few times to resolve any remaining errors.

I'm currently investigating to see if we can automate this post-deployment check directly in mkstack/Shakespeare; this will allow the agent to perform this process automatically.

Let me know if you have any questions, and best of luck!

Did again a run, copied error in MKstack but still don’t see the page like this one: https://npub14ejejtz4afxep3608dem92zljj8w30nllxgekqrtgawpqne6xp7ss2ze24.shakespeare.to/card/naddr1qvzqqqrkcgpzqsa64uxz3ek0kx2mzlhqs0seavay4l06c4xek6a0zup8pmge8c6vqqfxxctjvsknzde4xgmrqdecx5cn2v3eamx7pk

Reply to this note

Please Login to reply.

Discussion

Hah, that one is tricky. There were three errors regarding child element population, but the agent would likely only be able to recognize and act on the second one to fix the issue.

As another courtesy for your patience (and because this site is very cool), I have a fork of the project here with the fixes applied that you can import into Shakespeare if so desired:

https://gitlab.com/chad.curtis/pop-card-fork.git

Hope that helps!

Amazing! You rock🤙 the link doesn’t work for me, even when I signed up for gitlab