I've decided to publish my first extension -
http://www.mediawiki.org/wiki/Extension:Link
This extension enables user to create links to network locations with ease.
Basic behaviour can be configured.
Let me know what you think.
Regards,
Aretai
This extension allows the creation of a hierarchical page navigation structure.
It is not intended to structure the contents of a whole wiki like the
Treeview skin. Instead, it is suited to create hierarchical sets of
pages within a web-like wiki.
Possible applications are tutorials and reference manuals.
Homepage: http://www.mediawiki.org/wiki/Extension:Hierarchy
Introduction:
There are three main forms to organize content on a web site: webs,
sequences and hierarchies.
A web is the most common organization form for a wiki. In this
structure, pages have many free links among them. This format is
well-suited for pages that are loosely related, such as encyclopedic
entries.
In a sequence, pages are organized in a sequential form. One page
leads to the next. This structure is appropriate for tutorials and
presentations.
A more structured form is the hierarchy. It is useful when there is a
natural classification of the content that makes navigation more
intuitive. It could be used, for instance, for a product reference
manual.
MediaWiki excels at the web structure. It can also be used to
represent hierarchies, using internal links and subcategories. But
sometimes it is useful that, in addition to the web structure, the
user is presented with some guidance that will help him to have a
global vision of an information body and to achieve an easier
navigation.
The Hierarchy Extension can be used to create sequential and
hierarchical structures.
Hi,
I've created a dump of my wiki, and was wondering if there is a way of
adding additional pages to the dump and for the pages to display and be
searched correctly. I have tried copying the syntax used for other
pages and then importing the dump - this seems to create the page
however searching for the page is not possible (even after running the
rebuildall.php script). Any ideas?
Cheers
Tom
I won't go into reasons, but we would like to be able to have a single
account that might be accessed by a number of people. This implies that
more than one person might be logged into that account (and editing) at
the same time. Will this mess with MW's head?
Thank you,
Ken
P.S. Thanks once again to all those who have answered my questions in
the past, especially Rob. My company _will_ be making a small donation
to MediaWiki in the near future...(as soon as I get around to finding
and sending them the donations URL :-) )
The Treeview skin has finally made it out of alpha and is available for
public use as a beta. The skin adds a dynamic and configurable
javascript-based treeview component in place of Monobook's navigation
sidebar, supporting load-on-demand when expanding nodes. It also adds a
couple of other niceties that you can see here:
http://clc-wiki.net
The skin can be downloaded from here:
http://members.dodo.com.au/~netocrat/software
and feedback can be viewed/added here:
http://clc-wiki.net/wiki/Planning:Treeview_skin:Feedback
The skin is best suited to small-medium sized sites with relatively low
edit rates and with a MediaWiki cache manager enabled.
--
http://members.dodo.com.au/~netocrat
Hrm, definitely using ImageMagick... why would it fail on .jpg only and not gif if a server misconfig?
Thanks,
Jen
Quoted Text:
Perhaps a miss-configuration on the webserver.
If u are using GDLib, just try to use ImageMagick!
Regards,
Jan
Niedziela, Jennifer schrieb:
> Running 1.9.1. When a user attempts to change the size of a *.jpg file (via [[Image:filename.jpg|thumb|Description]], an error is created reading: "Permission denied convert: no decode delegate for this image format ... missing an image filename".
>
> This works just fine for *.gif files. Any ideas?
>
> Thanks,
> Jen
Running 1.9.1. When a user attempts to change the size of a *.jpg file (via [[Image:filename.jpg|thumb|Description]], an error is created reading: "Permission denied convert: no decode delegate for this image format ... missing an image filename".
This works just fine for *.gif files. Any ideas?
Thanks,
Jen
Hi, I'm new to mediawiki, and tried to figure out how can I integrate
the content of more elementary pages into one single page (mainly for
printing purposes) using some "include" directive like thing, similar to
the {{pagename}}.
The problem for me is that in this case it tries to include the
Template:pagename template page content. (Understood that this is the
normal behaviour)
I found that if I have a sub-page, under "integrating_page" like
/subpage and put the {{/subpage}} into the integrating_page, then it
works, however sub pages are not allowed by default on the Main namespace.
- Is there any option different from this subpage thing in mediawiki, or
what I'm up to is completely alien from mediawiki's nature?
- If only this subpage trick works, is there any drawback (in search
performance or other) to enalbe subpages for the Main namespace by
adding the
--------8<--------8<--------8<--------8<
$wgNamespacesWithSubpages += array(
NS_MAIN => true,
);
--------8<--------8<--------8<--------8<
section to the LocalSettings.php?
Thanks,
Laszlo
I've modified my LocalConfig.php file to include the following at the
end (MediaWiki 1.6.8):
$wgGroupPermissions['*' ]['createaccount'] = true;
$wgGroupPermissions['*' ]['read'] = true;
$wgGroupPermissions['*' ]['edit'] = true;
$wgGroupPermissions['*' ]['createpage'] = true;
$wgGroupPermissions['*' ]['createtalk'] = true;
$wgGroupPermissions['*' ]['upload'] = true;
Also, the images directory and all directories/subdirs in it are fully
writable.
Even with this, MediaWiki says that you must be logged in to upload images.
Is there a php cache that needs to be cleared for the new settings to be
loaded? Or am I missing the effect of another setting.
Thanks,
Ken
Hi there!
With the inputbox extension, is there a way to directly create a page
without having to submit the edit form that is displayed after
clicking inputbox's create button?
Cheers,
Ingmar