Did you used @A_A solid-file-manager? Which version of @happybeing Plume did you used? Iāve tried to deploy on my POD using @A_A solid file manager and latest Plume release v0.11 and once deployed following instructions I got a download instead of a ālive deploymentā of Blog.
Not sure if the issue can be related to solid-file-manager extracting .zip files or NSS sideā¦
First Time, I used the same instructions as you and had same problem.
But another of install can be used as mentioned here Solid Plume - simple blog app
Thank you! I had already tried that method too but I was receving some HTTP 403 Errorsā¦
I have just realized that I would need to setup permissions of the Solid Copy App from @A_A in my POD and tried againā¦ This time has worked! Finally Deployed!
Then I guess itās clear that something wrong is going (bug?) with the actual version of solid file manager (react based app)
Yes, as mentioned above solid-filemanager uses content-type: undefined which likely causes the download instead of rendering it in the browser. It will be fixed in the future, but I will wait until the new solid-file-client library is released and until I have enough free time. Likely before the end of this year, but I canāt promise it.
The installing via Solid Copy (see above) works without errors afaik.
@Smag0 Click on the three dots in the top right corner -> Choose Root Location -> Logout
(If you have further questions or remarks to solid-filemanager, Iād suggest to do them in the solid-filemanager thread or in a github issue)
Using @A_A 's Solid Copy app, Iām also coping with either a never-ending ācopyā with no results or a 403 error (ā403 Origin Unauthorized https://mypodā¦/public/ā). @alexcorvis84, what do you mean with
?
Iāve tried with all āaccess modesā activated for https://otto-aa.github.io, but nothing helpsā¦
The only option on the menu is ālogoutā. Iām not seeing any way to edit anything, If I click on the āPlume (etc)ā link it briefly changes to āBlog Titleā before reverting back. The only other button that works is the profile button, which does take me to my profile.
Is there something else Iām supposed to do to set this up?
If you have any time to help it would be greatly appreciated.
Thanks
Edit: looking over this thread I found the Github page and submitted an issue there. Sorry for the duplication.
Edit 2: Iām seeing a few more resources in this thread and on the Github page, but it seems like the Deployment Guide went down with solid.community. Is it available anywhere else?
Itās a (new) CORS issue. In the browser console there are a bunch of CSS errors (also new I believe) but ignoring those, after a couple of minutes the following appears which is the main problem:
HEADhttps://thewebalyst.solid.community/public/posts/
CORS Failed
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://thewebalyst.solid.community/public/posts/. (Reason: CORS request did not succeed).
@jeffz@aveltens do you know if thereās a simple fix for this? Iām guessing itās a result of either a change in server config or upgrade, perhaps related to the change in custody of solidcommunity.net but donāt have a lot of time to investigate at the moment.
I think thatās the only copy. You could probably extract the code from Plume and view this in HTML running Plume on a localhost server if you want, or just wait to see if the CORS issue can be fixed.
I just tried loading with CORS disabled using a Firefox plugin but this didnāt help - it doesnāt always work. I think it may be fixable on the server side, but am not sure. I never really figured out CORS let alone CORS on Solid, but maybe someone else has the magic answer.
BTW Plume is a very nice demo of simple Solid app, but not really up to the job of a decent blog, nor a good codebase to build a better blog app IMO (see my summary in an earlier post here). It would of course be great to see someone build on the ideas Plume demonstrates.
BTW2, I took a different approach as well, not using Solid at all to demonstrate building a static blog (as Plume is) that can be used to publish simultaneously on the web and peer to peer storage / decentralised web (see: dweb.happybeing.com).
Doh! Thanks @aveltens, CORS is such a pain even when itās doing itās job
@TheScooterKing this appears fixed so please give it another go. It was due to Plume looking for posts on the old server address which moved domains a couple of months ago.
Thanks for looking into this@happybeing. I posted a comment back on your Github issues tracker, as Iām still having problems. Hereās what I wrote there:
"Hi again,
Thanks for your work on the earlier fix. Iām sorry I didnāt have time to look at it until just now.
I just tried your plume instance and although the page now loads with the āHow to deploy Plume blog on your Solid podā post preview, it gives an error after trying to lode when I hit ā-more-ā : ā- 999 undefinedā.
Also the āPlume Deployment Guideā in the README.md file here is directing to the old host.
Iām assuming that something in the guide would help me figure out how to configure Plume once Iāve uploaded it to my Solid pod. right now I have put the contents of the most recent release in a /plume/ folder in my public directory, and when I try to load https://mypodname.mypodprovider.net/plume/ I get the following:
@happybeing I was able to read the deployment guide this time, so thanks for fixing that. Iāve still got a problem with the app once itās installed though, in that what Iām seeing
Canāt find file requested: [object Object]
when I load the page. I have swapped out the ālocalhost:āā references with my pod address, but still no joy. Any idea what this might be?
@TheScooterKing Not sure what that might be, can we take this to a/the github issue and give me some more detail including your config. Thanks for persevering, is good to see Plume is still alive and kicking.