Hello,
I'd like to modify the edition buttons (the buttons you have above the
edition frame when you modify a page), to remove the date from the
signature button, and keep only the name.
It works manually when removing one of the '~' from the signature added
(the button adds --~~~~), so I'm trying to find where the javascript for
the buttons comes from.
--
*André Meunier*
My fellow wiki and semantic wiki-ers,
It's my honor to announce the next International Semantic MediaWiki
Conference - SMWCon Spring 2011 on April 28-30 in Arlington, VA, USA -
Greater Washington DC area. This longest SMWCon will have a tutorial day for
the first time, so we are calling for tutorial speakers as well as
participants. Please note that if you're an expert on MediaWiki, you're very
welcome to propose a tutorial (or be part of it).
For more information, please visit
http://semantic-mediawiki.org/wiki/SMWCon_Spring_2011.
Cheers,
Jesse <http://semantic-mediawiki.org/wiki/User:Jesse>
On 11-02-08 02:17 AM, Steve Bennett wrote:
> On Mon, Feb 7, 2011 at 9:05 PM, Daniel Friesen
> <lists(a)nadir-seen-fire.com> wrote:
>> If you have a MediaWiki skin you've built, feel free to bring out it's
>> source code. Currently most of the few custom skins that exist are
>> floating around the Internet, and they are various degrees of out of
>> date. Bring up the source code, and I'll look into committing the skin
>> into svn and cleaning it up stripping away the boilerplate.
> Have a look at userstyles.org[1]. I'm not sure what the licences are,
> but perhaps we can contact some of the authors? I'm a big fan of
> Wikipedia Grey Lady III.
>
> Btw would you mind explaining the difference between a skin and a CSS
> file, assuming there is one?
>
> Steve
> [1] For those unfamiliar with it, it's a repository of site-specific
> CSS files for use with the browser extension Stylish. You pick a style
> that someone has defined for a given site, and everytime you visit
> that site, you'll get that CSS layered over the top.
A CSS file is simply a stylesheet to style the markup, you can reference
some images from the styles as backgrounds.
An actual skin is comprised of css files, optionally js, images, and
most importantly a php file that is used to generate the markup.
I guess I should be clear, I'm not really looking for just stylesheets,
or the plethora of monobook clones with minor tweaks out there.
The reason why I asked for mockups especially rather than just asking
for skins (besides saying I'd be happy to clean them up and commit them
to svn so that we have an actual maintained repository of the skins) was
since what I'm especially looking for are mockups that have the areas
necessary for a skin to function as a wiki (something blog themes are
lacking making them hard to port as examples) but break the normal rules
(maybe they don't use the standard sidebar, have extra links, do
navigation differently, put categories somewhere else, etc...) of how a
skin looks. Besides some nice extra skins to add to the repo, I need
some examples that break the normal patterns to work with and build as I
rip out the restrictions in the current skin system. And hence I asked
for mockups since such skins are already hard enough that most people
probably would never have got to implementation.
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name]
I've been making some improvements to the skin system for awhile now, so...
If you have a MediaWiki skin you've built, feel free to bring out it's
source code. Currently most of the few custom skins that exist are
floating around the Internet, and they are various degrees of out of
date. Bring up the source code, and I'll look into committing the skin
into svn and cleaning it up stripping away the boilerplate.
I would LOVE skin designs right now. If you've got a nice idea for a
skin feel free to mock it up and post the mockup images for it. If it
looks interesting I'll consider turning it into a real skin, ESPECIALLY
if it break our de-facto traditions on what makes up a wiki skin. Our
rigid skin structure is one of the big limitations of our skinning
system right now, skins that define things beyond the current
restrictions are good examples needed while we break open the rigid
structure of our skins.
--
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name]
Hey,
I've installed a fresh MediaWiki using Mediawiki 1.16.2 and PostgreSQL 8.4.7.
Now i stuck in some trouble with the search function.
Example:
extract from the Main Page: "Therapieempfehlungen" (german)
If I search "Therapieempfehlungen" I got as result the Main Page. But
if I search "Therapie" MediaWiki cannot found this phrase on the Main
Page.
More examples: Therapiepfade, Chemotherapie. None of these words can
be found if I search 'Therapie'.
Is this a problem of the fulltext Search Engine of PostgreSQL or is
there a mistake in the configuration?
Thanks
Hi,
I'm trying to install mediawiki 1.16.2, but i'm getting these errors:
PHP 5.3.3 installed
* Found database drivers for: MySQL SQLite
* PHP server API is apache2handler; ok, using pretty URLs
(index.php/Page_Title)
* Have XML / Latin1-UTF-8 conversion support.
* Session save path (/var/lib/php/session) appears to be valid.
* PHP's memory_limit is 16M bytes. Raised memory_limit to 52428800
bytes.
* Couldn't find eAccelerator, APC or XCache; cannot use these for
object caching.
* Found GNU diff3: /usr/bin/diff3.
* Found ImageMagick: /usr/bin/convert; image thumbnailing will be
enabled if you enable uploads.
* Found GD graphics library built-in.
* Installation directory: /net6/web/private/mediawiki
* Script URI path: /private/mediawiki
* Installing MediaWiki with php file extensions
* Environment checked. You can install MediaWiki.
* Generating configuration file...
* Database type: MySQL
* Loading class: DatabaseMysql
* Attempting to connect to database server as mediawiki...success.
* Connected to mysql 5.1.51; enabling MySQL 4.1/5.0 charset mode
* Database wiki_mediawiki_IBERGRID exists
* Creating tables... FAILED
Query "CREATE FULLTEXT INDEX si_title ON `searchindex` (si_title) "
failed with error code "Column 'si_title' cannot be part of FULLTEXT
index (localhost)".
The database was created by me and the user has all privileges to that
database.
Can anyone give me a hand on this?
Best regards,
--
*************************************************
Hugo Gomes
LIP
Av. Elias Garcia 14, 1º
1000-149 Lisboa, Portugal
Telef.: +351- 217 998 587
URL: http://www.lip.pt
E-mail: hugo(a)lip.pt
*************************************************
Mediawiki version - 1.16.0 (r74364)
I have been running some experiments in moving pages to a newly created
Archive namespace. I created some test pages and moved two with redirects and
two without redirects, so that I could look for unwanted side-effects. I also
marked those four pages with __NOINDEX__. Up to that point everything seemed
fine.
A new category was automatically created - Noindexed_pages. All four of the
pages now in the Archive namespace bear a link to that category, yet when I
use the link I find that only one of the four pages is listed.
Is this a bug, or have I missed something important?
Anne
--
New to KDE Software? - get help from http://userbase.kde.org