I think It was in PAB.

Some modules do not support sorting, for example: module_catalogueselect

It would be great if you pass these in a collection that your collection could handle the BC sorting, OR its own. Syntax in liquid in other systems is below

{% for aCat in catSidebar.items order:Weight -%}

Or

{% for aCat in catSidebar.items | order:Weight -%}

Wholesale Pricing:

This is not as straight forward as it sounds of course but...

It would be great to show the wholsale price as a separate object for a product - Just for information pruposes, along with the sale price. These can just be something like...

wholeSalePrice:

originalSalePrice:

And just the values.

Why?

- Letting people know possible savings of being a wholesaler

- Showing the original price to wholesalers

- Doing math on the prices to show the discount saved

I have emailed about this but I want to add it here.

BC with Liquid has a math issue. Yep there are some bugs with < etc that need to be fixed and product prices return as a string right now when they should be number values... BUT....

There is a further underlining issue here with data in this regard. BC basically returns a string for just about everything so doing math on values will be a bit of an issue throughout the system. Let's say you got a web app with custom fields for example. Your custom field value could be something that needs to be "2.4342" for example. You can not use the BC custom number field as that only accepts whole numbers (and probably still returns a string, lol) so you need to use text which will be a string.

But you may want to run liquid on that?

I do not expect the BC engineers to spend the time making sure any possible number field renders as a number and more, that would take forever.

BUT

If you BC guys could work on a custom filter to convert the value type then we could do a lot of the leg work ourselves.

{{ Something | type="" }}

This would have the following options..

boolean,

string

float

int

And convert one type to another. Most things would be a string to one of these other types though. This would solve a lot of this math or possible value type conflicts when people try to do if conditions etc.

It is documented Scott, but like the BC module date, BC actually does not expose the server date in the system. I am not sure why, I forgot what Cristinel told me now. As you know the module just renders some javascript and string date for the users date / time.

What do you think of the type idea though Scott, that should solve a heap of issues I think.

You can pass as a variable into those modules scott

mything="{{company.phone}}" then in the module..

{{params.mything}}

Tag cloud tag object:

Currently returns the ID and name and one other object item.

To be useable you need to construct the tag cloud tag with url, the name and also know how popular it is (the class that is generated) and that class is currently not part of the object.

You can lowercase the name to form the tag cloud url, but it may be worth just including that for ease of use for people.

Ideal

- Name

- Url

- Class

- ID

Paramater passing:

You can pass a parameter into a module list layout, but this will not come through in the detail.

Is it possible to have passed paramaters in the list & Detail view?

You have all the page json stuff if you remember Gary. Any page can be set to show its contents as JSON.