Hey Jeroen
I got it all sorted out. I think I figured out what I did. I was using
the instructions on
https://github.com/JeroenDeDauw/ExtensionInstaller/blob/master/README.md.
The default contents of the json file specifies nothing should be
installed, and looks as follows:
{
"require": {
"php": ">=5.3.2"
}
}
When actually the example json file contains:
{
"require": {
"php": ">=5.3.2"
},
"config": {
"vendor-dir": "../../vendor"
},
"extra": {
"installer-paths": {
"../../extensions/{$name}": ["type:mediawiki-extension"]
}
}
}
Then dumb me skipped the step, "Copy the example.json file" which
contained the paths for the installation of /vender and /extensions
because I focused on the statement, "The default contents of the json
file specifies nothing should be installed, and looks as follows:" and
nothing else. :)
So a quick question, on our production server, we don't use w/. Which
would mean, "vendor-dir": "../../vendor" should become "vendor-dir":
"../vendor" and the same for ../../extensions, loose the proceeding ../
And will this:
if ( is_readable( __DIR__ . '/../../vendor/autoload.php' ) ) {
include_once( __DIR__ . '/../../vendor/autoload.php' );
}
will have to be changed to
if ( is_readable( __DIR__ . '/../vendor/autoload.php' ) ) {
include_once( __DIR__ . '/../vendor/autoload.php' );
}
for ExtensionInstaller to work because we are only going up one
directory since w/ doesn't exist? Maybe serendipity was telling me to
throw everything into the /ExtensionInstaller directory because I'll
have to edit .htaccess to allow direct calls to /vender through.... Ugh!
Take care
Tom
I am out of the office until 02/13/2014.
Thank you for your email. I will be in training from 2/10/2014 to
2/13/2014, returning to the office 2/14/2014. Please contact
BT-MMS-MiddlewareEngineering for any emergencies.
Thank you,
Best Regards,
Robert L. Garritano | Discover Financial Services
MMS - Middleware Engineering
2500 Lake Cook Road, Riverwoods, IL 60015
( Office (224) 405-1621
RobertGarritano(a)discover.com
Note: This is an automated response to your message "Re: [MediaWiki-l]
subskin customizations" sent on 02/10/2014 12:22:08.
This is the only notification you will receive while this person is away.
Please consider the environment before printing this email.
Today I found out that a wiki I like (but I don't edit) had started
being spammed, from its WikiApiary page: the exponential growth of
registered users, but not of active users, was suspect; a look to
RecentChanges immediately confirmed that a couple days ago (one) captcha
on signup was probably won by the spambots.
For those who do MediaWiki consultancy or would like to start, I think
there is an opportunity. Few wiki sysadmins go ask help, but putting
together some select metrics you could create a page on WikiApiary
reporting the wikis whose parameters recently got unhealthy: then go
offer an audit and improvement of their antispam setup, before it gets
so spammed as to require disinfestation (cleanup) services.
Just an idea I throw to get it out my mind, ;-)
Nemo
Hi All
Don't know what I missed, but everything appeared to run right from the
command line. I was trying to install subpagelist v1.0. I installed
composer in the ExtensionInstaller v2.2 directory per directions. Ran
php composer.phar after I created the json file. Output threw everything
into the Extension Installer directory as follows. Which I don't think
is what was supposed to happen.
ExtensionInstaller/
-extensions/
---SubPageList/
---Validator/
-vendor/
Anyway, looking at -
if ( is_readable( __DIR__ . '../../vendor/autoload.php' ) ) {
include_once( __DIR__ . '../../vendor/autoload.php' );
}
So changing it to -
if ( is_readable( __DIR__ . '/vendor/autoload.php' ) ) {
include_once( __DIR__ . '/vendor/autoload.php' );
}
worked for me.
At far as I can tell it seems to work, Special:Version shows SubPageList
and Validator, and the extension SubPageList is working. Going back and
looking at v2.0, I see my change was the original autoload.php. ??? Are
the instructions correct, for 1.22 only, or is v2.0 for 1.21? Should
make a note of it on instructions.
Thanks
Tom
Tom
Hello, is it possible to modify Mediawiki so that when you do a #REDIRECT,
it sends an HTTP 301 or 302 redirect to the target page? Currently, it just
returns HTTP 200 (OK), along with a near duplicate of the target's HTML.
The HTML that it returns includes a rel="canonical" link to the target
page, but Google has been equivocal about whether this passes as much
PageRank as an HTTP redirect, so I'd like to know if an HTTP redirect to
the target page is an option.
Cheers,
Forest
Thanks to this list I know have my wiki integrated into the local network.
It all works except that it does not pull the email from AD.
This:
$wgLDAPPreferences = array('HPM' => array( 'email' => 'mail','realname' =>
'displayname'));
pulls the realname and populates the correct field, but the email field
remains stubbornly empty.
Is there another setting somewhere I need to enable and/or disable?\
I am trying to get the LDAPAuthentication extension working.
I have samba authenticating against my Windows PDC, so the basic setup works.
Now I need to get mediawiki to authenticate against the same PDC.
I have tried following several different guides:
http://www.pickysysadmin.ca/2013/05/13/how-to-configure-mediawiki-to-authen…http://www.mediawiki.org/wiki/Extension:LDAP_Authentication/AD_Configuratio…
and my logins always fail.
What's worse is that there's nothing pertaining to this in any log file
that I can find, so I have no idea what is failing.
Does anyone have AD authentication working?
My latest attempt:
require_once ("$IP/extensions/LdapAuthentication/LdapAuthentication.php");
$wgAuth = new LdapAuthenticationPlugin();
$wgLDAPDomainNames = array(
'HPM'
);
$wgLDAPServerNames = array(
'HPM' => 'xxx.hpm.yyy'
);
$wgLDAPSearchAttributes = array(
'HPM' => 'sAMAccountName'
);
$wgLDAPBaseDNs = array(
'HPM' => 'dc=hpm,dc=yyy'
);
$wgLDAPEncryptionType = array(
'HPM' => 'ssl'
);
$wgMinimalPasswordLength = 1;
Hello,
sometimes my wiki adds some additional chars at the end of a page when saving the page.
But this not happened every time only sometimes.
I think it start some time after update to latest version.
For example on one page the software add
t
眠
Software Version
MediaWiki 1.21.3
PHP 5.3.27 (cgi-fcgi)
MySQL 5.1.42-community
Any Ideas where this can come from?
Greetings
Thomas