Bug #15242 Updated: PHP functions as extensions for libxslt
ID: 15242
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Closed
+Status: Open
Bug Type: Feature/Change Request
-Operating System:
+Operating System: Any
PHP Version: 4.1.1
New Comment:
Current version of DOM XML module, available in CVS only have support
for EXSLT, now available into libxslt. But this feature request means
adding possibility for PHP developers to define their own extension
functions/extension elements for XSLT, written directly in PHP.
According to libxslt documentation
(http://xmlsoft.org/XSLT/extensions.html) DOM XML module in PHP should
have a kind of converter between PHP functions and extension functions
for libxslt. From a PHP's point of view it should look like this:
PHP:
?php
// Creating new stylesheet
$xsl = new XsltStylesheet();
$xsl-register_ns('ext','http://www.my-extensions.com/');
// Register custom extension function
// At enter we give name of it, which will be used in XSLT
// and name of actual PHP function
$xsl-register_extension_function('ext:my_func','myExtension');
function myExtension(p1,p2,p3)
{
return(p1+p2+p3);
};
?
XSLT:
=
.
xsl:value-of select=ext:my_func(2,3,4)/
.
Previous Comments:
[2002-01-28 21:25:32] [EMAIL PROTECTED]
I don't use it (yet), but it's in PHP now.
[2002-01-27 07:36:22] [EMAIL PROTECTED]
Since DOM XML extension now have a code to work with libxslt (at least
version of DOM XML extension, available in CVS) and libxslt have an
ability to create extensions for XSLT it will be absolutely great to
allow writing extensions on PHP.
Is there any plans to implement this functionality? Because sometimes
it is very important.
--
Edit this bug report at http://bugs.php.net/?id=15242edit=1
Bug #15669: Shrinker error - Dispatcher initialisation error 6
From: [EMAIL PROTECTED] Operating system: win98 PHP version: 4.1.1 PHP Bug Type: *Configuration Issues Bug description: Shrinker error - Dispatcher initialisation error 6 downladed and unpacked php-4.1.1-Win32 and php-4.1.1-installer apps from PHP site. Installed using automatic method and checked entries under manual method in registry. Obtained MDAC latest version 2.7 and MDAC checker programfrom microsoft for PWS ran same and brought up to date on PWS standard install APP from New win98 2nd ed CD. (registered ver). Tried command line PHP -i and obtained output file. stored local. viewed in HTML browser as htm file. All seems OK wrote first php file. As example and tried in browser. Result CGI Error The specified CGI application misbehaved by not returning a complete set of HTTP headers. The headers it did return are: rest of page blank. simplehello world example. downloaded and tried to run iiscfg.exe after studying PHP site. This fails on Shrinker error - Dispatcher initialisation error 6 Checked around and found others were having same problem. my php.ini is disturbingly sparse, so I looked at the browscap config file which lists most browsers. there seems to be no entries for IE6.0 so I guess the install script didn't complete as it should have. All logs available for the asking. Any ideas guys(gals). PS you don't have installation issues as a type of bug on this page. http://bugs.php.net/report.php PPS keep up the good work. Hope to let you have some plug ins for this presently. Would fix it myself but I don't have the structure worked out yet. Or C++ compiler yet. :( -- Edit bug report at http://bugs.php.net/?id=15669edit=1 -- Fixed in CVS:http://bugs.php.net/fix.php?id=15669r=fixedcvs Fixed in release:http://bugs.php.net/fix.php?id=15669r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=15669r=needtrace Try newer version: http://bugs.php.net/fix.php?id=15669r=oldversion Not developer issue: http://bugs.php.net/fix.php?id=15669r=support Expected behavior: http://bugs.php.net/fix.php?id=15669r=notwrong Not enough info: http://bugs.php.net/fix.php?id=15669r=notenoughinfo Submitted twice: http://bugs.php.net/fix.php?id=15669r=submittedtwice
Bug #15242 Updated: PHP functions as extensions for libxslt
ID: 15242
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Analyzed
Bug Type: Feature/Change Request
Operating System: Any
PHP Version: 4.1.1
New Comment:
Extensibility is a part os XSLT specification, so i don't see any
evilness of this functionality. Yes, it will force some particular XSLT
templates to be used only together with PHP, but there is a reason of
doing it - speed. You know, XSLT is not a fastest language on the earth
:) And, moreover, there is available some small tasks, when one simple
function on PHP can solve a problem, much easier, then a bundle on XSLT
code.
I already have some stylesheets, which are executed in 10-15 seconds,
while only one small PHP function will reduce their execution time to
1-2 sec. And more extensive usage of XSLT will grow such situations...
Previous Comments:
[2002-02-22 04:17:10] [EMAIL PROTECTED]
I'm not sure, if this makes sense. You loose the whole interoperability
idea of xslt (your stylesheets will only run on PHP) and you will mix
again design and logic (ok, xslt allows you to do that already now..).
I do see, that it could be quite handy from time to time and maybe i
will implement it (some kind of evil eval...), but it's absolutely not
on top of my priority list.
[2002-02-22 03:39:44] [EMAIL PROTECTED]
Current version of DOM XML module, available in CVS only have support
for EXSLT, now available into libxslt. But this feature request means
adding possibility for PHP developers to define their own extension
functions/extension elements for XSLT, written directly in PHP.
According to libxslt documentation
(http://xmlsoft.org/XSLT/extensions.html) DOM XML module in PHP should
have a kind of converter between PHP functions and extension functions
for libxslt. From a PHP's point of view it should look like this:
PHP:
?php
// Creating new stylesheet
$xsl = new XsltStylesheet();
$xsl-register_ns('ext','http://www.my-extensions.com/');
// Register custom extension function
// At enter we give name of it, which will be used in XSLT
// and name of actual PHP function
$xsl-register_extension_function('ext:my_func','myExtension');
function myExtension(p1,p2,p3)
{
return(p1+p2+p3);
};
?
XSLT:
=
.
xsl:value-of select=ext:my_func(2,3,4)/
.
[2002-01-28 21:25:32] [EMAIL PROTECTED]
I don't use it (yet), but it's in PHP now.
[2002-01-27 07:36:22] [EMAIL PROTECTED]
Since DOM XML extension now have a code to work with libxslt (at least
version of DOM XML extension, available in CVS) and libxslt have an
ability to create extensions for XSLT it will be absolutely great to
allow writing extensions on PHP.
Is there any plans to implement this functionality? Because sometimes
it is very important.
--
Edit this bug report at http://bugs.php.net/?id=15242edit=1
Bug #15670: printing problem w/ Netscape 4.x when ob is enabled using gz_handler
From: [EMAIL PROTECTED] Operating system: Linux PHP version: 4.1.1 PHP Bug Type: Output Control Bug description: printing problem w/ Netscape 4.x when ob is enabled using gz_handler This is not a critical Bug... In Fact, it's probably a Netscape Bug rather than a php- bug... Symptoms: Netscape 4.x on Win98 (Possibly Win95/00 as well) won't display html-source or print Page Occurs: -when output-buffering is enabled - ob_start(gz_handler) Does not occur: -on any other Browser/System tested (IE, Opera, MacOSX) -when gz_handler is not specified as callback Example: not available, since problem was fixed by disabling ob for affected browsers on our production server. My Configure line: './configure' '--with-apache=../apache_1.3.22' '--with- mysql' '--with-pgsql=/usr/local/pgsql' '--with-t1lib' '-- with-tiff-dir=../tiff-v3.5.6-beta' '-with-ttf=/usr' '-- enable-inline-optimization--enable-shared-pdflib' '--with- swf=/usr/local' '--enable-ftp' '--with-openssl' '--disable- short-tags' '--with-pspell' '--enable-gd-native-tt' '-- enable-gd-imgstrttf' '--with-freetype-dir=/usr/local/ include/freetype2' '--with-zlib-dir=/usr/local' '--with-gd' '--with-jpeg-dir=../jpeg-6b' '--with-png-dir=../libpng- 1.2.0' '--with-oci8=/opt/oracle' '--enable-sigchild' -- Edit bug report at http://bugs.php.net/?id=15670edit=1 -- Fixed in CVS:http://bugs.php.net/fix.php?id=15670r=fixedcvs Fixed in release:http://bugs.php.net/fix.php?id=15670r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=15670r=needtrace Try newer version: http://bugs.php.net/fix.php?id=15670r=oldversion Not developer issue: http://bugs.php.net/fix.php?id=15670r=support Expected behavior: http://bugs.php.net/fix.php?id=15670r=notwrong Not enough info: http://bugs.php.net/fix.php?id=15670r=notenoughinfo Submitted twice: http://bugs.php.net/fix.php?id=15670r=submittedtwice
Bug #14391 Updated: gmmktime, gmdate work incorrect
ID: 14391 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: No Feedback Bug Type: Date/time related Operating System: Windows 2000 Server PHP Version: 4.0.6 New Comment: Hi, This bug is still here, and still causing grief. Sadly, it's been marked No Feedback now. Will someone please sort this? I can't imagine it's a particularly complicated thing to fix, since it seems to be okay on some platforms. Max Previous Comments: [2002-02-19 15:40:37] [EMAIL PROTECTED] Any updates on this bug as it appears to still be in 4.1.1 [2002-02-14 00:00:03] [EMAIL PROTECTED] No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to Open. [2002-01-27 18:40:15] [EMAIL PROTECTED] i have two systems a)redhat 7.0 and b) win2000. both have PHP Version 4.1.1 each has exactly the same code. any calls to gmmktime on linux are fine, but win2000 is not, which is unfortunate due to the fact that it's a calendar application. any idea when this will be cleared up? [2002-01-20 10:54:51] [EMAIL PROTECTED] Here's an example: first of all, to show that the system understands what's going on: $ date +%c %Z Tue Dec 18 22:51:16 2001 GMT $ date -u +%c %Z Tue Dec 18 22:51:21 2001 GMT - same result. so the machine knows what tz it's in. Now, I'm in GMT at the moment, so echo date(H:i,mktime(22,20,00,12,18,01)).p; //gives 22.20 echo gmdate(H:i,mktime(22,20,00,12,18,01)).p; // gives 22.20 as expected. but... echo date(H:i,gmmktime(22,20,00,12,18,01)).p; //gives 21.20 echo gmdate(H:i,gmmktime(22,20,00,12,18,01)).p; // gives 21.20 These should also give 22.20, so it looks to me that gmmktime() is screwed. Max [2002-01-20 10:41:42] [EMAIL PROTECTED] I've got this problem on 4.0.5 on solaris, could someone confirm this for me? SunOS mimosa 5.7 Generic_106541-14 sun4u sparc SUNW,Ultra-4 Max The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/14391 -- Edit this bug report at http://bugs.php.net/?id=14391edit=1
Bug #14391 Updated: gmmktime, gmdate work incorrect
ID: 14391 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: No Feedback Bug Type: Date/time related Operating System: Windows 2000 Server PHP Version: 4.0.6 New Comment: I setuped php4.1.1 on my Win2K, and now there is no problem with Z parameter in gmdate() function, but timestamp returned by gmmktime in winter time is still wrong. Will be this bug fixed? Previous Comments: [2002-02-22 05:16:06] [EMAIL PROTECTED] Hi, This bug is still here, and still causing grief. Sadly, it's been marked No Feedback now. Will someone please sort this? I can't imagine it's a particularly complicated thing to fix, since it seems to be okay on some platforms. Max [2002-02-19 15:40:37] [EMAIL PROTECTED] Any updates on this bug as it appears to still be in 4.1.1 [2002-02-14 00:00:03] [EMAIL PROTECTED] No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to Open. [2002-01-27 18:40:15] [EMAIL PROTECTED] i have two systems a)redhat 7.0 and b) win2000. both have PHP Version 4.1.1 each has exactly the same code. any calls to gmmktime on linux are fine, but win2000 is not, which is unfortunate due to the fact that it's a calendar application. any idea when this will be cleared up? [2002-01-20 10:54:51] [EMAIL PROTECTED] Here's an example: first of all, to show that the system understands what's going on: $ date +%c %Z Tue Dec 18 22:51:16 2001 GMT $ date -u +%c %Z Tue Dec 18 22:51:21 2001 GMT - same result. so the machine knows what tz it's in. Now, I'm in GMT at the moment, so echo date(H:i,mktime(22,20,00,12,18,01)).p; //gives 22.20 echo gmdate(H:i,mktime(22,20,00,12,18,01)).p; // gives 22.20 as expected. but... echo date(H:i,gmmktime(22,20,00,12,18,01)).p; //gives 21.20 echo gmdate(H:i,gmmktime(22,20,00,12,18,01)).p; // gives 21.20 These should also give 22.20, so it looks to me that gmmktime() is screwed. Max The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/14391 -- Edit this bug report at http://bugs.php.net/?id=14391edit=1
Bug #15671 Updated: Documentation error in pdf_setcolor
ID: 15671 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Open +Status: Closed Bug Type:Documentation problem PHP Version: 4.1.1 New Comment: This bug has been fixed in CVS. Previous Comments: [2002-02-22 05:12:45] [EMAIL PROTECTED] In the second code-example, the call should read pdf_setcolor($pdf, both, cmyk, 0, 0, 0, 1); (was also stated in the comments on this page) -- Edit this bug report at http://bugs.php.net/?id=15671edit=1
Bug #15651 Updated: Output is broken
ID: 15651 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Open +Status: Feedback Bug Type: *General Issues Operating System: Win2K-Server / UNIX PHP Version: 4.1.1 New Comment: Could you set up linux/freebsd box to reproduce this bug? And generate backtrace. (Or get exit code with gdb) You can write error_log(__FILE__.'(.'__LINE__.')') to locate to find ofending function/line also. Previous Comments: [2002-02-21 21:27:48] [EMAIL PROTECTED] Sorry. I wanted to say ... My site is complex enough... [2002-02-21 21:25:45] [EMAIL PROTECTED] I tryed to make some small scripts before, but there were no problems with them. My site is complete enough, there is a lot of includes (but execution time for homepage on my PC is less than 1 sec.). It looks like there are no problems for simply scripts, but I'll try again to make something ... By that time, if you like you may watch the results on different servers: 1) php4.0.6: http://www.sec4.wfdns.com/www.freetakeout.com/ 2) php4.1.1: http://vh110014.radntech.ca/fto/ - you may try to click some links there (log-in to your account, for example) to see the difference in cutting point. [2002-02-21 20:26:05] [EMAIL PROTECTED] If you can create _short_ _complete_ script that reproduces the problem. We can fix it :) [2002-02-21 18:37:26] [EMAIL PROTECTED] Unfortunately, my home OS is Win2K-Server, and I myself don't have VC++ to try to build PHP from sources... Can I provide any useful information for you, using my OS software which I already have? I have both IIS and Apache web servers. [2002-02-21 06:04:33] [EMAIL PROTECTED] Then you are having crash bug(s). First grab snapshot http://snaps.php.net and check if you still have the problem. (Make sure you build with --enable-debug) If you still have problems, check your httpd error logs. If you see segfaults, send a backtrace. The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/15651 -- Edit this bug report at http://bugs.php.net/?id=15651edit=1
Bug #15607 Updated: Apache Crash
ID: 15607
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Feedback
+Status: Closed
Bug Type: *Spelling functions
Operating System: Solaris 5.7
PHP Version: 4.1.1
New Comment:
Thanks for you report. I've added function entry terminator.
If you still have problem(s), let us know.
Previous Comments:
[2002-02-21 20:08:10] [EMAIL PROTECTED]
I believe I have found the bug. I'm no PHP coder, but I believe that a
{NULL, NULL, NULL} is required at the end of pspell_functions. The
backtrace *I saw* on a similar system (Solaris 8) indicates a segfault
in strlen() as called from zend_register_functions. The auto variable
ptr in that function was pointing one element past the end of the
pspell_functions array, and ptr-name was a bogus (but non-null)
pointer.
Seems likely that this lack of termination of the array works on most
platforms, by random chance of having NULLs there when PHP starts up.
But certain compiler/linker/config combinations put something other
than NULL there, and zend_register_functions runs amok all over the
process space.
Adding the terminator allowed Apache to start, and phpinfo() renders
correctly. Still waiting on more in-depth testing.
[2002-02-19 04:20:44] [EMAIL PROTECTED]
To properly diagnose this bug, we need a backtrace to see what is
happening behind the scenes. To find out how to generate a backtrace,
please read http://bugs.php.net/bugs-generating-backtrace.php
Once you have generated a backtrace, please submit it to this bug
report and change the status back to Open.
Yes, there are bugs. That's why I got a CVS account :)
BTW, could you try snapshot also?
http://snaps.php.net/
[2002-02-18 16:32:29] [EMAIL PROTECTED]
I'm Sys Admin of El Sitio (www.elsitio.com). I developed de Web Mail of
the Site (freemail.elsitio.com).
The Web Mail frontend run on Sun Netra t1 with Solaris 7 (patched 7
recommended). I use gnu gcc and ld (/usr/ccs/bin/ld).
I compile pspell and aspell with CC=gcc and CXX=g++.
My php include oci8 (Oracle 8.1.6), imap (imap-2001a), pspell
(pspell-.12.2) and aspell (aspell-.33.7).
PHP 4.0.5 works, but imap_mime_header_decode isn´t work, httpd crash.
PHP 4.0.6 works fine.
PHP is 4.1.0 and 4.1.1 segmentation fault when httpd start.
I was testing on Apache 1.3.19 and Apache 1.3.23.
When I compile, I don't get any error.
PHP is buggy buggy buggy :)
thanks and good luck!
--
Edit this bug report at http://bugs.php.net/?id=15607edit=1
Bug #15673 Updated: Quotes crash MySQL queries: $array['val'] = Parse Error, but $array[val] works
ID: 15673
Updated by: [EMAIL PROTECTED]
-Summary: Quotes crash MySQL queries: $array['val'] = Parse
Error, but $array[val] works
Reported By: [EMAIL PROTECTED]
-Status: Open
+Status: Feedback
Bug Type: Arrays related
Operating System: Linux 2.4.5
PHP Version: 4.1.1
New Comment:
Sounds very strange. Can you do a var_dump() on the sql string?
Can you also test and report back if it works with
SELECT * from {$table['users']}
?
Previous Comments:
[2002-02-22 06:45:23] [EMAIL PROTECTED]
Here is the code:
error_reporting(E_ALL);
$table = array('admin'= 'md_adm'
,'users'= 'usuarios'
,'tables' = 'md_tables'
,'product' = 'md_prods'
);
if(!connect_mydb()) die(unable to connect or select db);
if(isset($table['users'])) { // = works OK
echo $table[users] will warn me!br; // = warning
echo $table['users']; // = no warning
}
$query = SELECT * from $table['users'];
$result = mysql_query($query); // = PARSE ERROR!!
//But if I delete the '' in $query it works ok:
$query = SELECT * from $table[users];
$result = mysql_query($query); // = Query done!!
According to PHP Manual in Arrays : Why is $foo[bar] wrong? the
syntax $foo[bar] is deprecated despite working.
João Paulo M. Fischer
--
Edit this bug report at http://bugs.php.net/?id=15673edit=1
Bug #14457 Updated: Pspell ceases to work on upgrade from 4.0.6 to 4.1.0
ID: 14457 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Open +Status: Closed Bug Type: Pspell related Operating System: Linux 2.4.7 (RH7.2) PHP Version: 4.1.0 New Comment: This bug has been fixed in CVS. I suppose this is fixed in CVS. Please reopen if you still have problem with CVS version. Previous Comments: [2002-01-15 16:24:25] [EMAIL PROTECTED] pspell with php-4.1.1 causes apache-1.3.22ssl to core dump when starting apache. Same pspell using same configure options with php-4.0.6 works ok. [2002-01-04 15:09:56] [EMAIL PROTECTED] I did specify the /usr/local/pspell location in pspell's installation to see if it made any difference for 4.1.0 but it didn't. Things continued working in 4.0.6. I didn't save the procedure on installing pspell, I'm pretty sure the only parameter I passed was ./configure --prefix=/usr/local/pspell and then made the modules. I will write back when I attempt to upgrade to 4.1.0 again. I don't know whether Aspell/Pspell merge did anything. [2001-12-28 21:52:28] [EMAIL PROTECTED] ... well, in the original bug report you had: '--with-pspell=/usr/local/share' and in the new one you have '--with-pspell=/usr/local/pspell' That's very different I hope that you configured pspell with '--prefix=/usr/local/pspell', right? Otherwise you should have just specified '--with-pspell' in php configure line instead. First, how did you build pspell and aspell (what are the configure lines, versions, and in which order you built them) Second, could you go into the directory with pspell source and from there to examples, and try to compile and run an example: cd pspell/examples make example-c ./example-c en s helllo and please tell if it gives you a list of suggestions for the misspelled word 'helllo'. (I'll be in and out of the office for the next few days, so I might not respond in a timely manner) [2001-12-17 09:46:39] [EMAIL PROTECTED] './configure' '--with-mysql=/usr/local/mysql' '--with-apxs' '--enable-wddx' '--with-sablot' '--with-pspell=/usr/local/pspell' '--enable-force-cgi-redirect' '--with-gettext' '--with-ldap' '--with-cpdflib=/usr/local' '--with-jpeg-dir' '--with-tiff-dir' is the latest iteneration of my configuration. This is the exact configuration I am using in a 4.0.6 installation. Pspell does not work with the same using 4.1.0. (I re-installed pspell to that directory just to make sure) [2001-12-13 23:37:36] [EMAIL PROTECTED] It is strange it even compiled. Are you sure that pspell is installed in --with-pspell=/usr/local/share and not in --with-pspell=/usr/local ??? (e.g. do you have a directory /usr/local/include/pspell or /usr/local/share/include/pspell if the former, you probably need to recompile PHP specifying the right directory) Do you have a configure line for your 4.0.6 installation to compare against? The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/14457 -- Edit this bug report at http://bugs.php.net/?id=14457edit=1
Bug #15673 Updated: Quotes crash MySQL queries: $array['val'] = Parse Error, but $array[val] works
ID: 15673
Updated by: [EMAIL PROTECTED]
-Summary: Quotes crash MySQL queries: $array['val'] = Parse
Error, but $array[val] works
Reported By: [EMAIL PROTECTED]
-Status: Feedback
+Status: Open
Bug Type: Arrays related
Operating System: Linux 2.4.5
PHP Version: 4.1.1
New Comment:
d
Previous Comments:
[2002-02-22 06:55:12] [EMAIL PROTECTED]
Sounds very strange. Can you do a var_dump() on the sql string?
Can you also test and report back if it works with
SELECT * from {$table['users']}
?
[2002-02-22 06:45:23] [EMAIL PROTECTED]
Here is the code:
error_reporting(E_ALL);
$table = array('admin'= 'md_adm'
,'users'= 'usuarios'
,'tables' = 'md_tables'
,'product' = 'md_prods'
);
if(!connect_mydb()) die(unable to connect or select db);
if(isset($table['users'])) { // = works OK
echo $table[users] will warn me!br; // = warning
echo $table['users']; // = no warning
}
$query = SELECT * from $table['users'];
$result = mysql_query($query); // = PARSE ERROR!!
//But if I delete the '' in $query it works ok:
$query = SELECT * from $table[users];
$result = mysql_query($query); // = Query done!!
According to PHP Manual in Arrays : Why is $foo[bar] wrong? the
syntax $foo[bar] is deprecated despite working.
João Paulo M. Fischer
--
Edit this bug report at http://bugs.php.net/?id=15673edit=1
Bug #13824 Updated: /usr/libexec/libphp4.so: undefined symbol: mm_create
ID: 13824 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Bogus Bug Type: Compile Failure Operating System: linux slackware 8.0 PHP Version: 4.0.6 New Comment: I have the same problem. It seems that oracle also contains a libmm.a in his lib directory, and this haven't mm_create. Maybe usefull to rename the oracle's libmm when compiling php. But I'm not sure, that this is a correct solution. But It helped for me for compiling php. Previous Comments: [2001-10-27 06:18:18] [EMAIL PROTECTED] Of course it's not..ask further support questions on the mailing lists. This is not a discussion forum. [2001-10-27 06:12:25] [EMAIL PROTECTED] I'm sure this is not the case because things worked fine till I tried to add in oracle. Remember that first I recompiled php 4.0.6 with exact same options of original slackware package things worked fine (including apache) . [2001-10-27 06:07:09] [EMAIL PROTECTED] Propably something wrong with the libs. Reinstall libmm. And try also with latest CVS snapshot from http://snaps.php.net/ I'm sure this is not a bug in PHP. Something wrong in your system. --Jani [2001-10-27 05:18:52] [EMAIL PROTECTED] this is the situation on my box: root@extensa:~# ls -l /usr/lib/libmm* -rw-r--r--1 root root15554 Oct 19 16:28 /usr/lib/libmm.a -rw-r--r--1 root root 629 Oct 19 16:28 /usr/lib/libmm.la lrwxrwxrwx1 root root 16 Aug 2 19:43 /usr/lib/libmm.so - lib mm.so.11.0.23* lrwxrwxrwx1 root root 16 Aug 2 19:43 /usr/lib/libmm.so.11 - libmm.so.11.0.23* -rwxr-xr-x1 root root18748 Oct 19 16:28 /usr/lib/libmm.so.11.0.2 3* root@extensa:~# nm /usr/lib/libmm.a | grep -i mm_create T MM_create U mm_create T mm_create root@extensa:/usr/src/php-4.0.6# ldd ./.libs/libphp4.so libdl.so.2 = /lib/libdl.so.2 (0x4018f000) libreadline.so.4 = /usr/lib/libreadline.so.4 (0x40193000) libhistory.so.4 = /usr/lib/libhistory.so.4 (0x401b7000) libncurses.so.5 = /lib/libncurses.so.5 (0x401bd000) libclntsh.so.1.0 = /usr/lib/libclntsh.so.1.0 (0x401fd000) libm.so.6 = /lib/libm.so.6 (0x4057e000) libnsl.so.1 = /lib/libnsl.so.1 (0x405a) libmysqlclient.so.10 = /usr/lib/libmysqlclient.so.10 (0x405b5000) libz.so.1 = /usr/lib/libz.so.1 (0x405d) libgmp.so.3 = /usr/lib/libgmp.so.3 (0x405df000) libpng.so.2 = /usr/lib/libpng.so.2 (0x4060) libjpeg.so.62 = /usr/lib/libjpeg.so.62 (0x4062a000) libgdbm.so.2 = /usr/lib/libgdbm.so.2 (0x40649000) libbz2.so.1.0 = /lib/libbz2.so.1.0 (0x4065) libcrypt.so.1 = /lib/libcrypt.so.1 (0x4066) libssl.so.0 = /usr/lib/libssl.so.0 (0x4068e000) libcrypto.so.0 = /usr/lib/libcrypto.so.0 (0x40744000) libresolv.so.2 = /lib/libresolv.so.2 (0x40804000) libc.so.6 = /lib/libc.so.6 (0x40815000) /lib/ld-linux.so.2 = /lib/ld-linux.so.2 (0x8000) libmm does not seem to be there but configure ended with ++ | License: | | This software is subject to the PHP License, available in this | | distribution in the file LICENSE. By continuing this installation | | process, you are bound by the terms of this license agreement. | | If you do not agree with the terms of this license, you must abort | | the installation process at this point.| ++ Thank you for using PHP. whitch is a goo sign (and produced nothing in debud.log) and moreover gere's a grep from output of configure: root@extensa:/usr/src/php-4.0.6# grep -i mm log checking for sys/mman.h... yes checking for memmove... yes checking for mmap... yes checking for memmove... (cached) yes checking for mm support... yes checking command to parse /usr/bin/nm -B output... ok checking how to hardcode library paths into programs... immediate Now what do you suggest ? [2001-10-26 13:29:25] [EMAIL PROTECTED] You mentioned that you have libmm.a (or .so) in /usr/lib? Does this library have mm_create symbol in it: # nm /usr/lib/libmm.a | grep mm_create Replace libmm.a with libmm.so if you don't have the static lib installed. What does ldd output when you have compiled PHP with mm support? --Jani
Bug #15673 Updated: Quotes crash MySQL queries: $array['val'] = Parse Error, but $array[val] works
ID: 15673
Updated by: [EMAIL PROTECTED]
-Summary: Quotes crash MySQL queries: $array['val'] = Parse
Error, but $array[val] works
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: Arrays related
Operating System: Linux 2.4.5
PHP Version: 4.1.1
New Comment:
Sorry: The error occurs when we define the $query:
$query = SELECT * from $table[users]; // = This causes the parse
error
echo Table $table['users'] //= Parse Error too
echo Table.$table['users']; //=OK
$query = SELECT * from .$table['users']; //= OK TOO
Previous Comments:
[2002-02-22 06:59:46] [EMAIL PROTECTED]
d
[2002-02-22 06:55:12] [EMAIL PROTECTED]
Sounds very strange. Can you do a var_dump() on the sql string?
Can you also test and report back if it works with
SELECT * from {$table['users']}
?
[2002-02-22 06:45:23] [EMAIL PROTECTED]
Here is the code:
error_reporting(E_ALL);
$table = array('admin'= 'md_adm'
,'users'= 'usuarios'
,'tables' = 'md_tables'
,'product' = 'md_prods'
);
if(!connect_mydb()) die(unable to connect or select db);
if(isset($table['users'])) { // = works OK
echo $table[users] will warn me!br; // = warning
echo $table['users']; // = no warning
}
$query = SELECT * from $table['users'];
$result = mysql_query($query); // = PARSE ERROR!!
//But if I delete the '' in $query it works ok:
$query = SELECT * from $table[users];
$result = mysql_query($query); // = Query done!!
According to PHP Manual in Arrays : Why is $foo[bar] wrong? the
syntax $foo[bar] is deprecated despite working.
João Paulo M. Fischer
--
Edit this bug report at http://bugs.php.net/?id=15673edit=1
Bug #15673 Updated: Quotes crash MySQL queries: $array['val'] = Parse Error, but $array[val] works
ID: 15673
Updated by: [EMAIL PROTECTED]
-Summary: Quotes crash MySQL queries: $array['val'] = Parse
Error, but $array[val] works
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: Arrays related
Operating System: Linux 2.4.5
PHP Version: 4.1.1
New Comment:
It seems we cannot use the correct syntax $table['users'] inside the
two ...
This will work:
$result = mysql_query(SELECT * from .$table['users']);
This wont work:
$result = mysql_query(SELECT * from $table['users']);
This will, but should send a warning and it isnt:
$result = mysql_query(SELECT * from $table[users]);
The errors happens everywere I call any array with the '' or like
$table[something] or $table['something'] inside s...
Previous Comments:
[2002-02-22 07:06:12] [EMAIL PROTECTED]
Sorry: The error occurs when we define the $query:
$query = SELECT * from $table[users]; // = This causes the parse
error
echo Table $table['users'] //= Parse Error too
echo Table.$table['users']; //=OK
$query = SELECT * from .$table['users']; //= OK TOO
[2002-02-22 06:59:46] [EMAIL PROTECTED]
d
[2002-02-22 06:55:12] [EMAIL PROTECTED]
Sounds very strange. Can you do a var_dump() on the sql string?
Can you also test and report back if it works with
SELECT * from {$table['users']}
?
[2002-02-22 06:45:23] [EMAIL PROTECTED]
Here is the code:
error_reporting(E_ALL);
$table = array('admin'= 'md_adm'
,'users'= 'usuarios'
,'tables' = 'md_tables'
,'product' = 'md_prods'
);
if(!connect_mydb()) die(unable to connect or select db);
if(isset($table['users'])) { // = works OK
echo $table[users] will warn me!br; // = warning
echo $table['users']; // = no warning
}
$query = SELECT * from $table['users'];
$result = mysql_query($query); // = PARSE ERROR!!
//But if I delete the '' in $query it works ok:
$query = SELECT * from $table[users];
$result = mysql_query($query); // = Query done!!
According to PHP Manual in Arrays : Why is $foo[bar] wrong? the
syntax $foo[bar] is deprecated despite working.
João Paulo M. Fischer
--
Edit this bug report at http://bugs.php.net/?id=15673edit=1
Bug #15673 Updated: Quotes crash MySQL queries: $array['val'] = Parse Error, but $array[val] works
ID: 15673
Updated by: [EMAIL PROTECTED]
-Summary: Quotes crash MySQL queries: $array['val'] = Parse
Error, but $array[val] works
Reported By: [EMAIL PROTECTED]
Status: Analyzed
Bug Type: Arrays related
Operating System: Linux 2.4.5
PHP Version: 4.1.1
New Comment:
Yes, I get you get a NOTICE warning when you use $array[key] (because
key will be an undefined constant and therefore evaluate to a string).
Try with error_reporting(E_ALL); before using this syntax.
Previous Comments:
[2002-02-22 07:25:35] [EMAIL PROTECTED]
Hey man WOW, Im impressed, you have already replied!!!
Yes, this solution works:
$query = SELECT * from {$table['users']};
But shouldn't Blah $table['users'] work as well?
Shouldn't PHP at least send a warning when using $table[users] even
if the other $arr['foo'] syntaxes where wrong?
Thanks!
[2002-02-22 07:17:21] [EMAIL PROTECTED]
Use the {$array['key']} syntax as I told you.
However, I can't remember if foo $array['bar'] ever worked or not
right now. Someone else?
[2002-02-22 07:12:54] [EMAIL PROTECTED]
It seems we cannot use the correct syntax $table['users'] inside the
two ...
This will work:
$result = mysql_query(SELECT * from .$table['users']);
This wont work:
$result = mysql_query(SELECT * from $table['users']);
This will, but should send a warning and it isnt:
$result = mysql_query(SELECT * from $table[users]);
The errors happens everywere I call any array with the '' or like
$table[something] or $table['something'] inside s...
[2002-02-22 07:06:12] [EMAIL PROTECTED]
Sorry: The error occurs when we define the $query:
$query = SELECT * from $table[users]; // = This causes the parse
error
echo Table $table['users'] //= Parse Error too
echo Table.$table['users']; //=OK
$query = SELECT * from .$table['users']; //= OK TOO
[2002-02-22 06:59:46] [EMAIL PROTECTED]
d
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/15673
--
Edit this bug report at http://bugs.php.net/?id=15673edit=1
Bug #15673 Updated: Quotes crash MySQL queries: $array['val'] = Parse Error, but $array[val] works
ID: 15673
Updated by: [EMAIL PROTECTED]
-Summary: Quotes crash MySQL queries: $array['val'] = Parse
Error, but $array[val] works
Reported By: [EMAIL PROTECTED]
Status: Analyzed
Bug Type: Arrays related
Operating System: Linux 2.4.5
PHP Version: 4.1.1
New Comment:
Work's right with CVS:
$ php
?
error_reporting(E_ALL);
$foo['key'] = 'value';
echo $foo[key];
?
X-Powered-By: PHP/4.2.0-dev
Content-type: text/html
br /
bWarning/b: Use of undefined constant key - assumed 'key' in
b-/b on line b4/bbr /
-(4) : Warning - Use of undefined constant key - assumed 'key'
Previous Comments:
[2002-02-22 07:52:32] [EMAIL PROTECTED]
I did this tests using error_reporting(E_ALL);
Thats my point, the correct array syntax according the doc:
http://www.php.net/manual/en/language.types.array.php
is to call $array['value'] even thought $array[value] will work, but in
the later case it should send a NOTICE warning.
well, try this in you system:
error_reporting(E_ALL);
$arr = array( 'foo' = 'bar', 'etc' = 'other');
//This will make a Parse Error in PHP 4.1.1:
//echo Foo value is $arr['foo'];
//This works:
echo Foo value is .$arr['foo'];
echo Foo value is {$arr['foo']};
//This will work but WON'T send a warning as the doc says:
echo Foo value is $arr[foo];
// This will get a parse error
echo Foo value is $arr['foo'];
[2002-02-22 07:40:57] [EMAIL PROTECTED]
Yes, I get you get a NOTICE warning when you use $array[key] (because
key will be an undefined constant and therefore evaluate to a string).
Try with error_reporting(E_ALL); before using this syntax.
[2002-02-22 07:25:35] [EMAIL PROTECTED]
Hey man WOW, Im impressed, you have already replied!!!
Yes, this solution works:
$query = SELECT * from {$table['users']};
But shouldn't Blah $table['users'] work as well?
Shouldn't PHP at least send a warning when using $table[users] even
if the other $arr['foo'] syntaxes where wrong?
Thanks!
[2002-02-22 07:17:21] [EMAIL PROTECTED]
Use the {$array['key']} syntax as I told you.
However, I can't remember if foo $array['bar'] ever worked or not
right now. Someone else?
[2002-02-22 07:12:54] [EMAIL PROTECTED]
It seems we cannot use the correct syntax $table['users'] inside the
two ...
This will work:
$result = mysql_query(SELECT * from .$table['users']);
This wont work:
$result = mysql_query(SELECT * from $table['users']);
This will, but should send a warning and it isnt:
$result = mysql_query(SELECT * from $table[users]);
The errors happens everywere I call any array with the '' or like
$table[something] or $table['something'] inside s...
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/15673
--
Edit this bug report at http://bugs.php.net/?id=15673edit=1
Bug #15675: get_class() returns only lower chars
From: [EMAIL PROTECTED]
Operating system: linux w2000
PHP version: 4.1.1
PHP Bug Type: Class/Object related
Bug description: get_class() returns only lower chars
Hi,
i have some code like this:
?php
class getContentBlock {
}
$obj = new getContentBlock();
$classname = get_class($obj);
echo Class of Object: $classname !;
?
= Class of Object: getcontentblock !
The value of $classname should getContentBlock,
but i get getcontentblock !
This is incorrect and causes errors, Classnames are
case sensitiv.
Why is the return value in lower case ?
--
Edit bug report at http://bugs.php.net/?id=15675edit=1
--
Fixed in CVS:http://bugs.php.net/fix.php?id=15675r=fixedcvs
Fixed in release:http://bugs.php.net/fix.php?id=15675r=alreadyfixed
Need backtrace: http://bugs.php.net/fix.php?id=15675r=needtrace
Try newer version: http://bugs.php.net/fix.php?id=15675r=oldversion
Not developer issue: http://bugs.php.net/fix.php?id=15675r=support
Expected behavior: http://bugs.php.net/fix.php?id=15675r=notwrong
Not enough info: http://bugs.php.net/fix.php?id=15675r=notenoughinfo
Submitted twice: http://bugs.php.net/fix.php?id=15675r=submittedtwice
Bug #15673 Updated: Quotes crash MySQL queries: $array['val'] = Parse Error, but $array[val] works
ID: 15673
Updated by: [EMAIL PROTECTED]
-Summary: Quotes crash MySQL queries: $array['val'] = Parse
Error, but $array[val] works
Reported By: [EMAIL PROTECTED]
Status: Analyzed
Bug Type: Arrays related
Operating System: Linux 2.4.5
PHP Version: 4.1.1
New Comment:
Yes, I know your code works, thats not the problem.
Now change your own code:
echo $foo[key]; ==to== echo Key value is $foo[key]; // No
warnings!
And then TRY:
echo $foo['key']; // PARSE ERROR!!!
Does it happens with the cvs version?
Previous Comments:
[2002-02-22 08:12:54] [EMAIL PROTECTED]
Work's right with CVS:
$ php
?
error_reporting(E_ALL);
$foo['key'] = 'value';
echo $foo[key];
?
X-Powered-By: PHP/4.2.0-dev
Content-type: text/html
br /
bWarning/b: Use of undefined constant key - assumed 'key' in
b-/b on line b4/bbr /
-(4) : Warning - Use of undefined constant key - assumed 'key'
[2002-02-22 07:52:32] [EMAIL PROTECTED]
I did this tests using error_reporting(E_ALL);
Thats my point, the correct array syntax according the doc:
http://www.php.net/manual/en/language.types.array.php
is to call $array['value'] even thought $array[value] will work, but in
the later case it should send a NOTICE warning.
well, try this in you system:
error_reporting(E_ALL);
$arr = array( 'foo' = 'bar', 'etc' = 'other');
//This will make a Parse Error in PHP 4.1.1:
//echo Foo value is $arr['foo'];
//This works:
echo Foo value is .$arr['foo'];
echo Foo value is {$arr['foo']};
//This will work but WON'T send a warning as the doc says:
echo Foo value is $arr[foo];
// This will get a parse error
echo Foo value is $arr['foo'];
[2002-02-22 07:40:57] [EMAIL PROTECTED]
Yes, I get you get a NOTICE warning when you use $array[key] (because
key will be an undefined constant and therefore evaluate to a string).
Try with error_reporting(E_ALL); before using this syntax.
[2002-02-22 07:25:35] [EMAIL PROTECTED]
Hey man WOW, Im impressed, you have already replied!!!
Yes, this solution works:
$query = SELECT * from {$table['users']};
But shouldn't Blah $table['users'] work as well?
Shouldn't PHP at least send a warning when using $table[users] even
if the other $arr['foo'] syntaxes where wrong?
Thanks!
[2002-02-22 07:17:21] [EMAIL PROTECTED]
Use the {$array['key']} syntax as I told you.
However, I can't remember if foo $array['bar'] ever worked or not
right now. Someone else?
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/15673
--
Edit this bug report at http://bugs.php.net/?id=15673edit=1
Bug #15676: Problems with mcrypt and java
From: [EMAIL PROTECTED] Operating system: Linux RedHat 7.1 PHP version: 4.1.1 PHP Bug Type: Compile Failure Bug description: Problems with mcrypt and java When I configure my PHP without --with-java the following configure-command is successful: ./configure --bindir=/u/own/php-bin/php411 --with-config-file-path=/u/own/php-bin/php411 --enable-force-cgi-redirect --without-pear --with-zlib --with-bz2 --enable-calendar --with-curl --enable-ftp --with-gd=/usr --enable-gd-native-ttf --with-imap=/usr/local/src/imap-2001.BETA.SNAP-0105042209 --with-mcrypt --with-mhash --with-mysql=/usr --enable-shmop --enable-sockets --enable-sysvshm --enable-sysvshm --with-vpopmail --enable-wddx --enable-versioning --enable-memory-limit --enable-track-vars --with-xml --with-ttf --with-openssl But when I add --with-java=/usr/local/jdk to the configure-command the script fails with: checking for ircg support... no checking for Java support... yes checking whether to include LDAP support... no checking whether to enable mailparse support... no checking whether to enable multibyte string support... no checking whether to enable japanese encoding translation... no checking for MCAL support... no checking for mcrypt support... yes checking for mcrypt_module_open in -lmcrypt... no checking for init_mcrypt in -lmcrypt... no configure: error: Sorry It's funny that the configure-script complains about mcrypt while it doesn't complain about it without java!?? Best regards Stephan Sann -- Edit bug report at http://bugs.php.net/?id=15676edit=1 -- Fixed in CVS:http://bugs.php.net/fix.php?id=15676r=fixedcvs Fixed in release:http://bugs.php.net/fix.php?id=15676r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=15676r=needtrace Try newer version: http://bugs.php.net/fix.php?id=15676r=oldversion Not developer issue: http://bugs.php.net/fix.php?id=15676r=support Expected behavior: http://bugs.php.net/fix.php?id=15676r=notwrong Not enough info: http://bugs.php.net/fix.php?id=15676r=notenoughinfo Submitted twice: http://bugs.php.net/fix.php?id=15676r=submittedtwice
Bug #15673 Updated: Quotes crash MySQL queries: $array['val'] = Parse Error, but $array[val] works
ID: 15673
Updated by: [EMAIL PROTECTED]
-Summary: Quotes crash MySQL queries: $array['val'] = Parse
Error, but $array[val] works
Reported By: [EMAIL PROTECTED]
Status: Analyzed
Bug Type: Arrays related
Operating System: Linux 2.4.5
PHP Version: 4.1.1
New Comment:
Ah, I see. No, there's no warning either.
Previous Comments:
[2002-02-22 08:25:33] [EMAIL PROTECTED]
Yes, I know your code works, thats not the problem.
Now change your own code:
echo $foo[key]; ==to== echo Key value is $foo[key]; // No
warnings!
And then TRY:
echo $foo['key']; // PARSE ERROR!!!
Does it happens with the cvs version?
[2002-02-22 08:12:54] [EMAIL PROTECTED]
Work's right with CVS:
$ php
?
error_reporting(E_ALL);
$foo['key'] = 'value';
echo $foo[key];
?
X-Powered-By: PHP/4.2.0-dev
Content-type: text/html
br /
bWarning/b: Use of undefined constant key - assumed 'key' in
b-/b on line b4/bbr /
-(4) : Warning - Use of undefined constant key - assumed 'key'
[2002-02-22 07:52:32] [EMAIL PROTECTED]
I did this tests using error_reporting(E_ALL);
Thats my point, the correct array syntax according the doc:
http://www.php.net/manual/en/language.types.array.php
is to call $array['value'] even thought $array[value] will work, but in
the later case it should send a NOTICE warning.
well, try this in you system:
error_reporting(E_ALL);
$arr = array( 'foo' = 'bar', 'etc' = 'other');
//This will make a Parse Error in PHP 4.1.1:
//echo Foo value is $arr['foo'];
//This works:
echo Foo value is .$arr['foo'];
echo Foo value is {$arr['foo']};
//This will work but WON'T send a warning as the doc says:
echo Foo value is $arr[foo];
// This will get a parse error
echo Foo value is $arr['foo'];
[2002-02-22 07:40:57] [EMAIL PROTECTED]
Yes, I get you get a NOTICE warning when you use $array[key] (because
key will be an undefined constant and therefore evaluate to a string).
Try with error_reporting(E_ALL); before using this syntax.
[2002-02-22 07:25:35] [EMAIL PROTECTED]
Hey man WOW, Im impressed, you have already replied!!!
Yes, this solution works:
$query = SELECT * from {$table['users']};
But shouldn't Blah $table['users'] work as well?
Shouldn't PHP at least send a warning when using $table[users] even
if the other $arr['foo'] syntaxes where wrong?
Thanks!
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/15673
--
Edit this bug report at http://bugs.php.net/?id=15673edit=1
Bug #15675 Updated: get_class() returns only lower chars
ID: 15675
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Open
+Status: Suspended
Bug Type: Class/Object related
Operating System: linux w2000
PHP Version: 4.1.1
New Comment:
Classnames aren't case sensitive; if you write:
?php
class getContentBlock {
}
$obj = new GeTcOnTeNtBlOcK();
$classname = get_class($obj);
echo Class of Object: $classname !;
?
It will work too.
That's because the internal class representation is insenstive (thus
stored only in lowercase).
This may be subject of change in ZE2, susupending this report.
Previous Comments:
[2002-02-22 08:14:07] [EMAIL PROTECTED]
Hi,
i have some code like this:
?php
class getContentBlock {
}
$obj = new getContentBlock();
$classname = get_class($obj);
echo Class of Object: $classname !;
?
= Class of Object: getcontentblock !
The value of $classname should getContentBlock,
but i get getcontentblock !
This is incorrect and causes errors, Classnames are
case sensitiv.
Why is the return value in lower case ?
--
Edit this bug report at http://bugs.php.net/?id=15675edit=1
Bug #15676 Updated: Problems with mcrypt and java
ID: 15676 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Open +Status: Bogus Bug Type: Compile Failure Operating System: Linux RedHat 7.1 PHP Version: 4.1.1 New Comment: The bug system is not the appropriate forum for asking support questions. For a list of a range of more appropriate places to ask for help using PHP, please visit http://www.php.net/support.php Previous Comments: [2002-02-22 08:25:51] [EMAIL PROTECTED] When I configure my PHP without --with-java the following configure-command is successful: ./configure --bindir=/u/own/php-bin/php411 --with-config-file-path=/u/own/php-bin/php411 --enable-force-cgi-redirect --without-pear --with-zlib --with-bz2 --enable-calendar --with-curl --enable-ftp --with-gd=/usr --enable-gd-native-ttf --with-imap=/usr/local/src/imap-2001.BETA.SNAP-0105042209 --with-mcrypt --with-mhash --with-mysql=/usr --enable-shmop --enable-sockets --enable-sysvshm --enable-sysvshm --with-vpopmail --enable-wddx --enable-versioning --enable-memory-limit --enable-track-vars --with-xml --with-ttf --with-openssl But when I add --with-java=/usr/local/jdk to the configure-command the script fails with: checking for ircg support... no checking for Java support... yes checking whether to include LDAP support... no checking whether to enable mailparse support... no checking whether to enable multibyte string support... no checking whether to enable japanese encoding translation... no checking for MCAL support... no checking for mcrypt support... yes checking for mcrypt_module_open in -lmcrypt... no checking for init_mcrypt in -lmcrypt... no configure: error: Sorry It's funny that the configure-script complains about mcrypt while it doesn't complain about it without java!?? Best regards Stephan Sann -- Edit this bug report at http://bugs.php.net/?id=15676edit=1
Bug #15673 Updated: Quotes crash MySQL queries: $array['val'] = Parse Error, but $array[val] works
ID: 15673
Updated by: [EMAIL PROTECTED]
-Summary: Quotes crash MySQL queries: $array['val'] = Parse
Error, but $array[val] works
Reported By: [EMAIL PROTECTED]
Status: Analyzed
Bug Type: Arrays related
Operating System: Linux 2.4.5
PHP Version: 4.1.1
New Comment:
And the Parse Error, do you get it with the cvs ver too?
Previous Comments:
[2002-02-22 08:29:58] [EMAIL PROTECTED]
Ah, I see. No, there's no warning either.
[2002-02-22 08:25:33] [EMAIL PROTECTED]
Yes, I know your code works, thats not the problem.
Now change your own code:
echo $foo[key]; ==to== echo Key value is $foo[key]; // No
warnings!
And then TRY:
echo $foo['key']; // PARSE ERROR!!!
Does it happens with the cvs version?
[2002-02-22 08:12:54] [EMAIL PROTECTED]
Work's right with CVS:
$ php
?
error_reporting(E_ALL);
$foo['key'] = 'value';
echo $foo[key];
?
X-Powered-By: PHP/4.2.0-dev
Content-type: text/html
br /
bWarning/b: Use of undefined constant key - assumed 'key' in
b-/b on line b4/bbr /
-(4) : Warning - Use of undefined constant key - assumed 'key'
[2002-02-22 07:52:32] [EMAIL PROTECTED]
I did this tests using error_reporting(E_ALL);
Thats my point, the correct array syntax according the doc:
http://www.php.net/manual/en/language.types.array.php
is to call $array['value'] even thought $array[value] will work, but in
the later case it should send a NOTICE warning.
well, try this in you system:
error_reporting(E_ALL);
$arr = array( 'foo' = 'bar', 'etc' = 'other');
//This will make a Parse Error in PHP 4.1.1:
//echo Foo value is $arr['foo'];
//This works:
echo Foo value is .$arr['foo'];
echo Foo value is {$arr['foo']};
//This will work but WON'T send a warning as the doc says:
echo Foo value is $arr[foo];
// This will get a parse error
echo Foo value is $arr['foo'];
[2002-02-22 07:40:57] [EMAIL PROTECTED]
Yes, I get you get a NOTICE warning when you use $array[key] (because
key will be an undefined constant and therefore evaluate to a string).
Try with error_reporting(E_ALL); before using this syntax.
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/15673
--
Edit this bug report at http://bugs.php.net/?id=15673edit=1
Bug #15677: quoted array index in string should be possible
From: [EMAIL PROTECTED]
Operating system: *
PHP version: 4.1.1
PHP Bug Type: Feature/Change Request
Bug description: quoted array index in string should be possible
?php echo $array[index]; ?
works while
?php echo $array['index']; ?
gives
PHP Parse error: parse error, expecting `T_STRING' or `T_VARIABLE' or
`T_NUM_STRING' in - on line 1
the error message is not very helpfull (knowing the exact character
position in the line would help a little bit, but that's another story)
and the different syntax requirements for array indices within and outside
of strings are somtimes confusing for newbies, too
so $array['index'] should be supported by the parser
PS: i know about {$array['index']}, but that is not the point ...
--
Edit bug report at http://bugs.php.net/?id=15677edit=1
--
Fixed in CVS:http://bugs.php.net/fix.php?id=15677r=fixedcvs
Fixed in release:http://bugs.php.net/fix.php?id=15677r=alreadyfixed
Need backtrace: http://bugs.php.net/fix.php?id=15677r=needtrace
Try newer version: http://bugs.php.net/fix.php?id=15677r=oldversion
Not developer issue: http://bugs.php.net/fix.php?id=15677r=support
Expected behavior: http://bugs.php.net/fix.php?id=15677r=notwrong
Not enough info: http://bugs.php.net/fix.php?id=15677r=notenoughinfo
Submitted twice: http://bugs.php.net/fix.php?id=15677r=submittedtwice
Bug #15673 Updated: Quotes crash MySQL queries: $array['val'] = Parse Error, but $array[val] works
ID: 15673 Updated by: [EMAIL PROTECTED] -Summary: Quotes crash MySQL queries: $array['val'] = Parse Error, but $array[val] works Reported By: [EMAIL PROTECTED] Status: Closed Bug Type: Arrays related Operating System: Linux 2.4.5 PHP Version: 4.1.1 New Comment: Ok, but I think it should be seen as a BUG, since we cannot call the array as it should be and we are able to call it as it shouldn't. PHP is expected work with codes like: sql_query(SELECT * from $array['table']); and its expected to (but doesnt have to) work with: sql_query(SELECT * from $array[table]); and in such case its expected to give a warning... in both cases the behavior of 4.1.1 is buggy... Thanks for your time people! Best Regards João Paulo M. Fischer Previous Comments: [2002-02-22 09:42:58] [EMAIL PROTECTED] i'll close this here and create a feature request for $array['index'] to be possible or for a better error message at least ... see http://bugs.php.net/15677 [2002-02-22 08:40:58] [EMAIL PROTECTED] And the Parse Error, do you get it with the cvs ver too? [2002-02-22 08:29:58] [EMAIL PROTECTED] Ah, I see. No, there's no warning either. [2002-02-22 08:25:33] [EMAIL PROTECTED] Yes, I know your code works, thats not the problem. Now change your own code: echo $foo[key]; ==to== echo Key value is $foo[key]; // No warnings! And then TRY: echo $foo['key']; // PARSE ERROR!!! Does it happens with the cvs version? [2002-02-22 08:12:54] [EMAIL PROTECTED] Work's right with CVS: $ php ? error_reporting(E_ALL); $foo['key'] = 'value'; echo $foo[key]; ? X-Powered-By: PHP/4.2.0-dev Content-type: text/html br / bWarning/b: Use of undefined constant key - assumed 'key' in b-/b on line b4/bbr / -(4) : Warning - Use of undefined constant key - assumed 'key' The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/15673 -- Edit this bug report at http://bugs.php.net/?id=15673edit=1
Bug #15673 Updated: Quotes crash MySQL queries: $array['val'] = Parse Error, but $array[val] works
ID: 15673 Updated by: [EMAIL PROTECTED] -Summary: Quotes crash MySQL queries: $array['val'] = Parse Error, but $array[val] works Reported By: [EMAIL PROTECTED] Status: Closed Bug Type: Arrays related Operating System: Linux 2.4.5 PHP Version: 4.1.1 New Comment: PHP is expected work with codes like: sql_query(SELECT * from $array['table']); one *could* expect that it understood this, that's what my feature request is about, but PHP is expected is not right and its expected to (but doesnt have to) work with: sql_query(SELECT * from $array[table]); and in such case its expected to give a warning... no, this is the current and expected behavior no warning is generated here as no define() substitution is done in strings in both cases the behavior of 4.1.1 is buggy... it has been like this ever since 3.0, so you can't call this 'buggy', call it 'unexpected behaviour', 'inconsistent design' or whatever, but it is not a bug ... Previous Comments: [2002-02-22 10:02:10] [EMAIL PROTECTED] Ok, but I think it should be seen as a BUG, since we cannot call the array as it should be and we are able to call it as it shouldn't. PHP is expected work with codes like: sql_query(SELECT * from $array['table']); and its expected to (but doesnt have to) work with: sql_query(SELECT * from $array[table]); and in such case its expected to give a warning... in both cases the behavior of 4.1.1 is buggy... Thanks for your time people! Best Regards João Paulo M. Fischer [2002-02-22 09:42:58] [EMAIL PROTECTED] i'll close this here and create a feature request for $array['index'] to be possible or for a better error message at least ... see http://bugs.php.net/15677 [2002-02-22 08:40:58] [EMAIL PROTECTED] And the Parse Error, do you get it with the cvs ver too? [2002-02-22 08:29:58] [EMAIL PROTECTED] Ah, I see. No, there's no warning either. [2002-02-22 08:25:33] [EMAIL PROTECTED] Yes, I know your code works, thats not the problem. Now change your own code: echo $foo[key]; ==to== echo Key value is $foo[key]; // No warnings! And then TRY: echo $foo['key']; // PARSE ERROR!!! Does it happens with the cvs version? The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/15673 -- Edit this bug report at http://bugs.php.net/?id=15673edit=1
Bug #15658 Updated: session.save_path directive has no influence on session files save_path
ID: 15658 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Open +Status: Feedback Bug Type: *Configuration Issues Operating System: win2k PHP Version: 4.1.1 New Comment: Did you restart Apache? Previous Comments: [2002-02-21 09:37:38] [EMAIL PROTECTED] I try to get PHP to save it's session files in the /sessions directory (set session.save_path = e:\sessions) on my document drive, but no matter what I do and how I specify the directory (forward and backward slashes) it keeps saving them in the /tmp directory on that same drive (e:\tmp). There is no reference to /tmp in my whole php.ini file! From my point of view it looks like the session.save_path directive recognition in the php.ini file is broken. -- Edit this bug report at http://bugs.php.net/?id=15658edit=1
Bug #15670 Updated: printing problem w/ Netscape 4.x when ob is enabled using gz_handler
ID: 15670 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Open +Status: Closed Bug Type: Output Control Operating System: Linux PHP Version: 4.1.1 New Comment: Probably not a bug in PHP, but in Netscape. Previous Comments: [2002-02-22 04:42:49] [EMAIL PROTECTED] This is not a critical Bug... In Fact, it's probably a Netscape Bug rather than a php- bug... Symptoms: Netscape 4.x on Win98 (Possibly Win95/00 as well) won't display html-source or print Page Occurs: -when output-buffering is enabled - ob_start(gz_handler) Does not occur: -on any other Browser/System tested (IE, Opera, MacOSX) -when gz_handler is not specified as callback Example: not available, since problem was fixed by disabling ob for affected browsers on our production server. My Configure line: './configure' '--with-apache=../apache_1.3.22' '--with- mysql' '--with-pgsql=/usr/local/pgsql' '--with-t1lib' '-- with-tiff-dir=../tiff-v3.5.6-beta' '-with-ttf=/usr' '-- enable-inline-optimization--enable-shared-pdflib' '--with- swf=/usr/local' '--enable-ftp' '--with-openssl' '--disable- short-tags' '--with-pspell' '--enable-gd-native-tt' '-- enable-gd-imgstrttf' '--with-freetype-dir=/usr/local/ include/freetype2' '--with-zlib-dir=/usr/local' '--with-gd' '--with-jpeg-dir=../jpeg-6b' '--with-png-dir=../libpng- 1.2.0' '--with-oci8=/opt/oracle' '--enable-sigchild' -- Edit this bug report at http://bugs.php.net/?id=15670edit=1
Bug #15669 Updated: Shrinker error - Dispatcher initialisation error 6
ID: 15669 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Open +Status: Bogus Bug Type: *Configuration Issues Operating System: win98 PHP Version: 4.1.1 New Comment: The bug system is not the appropriate forum for asking support questions. For a list of a range of more appropriate places to ask for help using PHP, please visit http://www.php.net/support.php Very likeley to be a configuration error. Previous Comments: [2002-02-22 04:06:35] [EMAIL PROTECTED] downladed and unpacked php-4.1.1-Win32 and php-4.1.1-installer apps from PHP site. Installed using automatic method and checked entries under manual method in registry. Obtained MDAC latest version 2.7 and MDAC checker programfrom microsoft for PWS ran same and brought up to date on PWS standard install APP from New win98 2nd ed CD. (registered ver). Tried command line PHP -i and obtained output file. stored local. viewed in HTML browser as htm file. All seems OK wrote first php file. As example and tried in browser. Result CGI Error The specified CGI application misbehaved by not returning a complete set of HTTP headers. The headers it did return are: rest of page blank. simplehello world example. downloaded and tried to run iiscfg.exe after studying PHP site. This fails on Shrinker error - Dispatcher initialisation error 6 Checked around and found others were having same problem. my php.ini is disturbingly sparse, so I looked at the browscap config file which lists most browsers. there seems to be no entries for IE6.0 so I guess the install script didn't complete as it should have. All logs available for the asking. Any ideas guys(gals). PS you don't have installation issues as a type of bug on this page. http://bugs.php.net/report.php PPS keep up the good work. Hope to let you have some plug ins for this presently. Would fix it myself but I don't have the structure worked out yet. Or C++ compiler yet. :( -- Edit this bug report at http://bugs.php.net/?id=15669edit=1
Bug #15628 Updated: Multiple Connections not allowed
ID: 15628 Updated by: [EMAIL PROTECTED], [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Informix related Operating System: SunSolaris 8 Sparc PHP Version: 4.1.1 New Comment: Some information: SO - Red Hat 7.1 kernel 2.2.12 The file to be edited is ext/informix/ifx.ec Previous Comments: [2002-02-22 12:22:36] [EMAIL PROTECTED], [EMAIL PROTECTED] we´ve found the same bug. This solution worked very well! Thanks! [2002-02-19 14:29:36] [EMAIL PROTECTED] Hi, I would like to report a bug in the Informix module of PHP 4.1.1. When you try to use more than one connection, the last connection created is the one that receives every statement, and under this circumstances you may get a SQLCODE error code -206 when calling ifx_query as the table may not exist in the current database. I was debugging the Informix implementation and I found that in the function ifx_query the following statement is missing: EXEC SQL set connection :ifx; before the call of the macro PHP_IFX_CHECK_CONNECTION and the call to the PREPARE statement. If you add that statement, the funcion ifx_query works fine. This function call is needed as every time that you execute the statement CONNECT TO ... that connection is the active one and the former connections become dormant. When you want to use one of those connection, you need to active it again using the statement SET CONNECTION. I hope this helps. -- Edit this bug report at http://bugs.php.net/?id=15628edit=1
Bug #15668 Updated: translation of symbol '' when storing in Mysql
ID: 15668
Updated by: [EMAIL PROTECTED]
-Summary: translation of symbol '' when storing in Mysql
Reported By: [EMAIL PROTECTED]
-Status: Open
+Status: Bogus
Bug Type: MySQL related
Operating System: linux redhat 7.1
PHP Version: 4.0.5
New Comment:
The bug system is not the appropriate forum for asking support
questions. For a list of a range of more appropriate places to ask
for help using PHP, please visit http://www.php.net/support.php
Can't reproduce.
Previous Comments:
[2002-02-22 12:35:58] [EMAIL PROTECTED]
the script that causes the problem :
when the string $ragsoc1 contains in Mysql I found amp;
$preserve=;
while (strpos($ragsoc1, ))
{
$ragsoc1=str_replace( , ,$ragsoc1);
}
// print $ragsoc1;
$ragsoc1=cleanup_text($ragsoc1,$preserve);
$ragsoc2=cleanup_text($ragsoc2,$preserve);
$indir1=cleanup_text($indir1,$preserve);
$indir2=cleanup_text($indir2,$preserve);
$cap=cleanup_text($cap,$preserve);
$citta=cleanup_text($citta,$preserve);
$prov=cleanup_text($prov,$preserve);
$paese=cleanup_text($paese,$preserve);
$telef1=cleanup_text($telef1,$preserve);
$telef2=cleanup_text($telef2,$preserve);
$fax=cleanup_text($fax,$preserve);
$mytext=cleanup_text($mytext,$preserve);
// print $ragsoc1;
// echo '$check1';
session_register(recatt_soc);
if ($recatt_soc==3)
{
$a1=insert into societa
(ragsoc1,ragsoc2,indir1,indir2,cap,citta,prov,paese,;
$b1=telef1,telef2,fax,note) values
('$ragsoc1','$ragsoc2','$indir1','$indir2',;
$c1='$cap','$citta','$prov','$paese','$telef1','$telef2','$fax','$mytext');
$where_cat=;
}
else
{
$where_cat=where (IDSOC='$cod');
$a1=update societa set ragsoc1='$ragsoc1' , ragsoc2='$ragsoc2',
;
$b1=indir1='$indir1', indir2='$indir2', cap='$cap',
citta='$citta', ;
$c1=prov='$prov',paese='$paese', telef1='$telef1',
telef2='$telef2', fax='$fax', note='$mytext' ;
$z1=$where_cat;
}
$query=$a1 $b1 $c1 $where_cat;
// echo $query;
echo br\n;
$result=mysql_query($query)
or die (Query errata :
.lierrorno.mysql_errno()
.lierror=.mysql_error()
.lierror=.$query
);
session_register(recatt_soc);
// echo $recatt_soc;
[2002-02-22 12:20:58] [EMAIL PROTECTED]
Can you provide a sample script? You're very likely doing something
wrong...
[2002-02-22 02:58:56] [EMAIL PROTECTED]
In PHP script I have a variable with a string assigned containing the
symbol '' :
$myvariable = 'Smith Sons';
when I insert the variable in the database :
$query=insert into mytable (mycolumn) values
(myvalue1='$myvariable');;
$result=mysql_query($query);
if I edit directly the column in Mysql the symbol '' has been
translated to 'amp;'.
--
Edit this bug report at http://bugs.php.net/?id=15668edit=1
Bug #15668 Updated: translation of symbol '' when storing in Mysql
ID: 15668
Updated by: [EMAIL PROTECTED]
-Summary: translation of symbol '' when storing in Mysql
Reported By: [EMAIL PROTECTED]
Status: Bogus
Bug Type: MySQL related
Operating System: linux redhat 7.1
PHP Version: 4.0.5
New Comment:
You may want to try a never version anyway, 4.0.6 or 4.1.1 ...
Previous Comments:
[2002-02-22 12:47:34] [EMAIL PROTECTED]
The bug system is not the appropriate forum for asking support
questions. For a list of a range of more appropriate places to ask
for help using PHP, please visit http://www.php.net/support.php
Can't reproduce.
[2002-02-22 12:35:58] [EMAIL PROTECTED]
the script that causes the problem :
when the string $ragsoc1 contains in Mysql I found amp;
$preserve=;
while (strpos($ragsoc1, ))
{
$ragsoc1=str_replace( , ,$ragsoc1);
}
// print $ragsoc1;
$ragsoc1=cleanup_text($ragsoc1,$preserve);
$ragsoc2=cleanup_text($ragsoc2,$preserve);
$indir1=cleanup_text($indir1,$preserve);
$indir2=cleanup_text($indir2,$preserve);
$cap=cleanup_text($cap,$preserve);
$citta=cleanup_text($citta,$preserve);
$prov=cleanup_text($prov,$preserve);
$paese=cleanup_text($paese,$preserve);
$telef1=cleanup_text($telef1,$preserve);
$telef2=cleanup_text($telef2,$preserve);
$fax=cleanup_text($fax,$preserve);
$mytext=cleanup_text($mytext,$preserve);
// print $ragsoc1;
// echo '$check1';
session_register(recatt_soc);
if ($recatt_soc==3)
{
$a1=insert into societa
(ragsoc1,ragsoc2,indir1,indir2,cap,citta,prov,paese,;
$b1=telef1,telef2,fax,note) values
('$ragsoc1','$ragsoc2','$indir1','$indir2',;
$c1='$cap','$citta','$prov','$paese','$telef1','$telef2','$fax','$mytext');
$where_cat=;
}
else
{
$where_cat=where (IDSOC='$cod');
$a1=update societa set ragsoc1='$ragsoc1' , ragsoc2='$ragsoc2',
;
$b1=indir1='$indir1', indir2='$indir2', cap='$cap',
citta='$citta', ;
$c1=prov='$prov',paese='$paese', telef1='$telef1',
telef2='$telef2', fax='$fax', note='$mytext' ;
$z1=$where_cat;
}
$query=$a1 $b1 $c1 $where_cat;
// echo $query;
echo br\n;
$result=mysql_query($query)
or die (Query errata :
.lierrorno.mysql_errno()
.lierror=.mysql_error()
.lierror=.$query
);
session_register(recatt_soc);
// echo $recatt_soc;
[2002-02-22 12:20:58] [EMAIL PROTECTED]
Can you provide a sample script? You're very likely doing something
wrong...
[2002-02-22 02:58:56] [EMAIL PROTECTED]
In PHP script I have a variable with a string assigned containing the
symbol '' :
$myvariable = 'Smith Sons';
when I insert the variable in the database :
$query=insert into mytable (mycolumn) values
(myvalue1='$myvariable');;
$result=mysql_query($query);
if I edit directly the column in Mysql the symbol '' has been
translated to 'amp;'.
--
Edit this bug report at http://bugs.php.net/?id=15668edit=1
Bug #14026 Updated: Apache Crash
ID: 14026 Updated by: [EMAIL PROTECTED] -Summary: read_exif_data cannot read Ricoh DC jpg -Reported By: [EMAIL PROTECTED] +Reported By: [EMAIL PROTECTED] Status: Open Bug Type: *Graphics related -Operating System: Linux +Operating System: Linux 2.4.5 -PHP Version: 4.0.6 +PHP Version: 4.1.1 New Comment: Could you send me an image that has this problem? Or point me at a URL where I can grab one? It should be a simple fix if I can reproduce it locally here. Previous Comments: [2002-02-20 21:03:29] [EMAIL PROTECTED] I have a Minolta DiMage7 DC I am getting intermittent problems with FATAL: emalloc(): Unable to allocate -2147483648 bytes read_exif_data will work with most pictures, but sometimes will produce the error. [2001-11-12 05:42:16] [EMAIL PROTECTED] Thx much prompt reply. Tried PHP Version 4.2.0-dev at http://www.aimaker.com/info.php Still got the same error with ricoh.jpg but ok with canon jpg. [2001-11-12 04:59:29] [EMAIL PROTECTED] You might want to try a snapshot from snaps.php.net. AFAIK, this should be fixed. Derick [2001-11-12 04:55:20] [EMAIL PROTECTED] :) php-read_exif-data can read exif from Canon DC jpg file :( php-read_exif-data cannot read exif from Ricoh DC jpg file A server error got is - FATAL: emalloc(): Unable to allocate -2147483648 bytes A example of Ricoh DC jpg at http://www.aimaker.com/ricoh.jpg -- Edit this bug report at http://bugs.php.net/?id=14026edit=1
Bug #15682: Bitwise concatenation of constants in class variables
From: [EMAIL PROTECTED]
Operating system: WinXP
PHP version: 4.1.1
PHP Bug Type: Class/Object related
Bug description: Bitwise concatenation of constants in class variables
class foo {
$var bar = E_ALL ~E_NOTICE;
}
Obviously a scalar value (assigning a single value works perfectly), but
the following appears when it comes to execution:
Parse error: parse error, expecting , or ;
--
Edit bug report at http://bugs.php.net/?id=15682edit=1
--
Fixed in CVS:http://bugs.php.net/fix.php?id=15682r=fixedcvs
Fixed in release:http://bugs.php.net/fix.php?id=15682r=alreadyfixed
Need backtrace: http://bugs.php.net/fix.php?id=15682r=needtrace
Try newer version: http://bugs.php.net/fix.php?id=15682r=oldversion
Not developer issue: http://bugs.php.net/fix.php?id=15682r=support
Expected behavior: http://bugs.php.net/fix.php?id=15682r=notwrong
Not enough info: http://bugs.php.net/fix.php?id=15682r=notenoughinfo
Submitted twice: http://bugs.php.net/fix.php?id=15682r=submittedtwice
Bug #15682 Updated: Bitwise concatenation of constants in class variables
ID: 15682
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Open
+Status: Bogus
Bug Type: Class/Object related
Operating System: WinXP
PHP Version: 4.1.1
New Comment:
Not a bug. You can only use static assignments here:
From the manual @ http://www.php.net/manual/en/language.oop.php :
Note: In PHP 4, only constant initializers for var variables are
allowed. To initialize variables with non-constant values, you need an
initialization function which is called automatically when an object is
being constructed from the class. Such a function is called a
constructor (see below).
regards,
Derick
Previous Comments:
[2002-02-22 17:15:40] [EMAIL PROTECTED]
class foo {
var $bar = E_ALL ~E_NOTICE;
}
Obviously a scalar value (assigning a single value works perfectly),
but
the following appears when it comes to execution:
Parse error: parse error, expecting , or ;
[2002-02-22 17:14:17] [EMAIL PROTECTED]
class foo {
$var bar = E_ALL ~E_NOTICE;
}
Obviously a scalar value (assigning a single value works perfectly),
but the following appears when it comes to execution:
Parse error: parse error, expecting , or ;
--
Edit this bug report at http://bugs.php.net/?id=15682edit=1
Bug #10603 Updated: Problems changing the language.
ID: 10603 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Feedback +Status: No Feedback Bug Type: Gettext related Operating System: Windows 2000 PHP Version: 4.0.5 New Comment: No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to Open. Previous Comments: [2002-01-14 15:48:37] [EMAIL PROTECTED] Is this valid on 4.1.1? [2001-05-02 05:05:06] [EMAIL PROTECTED] I run php as apache module (apache 1.3.19) I put this code: putenv(LANG=RO); bindtextdomain (domain, ./locale); textdomain (domain); everything is ok. Then I modify the value of the language ( and it's ok 'cause I display it with getenv(LANG), but the translation doesn't change. If I run php as cgi this works fine. I have the same problem with php 4.0.4pl1 -- Edit this bug report at http://bugs.php.net/?id=10603edit=1
Bug #11793 Updated: file_exists() and friends
ID: 11793
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Bogus
Bug Type: Scripting Engine problem
Operating System: Redhat Linux
PHP Version: 4.0.6
New Comment:
I was having trouble with the following code:
$date = `date +%d-%b-%Y`;
$data_file = data/ . $date;
rtrim($data_file);
# $data_file = rtrim($data_file);
clearstatcache();
if( file_exists($data_file) ) {
$curr_data = yes;
} else {
$curr_data = no;
}
For the record the solution was to change the rtrim line to the one I
have commented out. I was thinking in perl. :)
Previous Comments:
[2001-06-29 04:51:07] [EMAIL PROTECTED]
This was not a PHP problem.
[2001-06-29 03:09:36] [EMAIL PROTECTED]
I'm having problem with file_exists(), is_file(),
file_size() since the upgrade to 4.0.6. It does not work
if I supply a variable as a filename. E.g.
file_exists( $var ); will return false even if the
variable contains a correct path.
file_exists( path/to/file.txt ); works.
Same for the is_file() and file_size();
--
Edit this bug report at http://bugs.php.net/?id=11793edit=1
Bug #15683 Updated: addslashes mis-recognises chinese-big5 words with 0xXX 0x5C
ID: 15683 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Strings related Operating System: ALL PHP Version: 4.1.1 New Comment: magic-quote is another function that creates the problem Addslashes is a php function that adds a slash in front of ' (single quotes), (double-quotes), and \ (back slashes) which makes Traditional Chinese words display improperly when parsing the string. They thought the chinese word to be quoted or something like that... Previous Comments: [2002-02-23 02:21:21] [EMAIL PROTECTED] addslashes and others always mis-recognise and display chinese big5-code words with the character 0xXX 0x5C by adding slashes into the words which makes Traditional Chinese words can never be displayed properly within php... it's very inconvenient for all traditional Chinese users Can anyone help? Someone suggests adding codes of procedure for identifying whether the words are in chinese-big-5 code or not before addslashes and other work... If that is a practical method, could someone make this patch for us chinese linux php users? If that's not too complicated even for php-developers, could you guys please consider this in your future versions Please help! -- Edit this bug report at http://bugs.php.net/?id=15683edit=1
Bug #15669 Updated: Shrinker error - Dispatcher initialisation error 6
ID: 15669 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Bogus Bug Type: *Configuration Issues Operating System: win98 PHP Version: 4.1.1 New Comment: * PHP Installation *** This is the install process for PHP4. I used php-4.0.1pl2-Win32.zip. The documentation claims that you need the updated dcom95.exe from microsoft. On win 98, dcom95.exe won't run, so bother getting it. There is a dcom98.exe, but PHP4 runs both with and without it, in my experience (Win 98SE). Unzip the file and copy all the files to your PHP directory. Rename: php.ini-dist to php.ini Open it in a text editor. Search for the string doc_root and make sure it is not set to any value. Search for extension_dir and set its value to c:\progra~1\PHP, or whatever your PHP directory is. Use the quotes. I've read that you don't need the quotes, or that you can use long filenames. I chose to play it safe, and follow the example set by the .ini file. Search for brows_cap and delete the semi-colon (;) before it to uncomment it. The various lines should now look like: doc_root = ; the root of the php pages, used only if nonempty extension_dir = c:\progra~1\PHP ; directory in which the loadable extensions (modules) reside browscap = c:\windows\system\inetsrv\browscap.ini Move the php.ini file to C:\WINDOWS\ Move the php4ts.dll msvcrt.dll files to C:\WINDOWS\SYSTEM\. If there is already a msvcrt.dll, you don't need to replace it. Now you need to tell the server what file extensions to associate with PHP. Create a file PHP.reg, enter the following text (except the start/end designations), save, and run it to add the keys to the Registry, as in the Perl installation. * start file: PHP.reg * REGEDIT4 [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\W3SVC\Parameters\S cript Map] .php=C:\\Program Files\\PHP\\php4isapi.dll .phtml=C:\\Program Files\\PHP\\php4isapi.dll * end file: PHP.reg * Reboot (things might work now, but I doubt it.) Time for a test. Enter the following code into a text editor and save it as test.html test.php test.phtml (or whatever other file extensions you associated with PHP). * start file: test.html, .php, .phtml * html head titleExample/title /head body Hello, I'm not a script!/P script language=php echo(Hi, I'm a PHP script!); /script /body /html * end file: test.html, .php, .phtml * Place all the files in your PHP install directory. The go to the URLs http://localhost/php/test.html http://localhost/php/test.php http://localhost/php/test.phtml If you set up the PHP virtual directory as described in the PWS installation, you will load the test file and execute the php code. The output will look like: Hello, I'm not a script! Hi, I'm a PHP script! for the .php and .phtml files. Only the 'not a script' text will appear for the .html file. If the scripts don't work, make sure you've got Execute privilege set in PWS for the folder the files are in; make sure you're browsing via the server (http://) and not the file directory (C:\My Documents); make sure the registry keys were set correctly. If it worked, congratulations, you've installed PHP! I now recommend rebooting (yes, again) and then testing everything again. Previous Comments: [2002-02-22 12:20:33] [EMAIL PROTECTED] The bug system is not the appropriate forum for asking support questions. For a list of a range of more appropriate places to ask for help using PHP, please visit http://www.php.net/support.php Very likeley to be a configuration error. [2002-02-22 04:06:35] [EMAIL PROTECTED] downladed and unpacked php-4.1.1-Win32 and php-4.1.1-installer apps from PHP site. Installed using automatic method and checked entries under manual method in registry. Obtained MDAC latest version 2.7 and MDAC checker programfrom microsoft for PWS ran same and brought up to date on PWS standard install APP from New win98 2nd ed CD. (registered ver). Tried command line PHP -i and obtained output file. stored local. viewed in HTML browser as htm file. All seems OK wrote first php file. As example and tried in browser. Result CGI Error The specified CGI application misbehaved by not returning a complete set of HTTP headers. The headers it did return are: rest of page blank. simplehello world example. downloaded and tried to run iiscfg.exe after studying PHP site. This fails on Shrinker error - Dispatcher initialisation error 6 Checked around and found others were having same problem. my php.ini is disturbingly sparse, so I
