Hey Anne.
This can be done without a problem.
Example:
http://userbase.kde.org/index.php?title=Special:NewPages&feed=atom&namespace=90
Use Recent changes to also include changes to existing posts:
http://userbase.kde.org/index.php?title=Special:RecentChanges&feed=atom&namespace=90
Siebrand
-
Purohit, Sumit wrote:
> Hi,
> Is there any way to deploy mediawiki without using web based form/script ?
>
> I am trying to deploy mediawiki 1.15.4 using some command line scripts and
> passing some config parameters but it seems that only way is to use web
> based config script.
>
> Thanks
>
On 17 October 2010 17:30, Steve VanSlyck wrote:
> OK - I'm pretty non-tech. What IS the htaccess file all about?
I meant .htpasswd:
http://en.wikipedia.org/wiki/.htpasswd
It puts a password on accessing a page (or site) at all. Then once
you've put in that password, you can access the wiki or
TechGeek,
I think you'll find the answer to this question of "benefits of a wiki", in
the non-technical advice given by George:
Some good resources:
Shirky's "Here Comes Everybody" and "Cognitive Surplus" books, Tapscott and
Williams "Wikinomics" book and the many magazine and web articles that
> reasonably common within organizations I've been at, though some have
> used Twiki or Plone or another one instead of MediaWiki. I advocate
> for it, and prefer using MediaWiki.
Just to give more clarity:
I am more looking for benefits of wiki in general and not which tools
to use because if we
Hi,
I've finally got the LDAP Authentication working on my mw installation.
Nearly everything works fine, even preferences like nickname and email
are retrieved from the ldap-database.
Though, the users are not able to change their passwords unfortunately.
Everytime the try to access the special-s
OK - I'm pretty non-tech. What IS the htaccess file all about?
- Original Message -
From: David Gerard
To: MediaWiki announcements and site admin list
Date: Sun, 17 Oct 2010 17:23:04 +0100
Subject: Re: [Mediawiki-l] Benefits of using wiki in a corporate
environment-how to convience?
>
On 17 October 2010 03:20, George Herbert wrote:
> On the followup question - yes. You need to have the landing pad
> "main page" visible to anyone, but you can create a group memberships
> structure with a custom group that keeps anyone from accessing content
> unless you approve them. That isn
Bruce,
You may also want to look at
http://www.mediawiki.org/wiki/Security_issues_with_authorization_extensions
It has some great information. You should be aware that in most "protected"
environments, there are three basic approaches:
1. Restrictions based on user (limiting access to certain u
On 17/10/10 11:33, Anne Wilson wrote:
> We use the Liquid Threads extension. It would be very useful to be able to
> set up an RSS or Atom feed to pick up new threads. It's obviously not
> practical to put a watch on every Talk page. Does anyone have a solution to
> this?
>
> Anne
>
>
>
>
We use the Liquid Threads extension. It would be very useful to be able to
set up an RSS or Atom feed to pick up new threads. It's obviously not
practical to put a watch on every Talk page. Does anyone have a solution to
this?
Anne
--
KDE Community Working Group
New to KDE Software? - get h
11 matches
Mail list logo
