Admin Categories/Product pages layout issue

[k9dug]

Hi,

I have googled for an answer to this, but no mention can I find.

I'm not sure if this is a bug but the page layout doesn't make sense to me, so it may be.

OK, I am in Admin, go to Catalogue -> Categories/Products, then open a category to see the product listing. This is fine. There is a table header with the following headings:

ID, Categories / Products, Model, Price/Special/Sale, Quantity, Status, Sort, Action

If I want to copy or move one of the products I click on the relevant coloured "c" button over to the right. A page opens with the "Copy To" dialogue box on the right side, eg:

http://www.myshop.com/admin/product....action=copy_to

On the left is the product listing table, but this time there is no header and only the following fields:

ID, Categories / Products, Model, Price/Special/Sale, Quantity, Status

The sort value and all the Action buttons are not presented (understandably).

This occurs for the following pages and versions:
m button ("Move Product" dialogue) (v150, v151) (URL ends: ..&action=move_product)
c button ("Copy To" dialogue) (v150, v151) (URL ends: ..&action=copy_to)
a button ("Attributes Changes for Products ID# xx" dialogue) (v150) (URL ends: ..&action=attribute_features&page=1)


My questions are:

1. Should there not be a table header in these pages?
2. Are the other products listed alongside the dialogue box for any particular reason? There is nothing in the list to indicate which product in the list is the one being managed (just an ID# under "Current Product: " in the dialogue) and I can't do anything with them except change status or go to a product edit page.
3. Any suggestions as to how to instate the table header?

Cheers,

Gav

[stevesh]

1. Probably, but I'm not sure I would call it's absence a bug. As you said, the column contents are pretty obvious.

2. I don't think so. Possibly just there to fill the page and remind you that you're copying the right product.

3. You could probably find the header code from a different page and add it to that page's code, but it would seem a waste of time to me.