Developers

developers@phpmyadmin.net

7004 discussions

[Phpmyadmin-devel] Bug #3881 Escaped html in error message
by Chirayu Chiripal 25 Jul '14

25 Jul '14

Hi, I was able to reproduce this bug #3881 in QA_4_0 but can't reproduce this anymore in QA_4_2, so it seems that it is fixed now (not sure in which version exactly). Can anyone else reproduce this bug on QA_4_2 or master? If no one is able to reproduce this anymore then maybe we can close this ticket [1]. [1]: https://sourceforge.net/p/phpmyadmin/bugs/3881/ -- Regards, Chirayu Chiripal phpMyAdmin Intern - Google Summer of Code 2014 https://chirayuchiripal.wordpress.com/

2 1

Re: [Phpmyadmin-devel] How hard is the requirement for MySQL >= 5.5 in phpMyAdmin?
by Marc Delisle 22 Jul '14

22 Jul '14

Le 2014-07-22 11:13, Robert Scheck a écrit : > Hello Marc, > > On Tue, 22 Jul 2014, Marc Delisle wrote: >> from my experience, only some specific features will break. I don't >> think that the phpMyAdmin team has collected a list of these features. > > something that really wonders me is that this enforcement happened during > the 4.2.x cycle...which is supposed to be a stable release series, no? Or > why did it happen during 4.2.x? IIRC, it was caused by something we noticed after 4.2.x started its existence, so we preferred to notice users about it. > >> For big databases, however, there will be a performance problem, as >> phpMyAdmin relies extensively on information_schema, whose performance >> with MySQL < 5.5 is worse. > > How do you define "big databases"? About how many tables or which size > would that be? For me it is a trade-off between sticking to 4.0.x or to > accept non-perfect but acceptable performance for e.g. nearly all cases > vs. it is always slow and quite unusable (aside of maybe some non-working > specific features). Thousands of tables and/or grants are definitely a problem. > > Or is the issue that the performance with MySQL < 5.5 is generally worse > and you just "recommend" to use a recent MySQL? But then using the latest > phpMyAdmin wouldn't then make things more bad at least :) You really feel the performance problem once you reach a certain amount of tables. > >> Maybe we can extend phpMyAdmin's 4.0 life (for security fixes). > > Depending on above (and given the fact that I do not have any clue if this > is realistic) I wonder if there is a chance to conditionalize support for > MySQL < 5.5, so to disable some specific features in phpMyAdmin simply in > the code? Not really, as the navigation panel (left) is the one suffering the most from older MySQL versions. > > > Greetings, > Robert > -- Marc Delisle | phpMyAdmin

1 0

Re: [Phpmyadmin-devel] How hard is the requirement for MySQL >= 5.5 in phpMyAdmin?
by Marc Delisle 22 Jul '14

22 Jul '14

Le 2014-07-22 05:09, Robert Scheck a écrit : > Hello phpMyAdmin developers, > > how hard is the requirement for MySQL >= 5.5 in phpMyAdmin? Actually, I am > the package maintainer of phpMyAdmin in Fedora and EPEL. EPEL is an add-on > repository for Red Hat Enterprise Linux and CentOS (and other derivates). > > However, Red Hat Enterprise Linux 6 is shipping only MySQL 5.1 and Red Hat > Enterprise Linux 5 is only shipping MySQL 5.0. And unfortunately since the > phpMyAdmin 4.2.3 release you are enforcing MySQL >= 5.5 as requirement - > which breaks both of them. > > We could stay with phpMyAdmin 4.0.x for both, but 4.0.x goes EOL already in > less than 6 months - quite early given that RHEL 6 is supported till 2020 > (and RHEL 5 until end of March 2017). I do not expect that you support old > releases same long like that. However it would be really helpful can give > some details why the requirement is enforced and what could break with an > older version (some specific features, mostly everything, everything?) of > MySQL. Hi Robert, from my experience, only some specific features will break. I don't think that the phpMyAdmin team has collected a list of these features. For big databases, however, there will be a performance problem, as phpMyAdmin relies extensively on information_schema, whose performance with MySQL < 5.5 is worse. Maybe we can extend phpMyAdmin's 4.0 life (for security fixes). > > Thank you very much for your time already and hope to hear some details :) > > > Greetings, > Robert > -- Marc Delisle | phpMyAdmin

1 0

[Phpmyadmin-devel] phpMyAdmin 4.0.10.1, 4.1.14.2 and 4.2.6 are released
by Marc Delisle 17 Jul '14

17 Jul '14

Welcome to phpMyAdmin 4.0.10.1, 4.1.14.2 and 4.2.6, which are bugfix versions containing security fixes. The announcements for the security fixes will be published soon on http://www.phpmyadmin.net/home_page/security/ as PMASA-2014-4 to PMASA-2014-7. Details will appear on http://phpmyadmin.net. You can also visit https://sourceforge.net/projects/phpmyadmin/files to download. The phpMyAdmin team

1 0

[Phpmyadmin-devel] Should a user be able to remove their own privileges?
by Isaac Bennetch 17 Jul '14

17 Jul '14

Bringing this to phpmyadmin--devel for further discussion. This is specifically related to implementing feature request 1488 "User privilege tab not shown in all relevant cases" [1] On 7/16/14, 4:00 PM, Chirayu Chiripal wrote: > Does it makes sense, to allow a user to revoke some of the global > privileges from himself? I think ideally, we would allow this but display a message warning that it's a bad idea. Something like "You are attempting to remove privileges from the user with which you are currently logged in. This is generally a bad idea and might result in you being unable to log in or change privileges. Are you sure you wish to remove these privileges?" I can't think of a scenario when a user would actually want to do this; but just because it's a bad idea doesn't mean we should prevent the user from doing it, right? Or in this case, is it reasonable to disallow this action? What does everyone else think? 1 - https://sourceforge.net/p/phpmyadmin/feature-requests/1488/

4 4

[Phpmyadmin-devel] [SPAM] cyber_jihad@ymail.com - 7/17/2014 8:18:20 PM
by cyber_jihad 17 Jul '14

17 Jul '14

http://www.pianissimo-sxm.com/vn/liybntah.ydibozcficumys

1 0

[Phpmyadmin-devel] [SPAM] cyber_jihad@ymail.com - 7/17/2014 8:17:47 PM
by cyber_jihad 17 Jul '14

17 Jul '14

http://pcjansen.nl/wspbn/gpevsfggyldxmie.kvpmegqqmpta

1 0

[Phpmyadmin-devel] Fix in multi versions
by Hugues Peccatte 15 Jul '14

15 Jul '14

Hi everyone, I think that I've found a fix for #4459. This bug is in 4.0, 4.1, 4.2 and master. In which version should I fix it please? 4.2 and then it will be merged in other branches? or 4.0 and then it will be merged in other branches? or a pull request for each one? Thanks for your answer ! Hugues.

2 2

[Phpmyadmin-devel] Access to Server > Users > User groups tab
by Chirayu Chiripal 14 Jul '14

14 Jul '14

Hi, Is everyone allowed to access Server > Users > User groups tab ? And if yes, Why? -- Regards, Chirayu Chiripal phpMyAdmin Intern - Google Summer of Code 2014 https://chirayuchiripal.wordpress.com/

2 4

[Phpmyadmin-devel] [Console] Help, about AJAX callback
by Edward Cheng 13 Jul '14

13 Jul '14

Hi, Till now, new console will log browse-generated-queries, but only happend at global AJAX handler, because I add some code in global AJAX handler: if(PMA_console && PMA_console.isEnabled) { PMA_console.ajaxCallback(data); } We can copy code above to everywhere--to every custom ajax response handler--it's terrible, do we have a better solution? Thanks -- Edward Cheng

2 2

Jump to page:

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