search

WardCunningham / Smallest-Federated-Wiki

This wiki innovates by: 1. federated sharing, 2. drag refactoring and 3. data visualization.
http://wardcunningham.github.com/
GNU General Public License v2.0
1.21k stars 178 forks source link

TypeError: Can't find plugin for 'html' #444

Open rbeesley opened 9 years ago

rbeesley commented 9 years ago

1) Install new SFW to localhost:3000 2) Navigate to Welcome Vistors: http://localhost:3000/view/welcome-visitors/view/how-to-wiki/fed.wiki.org/add-plugins 3) Navigate to How To Wiki: http://localhost:3000/view/welcome-visitors/view/how-to-wiki 4) Navigate to Add Plugins: http://localhost:3000/view/welcome-visitors/view/how-to-wiki/fed.wiki.org/add-plugins

The page will have several sections that says "TypeError: Can't find plugin for 'html'"

rbeesley commented 9 years ago

Researching this more, it would seem that this project is more or less abandoned as all current work has been moved to the new projects: https://github.com/fedwiki. This is not clear while reading this repo and it adds to confusion.

WardCunningham commented 9 years ago

Ah, I was thrown off by the fact that you were using port 3000, the default for the Node.js version but not what we commonly used with the original ruby version. I still host fed.wiki.org with this code which is not far behind the node.js. There are still a few things that this does that the other doesn't like Submit Changes.

We do include this warning in the ReadMe for the repo:

image

rbeesley commented 9 years ago

Sorry, I suppose the port change might have led to some confusion. I was reading documentation and watching videos, and I saw :1000, :1111, and :3000. 3000 seemed like what was being used in the latest content, so that's what I used when starting the server.

I'm up and running on the Node.js version today and experimenting with what I'm finding. Install was a breeze unlike when I first gave this code a go. That could very well be my lack of experience with Ruby, although my Node.js experience isn't much better.

WardCunningham commented 9 years ago

The node package manager has learned from what worked and didn't work for lots of other package managers. The simplicity of installation was the number one motivation for the shift. The ability to share code between client and server was a close second.

We would love to have someone who distributes ruby code every day to take charge of the ruby code and make it equally wonderful.

If you poke around deep in the How to Wiki pages you will find pages from other sites. Fork them and then you will find yourself hooked into the federation.