Solid Plume - simple blog app

Use Solid Solid Information
#65

Looks like I’m late to the party with this having just skimmed this thread but it looks nice and I just tried to install and have a play. I’ve got the files unzipped into public/blog/ but when I visit https:///public/blog I get a download of the index.html rather than it displaying in the browser. Any ideas why that might be?

This is my config:

    {
    "owners": [
        "https://<mypod>/profile/card#me"
    ],
    "title": "Plume (theWebalyst)",
    "tagline": "Light as a feather",
    "picture": "img/logo.svg",
    "fadeText": true,
    "showSources": true,
    "cacheUnit": "days",
    "defaultPath": "public/posts",
    "postsURL": "https://<mypod>/public/posts/",
    "postsElement": ".posts",
    "loadInBg": true
}
#66

This sounds like a problem with the server, possibly a bug introduced by one of the server upgrades. Can you find out which Solid server and version is running and open an issue for it?

I don’t think it can be a problem with plume.

Am I correct in thinking you are not using solid.community to host your pod? As you can see that server should work:

https://thewebalyst.solid.community/plume/

#67

Thanks for your reply. Actually I did try it on solid community. Maybe I made a mistake somewhere. I’ll poke around and see if I can figure it out.

1 Like
#68

In that case the only thing I can think of is that the file isn’t index.html (all lower case) but I expect you would have noticed that!

I’m not sure what else could cause this behaviour. Might still be worth raising an issue as it is the server side which is deciding to serve the file as text rather than HTML. I don’t know why it would do that though.

#69

Did you use solid-filemanager?
Is it the same as https://github.com/Otto-AA/solid-filemanager/issues/27

1 Like
#70

aha yeah, that sounds like it could be what’s happening

#71

I’ve written an example copy app which can be used to install plume easily. It is based on the new solid-file-client which will hopefully be released soon, so it will likely be integrated in solid-filemanager in the future.

Installing

Open Solid Copy (currently available here. In the future likely on the solid-file-client website)
Copy from https://otman.inrupt.net/public/solid-plume-0.11/
To https://your-pod.example.org/public/plume/
Wait until it is finished…

Then you need to edit and rename config-example.txt. For instance with solid-filemanager:

  • Open https://otto-aa.github.io/solid-filemanager/
  • Login and open the plume directory
  • Right-click and edit config-example.txt (change the webId to yours and the title)
  • Right-click and rename config-example.txt to config.txt

Now plume should be installed on your pod and you can open plume in your browser (/public/plume/ without index.html at the end).

@happybeing If you want to be sure, that Solid Copy and the solid-plume-0.11 links are persistent, I’d suggest you to copy them to your pod. It could happen that they get deleted while I test stuff, or when I need more storage space…

5 Likes
Conceptual Design - Solid better User Experience
#72

That’s cool @A_A thanks, I’ll do that :smile:

#73

I really like that!

#74

@A_A install worked for me https://smag0.solid.community/public/plume/ :muscle::+1:
But l’ve @happybeing, I’ve got an issue creating my first post :
I can type a word, then I want to type a space, and this appear and disappear, like if there was a .trim() function that cut the last space, and every time I type a space, the first word is concatenated to himself.
I type another space and the word is concatenated another time, until 6 times . See below

Screenshot_20191117-083532_Chrome
Screenshot_20191117-083532_Chrome720×1280 268 KB

#75

That’s very weird and I’ve not heard of it before. Can you file an issue and include info on browser and OS etc.

Also be great if you can you try after restarting the browser and in another browser to help gather info. Thanks for reporting!

#76

I think this issue is very similar https://github.com/facebook/draft-js/issues/1077
the problem is with the SimpleMDE editor
https://embed.plnkr.co/rLyQa4/ --> pb with android with 3 different browser & 2 differents keyboards

known issue with simpleMDE https://github.com/sparksuite/simplemde-markdown-editor/issues?utf8=✓&q=is%3Aissue+is%3Aopen+android but not fixed, it seems that the better solution is to migrate to easyMDE https://github.com/sparksuite/simplemde-markdown-editor/issues?utf8=✓&q=is%3Aissue+is%3Aopen+android

tested on this page https://easymde.tk/ looks good for me

1 Like
#77

Bad type for some “Plume” folders !
Installing Plume as preconised gave some of us some issue, like, for me, extract with @A_A’s filemanager gave me didn’t work well.

I think this is beaause the format of the folder "css " & “img” are wrong.
Make some test with @jeffz solid-file-client, here is what give me

plume
plume1906×992 155 KB

as you can see in the console for files[1] & files[3]
“https://smag0.solid.community/public/plume/css/” has type “text/css”
& “https://smag0.solid.community/public/plume/img/” has type “application/octet-stream”
and are considered as “files”

comparing to folders[0] “https://smag0.solid.community/public/plume/app” that has type “folder”

don’t you think “/css” & “/img” must be of type “folder” ?
here is the test page : https://scenaristeur.github.io/solidash/compagent-profile-explorer/

same with "“https://smag0.solid.community/public/chat/” which has type “application/x-chat” and not folder

#78

Any errors will be due to either the program used to upload or the server used at that time, so the best way to test this is to start from scratch with the files from the repo.

I don’t have time myself, so if you want to look further that would be great, or if you can’t please file an issue with what you’ve discovered.

#79

I could post an issue, but perharps the issue is not with Plume but instead with NSS :

I think the faulting part is "
css:
a cs:Resource,"

Does Plume install do that voluntary or Is it automatically put by the server?
Because the folder name is “css” and ends with “css”, so the server thinks it is a “css” file that name ends with “css”, that could explain why the folder “img” is of type “application/octet-stream” and “app” is not a file extension, so it is considered as a folder

@prefix cs: <http://www.w3.org/ns/iana/media-types/text/css#>.
...
css:
    a cs:Resource, ldp:BasicContainer, ldp:Container, ldp:Resource;
    terms:modified "2019-11-26T09:27:05Z"^^XML:dateTime;
    st:mtime 1574760425.555;
    st:size 4096.
#80

Plume doesn’t have an installer, so I think the issue is with how the files were created (on the server), hence the tool used to upload or the server. So what this needs is a bit of investigation using a specified version of say Solid Filemanager to upload to a specified version of a Solid server. The issue can then be investigated on either (assuming it remains).

#81

This was fixed a few days ago, here’s the related issue: https://github.com/solid/node-solid-server/issues/1361

This isn’t the error cause for the solid-filemanager though. I guess the cause here is, that it sends content-type: undefined while it (probably) should guess and specify it. I’d refactor it sometime after the solid-file-client update. If you want it to be changed earlier, PRs (which don’t break other stuff obviously) are accepted.

1 Like
#82

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… :thinking:

Happy to test any other combination :slight_smile:

1 Like
#83

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

2 Likes
#84

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)

Thank you so much! :slight_smile: