Debugging a package that won't appear in 'packages.json'

cedaro / satispress

Expose installed WordPress plugins and themes as Composer packages.

500 stars 49 forks source link

Debugging a package that won't appear in 'packages.json' #92

Closed danielbachhuber closed 5 years ago

danielbachhuber commented 5 years ago

We're using SatisPress to serve Restrict Content Pro. RCP has a beta3 version that's visible in the backend:

However, the beta3 version doesn't appear in packages.json

What's the best way to debug this situation? Thanks in advance!

danielbachhuber commented 5 years ago

Chatted with Brady in Slack. My specific issue was that the artifact hadn't been created for 3.0.0-beta-3 (a bug for SatisPress <0.3.2). Clicking the "Download" button created the artifact and fixed my issue:

TimothyBJacobs commented 4 years ago

I experienced this issue on 0.5.0. Manually doing the download fixed the issue as well.

bradyvercher commented 4 years ago

@TimothyBJacobs Just-in-time caching for the win! Do you have any idea why it didn't cache automatically, though?