Hello,
Please bear with me, I'm really new to using wikimedia, and am not
familiar with .htaccess work.
I have searched the mailing list archives, but haven't found much. I
have Googled, and have read several times the manual ('short URL' and
'using very short URL' in particular). I have attempted several
variations of the suggestions found there, but I must be missing
something relatively simple... Problem is, I have no idea what I'm
missing.
I am putting in a new wiki. I have the install in the root of the
domain. Currently, my urls look like:
http://mydomain.com/index.php?title=Main_Page
First, I want to make sure that the www is never used in urls, and
that if someone types in www.mydomain.com, the page that loads is
mydomain.com. I think have managed to stop jumping from www to no-www
between loging in by using $wgServer = "http://mydomain.com"; in my
localsettings.php page, but someone can still load a page by typing
the www in the address bar. Any thoughts on this one?
Second, I'm wanting to get Short URL/Very Short URL working. I'm
looking at using the .htaccess rewrite method, but all .htaccess
example base themselves on the wiki being installed in /wiki or /w and
I can't figure out how to get this to work? Would anyone have a
working .htaccess sample for a wiki installed at /root ?
Finally, what I'd *prefer* would be to reflect the site's structure
within the URL, and end up with something like:
http://mydomain.com/category/subcategory/article
or
http://mydomain.com/category/article
This obviously addresses those pages which belong in categories and/or
subcategories only.
Thank you for any assistance or pointers on this topic,
Sean
> I can't use the mod_rewrite rules unless I have root access, it seems,
> which I don't. I know there are two other methods for using the pretty
> URLs if you don't have root access, but will they work if I'm using PHP
> as a CGI module? I don't want to attempt the edit only to have to undo
> it because it doesn't work or causes problems.
> -Azurite
You should not need root access to use the basic mod_rewrite functionality, assuming your host allows you to override those directives. Otherwise you can only use it if you make the changes in the main httpd.conf file. Double check that your syntax is correct, and make sure you are not trying to do any logging. I remember something about logs being a bit flaky and crashing a lot. If anything try |RewriteLogLevel 0.
Regards,
Tikhon
|
I've gotten to the point where I'm dizzy from going around in circles on
this. I'm new to PHP, JavaScript, and MediaWki, doing as much reading
as I can and doing tutorials as fast as possible to get acquainted with
the basics of each piece so that things make a little more sense. In
the meantime I've got a user that would like to have extra edit buttons.
He keeps pointing out that he has them in Wikipedia, so would like them
on our internal-only wiki also.
I've looked at the AddButtonExtension that is listed at the MediaWiki
website, but that makes me a bit nervous due to the wanrings posted in
the article. see http://www.mediawiki.org/wiki/Add_Button_Extension
The MarkS extraeditbuttons.js seems to be referenced by a lot more
folks, and possibly is the the basis for the Wikipedia edit buttons...
not sure.
Here are my questions:
1 - First, has anyone recently done the extraeditbuttons in the Linux
environment and if so can you share what you learned?
2 - The article that documents the MarkS Edit buttons
http://en.wikipedia.org/wiki/User:MarkS/Extra_edit_buttons has a section
at the end for installing on your own wiki. It refers to monobook.js and
common.js and live.css, etc.. Do they mean a monobook.js or
[skinname].js in the skins directory that is in use as your default
skin? or are these special User: pages that a user can create?
3 - The articles imply that you can allow a single user to update edit
buttons by letting them run their own personal js script, as opposed to
updating site-wide edit buttons. Since they could put anything in a .js
this is might be a bit risky, but if I wanted to do it (we only have a
few users allowed to edit/udpate pages so the risk is low here), then I
let them create pages like "MediaWiki:monobook.js" or something? As
long as I allow users to execute java scripts is this how it would be
implemented?
4 - I also found an entry in the archive that pointed to wikibits.js. I
do see the section regarding CustomEditButtons in wikibits.js, but I
don't know enough about javascript to make thse changes. I assume that
this would be the best way to make the changes site-wide so anybody
could use the updated edit buttons.
5 - I plan to try again to follow the instructions at the end of the
MarkS article. There is no "common.js" that I can find on my wiki
installation though. Should it go in the skins/common subdirectory?
Many apologies if my inexperience is annoying... If you have
recommendations on how to quickly get up to speed and what my highest
priorities should be I'm open to advice.
Thanks,
Beth Russell
Hello,
I noticed that when a not-logged user goes to some category page together with category members also an edit textarea is opened to edit the category (a not created one).
Is it possible to set Mediawiki so that a not logged-in user can see some category members page, but the edit textarea is not opened (and it is a not created category page), so that only the members are displayed?
---------------------------------
Pinpoint customers who are looking for what you sell.
Hello,
I'm looking for the best way to backup and restore a mediawiki server.
I have an older server which I plan on migrating to a newer one, and was
trying to figure out the best way to do this.
Thank you,
Sean
Hi all,
recently I started working on a project of a small compiler that
should add more comfort to working with the Mediawiki templates. The
reason for starting it was that I found it rather very unjustifiably
hard to write, edit, debug or oversee any larger template. On a
suggestion of my wikipedian colleagues I write you this email
announcing this project, and calling you to contribute in form of
suggestions, wishes and bug reports if you find will and time for
that.
About the project:
http://sr.wikipedia.org/wiki/%D0%9A%D0%BE%D1%80%D0%B8%D1%81%D0%BD%D0%B8%D0%…
Download page:
http://cpptea.com/wiki/mtc/
Thank you for the audience,
Michael
TableEdit 0.75 was just released to mediawiki.orghttp://www.mediawiki.org/wiki/Extension:TableEdit
Two major changes and lots of bug/compatibility fixes:
Major change 1: database name is specified by $wgTableEditDatabase
Major change 2: an empty table appears instead of the Create Table
Here link
For those who haven't seen these release announcements before,
TableEdit is an extension that calls up a Special page to use forms
to edit tables.
I decided to move it from experimental to beta largely because we are
turning it loose on some actual users this week.
Jim
=====================================
Jim Hu
Associate Professor
Dept. of Biochemistry and Biophysics
2128 TAMU
Texas A&M Univ.
College Station, TX 77843-2128
979-862-4054
There's a protect link available in articles. Clicking on that link
lists only "block unregistered users" and "Sysops". Why the other
mediawiki user groups are not listed there?
Regards,
Jack
This electronic mail (including any attachment thereto) may be
confidential and privileged and is intended only for the individual or
entity named above. Any unauthorized use, printing, copying, disclosure
or dissemination of this communication may be subject to legal
restriction or sanction. Accordingly, if you are not the intended
recipient, please notify the sender by replying to this email
immediately and delete this email (and any attachment thereto) from your
computer system...Thank You
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
This electronic mail (including any attachment thereto) may be confidential and privileged and is intended only for the individual or entity named above. Any unauthorized use, printing, copying, disclosure or dissemination of this communication may be subject to legal restriction or sanction. Accordingly, if you are not the intended recipient, please notify the sender by replying to this email immediately and delete this email (and any attachment thereto) from your computer system...Thank You
I just moved to a VPS from shared hosting and not using pretty URLs
is enabled.
How can I turn this off? I have some custom code that will not work
with it.
Thanks,
-Adam
Welcome to mediawiki-l. This mailing list exists for discussion and questions
about the MediaWiki software[0]. Important MediaWiki-related announcements
(such as new versions) are also posted to this list.
Other resources.
If you only wish to receive announcements, you should subscribe to
mediawiki-announce[1] instead.
MediaWiki development discussion, and all Wikimedia technical questions, should
be directed to the wikitech-l[2] mailing list.
Several other MediaWiki-related lists exist:
- mediawiki-api[5] for API discussions,
- mediawiki-enterprise[6] for discussion of MediaWiki in the enterprise,
- mediawiki-cvs[7] for notification of commits to the Subverion repository,
- mediawiki-i18n[8] for discussion of MediaWiki internationalisation support,
- wikibugs-l[9] for notification of changes to the bug tracker.
List administrivia (unsubscribing, list archives).
To unsubscribe from this mailing list, visit [12]. Archives of previous postings
can be found at [3].
This list is also gatewayed to the Gmane NNTP server[4], which you can use to
read and post to the list.
Posting to the list.
Before posting to this list, please read the MediaWiki FAQ[10]. Many common
questions are answered here. You may also search the list archives to see if
your question has been asked before.
To post to the list, send mail to <mediawiki-l(a)lists.wikimedia.org>. This is a
public list, so you should not include confidential information in mails you
send.
When replying to an existing thread, use the "Reply" or "Followup" feature of
your mail client, so that clients that understand threading can sort your
message properly. When quoting other messages, please use the "inline" quoting
style[11], for clarity.
When creating a new thread, do not reply to an existing message and change the
subject. This will confuse peoples' mail readers, and will result in fewer
people reading your mail. Instead, compose a new message for your post.
Messages posted to the list have the "Reply-To" header set to the mailing list,
which means that by default, replies will go to the entire list. If you are
posting a reply which is only interesting to the original poster, and not the
list in general, you should change the reply to only go to that person. This
avoids cluttering the list with irrelevant traffic.
About this message.
This message is posted to the list once per week by <river(a)wikimedia.org>.
Please contact me if you have any questions or concerns about this mailing.
References.
[0] http://www.mediawiki.org/
[1] http://lists.wikimedia.org/mailman/listinfo/mediawiki-announce
[2] http://lists.wikimedia.org/mailman/listinfo/wikitech-l
[3] http://lists.wikimedia.org/pipermail/mediawiki-l/
[4] http://dir.gmane.org/gmane.org.wikimedia.mediawiki
[5] http://lists.wikimedia.org/mailman/listinfo/mediawiki-api
[6] http://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise
[7] http://lists.wikimedia.org/mailman/listinfo/mediawiki-cvs
[8] http://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
[9] http://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[10] http://www.mediawiki.org/wiki/FAQ
[11] http://en.wikipedia.org/wiki/Posting_style#Inline_replying
[12] http://lists.wikimedia.org/mailman/listinfo/mediawiki-l