Some questions about beta 2

[ferrante2]

Hi.

I have been using Xataface for a while. I am very happy with it, it is really powerful and flexible. I updated to beta 2 recently (I was using 0.6), and now I have some questions. Maybe they are not specific for beta 2, though.

First, when I use the group directive in fields.ini (with or without fieldgroup), it seems impossible to order the groups; they neither follow the "order" directive. Furthermore, if the primary key is added to any group, the detail view does not show any field.

Other thing that should be fixed is that the page numbers in the list view just show 1-9. When you advance, it does not show further numbers. This was asked before (http://xataface.com/forum/viewtopic.php ... highlight=), about 0.6, so I wonder if the bug is still there or if I did anything wrong when updating.

And last, I have miss the + for showing details in the list view. The list only shows an empty cell.

Very good work.

Felipe

[shannah]

when I use the group directive in fields.ini (with or without fieldgroup), it seems impossible to order the groups; they neither follow the "order" directive. Furthermore, if the primary key is added to any group, the detail view does not show any field.

For better or worse, I have changed the way that field groups work for 1.0. You should notice some improvements to the ordering of groups with beta 3 (I just released it 10 minutes ago), but they still won't work quite the same way.

Groups now must be ordered in the [fieldgroup:...] section for that group, rather than taking on the order of the first field in the group.

Other thing that should be fixed is that the page numbers in the list view just show 1-9. When you advance, it does not show further numbers. This was asked before (http://xataface.com/forum/viewtopic.php ... highlight=), about 0.6, so I wonder if the bug is still there or if I did anything wrong when updating.

Yes.... This still isn't fixed in beta 3. I have now added it to the issue tracker:
http://bugs.weblite.ca/view.php?id=198

[ferrante2]

Odd... I just updated to beta 3, but field order is not working yet.
My fields.ini starts with:
[fieldgroup:general]
label = "General"
order = 1

[fieldgroup:envase]
label = "Envase"
order = 2

[fieldgroup:localizacion]
label = "Localización"
order = 3

[fieldgroup:otros]
label = "Otros"
order = 4

And this is a typical field description:

[TipoMuestra]
widget:type = select
vocabulary = Muestras
group = general
order = 7
widget:label = "Tipo de muestra"
widget:description = "<br>Elija el tipo de muestra"
validators:required = true
filter = 1

Again, if I include the primary key in any group, nothing appears in the details view.

Worse yet, I obtain a blank screen when I try to edit a registry (in Firefox). Safari returns a kCFErrorDomainCFNetwork:302 error (?). When I remove the group directive, everything works again.

Do you have any idea why the + buttons for details in list view have dissapeared? I had them until I updated to v. 1. There is no problem with my browser, since they appear and work in several parts of your site.

Well, this is no really critical for me, but it would be nice to have the groups and the + back. Thank you for the effort!

[shannah]

Do you have any idea why the + buttons for details in list view have dissapeared? I had them until I updated to v. 1. There is no problem with my browser, since they appear and work in several parts of your site.

The preference setting 'disable_ajax_record_details' allows you to enable this.

e.g. in your conf.ini file in the [_prefs] section add:

Code: Select all

[_prefs]
    disable_ajax_record_details=0



[shannah]

Worse yet, I obtain a blank screen when I try to edit a registry (in Firefox). Safari returns a kCFErrorDomainCFNetwork:302 error (?). When I remove the group directive, everything works again.

It is difficult to diagnose these issues. Essentially this type of problem is a segmentation fault in PHP (and generally an obscure bug in PHP). To find workarounds I generally need to step through the code line by line..

However this may be similar to this issue:
http://bugs.weblite.ca/view.php?id=179

You can download the patch against 1.0-beta-3 in the issue tracker.

[shannah]

Again, if I include the primary key in any group, nothing appears in the details view.

I can't seem to reproduce this behavior. Can you give me some details about your primary key column (e.g. data type, widget type) so I can try further tests.

It works fine with an auto increment primary key with hidden widget.

-Steve

[shannah]

Odd... I just updated to beta 3, but field order is not working yet.

I can't seem to reproduce any problems here either.

e.g.

Code: Select all

[fieldgroup:groupa]
    order=1

[fieldgroup:groupb]
    order=2

[field1]
    group=groupa

[field2]
    group=groupb



Has groupa appearing before groupb

However

Code: Select all

[fieldgroup:groupa]
    order=2

[fieldgroup:groupb]
    order=1

[field1]
    group=groupa

[field2]
    group=groupb



Has groupb appearing before groupa

-Steve

[ferrante2]

Hi.
My primary key is an integer with auto-increment. In fields.ini it is configured as:
[doseID]
widget:label="Orden"
order=1
visibility:list=0
widget:type="hidden"
visibility:browse=0

Nevertheless, visibility:list works, but visibility:browse does not

I do not need groups by now, so I will do without them. Everything seems to work fine except for that.

Thank you for your really quick responses.