Puppy's Website: Discussion
Done a test site
Oli, I've done a test site for Dokuwiki and informed you via PM of the access info. Am afraid that servage's server software could be too old - hope the scripts will work.
- ttuuxxx
- Posts: 11171
- Joined: Sat 05 May 2007, 10:00
- Location: Ontario Canada,Sydney Australia
- Contact:
Hey guys if a Forum is needed let me say one thing, PhpBB is terrible for spam, I used to get over 100 xxx post a month, some were just over the top for a linux website, I then Deleted PhpBB and installed SMF forum and have 0 spam for over 1 month now. It is so nice, I will never go back to PhpBB
ttuuxxx
ttuuxxx
http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
- Pizzasgood
- Posts: 6183
- Joined: Wed 04 May 2005, 20:28
- Location: Knoxville, TN, USA
That may not be because of better forum software. I've gotten the same effect by just moving my forum to another directory. After a month or two the bots seemed to find me again. I don't know if the URL changed in your case, but the methods of posting will certainly have, so right now you might just be in the lull period while you wait for the bots to adjust.
Not saying something else wouldn't help. The less mainstream the better as far as spam goes. But I do think you need to give it three months or so before you can judge how good it really is.
Not saying something else wouldn't help. The less mainstream the better as far as spam goes. But I do think you need to give it three months or so before you can judge how good it really is.
[size=75]Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib[/size]
[img]http://www.browserloadofcoolness.com/sig.png[/img]
[img]http://www.browserloadofcoolness.com/sig.png[/img]
- Dingo
- Posts: 1437
- Joined: Tue 11 Dec 2007, 17:48
- Location: somewhere at the end of rainbow...
- Contact:
o yeah my site is based on dokuwikioli wrote:I had a search at the web. I suggest to use dokuwiki ( http://wiki.splitbrain.org/wiki:dokuwiki ) for the manual. Eric (Caneri) or Tom (tombh), could you install dokuwiki at the website and send me a link so that I can make some tests with the manual?
http://puppylover.netsons.org/dokupuppy/doku.php
and dokuwiki can be expanded with many plugins adding extra features
replace .co.cc with .info to get access to stuff I posted in forum
dropbox 2GB free
OpenOffice for Puppy Linux
dropbox 2GB free
OpenOffice for Puppy Linux
Bump.LOF wrote:...The problem is that I don't know if a hierarchy system is possible to do with Wikka. The category feature is the closest thing that I know of but this has proved very confusing to orchestrate. I also would suggest not going with a Drupal extension wiki as realistically the wiki needs to have the power of a dedicated content system. Would a change of wiki software be possible? I know that http://moinmo.in/ (used by Ubuntu wiki) is capable of doing subpages (e.g. .../Manual/French)
What do people think of changing the wiki software if we start it over from scratch?
Cheers,
[b]LOF[/b]
:D
[b]LOF[/b]
:D
LOF
Are you talking about a manual wiki, other or everything combined into one wiki.
I am strongly against throwing away the existing content. There is over 800 pages there and this action gives a very bad signal to those that have put the most effort into it. These are also the people most likely to contribute to the new wiki. If we choose to move to a new wiki engine all the existing material should be transferred. Each page should be automatically marked as "Needs review for style and content", then we can edit and reorganise as time allows. Maybe it is possible to automatically add these pages to a category NeedsReview.
Are you talking about a manual wiki, other or everything combined into one wiki.
I am strongly against throwing away the existing content. There is over 800 pages there and this action gives a very bad signal to those that have put the most effort into it. These are also the people most likely to contribute to the new wiki. If we choose to move to a new wiki engine all the existing material should be transferred. Each page should be automatically marked as "Needs review for style and content", then we can edit and reorganise as time allows. Maybe it is possible to automatically add these pages to a category NeedsReview.
Will
contribute: [url=http://www.puppylinux.org]community website[/url], [url=http://tinyurl.com/6c3nm6]screenshots[/url], [url=http://tinyurl.com/6j2gbz]puplets[/url], [url=http://tinyurl.com/57gykn]wiki[/url], [url=http://tinyurl.com/5dgr83]rss[/url]
contribute: [url=http://www.puppylinux.org]community website[/url], [url=http://tinyurl.com/6c3nm6]screenshots[/url], [url=http://tinyurl.com/6j2gbz]puplets[/url], [url=http://tinyurl.com/57gykn]wiki[/url], [url=http://tinyurl.com/5dgr83]rss[/url]
@LOF - I'm with Will on this one. There are also a myriad of links, HOWTO's and other stuff that is very important for understanding Puppy.HairyWill wrote:I am strongly against throwing away the existing content.
Either we should go for the upgraded version of Wikkawiki (our current wiki engine), or move the content to Drupal's wiki for better control and security. Either way, the content is indispensable, IMHO.
[i]Actions speak louder than words ... and they usually work when words don't![/i]
SIP:whodo@proxy01.sipphone.com; whodo@realsip.com
SIP:whodo@proxy01.sipphone.com; whodo@realsip.com
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
I am already using an updated wakkawiki for tmxxine and the main difference is in better editing facilities.WhoDo wrote:go for the upgraded version of Wikkawiki (our current wiki engine)
It seems to be stable but the security updates for spam have not yet been added
http://docs.wikkawiki.org/WikkaReleaseNotes1164
A wakkawiki update is due this month - however I heard that one 4 months ago
mod_php4
Surprise, surprise - I saw it last night but could not believe it. Now am starting to believe. The Apache server at puppylinux.org has no version* number and it runs mod_php4 (version 4.3.11).
Oli can't get dokuwiki to work since yesterday, and am running out of solutions, so I looked again at phpinfo. AFAIK, servers should now be running PHP5, and dokuwiki coders know this.
I could be wrong, but I have used dokuwiki before in a netfirms site, without problems.
Possible solution: use another server that can run dokuwiki.
-------------------
* phpinfo says "Servage.net Cluster/(Enhanced Apache)" without giving any number.
Oli can't get dokuwiki to work since yesterday, and am running out of solutions, so I looked again at phpinfo. AFAIK, servers should now be running PHP5, and dokuwiki coders know this.
I could be wrong, but I have used dokuwiki before in a netfirms site, without problems.
Possible solution: use another server that can run dokuwiki.
-------------------
* phpinfo says "Servage.net Cluster/(Enhanced Apache)" without giving any number.
Puppy user since Oct 2004. Want FreeOffice? [url=http://puppylinux.info/topic/freeoffice-2012-sfs]Get the sfs (English only)[/url].
Good point guys. Sorry I completely forgot about the need to change all links around and reformat everything when transferring content. I guess I just thought of copying and pasting. Soz.WhoDo wrote:@LOF - I'm with Will on this one. There are also a myriad of links, HOWTO's and other stuff that is very important for understanding Puppy.HairyWill wrote:I am strongly against throwing away the existing content.
Either we should go for the upgraded version of Wikkawiki (our current wiki engine), or move the content to Drupal's wiki for better control and security. Either way, the content is indispensable, IMHO.
Anyway, a quick question. Have people considered using the current wiki for the manual? If there are technical problems in setting up a new one, and we can somehow set access levels for users of a particular catergory on the existing wiki (can this be done?), then surely it would make sense to put manual development onto the existing structure.
Just throwing some ideas out there, feel free to shoot them down...
Cheers,
[b]LOF[/b]
:D
[b]LOF[/b]
:D
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
html can be displayed on a wiki page by putting it between a set of double quotation marks
eg
http://puppylinux.org/wikka/AdditionalPrograms
eg
http://puppylinux.org/wikka/AdditionalPrograms
Sorry to have not contributed for the past few days, I was discussing some stuff with raffy.
So anyway, Drupal, yes my favourite, the self-proclaimed provider of "community plumbing". It is the complete Content Management System, not really possessing a specific speciality, but excelling in adaptability whilst keeping all its functionality under one roof. With only Joomla to compete with it is widely considered to be the most powerful non-commercial CMS.
It literally has thousands of modules and a huge, friendly and helpful community following. The Internationalisation module (which I have some experience with) and the Localisation module might be interesting to Oli (there are even more translation modules that I have not looked at) -- let me know if you'd be interested in trying them out.
Its core functionality is all about providing means to manage and manipulate large amounts of varied content, pages, wikis, images, blogs and even custom content types. Also part of the core is the ability to finely control privileges on a per user and per role basis.
Drupal is perfectly built for the kind of project that we are talking about here, it's the kind of thing were, scattered throughout its code, there will be numerous gadgets, gizmos and features that cover eventualities that we could have never foreseen. I think it would also be a great investment for the future, because if we ever start thinking about adding new features to Puppy's web life, we can just consider adding new modules rather than a whole new piece of separate software that needs to be separately installed, themed, administrated, maintained and registered with unique usernames.
If anyone would like admin access to the Drupal backend of my proto-site, just PM me.
PS Oli's been sorted out with his test docuwiki installation, so no worries there.
So anyway, Drupal, yes my favourite, the self-proclaimed provider of "community plumbing". It is the complete Content Management System, not really possessing a specific speciality, but excelling in adaptability whilst keeping all its functionality under one roof. With only Joomla to compete with it is widely considered to be the most powerful non-commercial CMS.
It literally has thousands of modules and a huge, friendly and helpful community following. The Internationalisation module (which I have some experience with) and the Localisation module might be interesting to Oli (there are even more translation modules that I have not looked at) -- let me know if you'd be interested in trying them out.
Its core functionality is all about providing means to manage and manipulate large amounts of varied content, pages, wikis, images, blogs and even custom content types. Also part of the core is the ability to finely control privileges on a per user and per role basis.
Drupal is perfectly built for the kind of project that we are talking about here, it's the kind of thing were, scattered throughout its code, there will be numerous gadgets, gizmos and features that cover eventualities that we could have never foreseen. I think it would also be a great investment for the future, because if we ever start thinking about adding new features to Puppy's web life, we can just consider adding new modules rather than a whole new piece of separate software that needs to be separately installed, themed, administrated, maintained and registered with unique usernames.
If anyone would like admin access to the Drupal backend of my proto-site, just PM me.
PS Oli's been sorted out with his test docuwiki installation, so no worries there.
Thanks to Raffy, Tom and Eric I can test dokuwiki now. It is very easy to use and - if everything I need works - I would like to use it for the manual.
Perhaps Raffy and Eric can manage to run dokuwiki at the prospective website (www.puppylinux.org ?) too. Then there should be a login so that only the manual's maintainer can edit.
Perhaps Raffy and Eric can manage to run dokuwiki at the prospective website (www.puppylinux.org ?) too. Then there should be a login so that only the manual's maintainer can edit.
@Oli: What do you think about using Drupal? I can see that Dokuwiki is certainly capable of maintaining the manual, but from the wider point of view of the whole Puppy website there would be many advantages to just using one CMS.
From what I have read I can see that maintaining the manual will require 3 main areas:
Revision Control: If someone makes a change to a manual page the old version needs to be retained automatically. Drupal has this as standard.
Access Control: Only users that are trusted translators or maintainers should be able to edit manual pages. Again Drupal has this functionality as standard.
Notification Support: Whenever a manual page is updated, in ANY language, the maintainers of the other manual pages need to be notified. Drupal has a notification module. It also provides a comment feature for all content types, access to read/write these can be finely controlled.
There is also a clone module that may come in useful when upgrading the manual to a new version -- we can simply make a copy of the entire manual, then hide it from public view and edit it privately until it is ready, then simply switch the manuals around.
I appreciate that this maybe a compromise for you, learning something which might be quite new to you. However, I mention it because I think it would be worth considering from the broader perspective of the other features that we need to integrate now (ie, the general WIKI and main website) and in the future.
From what I have read I can see that maintaining the manual will require 3 main areas:
Revision Control: If someone makes a change to a manual page the old version needs to be retained automatically. Drupal has this as standard.
Access Control: Only users that are trusted translators or maintainers should be able to edit manual pages. Again Drupal has this functionality as standard.
Notification Support: Whenever a manual page is updated, in ANY language, the maintainers of the other manual pages need to be notified. Drupal has a notification module. It also provides a comment feature for all content types, access to read/write these can be finely controlled.
There is also a clone module that may come in useful when upgrading the manual to a new version -- we can simply make a copy of the entire manual, then hide it from public view and edit it privately until it is ready, then simply switch the manuals around.
I appreciate that this maybe a compromise for you, learning something which might be quite new to you. However, I mention it because I think it would be worth considering from the broader perspective of the other features that we need to integrate now (ie, the general WIKI and main website) and in the future.
drupal sounds good to me
I've never worked with drupal, but I do know it is taking over from commercial content management systems all over the place. Even the local polytechnic has decided to move all its content over to a drupal system (except for online learning, for which they are using the Australian created Moodle instead of Blackboard, which they used to use).
If tombh is offering to set up a Drupal site, I think it would be daft not to go with that. Anyway, its a useful skill to learn as far as I'm told; its expanding in use so rapidly that a former colleague tells me that there is lots of work in that area.
If tombh is offering to set up a Drupal site, I think it would be daft not to go with that. Anyway, its a useful skill to learn as far as I'm told; its expanding in use so rapidly that a former colleague tells me that there is lots of work in that area.
Hi William and all,
Yes, Drupal is the way to go for me. I plan on moving to Drupal for all of puppylinux.ca in the not too distant future.
With Tom's help and his knowledge of Drupal this should be a fairly smooth process.
You never know but maybe Tom can earn some real money in the future from the test runs that will be done here.
Best,
Eric
Yes, Drupal is the way to go for me. I plan on moving to Drupal for all of puppylinux.ca in the not too distant future.
With Tom's help and his knowledge of Drupal this should be a fairly smooth process.
You never know but maybe Tom can earn some real money in the future from the test runs that will be done here.
Best,
Eric
[color=darkred][i]Be not afraid to grow slowly, only be afraid of standing still.[/i]
Chinese Proverb[/color]
Chinese Proverb[/color]
I had a look at Drupal, especially at "How to make a manual". If I understood right you have to use html-code to format the content. This is a disadvantage in comparison to dokuwiki because content and layout is not seperated. Dokuwiki seems to be much easier to use.
@ Tombh, Caneri, Raffy: I've made some test pages in dokuwiki (you know the URL), simulating two languages and (at one page of the manual) two versions. Pictures are still missing.
@ Tombh, Caneri, Raffy: I've made some test pages in dokuwiki (you know the URL), simulating two languages and (at one page of the manual) two versions. Pictures are still missing.
@Oli
I was wanting to know that you understand that we're considering Drupal for the whole website not just the manuals. Dokuwiki is good for the manuals but not so good for the other aspects of the website (ie, main website and general WIKI).
In order to give these 3 aspects a consistent design it will be easier for me if they all use the same CMS. It will also be easier for users and maintainers because they will only have one username and password.
I understand that Drupal will be harder to use at first, but is it so much harder that we seriously need to consider using separate CMSs?
PS. You don't have to use HTML to format the content in Drupal, it is just an option. It has the same WYSIWYG (What You See Is What You Get) editor as Dokuwiki -- see the TINYMCE editor in action here.
I was wanting to know that you understand that we're considering Drupal for the whole website not just the manuals. Dokuwiki is good for the manuals but not so good for the other aspects of the website (ie, main website and general WIKI).
In order to give these 3 aspects a consistent design it will be easier for me if they all use the same CMS. It will also be easier for users and maintainers because they will only have one username and password.
I understand that Drupal will be harder to use at first, but is it so much harder that we seriously need to consider using separate CMSs?
PS. You don't have to use HTML to format the content in Drupal, it is just an option. It has the same WYSIWYG (What You See Is What You Get) editor as Dokuwiki -- see the TINYMCE editor in action here.
Hi tombh
Following on from nathan's post I just posted elsewhere about spam assassin, though it's not my field, however
http://www.murga-linux.com/puppy/viewto ... 439#183439
and the altering of pizzasgood's post here
http://murga-linux.com/puppy/viewtopic. ... 9388da2335
are examples of problems of relying on badly set up filters
perhaps you should invite suggestions for dealing with via*** type spam advertising getting through, as alienjeff is going to explode if it transfers to the new site after all your efforts
Thanks
Aitch
Following on from nathan's post I just posted elsewhere about spam assassin, though it's not my field, however
http://www.murga-linux.com/puppy/viewto ... 439#183439
and the altering of pizzasgood's post here
http://murga-linux.com/puppy/viewtopic. ... 9388da2335
are examples of problems of relying on badly set up filters
perhaps you should invite suggestions for dealing with via*** type spam advertising getting through, as alienjeff is going to explode if it transfers to the new site after all your efforts
Thanks
Aitch