At 14:41 05/11/2014, John wrote:
>Content-Transfer-Encoding: base64
John,
Thank you for the response. But I have scores of files to maintain
through synchronizing scripts. I cannot manage them through uploads.
Moreover that some are on the same computer at another place. I
suppose I have to go through the nightmare you announce ... Where the
solution could be detailed ?
Let me phrase it in the most simple way.
1. I have a file under /jefsey/graphs/xxxx.jpg.
2. I have a wiki under /home/name/www with its /home/name/www/images directory.
How can I make [[File:xxxx.jpg]] display the file?
Or another command do it?
Or may be is there a list more appropriate to ask for such a solution?
Deep thanks.
jfc
>You are asking for a headache, My suggestion is to enable file uploads but
>restrict it to a special user group and have yourself as they only member
>
>On Wed, Nov 5, 2014 at 8:26 AM, JFC Morfin <jefsey(a)jefsey.com> wrote:
>
>H[ieved that if I installed a xxxx.jpg file in the /images directory it
> > would be accessible through the [[File:xxxx.jpg]]. It does seem to be the
>Ø\Ù@£â'fRæ÷BVæled uploading. Which parameter should I aad in
>ØØ[Ù]tings.php for [[File:xxxx.jpg]] to work?
>Y\[ÜËÂ jfc
>×××××××××××××××××××××××××××××××××××××××××××××À_
>YYXUÚZÚK[XZ[[È\ÝFòVç7V'67&&RÂvòFó
>£âttps://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>
>_______________________________________________
>MediaWiki-l mailing list
>To unsubscribe, go to:
>https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
You are asking for a headache, My suggestion is to enable file uploads but
restrict it to a special user group and have yourself as they only member
On Wed, Nov 5, 2014 at 8:26 AM, JFC Morfin <jefsey(a)jefsey.com> wrote:
> I believed that if I installed a xxxx.jpg file in the /images directory it
> would be accessible through the [[File:xxxx.jpg]]. It does seem to be the
> case?
> I have not enabled uploading. Which parameter should I aad in
> LocalSettings.php for [[File:xxxx.jpg]] to work?
> Deep thanks/
> jfc
>
>
> _______________________________________________
> MediaWiki-l mailing list
> To unsubscribe, go to:
> https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>
Greetings!
I'm working on a test installation of MediaWiki 1.23.6-0 for OS X (Yosemite), based on an install package I downloaded from Bitnami.
I have 2 questions regarding my installation:
1. Why can't I edit my own MediaWiki: and Special: namespace pages using my login ID? I'm using my original login that has the bureaucrat role.
2. How do I get a larger font size for the edit box when I edit a page? I have tried to change my CSS, but I suspect that I'm not using the correct selector.
Regards,
Joe Malin
----
Joe Malin
Senior Technical Writer
EXO U, Inc.
Palo Alto, CA, USA
jmalin(a)exou.com
Hi everybody,
here's something I don't understand.
I've just updated my mediawiki-installation to the current version 1.23.5 -
which I thought was up to date, and now I'm running up against one error-message
after the other with deprecated functions like this one:
Deprecated: preg_replace(): The /e modifier is deprecated, use
preg_replace_callback instead in
/opt/lampp/htdocs/_fhbwiki/includes/GlobalFunctions.php on line 1271
And also this:
Strict Standards: Non-static method Mail::factory() should not be called
statically in /opt/lampp/htdocs/_fhbwiki/includes/UserMailer.php on line 154
or this:
Strict Standards: Non-static method PEAR::isError() should not be called
statically, assuming $this from incompatible context in
/opt/lampp/lib/php/Net/SMTP.php on line 450
Now, I'd understand if these would happen in modules where I had made any kind
of adaptation, but I pretty sure I never touched any of these files. So why
aren't they just updated to the correct and working version???
Or did I do something wrong while updating? Is there a way to check?
Kate
Hello everybody,
I've just updated my wiki from version 1.16.2 to version 1.23.5 and updated the
extension Renamuser to the current version. But when I try to open the
rename-user-page in my wiki I get the following error-message:
Fatal error: Call to undefined method SpecialRenameuser::getOutput() in
/opt/lampp/htdocs/_fhbwiki/extensions/Renameuser/specials/SpecialRenameuser.php
on line 24
When looking at the file mentioned in the error-message I noticed that there is
indeed no such function as getOutput in this file. With the help of grep I
ensured that there is no such function in the whole
/opt/lampp/htdocs/_fhbwiki/extensions/Renameuser-directory
I even went so far as to have grep look in my whole wiki-directory:
wiki-t00:/opt/lampp/htdocs/_fhbwiki # grep -i -r 'getoutput' * > getoutput.txt
Here is the result of that grep:
extensions/Renameuser/specials/SpecialRenameuser.php: $out = $this->getOutput();
extensions/Renameuser/Renameuser.hooks.php: $out =
$article->getContext()->getOutput();
extensions/Renameuser/getoutput.txt:Renameuser.hooks.php: $out =
$article->getContext()->getOutput();
extensions/Renameuser/getoutput.txt:specials/SpecialRenameuser.php: $out =
$this->getOutput();
includes/Article.php: $this->mParserOutput = $this->getOutputFromWikitext(
$text, $cache, $parserOptions );
includes/Article.php: public function getOutputFromWikitext( $text, $cache =
true, $parserOptions = false ) {
includes/Article.php: return $this->getOutputFromWikitext( $rev->getText(),
$useParserCache );
includes/OutputPage.php: foreach ( $parserOutput->getOutputHooks() as
$hookInfo ) {
includes/Profiler.php: return $wgProfiler->getOutput( $start, $elapsed );
includes/Profiler.php: function getOutput() {
includes/parser/Parser.php: function getOutput() { return $this->mOutput; }
includes/parser/ParserOutput.php: function getOutputHooks() { return
(array)$this->mOutputHooks; }
includes/parser/LinkHolderArray.php: $output = $this->parent->getOutput();
includes/parser/LinkHolderArray.php: $output = $this->parent->getOutput();
includes/ProfilerSimpleTrace.php: function getOutput() {
Now I'm wondering whether one of those getOutput-functions is the one the
Renameuser-extension is supposed to use and why that isn't working properly? The
reason I wondering that at all is that a similar "Fatal error: Call to undefined
method"-error-message occured when I tried to update another extension before.
But since it turned out that the older/previous version was working fine I
didn't follow up on the update and the error any further...
I'm a rather PHP-noob so I cannot really follow up all the
programming-intricaies indepth. :-( I hope someone can help me or at least point
me in the right direction.
Kate
Dear all -
As most of you will know, Drupal has recently announced a critical vulnerability and automated MySQL injection attacks in the wild have compromised servers(1). Our sysadmins are wiping affected machines, in order to reinstall data from pre Oct. 15 backups. We users need to figure out how to handle the data loss from Oct. 15 to current.
If I understand the Drupal advisory correctly, backdoors could have been installed in the database. I don't know nearly enough about this, but I suspect this could mean that a backdoor could reappear on the new machine if I were to dump my current Wiki tables from the old machine and reinstall them on the new machine. Is this correct? And if so, what would the best strategy be for recovery? I hope this can be done more efficiently than copy/pasting Wikitext.
Any insight much appreciated.
Cheers,
Boris
(1) https://www.drupal.org/PSA-2014-003