For bug reports. I currently group bug incidents that occur on the
same file in the same line into one bug report since they are most
likely the same. I do not however take into account phpma version.
should I only group bug incidents from the same file and line if they
share a phpma version?. I looked at [0]. I am not sure how they group
bug incidents but every report has a single kernel version. I think I
should do the same and rely on manual interference by developers to
mark the bug reports in different versions as the same.
[0] http://oops.kernel.org/browse-reports/
--
Mohamed Ashraf
Hi,
I'm seeing an odd behavior with Designer. Trying to create a relation,
I click the Create relation button (about four in from the left in the
menu), then select a table's primary key and then click on a column in
a different table. I get a prompt: "Create relation OK / Cancel" --
selecting OK does not create the relation and instead opens a new
browser window with the main phpMyAdmin page loaded. Does anyone else
see this behavior?
We have deployed an early version of the error reporting server at
[0]. while there are still a few things not implemented the view will
not change much from what is currently there. I have filled the
database with fake reports to help you see how things will look in the
real world.
Since I am finishing up with the features I need feedback on the
currently implemented functionality and if anyone has any idea on how
to do something differently please feel free to say it.
currently there is a list of reports and clicking on the id of the
report you get redirected to a view containing the summary of the
related reports. you can submit error reports to the sourceforge bug
tracker.
if anyone thinks there is missing functionality or if something needs
to be displayed in a better way, please tell me so as to schedule the
change in the coming weeks.
[0] http://reports.phpmyadmin.net/
--
Mohamed Ashraf
> -----Original Message-----
> From: Mohamed Ashraf [mailto:mohamed.ashraf.213@gmail.com]
> Sent: Saturday, August 3, 2013 3:53 PM
> To: phpmyadmin-devel(a)lists.sourceforge.net
> Subject: [Phpmyadmin-devel] Need feedback on error reporting server
>
> We have deployed an early version of the error reporting server at [0].
while
> there are still a few things not implemented the view will not change much
> from what is currently there. I have filled the database with fake reports
to
> help you see how things will look in the real world.
>
> Since I am finishing up with the features I need feedback on the currently
> implemented functionality and if anyone has any idea on how to do
something
> differently please feel free to say it.
>
> currently there is a list of reports and clicking on the id of the report
you
> get redirected to a view containing the summary of the related reports.
you
> can submit error reports to the sourceforge bug tracker.
>
> if anyone thinks there is missing functionality or if something needs to
be
> displayed in a better way, please tell me so as to schedule the change in
the
> coming weeks.
>
> [0] http://reports.phpmyadmin.net/
>
> -- Mohamed Ashraf
>
Hello Mohamed,
Thanks for this! It looks nice and works properly.
Things I have noticed, from a user interface perspective:
1. The drop downs for filtering, can you place them directly below the
headline?
Like this:
ID ....... Reference Name ...
[ v] .... [ v ] ...
2. Can you allow the whole "ID" cell to be clickable?
(using "display: block" for the link)
This will make clicking easier, especially for low numbers.
3. The Sourceforge link "Sourceforge Report [Submit report] " does not work
yet.
I read: Error: The requested address
'/source_forge/new_ticket/2?url=%2Fsource_
forge%2Fnew_ticket%2F2' was not found on this server.
Best,
JM
Hi devs,
I am refactoring tbl_columns_definition_form.inc.php. At
https://github.com/phpmyadmin/phpmyadmin/blob/master/libraries/tbl_columns_…
the
$fields_meta variable is checked for moving, load all available column
names. But as far as I could find this feature is set in table structure
tab and is handled by tbl_structure.php . Is this dead code ?
Regards Supun.
Hi all,
The error reporting server is based on cakePHP which is licensed under
MIT license [0].
It is compatible with GPL, the license under which phpMyAdmin is licensed.
Under which license shall we license the code that is added to create
the error reporting server?
Both licensing under GPL or MIT is a possibility.
It makes sense to license under GPL because phpMyAdmin itself is
licensed under GPL.
But it might be easier to use the MIT license, especially for files
with mixed copyright (original cakePHP files being modified creating
the error reporting server).
BTW : Conservancy allows us to license under the MIT license.
Anyway, there should be a license file (LICENSE and/or COPYING) in the
root dir of error reporting server repo.
And the files added to create the error reporting server should
contain a header indicating the licensing info.
[0] http://opensource.org/licenses/mit-license.php
--
Kind regards,
Dieter Adriaenssens
I noticed that the selflink is not appearing in some pages like for
example tbl_addfield.php. It took me a couple of hours to find out why
and it was because a global variable was set which was
$checked_special it was set in the checkParameters method in
Util.class.php I am not sure what this variable means.
anyways this variable gets checked in getDisplay in the footer class
and if it is true the self link is not shown.
can someone tell me if this is correct behavior and why should we not
show the self link in those pages. I need the self link to get the
current token so it is important that the self link should be
available in all pages.
--
Mohamed Ashraf