php 4.3.10 -> should we upgrade?

Next topic

Author	Message
Georg Franz	Thursday 16 December 2004 5:00:34 am Hi, php 4.3.10 is out and solves a reference issue: http://bugs.php.net/bug.php?id=28325 But I think, that's not the bug, ez is fighting with. Nevertheless I am asking: Is it recommended to upgrade to 4.3.10 in the view of using ez3rc2? Best wishes, Georg. -- http://www.schicksal.com Horoskop website which uses eZ Publish since 2004
Hans Melis	Thursday 16 December 2004 5:26:54 am PHP 4.3.10 also contains a foreach optimization backported by Derick. http://ez.no/community/blog/foreach_performance_improvement_backport I've installed the new PHP on my workstation and haven't found a reason why not to upgrade. Hans http://blog.hansmelis.be
Kenneth Colwell	Friday 17 December 2004 10:09:44 am Hi, I just attempted to upgrade to php 4.3.10 and after doing the upgrade and restarting apache the non ezpublish portions of my site worked fine but all of my ezpublish pages came up blank. Nothing unusual could be found in apache's error logs or the ezpublish error logs. Does anyone have any ideas what is wrong? Thanks, Ken Colwell
Georg Franz	Friday 17 December 2004 11:12:58 am Hi, I've found a notice from amos in the trunk-code that the current php-version (4.3.10) has a problem with var_export(). So, maybe that causes the problem? Best wishes, Georg. -- http://www.schicksal.com Horoskop website which uses eZ Publish since 2004
Gabriel Ambuehl	Friday 17 December 2004 12:03:30 pm Generally speaking: Yes you should, as apparently there are major security risks in older PHP versions. Edit: ezpublish 3.5.0RC2 seems to work just fine on my PHP 4.3.10 (Apache 1.3, FreeBSD) Visit http://triligon.org
Tony Wood	Saturday 18 December 2004 6:05:20 am Hi Georg, We are testing PHP 4.3.10 at the moment. We have not found any major issues in < 3.5 yet. If we do we will post them here. tony Tony Wood : twitter.com/tonywood Vision with Technology Experts in eZ Publish consulting & development Power to the Editor! Free eZ Training : http://www.VisionWT.com/training eZ Future Podcast : http://www.VisionWT.com/eZ-Future
Kenneth Colwell	Saturday 18 December 2004 1:29:27 pm I was having the problem above using the following: ezpub Version 3.4.4 (3.4.4) SVN revision 9297 php 4.3.10 Extensions: yp, xml, wddx, tokenizer, sysvshm, sysvsem, standard, sockets, shmop, session, pspell, posix, pcre, overload, mssql, mbstring, iconv, gmp, gettext, gd, ftp, exif, domxml, dio, dbx, dba, curl, ctype, calendar, bz2, bcmath, zlib, apache2filter, imap, ldap, mysql, odbc Safe mode is off. Basedir restriction is off. Global variable registration is off. File uploading is enabled. Maximum size of post data (text and files) is 200M. Script memory limit is 400M. Maximum execution time is 180 seconds. PHP Accelerator: ionCube PHP Accelerator: 1.3.3r2
Peter Gray	Thursday 23 December 2004 5:07:03 am Hmmm, not sure if my last message was actually posted, as it was sent from work and we have occasional problems with online forms, so I've nipped home to try again. My hosting provider upgraded to PHP 4.3.10 this morning and instantly three sites stopped working, all with the same errors showing. Lots of: Notice: Array to string conversion in /home/.../public_html/lib/ezfile/classes/ezdir.php on line 272 and lots of (but not quite as much) of: Notice: Array to string conversion in /home/.../public_html/lib/ezfile/classes/ezdir.php on line 288 Then once at the end: Notice: Array to string conversion in /home/dunbargr/public_html/lib/ezutils/classes/ezexecution.php on line 78 Any clues as to the best course of action? -- Pete
Peter Gray	Thursday 23 December 2004 7:36:44 am Following up my own post now -- back at work. Everything now seems to be working again. Which has just left me even more confused. -- Pete
Hapee de Groot	Thursday 23 December 2004 7:52:42 am I found empty pages after upgrading but after stopping Apache, emptying the tmp directory used by Ioncube, I had all my pages again, so no problem.
Andre Felipe Machado	Monday 24 January 2005 6:43:31 pm Hello, My hosting upgraded the php and my site showed the same error. I pointed to them this url, with its hints about tmp files, and now the site is almost back. I am still unable to login at admin interface and some public links are crazy, returning to home page. I guess that a cache clear is needed. But how to clear without admin acess? Could I manually erase the /var/cache directories? Thanks. Andre Felipe --- A Debian user never dies. Issues a last command: shutdown -h now http://www.techforce.com.br
Eirik Alfstad Johansen	Monday 24 January 2005 11:14:26 pm Hi Andre, Try: ./bin/shell/clearcache.sh --clear-all from the command line. Sincerely, Eirik Alfstad Johansen http://www.netmaking.no/
Andre Felipe Machado	Sunday 30 January 2005 4:41:05 am Hello, Many thanks for your answer. Unfortunatelly, my hosting provider also closed my ssh access.... And he is not willing to reopen for my account or any other on shared hosting plans. I used the cpanel filemanager to manually erase the files. But hosting new safe_mode configs are blocking ezpublish to work. This is the second time huge server modifications, not previously told, break my site. Enough. It is time to move to another hosting, I guess. I am contacting firebright. Thanks. Andre Felipe --- A Debian user never dies. Issues a last command: shutdown -h now http://www.techforce.com.br

eZ debug

Timing:	Jan 18 2025 15:01:39
Script start
Timing:	Jan 18 2025 15:01:39
Module start 'layout'
Timing:	Jan 18 2025 15:01:39
Module start 'content'
Timing:	Jan 18 2025 15:01:40
Module end 'content'
Timing:	Jan 18 2025 15:01:40
Script end

Main resources:

Total runtime	1.1268 sec
Peak memory usage	4,096.0000 KB
Database Queries	103

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0075	589.0469	152.6250
Module start 'layout'	0.0075	0.0037	741.6719	39.4453
Module start 'content'	0.0112	1.1141	781.1172	969.0938
Module end 'content'	1.1254	0.0014	1,750.2109	28.1563
Script end	1.1267		1,778.3672

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0046	0.4121	16	0.0003
Check MTime	0.0018	0.1577	16	0.0001
Mysql Total
Database connection	0.0009	0.0796	1	0.0009
Mysqli_queries	1.0227	90.7621	103	0.0099
Looping result	0.0012	0.1086	101	0.0000
Template Total	1.0928	97.0	2	0.5464
Template load	0.0021	0.1849	2	0.0010
Template processing	1.0907	96.7948	2	0.5453
Template load and register function	0.0001	0.0076	1	0.0001
states
state_id_array	0.0016	0.1388	1	0.0016
state_identifier_array	0.0014	0.1234	2	0.0007
Override
Cache load	0.0019	0.1727	95	0.0000
Sytem overhead
Fetch class attribute can translate value	0.0006	0.0550	10	0.0001
Fetch class attribute name	0.0013	0.1178	19	0.0001
XML
Image XML parsing	0.0057	0.5081	10	0.0006
class_abstraction
Instantiating content class attribute	0.0000	0.0030	21	0.0000
General
dbfile	0.0033	0.2932	45	0.0001
String conversion	0.0000	0.0008	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
8	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
13	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
24	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
13	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	content/datatype/view/ezxmltags/literal.tpl	<No override>	extension/community/design/standard/templates/content/datatype/view/ezxmltags/literal.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 61 Number of unique templates used: 7

Time used to render debug report: 0.0001 secs