Developers November 2003

developers@phpmyadmin.net

8 participants
13 discussions

[Phpmyadmin-devel] On Documentation.txt
by Alexander M. Turek 04 Dec '03

04 Dec '03

Hi list, It's just a thought, but couldn't the Documentation.txt file be created by create_release.sh automatically when building a distribution kit? I can't see the point of having this file inside the CVS tree since it contains redundant information. Regards, -- Alexander M. Turek <rabus(a)users.sourceforge.net> _ __ __ _ _ _ _ __ | |__ _ __ | \/ |_ _ / \ __| |_ __ ___ (_)_ __ | '_ \| '_ \| '_ \| |\/| | | | | / _ \ / _` | '_ ` _ \| | '_ \ | |_) | | | | |_) | | | | |_| |/ ___ \ (_| | | | | | | | | | | | .__/|_| |_| .__/|_| |_|\__, /_/ \_\__,_|_| |_| |_|_|_| |_| |_| |_| |___/ <http://www.phpmyadmin.net>

4 8

[Phpmyadmin-devel] require_once
by Michal Cihar 04 Dec '03

04 Dec '03

Hi all As we dropped PHP 3 support, we might also want to start use require_once to get rid of bug #571409. Does any of you know something that will need special care or just replacing every require with require_once should be okay? -- Regards Michal Cihar http://cihar.com

4 5

[Phpmyadmin-devel] 2.5.5-dev and browser transformations
by Marc Delisle 04 Dec '03

04 Dec '03

Hi, is it just me, or we have lost since the last few changes, the value of Browser transformations? MIME-type and transformation options are still there in the structure page of my field, but Browser transformation is blank. Marc

2 2

[Phpmyadmin-devel] demo problem (preg_match)
by Marc Delisle 04 Dec '03

04 Dec '03

Hi, can someone have a look at the demo problem: Warning: Compilation failed: missing terminating ] for character class at offset 13 in /home/groups/p/ph/phpmyadmin/htdocs/phpMyAdmin/libraries/common.lib.php on line 1108 This does not happen on my server. Marc

3 2

[Phpmyadmin-devel] Re: PHP 3 Compatibility
by Michal Cihar 04 Dec '03

04 Dec '03

Hi all moving this duscussion to list, because I thing it should be there :-) Original message (Garvin Hicking, 19.11.2003 11:57): > a) Wait until after 2.5.5 RC1 and apply changes to HEAD then. > Pro: No hurry for now. > Con: I might not have the time then :) No need to wait, if you have time :) > b) Branch off a QA_2_5_5 tree now, make the RC out from that branch > and apply my changes to HEAD now. > Pro: Work can start immediately, a quite stable 2.5.5 release. > Con: Later PHP4-enabled release We will say that we don't support php3, but the code will still contain many things for php3... > c) Branch of a PHP4_QA tree, apply my changes to that branch, merge > the changes to HEAD later on. > Pro: Agitate on a 'secure' branch, work can start immediately > Con: Maybe harder to merge afterwards, less people testing it (because > CVS snapshot is from HEAD, and people using CVS directly will most > likely use HEAD as well). People expect HEAD to be the currently developped one, changing this confuses them. > d) Make changes to HEAD. Make 2.5.5 the first PHP4-release, thus > moving the 2.5.5 RC1 about 1-2 weeks later and having huge changes in > that 2.5.5 release. > Pro: Making a real worthy 2.5.5 release? Work can start immediately. > Larger testing user base. > Con: No 2.5.5 release with the latest features, moved schedule. Good solution. If there are not any things that are worth of releasing quickly, I'd prefer this. -- Regards Michal Cihar http://cihar.com

4 5

[Phpmyadmin-devel] demo site and preg_match
by Marc Delisle 27 Nov '03

27 Nov '03

Hi, Warning: Unknown modifier '%' in /home/groups/p/ph/phpmyadmin/htdocs/phpMyAdmin/main.php on line 245 Marc

1 0

[Phpmyadmin-devel] (no subject)
by Alexander M. Turek 25 Nov '03

25 Nov '03

Hi list, I just thought about a small optimization that could make our lives a little easier: As far as I can see, footoer.inc.php is always the last page to be called. This is why we find much code like this: include('./footer.inc.php'); exit; imho, we should be able to put the exit call into footer.inc.php, so that we do not always have to call it manually after having displayed the footer. Comments? Regards, -- Alexander M. Turek <rabus(a)users.sourceforge.net> _ __ __ _ _ _ _ __ | |__ _ __ | \/ |_ _ / \ __| |_ __ ___ (_)_ __ | '_ \| '_ \| '_ \| |\/| | | | | / _ \ / _` | '_ ` _ \| | '_ \ | |_) | | | | |_) | | | | |_| |/ ___ \ (_| | | | | | | | | | | | .__/|_| |_| .__/|_| |_|\__, /_/ \_\__,_|_| |_| |_|_|_| |_| |_| |_| |___/ <http://www.phpmyadmin.net>

2 1

[Phpmyadmin-devel] Comments wanted
by Michal Cihar 20 Nov '03

20 Nov '03

Hi * Could some of you look at RFE 832819 [1], I don't see anything useful in that so I'm going to reject it, but maybe I'm missing some genial idea there :-). 1. https://sourceforge.net/tracker/index.php?func=detail&aid=832819&group_id=2… -- Regards Michal Cihar http://cihar.com

1 0

[Phpmyadmin-devel] Big change php3 -> php
by Michal Cihar 18 Nov '03

18 Nov '03

Hi all as decided long time ago and finally approved today I switched all files in cvs from php3 to php. Mostly because of dropping support for old PHP and MySQL versions. Only thing you may need to change after cvs update is mv config.inc.developer.php3 config.inc.developer.php (if you are using this). -- Regards Michal Cihar http://cihar.com

1 0

[Phpmyadmin-devel] 2.5.5 schedule
by Marc Delisle 13 Nov '03

13 Nov '03

Hi, I suggest November 23rd. for 2.5.5-rc1. Marc

3 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

Developers November 2003