Dosen't work with ubercart catalog view

I don't have Ubercart, so I cannot test this.

I have Ubercart, this is a bit off-topic for Weight module, but hopefully it helps.

The Catalog View is created within the uc_catalog.module, which is a "sub-"module to Ubercart, but is included within its installation. It's nice to have the module, for it automatically gives the site a full view of all products in a nice orderly grid. But making changes to it requires PHP development, and many designers and webmasters would rather avoid getting too involved with it.

Though it is possible to override the theming for the default catalog view via PHP coding and a template.php file in your theme folder, I suggest instead creating a custom View (using the Views module) and then redirecting traffic from the original catalog_view page to your custom View using a global redirect.

The Views module is a bit daunting at first, so give yourself time and patience to learn it, but you can reproduce the catalog_view and even apply the catalog's CSS to your View. Remember that Views2 for D6 has a "Theming Information" option that shows the filenames you would need to create templates to really customize your view.

I, too, tried to customize the catalog view directly, but if you want access to the Weight module in nodes, or really any node-related data, Views is a better option. It has a learning curve, but its well worth the initial FUD to get the hang of it.

Hope this helps. Good luck!

Thanks. Does Ubercart not use "sticky" in its node queries per the Drupal standard? Perhaps that's where the true issue lies.

So there is no other solution for the Weight module and Ubercart? I changed about 500 products' weight and then re-indexed and did a search and nothing happened (the products did not list first, I mean -sorry for the edit), this must be why.

The views solution would be awesome for just the catalog but what about searches? Is this an issue I should take up with the Ubercart developers? Any assistance is appreciated, thanks!

If they don't include sticky in their queries, then, yes, indeed, they should fix that.

Looking at the Ubercart catalog code, it seems they have their own ordering column; it looks like "List position" in the node form. That column is exposed to Views, so you can use that. For non-Views, it should already be effective. However, I would suggest opening an issue against Ubercart to also honor "sticky." [Hint: Reassign this issue to Ubercart so they can see the whole thread.]