Important sugestions for post 3.9.2 releases !

Author Message

H-Works Agency

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

Heath

Tuesday 24 July 2007 7:38:50 pm

Hello Martin!

It is so cool that your still in the forums for so long! I remember the first time we spoke on #ezpublish (freenode.net irc)!

<i> > After tweaking ezpublish upside-down for 3 years now i would suggest a list of improvement by order of importance...according to me :</i>

I think this kind of feedback is fantastic because with eZ it can take time to become strong enough to really know / make time to point out all the issues from one's perspective.

<i> > Interface
>
> 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.</i>

I have to agree on this one. After using gmail for a few years. There have been times when I noticed that this change would be most useful over the existing feature.

<i> > Transform "Repository" into an array in icon.ini . This would allow to have a per-siteaccess icon config with a fallback system.</i>

We have spoke on this a few times. It's more and more an issue which affects an increasingly larger number of people as time goes on and it's not addressed.

<i>http://ez.no/community/forum/developer/using_customs_class_icons_in_admin_siteaccess#msg141849
http://ez.no/community/forum/developer/icons_for_each_class#msg116239
http://ez.no/content/advancedsearch?&SearchText=icon.ini&SubTreeArray%5B%5D=308&SearchDate=-1&SearchPageLimit=5
http://ez.no/community/forum/install_configuration/how_can_i_setup_multiple_pathes_for_custom_icons_images</i>

<i> > Shop
> In admin order list view : Being able to modify the item limit (15 by default). And the fact that the item_count in the title doesn't reflect the order total but only the orders in the page. So its always 15 even if you have 300 orders.</i>

Again, Agreed :)

Further worse that you may not order / reorder the list by the column headers, ID, Total, Time or Status. The user / shop admin really would prefer this flexibility.

<i> > Operators
>
> 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.</i>

I heard in 3.10 there is an updated admin menu tree but I can't say much more than point to the changelog.

The following documents say / mention ...

<i>http://ez.no/community/news/ez_publish_3_10_alpha1_released</i>
- "Improved tree menu"

<i>http://ez.no/community/news/community_newsletter_9_20th_july_2007</i>
- "an AJAX-based dynamic content structure tree menu (in the Administration Interface)"

<i>http://pubsvn.ez.no/nextgen/trunk/doc/changelogs/3.10/unstable/CHANGELOG-3.9.0-to-3.10.0alpha1</i>
- Unknown / N/A ..

Cheers!
Heath

Brookins Consulting | http://brookinsconsulting.com/
Certified | http://auth.ez.no/certification/verify/380350
Solutions | http://projects.ez.no/users/community/brookins_consulting
eZpedia community documentation project | http://ezpedia.org

Clay Pereira

Tuesday 24 July 2007 8:03:09 pm

Hi Martin,

I sure appreciate your feedback when it comes to eZ commerce. There really needs to be more of us speaking out. I ditto everything you and Heath have said. I just would like to point out that we had to create a new shop orders pagelayout that allows our administrators to select orders by date ranges. It is really quite nice. Here is a snapshot of it. It makes a world of difference to our Admins

http://dev.clicktechnologies.com/var/ezwebin_site/storage/images/communities/photos/ez_webshop_orders/794-2-eng-US/ez_webshop_orders_imagelarge.jpg

H-Works Agency

Wednesday 25 July 2007 1:41:15 am

Hi Heath & Clay !

Thanx for those informations. Its cool those issues are being adressed.

The orderlist view you have created is great. There is a pretty small work to do in the shop menu to improve shopping (admin+public) a lot.

Later.

EZP is Great

Clay Pereira

Wednesday 25 July 2007 8:42:02 am

Hi Martin,

It really is crazy that the Quantity is hard coded. We have to hack the kernel for this which is really a quite dumb thing to have to hack. EZ please fix this!!! It really is extremely important for commerce sites.

H-Works Agency

Wednesday 25 July 2007 9:17:52 am

Yes this is difficult to understand. There must be a reason but its very annoying.

EZP is Great

André R.

Wednesday 25 July 2007 10:18:59 am

Heath: The tree menu operator and the content structure tree menu are two different things, the latter is the one used on the left side in the admin interface.

eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom

Heath

Monday 20 August 2007 7:39:55 am

OK André R...

Thanks for chiming in again :)

Any other helpful suggestions from the others in the community?

Cheers,
Heath

Brookins Consulting | http://brookinsconsulting.com/
Certified | http://auth.ez.no/certification/verify/380350
Solutions | http://projects.ez.no/users/community/brookins_consulting
eZpedia community documentation project | http://ezpedia.org

Heath

Monday 03 September 2007 4:18:52 am

<i>@Martin</i>

I think it is a good idea to add these comments to / in the form of enhancements/bug reports to the issue system at, http://issues.ez.no/

Then publish the links to the issues you file here in this forum thread so other users who wish for these improvements can comment, vote and subscribe to these issues in a show of support.

Cheers,
Heath

Brookins Consulting | http://brookinsconsulting.com/
Certified | http://auth.ez.no/certification/verify/380350
Solutions | http://projects.ez.no/users/community/brookins_consulting
eZpedia community documentation project | http://ezpedia.org

H-Works Agency

Monday 03 September 2007 4:27:14 am

Hi Heath !

Yes i will do that...

I am gonna take a look at your payment gateway project. I'd be glad to participate.

++

EZP is Great

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.