Download
2015-09-08, 09:15:36
Hi Bigin. I've been taking a look at this new version 2.1, and here is my bug report. Most of the problems I mention here were already present in the previous version; this time I've been doing more tests to try to better specify in what cases some of these errors occur. I hope you find it useful.
1 - If you double-click on a position number in the lists of categories and items, an input field appears, and you can change the position number there. But that field disappears when you click anywhere... It's Ok if it hides when you click outside the input, but not when you click inside the input, because you can't click the arrows to change the number, or select the old number with the mouse, or reposition the cursor with the mouse...
2 - The ascending or descending sort order you select in the settings for categories is not working. It's always descending. It works well with the items.
3 - The position data you see when you edit a category is not always correct. It seems it's not read from the <position> tag of the XML file. But it is correctly written... For example:
1-Create 3 categories: cat1, cat2, cat3.
2-Click on cat3 to edit. Change the position 3 to 4. Click on save.
3-Go back to the categories list. cat3 has position 4. In the XML, the tag <position> is 4. Everything is right so far.
4-Click on cat3 again. There's a 3 in the position field, instead of 4...
Position data is correctly saved from the categories editing screen, but it's not correctly read. What is shown there may be the ID...
With the items, I think it's the opposite... The position field in the item editing screen is not saved, but it's correctly read. Try this:
1-Create 3 items: item1, item2, item3.
2-Click on item3 to edit. Change the position 3 to 4. Click on save.
3-Go back to the items list. Item3 position is 3 instead of 4.
4-Double click on the Pos column in the items list and change the position. This time item3 position changes, and its value is correctly shown in the item editing screen.
4 - I think the numerical change of the position of an item should renumber the position of every item in that category, as with drag&drop. Suppose we have a category with these items:
Pos Name
1 item1
2 item2
3 item3
4 item4
If I change the position number of Item4 to 2 in the items list screen or in the item editing screen, this should be the result:
Pos Name
1 item1
2 item4
3 item2
4 item3
And if I change Item1 position to 13, this should be the result:
Pos Name
1 item4
2 item2
3 item3
4 item1
If it doesn't work like that, there may be problems like this:
1-Let's say I create 60 items in a category. I want them to be in a specific order, both in back-end and front-end.
2-Later, I want to put the last item at the beginning of the list. How can I do that? I can't drag&drop because I can't see more than 50 items at a time, and if I change the last item position to 1 numerically, I'll have 2 items with position number 1. When there are multiple items with the same position number, it seems they are sorted by the file name of the XML (I'm not sure...) In any case, I can't choose which of my two items with position 1 will be first and which will be the second... Decimal numbers are not accepted as position numbers (if they were accepted I could write 1 and 1.5), so the only solution I can see for this problem is to change by hand, one by one, the position numbers of the 60 items...
Categories have the same problem with manually changed position numbers. The only unproblematic way to custom sort items or categories is to always use drag&drop, and it is not always possible.
5 - If custom fields are deleted from a category, the data is not deleted from the XML files of items, creating unnecessarily large files that will need more RAM when processed. The way to solve this is to re-save all items, one by one. I think a safe and easy solution would be to add to the settings something similar to the "Retention period for the recoverable items", to re-save all items periodically and delete the useless tags.
6 - If you create a new custom field with a name that already exists and click on "confirm", you get a message that says "The field names must be unique. The duplicates have been removed." That's fine. But if you try to rename an existing custom field and write the name of another existing custom field by mistake, it is removed without previous warning, and that's not good (there could be many items with data in that field...) I know the data is not deleted from the XML files of the items, and it will be back if you create the field again with the old name, but the end user probably won't notice that and will think all that data is lost. I think the best behavior here is to do nothing, just not to rename the custom field and show a message like "Field names must be unique. The field can't be renamed".
7 - The date picker does not work (the chosen date does not appear in the field, tested in Chrome and Firefox). The small calendar has transparent background, and it would be easier to read if it had opaque background.
8 - I think there's a small mistake in the Admin Settings text. The grey info texts about "Retention period for the recoverable items" and "Retention period for temporary image containers" are both the same. And where it says "here, you can define the minimum number of days to keep temp image data in the system directory" I guess it should say "the maximum number of days".
That's all. Keep up the good work!
1 - If you double-click on a position number in the lists of categories and items, an input field appears, and you can change the position number there. But that field disappears when you click anywhere... It's Ok if it hides when you click outside the input, but not when you click inside the input, because you can't click the arrows to change the number, or select the old number with the mouse, or reposition the cursor with the mouse...
2 - The ascending or descending sort order you select in the settings for categories is not working. It's always descending. It works well with the items.
3 - The position data you see when you edit a category is not always correct. It seems it's not read from the <position> tag of the XML file. But it is correctly written... For example:
1-Create 3 categories: cat1, cat2, cat3.
2-Click on cat3 to edit. Change the position 3 to 4. Click on save.
3-Go back to the categories list. cat3 has position 4. In the XML, the tag <position> is 4. Everything is right so far.
4-Click on cat3 again. There's a 3 in the position field, instead of 4...
Position data is correctly saved from the categories editing screen, but it's not correctly read. What is shown there may be the ID...
With the items, I think it's the opposite... The position field in the item editing screen is not saved, but it's correctly read. Try this:
1-Create 3 items: item1, item2, item3.
2-Click on item3 to edit. Change the position 3 to 4. Click on save.
3-Go back to the items list. Item3 position is 3 instead of 4.
4-Double click on the Pos column in the items list and change the position. This time item3 position changes, and its value is correctly shown in the item editing screen.
4 - I think the numerical change of the position of an item should renumber the position of every item in that category, as with drag&drop. Suppose we have a category with these items:
Pos Name
1 item1
2 item2
3 item3
4 item4
If I change the position number of Item4 to 2 in the items list screen or in the item editing screen, this should be the result:
Pos Name
1 item1
2 item4
3 item2
4 item3
And if I change Item1 position to 13, this should be the result:
Pos Name
1 item4
2 item2
3 item3
4 item1
If it doesn't work like that, there may be problems like this:
1-Let's say I create 60 items in a category. I want them to be in a specific order, both in back-end and front-end.
2-Later, I want to put the last item at the beginning of the list. How can I do that? I can't drag&drop because I can't see more than 50 items at a time, and if I change the last item position to 1 numerically, I'll have 2 items with position number 1. When there are multiple items with the same position number, it seems they are sorted by the file name of the XML (I'm not sure...) In any case, I can't choose which of my two items with position 1 will be first and which will be the second... Decimal numbers are not accepted as position numbers (if they were accepted I could write 1 and 1.5), so the only solution I can see for this problem is to change by hand, one by one, the position numbers of the 60 items...
Categories have the same problem with manually changed position numbers. The only unproblematic way to custom sort items or categories is to always use drag&drop, and it is not always possible.
5 - If custom fields are deleted from a category, the data is not deleted from the XML files of items, creating unnecessarily large files that will need more RAM when processed. The way to solve this is to re-save all items, one by one. I think a safe and easy solution would be to add to the settings something similar to the "Retention period for the recoverable items", to re-save all items periodically and delete the useless tags.
6 - If you create a new custom field with a name that already exists and click on "confirm", you get a message that says "The field names must be unique. The duplicates have been removed." That's fine. But if you try to rename an existing custom field and write the name of another existing custom field by mistake, it is removed without previous warning, and that's not good (there could be many items with data in that field...) I know the data is not deleted from the XML files of the items, and it will be back if you create the field again with the old name, but the end user probably won't notice that and will think all that data is lost. I think the best behavior here is to do nothing, just not to rename the custom field and show a message like "Field names must be unique. The field can't be renamed".
7 - The date picker does not work (the chosen date does not appear in the field, tested in Chrome and Firefox). The small calendar has transparent background, and it would be easier to read if it had opaque background.
8 - I think there's a small mistake in the Admin Settings text. The grey info texts about "Retention period for the recoverable items" and "Retention period for temporary image containers" are both the same. And where it says "here, you can define the minimum number of days to keep temp image data in the system directory" I guess it should say "the maximum number of days".
That's all. Keep up the good work!
