|
Tuesday 24 July 2007 6:22:16 am
Hi all, After tweaking ezpublish upside-down for 3 years now i would suggest a list of improvement by order of importance...according to me : <b>Admin content list functions</b>
In admin children list view : I would replace the "remove selected" button by a html select menu that would apply those functions to the selected list of nodes : "move selected", "remove selected"
This would allow to move multiple nodes to new location. For now its very tedious having to move every node individually. <b>Settings</b>
Transform "Repository" into an array in icon.ini.
This would allow to have a per-siteaccess icon config with the fallback system.
<b>Admin Shop</b>
Repair all "Shop" view that are full of errors :
- Order list view : Being able to modify the item limit (15 by default).
- Can't view customerorderview when orders are archived (really don't get why it was made like that)
- Numbers at the top of orders list (archived or not) never show the total number but only the number of elements in the page (which is always item_limit !).
- Can't sort any list by column name.
<b>Datatype</b>
Modify option datatype to make product options more flexible.
For now you are stuck with this "value + additional_price" structure. If you don't want to go and devellopp your own option datatype (with almost no documentation :) you have to fit all your variables into the "value" field. For exemple i had to be able to insert "Ref|Size|Quantity" in that field then making an explode() to use the data. <b>Kernel functions</b>
In the addtobasket function : Item_count (=quantity) is hard coded to '1' !!!
Making impossible to put a "quantity" field in you product form.
I can't understand why it is still like this in a 3.9 stable version.
Being able to rewrite/overwrite kernels functions.
For exemple i would like to rewrite "addtobasket" function without any modifications to the base files. This would allow us to further improve ezp by working on functions that for now cannot be modified without breaking ezp base files.
Using removesubtrees" function to remove a nodes+objects doesn't clean the discount table of those deleted nodes and objects.
Then you have a discount table full of objectids that doesn't exists anymore.
<b>Fetch Operators</b>
Modify the treemenu operator to allow showing of the whole subtree. Not only the one under current node.
This is so frustrating having to use a nested "fetch list" to achieve this.
Being able to fetch products which are discounted (has_discount).
Adding Group_by attribute in fetch list and fetch tree.
This would be very nice to be able to list content grouped by an attribute value.
Adding a 'fetch history' operator.
This would make possible to implement a new toolbar called "Last viewed pages". <b>Search</b>
Recording search results.
This would allow to implement a very cool toolbar i would love to implement that present those functions : Return to search results, next result, previous result...Etc. In fact when you consult pages after a search on a site it would be great to redisplay the search result's in one click, without having to actually redo the search, or to browse "next result", "previous result"...even a long time after the search was made. Each new search call would overwrite existing datas. I don't know on which ez layer this has to be implemented. <b>Extensions - Extended filters - Custom operators...etc</b>
Allow more flexibility for extensions, modules, cronjobs...'s path.
In fact it would be cleaner to be able to put everything concerning a certain siteaccess inside its "design/siteaccess" folder. But its impossible for now because modules must be in "extension" folder.
------------------------------------------------------------------------------ Thanx
EZP is Great
|
