I'll help to translate the documentation to german. Therefore I need cvs access to
[phpdoc-de].
I've been developing with php mainly on win32 for more than three years. Meanwhile I
have gained a level of knowledge which should permit this kind of work.
Christoph
--
PHP Development
[EMAIL PROTECTED] (Sascha Schumann) wrote:
And we should not close our eyes from the possibility of a
4.3.1 release (e.g. due to a security issue). In that
not-so-remote event, having a 4.3 branch with minimal changes
is a simple requirement.
With 4.3.0 you introduced lots of
[EMAIL PROTECTED] (Derick Rethans) wrote:
So why not release a bugfix 4.3.1 not because of a security hole but
just to complete the great work already done on PHP 4.3 - before
definitely jumping to PHP 5?
Who said that we're not going to release a 4.3.1 or 4.3.n? I'm just not
favoring new
/pi3web.
Edin
- Original Message -
From: Steph [EMAIL PROTECTED]
To: Christoph Grottolo [EMAIL PROTECTED]; Michael Sisolak
[EMAIL PROTECTED]
Cc: PHP DEV [EMAIL PROTECTED]
Sent: Tuesday, January 07, 2003 8:44 PM
Subject: Re: [PHP-DEV] What headers/libs does Win32 Snaps build use
Basically what I'm talking about is updating win32build.zip so that it
has all the current libraries that are really used to do a PHP build
on Win32. Is there a practical or licensing reason why that couldn't
be done? Would it be a lot more work than just packaging up a few
directories on
Hi
Jean Baptiste Favre wrote:
Jim Bierlein [EMAIL PROTECTED] a écrit dans le message de news:
[EMAIL PROTECTED]
My problem is that I cannot get Apache to properly load the mcrypt
module, I keep getting the warning message:
Unknown(): Unable to load dynamic library
Frank M. Kromann wrote:
Hi,
It was decided to move php_printer.dll, as well as other extensions
(iisfunc and ixsfunc) from the php repository to PECL. This was not
caused by instability. These extensions all work fine (AFAIK).
They were moved from php to PECL to reduce the size of PHP and
Hi
Andrei Zmievski wrote:
Everyone,
I have just released 4.3.0RC4. Despite the quote in my signature, I am
determined to keep this one the very last final RC of the interminable
4.3.0 development cycle. Towards that end, I will closely monitor the
CVS commits and revert any that do not
Hi
Marcus Börger wrote:
Hi,
i can no longer load mhash and domxml dll's under windows RC4.
marcus
I can load both of them with RC4 (tried with ISAPI).
Christoph
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
Hi
Andrei Zmievski wrote:
What was the consensus on CGI vs. CLI naming or merging issue? Or was
there a consensus at all? I full plan to go ahead with 4.3.0 release
before the end of the year, so those interested in doing anything
about this issue better get their butts in gear.
-Andrei
Derick Rethans wrote:
On Wed, 18 Dec 2002, Sebastian Nohn wrote:
But renaming php-cli to php means renaming php to anything else
(php-cgi, cgi-php, phpcgi, phpfoo, whatever), right?
No, we didn't do that for 4.2.[0-3] either:
[root@saturnus php-4.2.1]# ./configure --enable-cli
Please mention the name change at least in the NEWS file and maybe
php-cli could even output a readable error when beeing called as cgi.
that sounds like a nice idea, but how would you know?
Derick
Perhaps by the presence of CGI environment vars? Sorry I'm amateur.
Christoph
--
PHP
Please mention the name change at least in the NEWS file and
maybe php-cli
could even output a readable error when beeing called as cgi.
that sounds like a nice idea, but how would you know?
Derick
Maybe you can test the presence of CGI environment variables? I'm
amateur...
Christoph
Hi
evolution is not an excuse here. We want to use PHP on the
command line and many people will do also. And we make the
command line usage as easy as possible. Even if that requires
some mauals being updated and marking some bug reports as
bogus.
marcus
If you really want to easy shell
When installing a sapi for a web server i do it once and
every time i update it i look if i have to change something in the
setup - even file names. And before updating anything i test the
stuff on a non production system.
I hope (and I know) there's more evolution in php 4.3 than a
Marcus Börger wrote:
There was no cli and only cgi binary called php.exe.
Then we decided to have a command line executable (abbrevation CLI).
And the we decided to use 'php.exe' for the new CLI and to avoid
confusion we chose to rename the CGI binary from 'php.exe'. So now
there will be
Hi
In the NEWS file for 4.3.0 there should definitly be an entry about renaming
php.exe to php-cgi.exe on win32, maybe this should even be mentioned on the
download page together with the release. If not, there will be many bug
reports about HTTP 500 errors and premature end of script headers
Marcus Börger wrote:
I understand the reason why cli has to get a short name (the
lazyness of good programmers). What i don't understand is why it has
to be called php.exe. You force each and every user of php-cgi on
win32 to change his webserver configuration when switching to 4.3.0.
yes
If so ... maybe you can suggest something to me then?
What about setting server variables? You can set them once, they stay in
memory and your scripts can read them. Just an idea...
Christoph
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit:
Hi Dan
I've been trying out with the snapshots from snaps.php.net/win32 but I still
have the same errors. The actual snaps of 4.2 don't work either.
Christoph
I'm looking into these problems right now. Please be patient. A recent
slew of bug reports suggests that there might be some stuff
Jim Winstead [EMAIL PROTECTED] schrieb im Newsbeitrag
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
Marko Karppinen [EMAIL PROTECTED] wrote:
Even though no sane person can dispute the fact that the frantic
pace of PHP3 development warrants fresh snapshot of the venerable
scripting
| I tried to fopen(\\machine\shaer\file.txt,w)
|
| on w2k iis 5.0 PHP 4.1.0 and I got fopen invalid argument error. I know,
| that UNC filenames are supported since PHP 4.0.6. I tried variants with
| machine\\share\\file.txt, ... but the error was the same.
Please read the latest threads
ID: 14877
User updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Old Status: Feedback
Status: Open
Bug Type: FDF related
Operating System: XP Pro
PHP Version: 4.1.0
New Comment:
yes, fdf is enabled.
I found out that I can get HTTP_FDF_DATA in PHP when I append #FDF to
the
From: [EMAIL PROTECTED]
Operating system: XP Pro
PHP version: 4.1.0
PHP Bug Type: FDF related
Bug description: HTTP_FDF_DATA not available
The data from a PDF form doesn't arrive at the php script when submitted in
FDF format, however it works, when the same data is
[EMAIL PROTECTED] schrieb im Newsbeitrag
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
ID: 14563
User updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Bogus
Bug Type: *Configuration Issues
Operating System: Windows 2000 (Win2K)
PHP Version: 4.1.0
New Comment:
But it would be cool to be at least able to add comments to bug reports of
other users - like in the manual. Sometimes a non-dev member can reproduce a
bug, give a hint or even an answer. Now, a common user who wants to comment
a bug has to post to the dev list.
Christoph
Rasmus Lerdorf [EMAIL
For me it works since php-dev from july 4 2001 and also in 4.1.0. We had to
install the July 4 version on our production website to be able to access
UNC-style paths, now we could switch to 4.1.0.
We've made better experiences using //server instead of because there
has been a bug in the
Hi
Actually, a bug entry can only be modified by the one who submitted the bug
or by a developer with karma.
It would be handy, if common users could add comments to existing bug
reports. Otherwise they have to enter a new bug report if they want to
provide additional information to a bug which
28 matches
Mail list logo
