Now that the test suite is mostly working (I still need to fill in
some things like testing the Math functions), I'm emboldened to do
some code cleanup.
One of the first things I'd like to do is simplify the installation
and update procedures, for the same reason as having the test suite:
it will make it faster to make and test changes, and easier to
maintain the multiple installations.
Some questions first:
- Is there any reason to retain the Phase II conversion scripts?
Do there exist any Phase II installations anymore that might need
to be converted, or can I safely arcive those off somewhere?
- I'd like to have a nice separation between the source tree and
the installation set, with scripts for installs and updates and
maintenance. Should the maintenance scripts be "installed"
somewhere as well, or should they be run from the source tree?
I'm inclined toward the latter, so that dangerous functions don't
get accidentally exposed as web pages, but perhaps they should be?
- Brion, are there any temporary measures you have taken on the
existing wikis in which some configuration option is not isolated
in LocalSettings.php? I'd like to arrange it so that we'll be
able to grab the latest source from CVS, and just run an update
script on any of the wikis which will look in the target
directory's LocalSettings for everything it needs and update all
the rest of the code properly. If there are other changes that
might complicate that, let me know and I'll put them into
LocalSettings.
--
Lee Daniel Crocker <lee(a)piclab.com> <http://www.piclab.com/lee/>
"All inventions or works of authorship original to me, herein and past,
are placed irrevocably in the public domain, and may be used or modified
for any purpose, without permission, attribution, or notification."--LDC
Hi!
Windows me, Xitami, PHP 4.3.1, wikipedia scripts: source forge dump 29.03
Trying to find out why the submit does not return correctly, I stumbled on
the cgi error log file of Xitami.
I have no idea if there is a relation with the issue, but there are quite a
number of disturbing warnings (they appear in case of opening a page and
modifying it).
This can be because of Xitami, or a wrong php version, or Windows, or
because it is running locally, or of installation errors...
However, if this can explain my submit pb, let me know.
Michel Mouly
PHP Notice: Undefined index: HTTP_ACCEPT_CHARSET in OutputPage.php on
line 388
PHP Warning: date() [<a
href='http://www.php.net/function.date'>function.date</a>]: Unexpected
error in DatabaseFunctions.php on line 117
PHP Warning: Cannot modify header information - headers already sent in
OutputPage.php on line 315
PHP Warning: Cannot modify header information - headers already sent in
OutputPage.php on line 316
PHP Warning: Cannot modify header information - headers already sent in
OutputPage.php on line 322
PHP Warning: Cannot modify header information - headers already sent in
OutputPage.php on line 324
PHP Warning: Cannot modify header information - headers already sent in
OutputPage.php on line 325
PHP Notice: Undefined index: HTTP_X_FORWARDED_FOR in OutputPage.php on
line 460
PHP Notice: Undefined index: HTTP_CLIENT_IP in OutputPage.php on line 462
PHP Notice: Undefined index: HTTP_FROM in OutputPage.php on line 464
PHP Notice: Undefined index: REQUEST_URI in OutputPage.php on line 470
PHP Warning: Cannot modify header information - headers already sent in
OutputPage.php on line 318
PHP Warning: Cannot modify header information - headers already sent in
OutputPage.php on line 319
PHP Warning: Cannot modify header information - headers already sent in
OutputPage.php on line 320
PHP Warning: Cannot modify header information - headers already sent in
OutputPage.php on line 322
PHP Warning: Cannot modify header information - headers already sent in
OutputPage.php on line 324
PHP Warning: Cannot modify header information - headers already sent in
OutputPage.php on line 325
>Hi!
>
>Did anybody ever tried to port texvc on Windows??
>
>I did not, but trying to emulate it, I found no way to handle correctly the
>character + in a command line
>argument. This is quite annoying for math formulae!
>
>My emulation is via a php script. The problem could be because of DOS or of
>php. I tried to get some help on the windows-php forum, and the answers I
>got are not conclusive: it could then be a DOS issue, in which case the
>present approach for the interface between outputpage.php and texvc will be
>difficult to port on Windows...
I doubt it's a DOS problem -- some DOS commands require passing of + on the
command line (attrib and copy for example). Try typing "echo +" if you don't
believe me.
>In addition, the php function escapeshellarg does not seem to be adapted to
>Windows, either.
>
>My original approach, using a file as interface, has not such problem.
It might be a PHP bug. I couldn't find any mention of it in
http://www.php.net/manual/en/features.commandline.php . You might have to
just think of a workaround. Maybe you can try using W32api to call
GetCommandLineA, if you're brave.
-- Tim Starling.
_________________________________________________________________
MSN Instant Messenger now available on Australian mobile phones. Go to
http://ninemsn.com.au/mobilecentral/hotmail_messenger.asp
I've installed the latest security fix packages for sendmail, yet again.
Any thoughts on switching to postfix or such?
-- brion vibber (brion @ pobox.com)
Hi!
Did anybody ever tried to port texvc on Windows??
I did not, but trying to emulate it, I found no way to handle correctly the
character + in a command line
argument. This is quite annoying for math formulae!
My emulation is via a php script. The problem could be because of DOS or of
php. I tried to get some help on the windows-php forum, and the answers I
got are not conclusive: it could then be a DOS issue, in which case the
present approach for the interface between outputpage.php and texvc will be
difficult to port on Windows...
In addition, the php function escapeshellarg does not seem to be adapted to
Windows, either.
My original approach, using a file as interface, has not such problem.
Michel Mouly
Hi there,
this is Urbanus, one of the new sysops of the German Wikipedia. At
the moment the Wikipedia is extremely slow again. Can anyone of the
server people have a look if the load is high or if there is Google
indexing the Pedia?
Thanks & smiles
Thomas aka Urbanus
Okay, how about now? Any comments would be appreciated.
Original: http:///www.twoevils.org/files/wiki/Rabbit.html
Minimal: http:///www.twoevils.org/files/wiki/Rabbit-minimal.html
Note that I think the footer (on all the pages) should be changed from
'It was last modified...' to '(Article title) was last modified...'; but
that isn't part of my skin. :)
--
Nick Reinking -- eschewing obfuscation since 1981 -- Minneapolis, MN
So, if the masses finally decide that we "need" SSL, who's paying for
the security certificate? Or would we have to plan to run without a
properly signed cert?
Of course, the certifiacte would have to be "owned" by someone. Who's
name is going to be on the certificate? Bomis'? That wouldn't make
sense, since we'd have to get a new one when the non-profit is set up.
Whether SSL is a good idea in this situation isn't the issue. Setting
it up properly involves getting some other things done first. IMHO,
Moving forward on SSL at this point would be slightly premature.
Jason
Tomasz Wegrzanowski wrote:
> On Mon, Mar 31, 2003 at 01:38:19PM -0600, Lee Daniel Crocker wrote:
> > > (Tim Starling <ts4294967296(a)hotmail.com>):
> > >
> > > If we really want to be serious about security we'll have to use
> > > ssl for login, but I don't know how to do that.
> >
> > That's entirely too paranoid. Frankly, I don't see much need
> > for high security of Wikipedia logins. It's not like we're
> > storing medical records. (Oh my God! My neighbor might find
> > out that I like the "Nostalgia" skin!) The only real risk is
> > that someone might log in as me and make edits in my name, but
> > then I'd just disavow them and change my password.
>
> We should make it an option to login via SSL at least for sysops.
> It's pretty dangerous to send sysop passwords unencrypted.
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)wikipedia.org
> http://www.wikipedia.org/mailman/listinfo/wikitech-l
--
"Jason C. Richey" <jasonr(a)bomis.com>
>Si.
>And remember, on the first of january 2003, someone
>took over three sysops accounts on the french wiki,
>and indicated our passwords in clear to the three of
>us.
>So...well...security...hum
If we really want to be serious about security we'll have to use ssl for
login, but I don't know how to do that.
-- Tim Starling
_________________________________________________________________
MSN Instant Messenger now available on Australian mobile phones. Go to
http://ninemsn.com.au/mobilecentral/hotmail_messenger.asp