patch loaded into PdWebParty via URL is unchangeable

[yannseznec]

I imagine this may be an unchangeable thing that is due to servers or heroku or something, but...

I'm currently using PdWebParty mainly with GitHub. I push a new patch to a repo, get the raw URL, and then share it using the ?url= sharing method. However, if I change my patch, push the changes, and then reload the PdWebParty link, it stays in the state that it was at when I first generated that link. to make a new version I have to create a new filename (and thus a new link).

Is it at all possible to use the sharing system to create a link to a WebPdParty link that updates dynamically based on the most recent Pd Patch that it's referencing?

[cuinjune]

Hi @yannseznec That's weird. The patch should update as soon as you make change and upload it again. The app will basically read the ?url= link and dynamically load the file from the link every time. The app doesn't cache these files.

I'm not sure why that happened but I think it could be your Github repo taking some time to update the file, or you can also try clearing your browsing data.

[yannseznec]

Oh weird! The behavior you describe is exactly what I’d love to happen, but I could have sworn it wasn't working that way…I’ll test again.

…

On Apr 5, 2021, at 3:36 PM, Zack Lee ***@***.***> wrote: Hi @yannseznec <https://github.com/yannseznec> That's weird. The patch should update as soon as you make change and upload it again. The app will basically read the ?url= link and dynamically load the file from the link every time. The app doesn't cache these files. I'm not sure why that happened but I think it could be your Github repo taking some time to update the file, or you can also try clearing your browsing data. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAATDCXWR76P5LVFAUUAGZ3THIGLTANCNFSM42NADSHQ>.

[yannseznec]

ok my mistake, this is definitely not a bug and is working fine. I must have been doing something dumb with my files.

[yannseznec]

oh upon further testing I think your theory about browser caching is the answer - I think the browser will inconsistently load the latest version of the file. if I open a recently-changed patch in a new browser it loads the latest version.