I am S.Pranavan, a B.Sc. computer engineering undergraduate from
University of Peradeniya, Sri Lanka.I am currently following third year of my degree and I have proficient knowledge in PHP and JavaScript.I would like to start working on open source developments and I found phpMyAdmin is thebest place for a good start. I have been using phpMyAdmin for more than two years and I am very much willingto get involved in the development process of phpMyAdmin.Along with me some of my friends also would like to join the development team of phpMyAdmin.Can you guide us to get started with the project?
Best Regards,S.Pranavan
Hi you lot,
I've been ill recently and just sort of dropped everything, my phone and
this "clutter" thing purging anything I don't read after a while have
slowed me down.
What happened with that? I'm sort of hoping everything froze and nothing
happened while I was gone but I doubt that happened.
Alec
Hi,
I noticed the phpMyAdmin-4.6.3-all-languages.tar.bz2 in the downloads
section is corrupt (untarring doesn't work, the file is also much too small
: 32 KB vs ~8 MB)
--
Kind regards,
Dieter Adriaenssens
The phpMyAdmin project announces the release of phpMyAdmin versions
4.0.10.16, 4.4.15.7, and 4.6.3. All versions feature many security fixes
that are announced as PMASA-2016-17 through PMASA-2016-28 which are
posted at https://www.phpmyadmin.net/security/
Furthermore, version 4.6.3 includes the regularly scheduled maintenance
improvements and bug fixes. In addition to bugs affecting particular
version combinations, some of the other bugs fixed include:
* Fixing cookie path on Windows
* Fix MySQL SSL connections with some PHP versions
* Fix listing of routines for non-privileged user
As well as several more. Complete details are available in the ChangeLog.
We highly recommend updating all affected versions immediately.
Downloads are available at https://www.phpmyadmin.net/downloads
We thank the security researchers who found and reported these flaws.
The phpMyAdmin team
To be upfront and direct, I'm not a huge fan of having a scheduled
release. I think we should release 4.6.3 when it has enough fixes to
justify a new release or if a major usability issue is fixed, not just
because a date on the calendar is approaching. On the other hand, it can
help web hosts to know when a maintenance release is coming, although it
seems many don't generally upgrade unless there's a security problem.
According to our milestone, 4.6.3 is due for release in just over a
week. I don't think we're ready for 4.6.3 because there haven't been a
lot of fixes in 4.6.3. I'd rather put it off, perhaps for a month,
depending how things go, basically until there are more fixes justifying
a release.
Hi,
The server variables are not configurable because of javascript.
The Jquery's .text() function is not useable in this HTML structure because
it will collect all '\n's and spaces which are inside the tr element with
'class=.var-name'. This is why varName will be "
____________
____________slow_query_log________
________"
POST request:
ajax_request=true&type=setval&varName=%0A____________%0A____________slow_query_log________%0A________&varValue=off&_nocache=1465473774538469936
Query SHOW GLOBAL VARIABLES WHERE Variable_name='
____________
____________slow_query_log________
________'
My solution is find the span element inside the tr and use title of this
span.
/js/server_variables.js
function editVariable(link) {
var $cell = $(link).parent();
var $valueCell = $(link).parents('.var-row').find('.var-value');
-- var varName = $cell.parent().find('.var-name').text().replace(/ /g,
'_');
++ var TvarName = $cell.parent().find('.var-name');
++ var varName = TvarName[0].children[0].title.replace(/ /g, '_');
var $mySaveLink = $saveLink.clone().show();
Query SHOW GLOBAL VARIABLES WHERE Variable_name='slow_query_log'
POST request:
ajax_request=true&type=setval&varName=slow_query_log&varValue=on&_nocache=1465473600358154148
Regards,
Szabolcs
