Hi all...
I'm having a weird issue with links in an index page in my new wiki. This
is a fresh install of 1.8.2.
To populate my Help section, I've been exporting/importing stuff from
meta.mediawiki.org's Help section. Right now, all of the pages are loaded
onto my site, and if you go to http://mywiki/Help:Whatever, you get the
appropriate page. The issue, however, is that if you go to Help:Contents,
all but 4 of the links show up red. If you go to Category:Help, all of
the pages show up, and if you click on any of the red links, it takes you
to the edit page for that article, with the source of that page already in
the editor.
And here's where it gets really weird...
If you remove one of the links that shows up blue, another link will turn
blue in its place. Always 4 at a time, though.
I've tried deleting and recreating the page. That didn't help, either.
I also already ran refreshlinks.php, and that didn't seem to have any effect.
I'm really confused as to what's causing this...
Hopefully relevant versions:
MediaWiki: 1.8.2
MySQL: 4.1.22
PHP: 5.2.0
And some outputs:
php -v:
PHP 5.2.0 with Suhosin-Patch 0.9.6.1 (cli) (built: Nov 7 2006 09:16:23)
Copyright (c) 1997-2006 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2006 Zend Technologies
uname -a:
FreeBSD Pancake.jlauser.net 6.1-RELEASE-p10 FreeBSD 6.1-RELEASE-p10 #7:
Sun Oct 1 11:31:43 EDT 2006
root@Pancake.jlauser.net:/usr/obj/usr/src/sys/GENERIC sparc64
-- James L. Lauser
james(a)jlauser.net
+--------------+
| +--------+ +-+
| | + \ | | | |
| | - | | | | |
| | + / | | |
| +--------+ + +-+
+--------------+
Ok thank you much.
----- Original Message ----
From: Gary Kirk <gary.kirk(a)gmail.com>
To: MediaWiki announcements and site admin list <mediawiki-l(a)wikimedia.org>
Sent: Tuesday, December 5, 2006 11:41:57 AM
Subject: Re: [Mediawiki-l] Block specific page from specific user?
No, there isn't. That is not what MediaWiki was designed for.
-Gary Kirk
On 12/5/06, beachboy22(a)verizon.net <beachboy22(a)verizon.net> wrote:
> Hello all,
>
> Sorry about the barrage of questions, but I have a pretty demanding user
> group.
>
> Is there a way to black a specific user against a specific page?
>
> Thanks.
>
> Philip B.
> _______________________________________________
> MediaWiki-l mailing list
> MediaWiki-l(a)Wikimedia.org
> http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
>
--
Gary Kirk
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)Wikimedia.org
http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
Yes, this would work globally, but is there any way to set a background image to only the page you are editing?
----- Original Message ----
From: Tim Ware <tim(a)hyperarts.com>
To: MediaWiki announcements and site admin list <mediawiki-l(a)Wikimedia.org>
Sent: Tuesday, December 5, 2006 10:52:09 AM
Subject: Re: [Mediawiki-l] Background Image
On Dec 5, 2006, at 7:01 AM, beachboy22(a)verizon.net wrote:
> Is there a way to use an uploaded picture as the background of a
> new page?
You could modify the style sheet to set a background image globally.
If you use monobook, you'd edit:
/skins/monobook/main.css
Tim
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)Wikimedia.org
http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
Hi, I am using MediaWiki 1.8 with Magpierss and an rss extension and am
trying to use templates for pages but am unable to get the variable to
swap in to the RSS feed. I may not b explaining it right so I've
included what I am trying to do.
My customer page looks like this
{{customer_template|Customer=We sell widgets|}}
And my template looks like this
<UL>
<LI>[[{{{Customer}}} Access|Access]]</LI>
<LI>[[{{{Customer}}} Environment|Environment]]</LI>
<LI>[[{{{Customer}}} Contacts|Contacts]]</LI>
<LI>[[{{{Customer}}} Troubleshoot|Troubleshooting]]</LI>
<LI>[[{{{Customer}}} Other|Other]]</LI>
</UL>
<rss>http://ed/ee/EEsByCustomer.ashx?c={{{Customer}}}|Title={{{Customer}
}} Recent Issues</rss>
{{{Customer}}} is being replaced everywhere except within the RSS tag.
Is there a way to make this work so that it is replaced?
Thanks,
Dylan
I had to change my server to upgrade from 1.6.8 because my old hoster
didn't provide the php5 the way i needed it.
i made a backup of my database.
put my complete Mediawiki-Folder onto the new server.
uploaded the 1.7.1 files.
performed the installscript (since i have no shell there).
it worked.
then i uploaded the 1.8.2 files.
performed the installschript.
and THIS stopped with this page:
---snip
MediaWiki 1.8.2 Installation
▪ Don't forget security updates! Keep an eye on the low-traffic
release announcements mailing list.
Checking environment...
Please include all of the lines below when reporting installation problems.
▪ PHP 5.1.4 installed
▪ Found database drivers for: MySQL PostgreSQL
▪ Warning: PHP's register_globals option is enabled. Disable it if
you can.
MediaWiki will work, but your server is more exposed to PHP-based
security vulnerabilities.
▪ PHP server API is cgi; using ugly URLs (index.php?title=Page_Title)
▪ Have XML / Latin1-UTF-8 conversion support.
▪ PHP's memory_limit is 50M. If this is too low, installation may fail!
▪ Have zlib support; enabling output compression.
▪ Couldn't find Turck MMCache, eAccelerator or APC. Object caching
functions cannot be used.
▪ 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: /kunden/XXXXX/webseiten/juliwiki.de
▪ Script URI path:
▪ Environment checked. You can install MediaWiki.
Generating configuration file...
▪ Database type: MySQL
▪ Loading class: DatabaseMysql
▪ Attempting to connect to database server as db114494_9...success.
▪ Connected to 4.1.22-debug-log
▪ Database XXXXXXX exists
▪ There are already MediaWiki tables in this database. Checking if
updates are needed...
▪ DB user account ok
...hitcounter table already exists.
...querycache table already exists.
...objectcache table already exists.
...categorylinks table already exists.
...logging table already exists.
...user_newtalk table already exists.
...transcache table already exists.
...trackbacks table already exists.
...externallinks table already exists.
...job table already exists.
...langlinks table already exists.
...querycache_info table already exists.
...filearchive table already exists.
...have ipb_id field in ipblocks table.
...have ipb_expiry field in ipblocks table.
...have rc_type field in recentchanges table.
...have rc_ip field in recentchanges table.
...have rc_id field in recentchanges table.
...have rc_patrolled field in recentchanges table.
...have user_real_name field in user table.
...have user_token field in user table.
...have user_email_token field in user table.
...have user_registration field in user table.
...have log_params field in logging table.
...have ar_rev_id field in archive table.
...have ar_text_id field in archive table.
...have page_len field in page table.
...have rev_deleted field in revision table.
...have img_width field in image table.
...have img_metadata field in image table.
...have img_media_type field in image table.
...have ss_total_pages field in site_stats table.
...have iw_trans field in interwiki table.
...have ipb_range_start field in ipblocks table.
...have ss_images field in site_stats table.
...have ipb_anon_only field in ipblocks table.
...already have interwiki table
...indexes seem up to 20031107 standards
Already have pagelinks; skipping old links table updates.
...image primary key already set.
The watchlist table is already set up for email notification.
...watchlist talk page rows already present
...user table does not contain old email authentication field.
Logging table has correct title encoding.
...page table already exists.
revision timestamp indexes already up to 2005-03-13
...rev_text_id already in place.
...page_namespace is already a full int (int(11)).
...ar_namespace is already a full int (int(11)).
...rc_namespace is already a full int (int(11)).
...wl_namespace is already a full int (int(11)).
...qc_namespace is already a full int (int(11)).
...log_namespace is already a full int (int(11)).
...already have pagelinks table.
...templatelinks table already exists
No img_type field in image table; Good.
Already have unique user_name index.
...user_groups table already exists.
...user_groups is in current format.
...wl_notificationtimestamp is already nullable.
...timestamp key on logging already exists.
Setting page_random to a random value on rows where it equals
0...changed 0 rows
Checking for additional recent changes indices...
...seems to be ok
Fatal error: Call to undefined function: initialisemessages() in
/kunden/XXXXXXXX/webseiten/juliwiki.de/maintenance/updaters.inc on line 848
---snap
i changed only some lines with personal information with XXXXXs.
So i don't get over that point.
The result is, that i have problems with german umlauts (not in the
articles but in the menue and the headlines that are generated by the
system).
you can see the problem here:
http://juliwiki.de
go to recent changes and see the headline. Letzte Änderungen ist spelled
differently there. The Ä and ä in the articles are correct.
I have no clue wehre else to look.
Do you?
With kind regards.
thomas.
Hello together, especially Fernando
I managed to find a much easier way to do this (excuse me not using
diff to highlight the changes):
CategoryPage.php
- --
44: $wgOut->addWikiText( $viewer->getHTML() );
- --
If you've done this, you now can adjust columnList(); and shortList();
to contain WikiText like {{:pagetitle}} or [[pagetitle]] etc. It then
gets automatically parsed. Note that you might want to change the Array
$this->articles[] in addPage(); to contain not a HTML formatted link
(<a href=""></a>) but the pagetitle itself to further use it in the
other functions mentioned above. I used $title->getBaseText(); to get
the corresponding link-title to a page (I hope I did choose wisely?).
Beautiful!
Kind regards
Mario
--
Mario Aeby
Stritenstrasse 47
CH-3176 Neuenegg
Mobile 078 690 50 11
Fax 031 741 28 93
http://www.eMeidi.com/
Frisoni:
Well, you should try the fix at item #153 at:
http://www.mediawiki.org/wiki/Project:Support_desk
....before leaving HostMonster for good. I ended up going to SiteGround.com,
which claim to be specialists at hosting MediaWikis. I got the wiki to work
just fine, but I find their servers to be MUCH slower than HostMonster and
they do NOT offer phone support (email only). On the plus side, my wiki does run
and they answer email fairly quickly.
....but I changed before I heard about the fix listed above. I hear the fix
works on HostMonster.
--Bruce
Damien,
I use the following in LocalSettings.php:
$wgWhitelistRead = array( "Main Page", "Special:Userlogin", "-", "MediaWiki:Monobook.css" );
$wgGroupPermissions['*']['createaccount'] = false;
$wgGroupPermissions['*']['read'] = false;
$wgGroupPermissions['*']['edit'] = false;
$wgGroupPermissions['*']['createpage'] = false;
$wgGroupPermissions['*']['createtalk'] = false;
This effectively locks down the wiki to anyone not logged in. We have a very small userbase that rarely changes, so I don't mind having to manually create the accounts. Obviously if you want anonymous users to have read access you'd change it to true.
JT
----- Original Message ----
From: Damien Hull <dhull(a)digitaloverload.net>
To: MediaWiki announcements and site admin list <mediawiki-l(a)wikimedia.org>
Sent: Tuesday, November 28, 2006 10:55:55 PM
Subject: [Mediawiki-l] Hiding the "edit" link
How do you hide the "edit" link to people who are not logged in?
I know it can be done because I've done it before. Unfortunately I don't
remember what I did. I checked the LocalSettings.php file and didn't
find anything. I'm using version 1.8.2.
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)Wikimedia.org
http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
____________________________________________________________________________________
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
http://new.mail.yahoo.com
Thanks. I'll try it!> Date: Mon, 4 Dec 2006 09:35:08 -0800> From: traviskiger(a)yahoo.com> To: mediawiki-l(a)Wikimedia.org> Subject: Re: [Mediawiki-l] Page tracking (statistics) code> > That's correct. Add the JavaScript snippet right before the "</head>" section of /skins/MonoBook.php. You should probably add it to any other skins that you allow your users to select. Google Analytics works just as expected if you install it like this.> > ----- Original Message ----> From: Fernando Correia <fernandoacorreia(a)gmail.com>> To: MediaWiki announcements and site admin list <mediawiki-l(a)wikimedia.org>> Sent: Monday, December 4, 2006 9:26:14 AM> Subject: Re: [Mediawiki-l] Page tracking (statistics) code> > Maybe on the skins (eg. MonoBook.php).> > 2006/12/3, Yusuf M <yusufm(a)hotmail.com>:> >> > Hi,I'm trying to figure out where I can add the little snippet of code> > that a web statistics site like google analytics provides, to track visitor> > usage of the site. Should it be somewhere in the footer? Would appreciate if> > someone else has found where to add it to.Thanks.> > _________________________________________________________________> > Search from any Web page with powerful protection. Get the FREE Windows> > Live Toolbar Today!> > http://get.live.com/toolbar/overview> > _______________________________________________> > MediaWiki-l mailing list> > MediaWiki-l(a)Wikimedia.org> > http://mail.wikipedia.org/mailman/listinfo/mediawiki-l> >> _______________________________________________> MediaWiki-l mailing list> MediaWiki-l(a)Wikimedia.org> http://mail.wikipedia.org/mailman/listinfo/mediawiki-l> > > > > _______________________________________________> MediaWiki-l mailing list> MediaWiki-l(a)Wikimedia.org> http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
_________________________________________________________________
Express yourself with gadgets on Windows Live Spaces
http://discoverspaces.live.com?source=hmtag1&loc=us
Hello,
Thank you for the responses to my inquiry regarding blog-like comments on
MediaWiki. So far, it doesn't appear this is possible.
If we use the Discussion pages (and lock down the Article pages to
editors/admins only), is there a way to hold Discussion posts (by registered
users) in some sort of moderating queue, so that Admins can approve
Discussion page posts prior to publication?
Thank you,
Colleen Robledo
On 12/4/06, Fernando Correia <fernandoacorreia(a)gmail.com> wrote:
>
> Maybe you should give the "talk" page a try. If not, you could:
>
> a) integrate with a forum software
> b) develop an extension
>
> I'm new to PHP and MediaWiki but I found out that developing an extension
> to
> MediaWiki is not too hard.
>
> 2006/12/1, Morten Blaabjerg <morten(a)crewscut.com>:
> >
> > There's been several attempts at making Blog type extensions, take a
> look
> > at
> > http://meta.wikimedia.org/wiki/Category:MediaWiki_extensions
> > Although AFAIK there's nothing in the true vein of what you describe.
> >
> > I've been looking for something similar, but in the end I just came to
> the
> > conclusion that a wiki and a blog is two quite different things.
> >
> > MediaWiki in particular was designed to split the content of a page and
> > the
> > discussion into two distinct pages. This has advantages, if you want to
> > keep
> > a distinction between "front end" and "back end" of the system. I've
> seen
> > a
> > lot of other wikis where everything is kept on the same page. In a
> sense,
> > they are more true to the original wiki idea than MW, in that they keep
> > process and content together in the same context, which makes things a
> lot
> > simpler. MW has a lot of strength though, in making an informal page
> where
> > "everything is allowed", as opposed to the "encyclopedic article" page
> > where
> > things has to be presented by the book. It all depends on the project.
> >
> > If you want a blog, better go with a blog-friendly system. A blog-tool
> is
> > great for getting a message out quickly and discussing it. A wiki is an
> > incredibly strong collaborative working environment. Which do you want
> the
> > more? There's no reason both couldn't coexist, using CSS and some kind
> of
> > common structure.
> >
> > Best wishes,
> > Morten :-)
> >
> >
> > --
> > Morten Blaabjerg / Crews Cut Production
> > http://morten.crewscut.com
> > morten(a)crewscut.com
> >
> >
> > ----- Original Message -----
> > From: "Colleen Robledo" < colleenrobledo(a)gmail.com>
> > To: <mediawiki-l(a)wikimedia.org>
> > Sent: Friday, December 01, 2006 10:37 PM
> > Subject: [Mediawiki-l] Incorporating blog-like "Comments"
> >
> >
> > > Hello,
> > >
> > > I run an internal MediaWiki wiki for our company, and we're now
> looking
> > at
> > > using the software to develop a public wiki for our customers. What
> my
> > > future team of public wiki admins would like, however, is for each
> > Article
> > > to include a blog-like Comments tool (comments form, and comments
> posts,
> > > all
> > > on the Article page) to encourage public discussion of each
> > Article. They
> > > do not like the Discussion tab option because it breaks the
> conversation
> > > flow.
> > >
> > > Has anyone successfully used any type of plug-in for this type of
> > feature?
> > > Or do you have other suggestions?
> > >
> > > The other side of this request, is that they would like anyone (not
> just
> > > registered users) to be able to Comment, and for those Comments to be
> > able
> > > to sit in a moderation queue for approval.... in other words, exactly
> > what
> > > blogs do with Comments.
> > >
> > > Thank you!
> > >
> > > --
> > > Colleen Robledo
> > > http://www.colleenrobledo.info
> > > _______________________________________________
> > > MediaWiki-l mailing list
> > > MediaWiki-l(a)Wikimedia.org
> > > http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
> > >
> >
> >
> > _______________________________________________
> > MediaWiki-l mailing list
> > MediaWiki-l(a)Wikimedia.org
> > http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
> >
> _______________________________________________
> MediaWiki-l mailing list
> MediaWiki-l(a)Wikimedia.org
> http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
>
--
Colleen Robledo
http://www.colleenrobledo.info