updated by @blindmime: 12/07/13 10:15:14AM
JAMROOM
Form Designer Language
I'm seeing different behavior when adding a custom field via the form designer. When I add the field, it's placing language string ids in label, sublabel and help fields. I can change these, but when I go to the module's language settings I see the form designer has created duplicate fields.
updated by @blindmime: 12/07/13 10:15:14AM
updated by @blindmime: 12/07/13 10:15:14AM
The screen shot above shows 6 language string fields created for a single Event custom field named event_file.
Also, there is no page navigation dropdown menu in the Blog module Language tab (see below). The Event module Language tab does have a page navigation dropdown.
updated by @blindmime: 11/01/13 05:19:29AM
Also, there is no page navigation dropdown menu in the Blog module Language tab (see below). The Event module Language tab does have a page navigation dropdown.
updated by @blindmime: 11/01/13 05:19:29AM
I tested form designer with a different module (blog) and while it enters language string IDs into fields, it doesn't create duplicate language string fields. Perhaps this is intended, however, I'm not sure what entering the IDs as values accomplishes.
updated by @blindmime: 11/01/13 05:29:18AM
updated by @blindmime: 11/01/13 05:29:18AM
blindmime:
I'm seeing different behavior when adding a custom field via the form designer. When I add the field, it's placing language string ids in label, sublabel and help fields. I can change these, but when I go to the module's language settings I see the form designer has created duplicate fields.
I'm seeing different behavior when adding a custom field via the form designer. When I add the field, it's placing language string ids in label, sublabel and help fields. I can change these, but when I go to the module's language settings I see the form designer has created duplicate fields.
This sounds correct - there is going to 3 (title, sub title and help) created for the "blog create" form, and then 3 more created for the "update form". The blog module has 2 forms that can be customized (create and update), and when you create a new custom form field there is a checkbox that says "add to update form" - if you check that then 2 custom designer form fields are created.
Let me know if that helps.
Thanks!
--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
blindmime:
Also, there is no page navigation dropdown menu in the Blog module Language tab (see below). The Event module Language tab does have a page navigation dropdown.
Also, there is no page navigation dropdown menu in the Blog module Language tab (see below). The Event module Language tab does have a page navigation dropdown.
The page select jumper only shows up when there is more than like 5 pages - otherwise you just get prev/next buttons. No need for a page jumper when there is only a couple pages.
Let me know if that helps.
--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
I hate clicking on the right arrow more than once. I'm old, I need to maximize my time whenever possible. I don't have much of it left.
I just check the source code and as soon as you hit 4 pages the jumper will show, which means it is the same number of clicks to get to page 3. I can change it to be 3 pages though (showing it for 2 doesn't make sense) as that might be a bit faster if you know you have to skip page 2.
Thanks!
--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
Thanks!
--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
I think I'd have a drop down whenever there are multiple pages (i.e., at 2). While at 2, it's not more efficient to use the dropdown, it keeps the navigation consistent. I expect the drop to be there whether it's more useful or not. I get in the habit of using it if it's there sometimes, so I expect to be there all the time and am put off when it's not. Just my thoughts.
Also, I would add a button, around where the forward button resides, that goes to the last page. That's actually what the drop down menu is used most often to do. For instance, I've just created a custom form field and I go to the module's Language Settings and want to edit them -- I'll want to go to the last page of language settings.
Also, I would add a button, around where the forward button resides, that goes to the last page. That's actually what the drop down menu is used most often to do. For instance, I've just created a custom form field and I go to the module's Language Settings and want to edit them -- I'll want to go to the last page of language settings.
