Sigh, having written a couple of extensions to (separately) insert HTML
opening and closing tags into pages, I find that the output of those
extension tags is being wrapped in <p>...</p>. This occurs even if I
don't put line breaks before/after the tags (and omitting line breaks
messes other things up anyway).
For example, one of my tags outputs: <span style="display:block;
float:left; width:33%">
and in the HTML I get:
<p><span style="display:block; float:left; width:33%">
</p>
which is not only not what I want, but also incorrect HTML!
Thanks,
Ken
Hello all!
I do not follow this list, nor am I subscribed to it. However, I have
not found this information elsewhere, and so I wished to post it. This
method allows Drupal-style wiki farms in what I feel is the easiest way
available that I have found.
The link is here:
http://www.mediawiki.org/wiki/Manual:Wiki_family#Scenario_3:_Drupal-style_s…
Please let me know (by emailing directly or CCing me in addition to the
list) how it works out.
tarek : )
Hallo,
also ich bin neu in der ganzen Wiki Sache.
Aufjedenfall will ich das Layout anpassen, habe auch schon im Internet
gesucht, aber leider nix passendes gefunden was auch läuft.
Mein Problem:
Ich möchte die Position von der Such-Box und der Werkzeug-Box vertauschen...
Ich hab dazu auch Code gefunden, der genauso wie meine eigentliche Idee
war, in der MonoBook.php einfach die Positionen vertauschen. Aber egal
was ich in meiner MonoBook.php mache, es zeigen sich keine Veränderungen
auf meiner Seite.
Könnte es sein das ich die falsche Monobook.php bearbeite!?
(wiki/data/skins/MonoBook.php)
Ich bin etwas ratlos....
Desweiteren habe ich noch das Problem, das ich in der main.css einfach
nciht die p-tb Abschnitt finde, der zur Klasse Portlet dazu gehört und
den Style der Werkzeugbox definiert. In meiner main.css geht es los mit
Portlet
Logo
Navigations Portlet
Search Portlet
Personal Toolbar
Page related Actios (mit p-cactions)
Remaining Portlets (p-tbx, p-lang)
Vielen Dank für Hilfe
Its is good to know that the idea is workable. However, Instead of writing an extension, I also considered setting-up an second wiki whose MySQL database was just daily replication of the private one. Then I could just modify the common skins code to look for a "magic word" which will allow the page to render. This solution is closer to what my current programming strengths are. How does this aproach sound to the group?
--- Does it pass the experts ho-ho, ha-ha test?
> Don't refer to yourself as "we" :) Yes, you can.
>
Agreed! :-) --- What I should have said is: "I will", but only after I am convinced that it hasn't been done yet and that the group affirms its value and approves of the approach. Before I begin what would be a serious endeavor like this (for me, that is), I really wanted like to do a little more research here in the list; which, imho, is one of the many things this group is good for (heh heh, I'm referring to the recent post on that topic) by polling the folks who really have their pulse on the wiki development big-picture. I'm not interested in programming for the sake of programming or for my own edification - I'm interested in working towards a functional goal. All in all, Michael, your reply is very positive and affirming. Thank you. However, I noticed that you were careful not to state weather or not this (an extension for pushing updates to another wiki) has been done already, which is the heart of my question.
What I'm hoping for is a consensus about what is the "ideal" approach to achieving the stated functionality.
Thanks gang,
- Rich (revansx)
---- Michael Daly <michaeldaly(a)kayakwiki.org> wrote:
> revansx(a)cox.net wrote:
>
> > I have no experiance doing various language wiki so the whole thing would be new to me.
>
> It's not hard - just follow the instructions in Manual:Wiki Family on
> the mediawiki web site.
>
> > The biggest concern/goal is for the user's experiance to be simple
> > and not have them need to keep track of what is where.
>
> Use two simple but different domain names and use htaccess or virtual
> host to redirect to the appropriate wiki.
>
> > What woudl be geat is if there is an extension that can force an update
> > to a second wiki such that only the protected wiki would user
> > editable and then the extention tag could be dropped in to the article
> > to push updates to the public wiki. That would be really slick!
>
> I thought that this kind of approach could be used instead of fancy
> protection schemes for wikis that want to have a protected production
> system and an editable development version (e.g. wiki as instruction
> manual). The difference is what gets seen rather than what gets
> edited/pushed.
>
> > can we (the group) make it?
>
> Don't refer to yourself as "we" :) Yes, you can.
>
> Mike
>
>
> _______________________________________________
> MediaWiki-l mailing list
> MediaWiki-l(a)lists.wikimedia.org
> http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
I'll know soon enough, I guess :-), but thought I'd ask in case anyone
had further info; if I write an extension tag (say, 'mytag') that takes
no text, can I use it as <mytag/>, or do I need to say <mytag></mytag>?
Thanks,
Ken
I notice that search results being brought back include text within
infoboxes and other wiki markup that the user would not normally see within
the page.
Is there way to prevent this from being displayed in search results?
For example, a search for Florida brings back...
1. Classification, OED Office - Florida (1,230 bytes)
1: {{Test Info Box|name= Office Class - Florida Info Box
4: | CGTCoord=[[:Category:OED Coord, Florida| Tallahassee]]
5: | state=[[:Category:PTO Offices - Florida, United States|Florida]]
35: [[Florida State, XXXXX Xxxxxxx|Florida XXXXXX]] -
48: ...Florida IP Code - ]] [[Category: Florida-Code_IP]]
None of the code in the example above is something that a user would see,
other than the title on line 1.
Now, the fact that it matched on the page is fine but I would rather not
have the user have to wade through the 75 results seeing 5 meaningless lines
per listing.
I am keeping my fingers crossed that this is configuration.
Thank,
Paul
I would like to define two templates, one being a "start" template which
contains
<div style="bunch of stuff">
and the other containing just
</div>
However, the "</div>" is being escaped by the MW engine, so appears
verbatim in the page, rather than functioning as an HTML end tag.
Is there a way around this? I'm guessing the problem is that the MW
engine doesn't see matching start and end divs when it parses the
markup, and so decides that </div> should be interpreted literally
rather than as HTML.
Defining just a single template that wraps the tags around the content
is not an option; the stuff within the tags can be quite complex, and
our experience is that the standard markup is just too fragile to be
able to do that sort of thing.
We could of course just put literal divs into the pages, but that gets
messy, and also means we can't change the style in the future.
Many thanks for your suggestions,
Ken
Liebe Wikianer,
ich habe das Programmpaket V. 1.10. bei meinem Hoster geladen, kann aber
leider keine Installation starten. Wer kann mir entsprechende deutsche Hilfe
geben. Ich betreibe keinen Localhost, sondern alles über den Provider.
Ich freue mich auf eine Antwort.
Mit freundlichem Gruß aus Dresden
René
René Gränz
PF 280214
01142 Dresden
Funk: 0162/1 76 53 55
e-Mail: rgraenz(a)gmx.de
http://www.graenz.name
----------------------------------------
+++ Aktualisierte Daten per Mai 2007 +++
+++ www.ahnenliste.graenz.name +++ Neu +
----------------------------------------
+++ Sie helfen bei geneal. Projekten +++
+++ Neu +++ www.projekte.graenz.name +++
----------------------------------------
> Arthur wrote: I thought you had set it up
> already, why do you need more instructions?
Peter Blaise responds: Thanks for hanging in there, Arthur, and showing
ongoing interest.
For me, support is support. I have the service manuals for everything
in my life - my car, my tape recorders (reel-to-reel and cassette), my
turntable (hmm ... hi-fi buff here), my cameras, and so on. I tend to
red-pen them and add much to them because they're not perfect, nor are
they complete. But they're a start. I also join Internet groups of
like-minded owners who share our experiences and share our
documentation, FAQs, detail instructions on maintenance, repair,
customization, and so on. In other words, for me, support is support.
MediaWiki wise, I have the additional challenge of selling MediaWiki
(versus Peter Thoeny's TWiki, or about 60 other Wikis, versus CMS
Content Management Systems, versus Microsoft Share Point, and other
non-Wikis) to my "group". Open source is scary since there is seldom an
800 number or warranty that comes with the product (though us techies
know that 800 numbers and warranties with no one who is smart at the
other end is mere marketing chutzpah - but it makes the sale!).
MediaWiki is further compromised by depending on 3 or 4 *other* open
source products being "properly" installed and working, first. Having
reliable, dependable documentation of other people's success with
MediaWiki and the other supporting open source programs would go a long
way towards encouraging MediaWiki's success in my arena.
And, besides, just like the documentation I collect on my other high
tech stuff, it reduces the time-wasting, "reinventing the wheel"
syndrome for the next person. If we can stand on each other's
shoulders, I imagine each MediaWiki newbie will see a lot farther,
versus standing shoulder to shoulder, with each person reinventing how
to install and tune and troubleshoot each of the myriad components from
scratch on their way to their own MediaWiki ... or to one of the 60
others Wiki's out there.
Anyway, Arthur, as I mentioned, "no" (or no response) is an appropriate
answer to the question: "Any leads on a basic wiki setup-and-configure
instruction manual?" Offering to help me troubleshoot is very nice, and
will definitely help me create the reliable documentation I am after,
and I thank everyone who has contacted me on and off list. I'll send
you all a link on MediaWiki.org when I publish whatever works for me!
And, again, if anyone wants to update MediaWiki.org and document their
own successful install, please do so, since MediaWiki.org resources were
never complete, and what's there is also outdated.
My own target will be working on:
(a) "Why MediaWiki at all?" - features and benefits listings, how to
decide if MediaWiki can do what you want to do,
(b) "WAMPPM" - Windows, Apache, MySQL, PHP, PHPMyAdmin, MediaWiki, and
so on, with an emphasis on minimum footprint installation without
requiring administrative privileges!
I'm sure each of us has our own custom avenue of successful experience.
Sharing it on demand in response to inquiries here is very considerate
and helpful. I'm also asking for preemptive assistance by putting it up
on MediaWiki.org before someone asks or has a problem. What's the
phrase, "... an ounce of prevention is worth a pound of cure ..."?
-- Peter Blaise
Hello again,
I have found the Common.js page in our wiki and copied the content from
wikipedia into it. I also found the corresponding Common.css page and
copied that content into our wiki as well. I can now see the changes
made in Common.css. However, there appears to be no effect of java on
any pages and the WP:NavFrame feature mentioned
here:http://en.wikipedia.org/wiki/WP:NAVFRAME
<http://en.wikipedia.org/wiki/WP:NAVFRAME> still is not working
correctly.
Any suggestions?
John Getzke
Jgetzke(a)ptc.com
John,
Go to the page MediaWiki:Common.js on your wiki. If you have not edited
this page, it will be blank and you will have to add content to it. The
page is used to add features to every page on your wiki, in your case
the navFrame feature. Just create the page and it will work.
Mark