Liquid render questions

Bug? Doing something wrong?

I may be doing this wrong but if you have a web app in a layout, like the large product layout.

And in the list layout of the web app you have:

{{this.name}}

This renders the name of the product and not the name of the web app as I expected. I assumed that this. was in context to the layout / BC part it is in?

{{name}} also renders the product name not the web app name.

EDIT:

I found the tags did not work either, But I made some changes to the large product layout and then it rendered correctly. Just some glitches but hopefully this info may help to identify what this may be.

You can declare a custom value:

{% assign somevar = 'Sale Terms and Conditions ' %}

and if you have a web app in a layout inside a large product layout for example you can fetch that global variable..

{{somevar}}

And you can use..

{% assign my_variable = false %}

  {% if my_variable != true %}

  This statement is valid.

  {% endif %}

In any layout

But how do you get a global variable in an if?

{% if global.somevar == 'Real Cotten' %}

Does not seem to work, nor does just having somevar

Is it something like global.variable.somevar ?

In testing Lucian, You actually can passed assigned variables through.

In my case I could assign a variable in the large product layout, change it based on conditions and if a web app is in that layout, in the list layout of that web app it would render.

The only elements that would not work are the operators like the if.

On that intended or not it does work, I am not sure if you want to prevent that from working to avoid confusion? Or make sure documentation states not to do it that way.

I hear you on the this.params.paramname - That was I tried as well so good to know it will work and I like how you have presented that. I can let people know in the webinar this and that it is coming.

My goal on this stuff are to avoid what I have for our webinar demo where you are doing an if this - render module, if that - render module. As you noted to me that this all counts. While your increasing the modules, My goal is always to be efficient with my code.

If I can just run one web app and vary parameters and operators etc then I am a happy man.

In terms of the render issue I will try to look at this more. It just seems to not work sometimes and returns the parent. This may be a glitch but I will try see if I can get it more consistently failing.

Cool, thanks.

Again I think with Liquid being a server side OO language I think a "Best practise" Section of the documentation will be quite important.

"This does this but we recommend you do not do it like this, do it like that"

I know you do not have the documentation up saying you can do custom variables in liquid yet, but you know me, I will try stuff regardless and work it out.

Hey Lucian,

Are you guys working on as well to expose the same CRM information you can with modules?

{{globals.user.homephone}}

....

Down to the custom CRM fields?

May I ask why?

It would be ideal to be able to tap into things so you could properly pull out a relationship for a person and their company for example

Pagination:

Has this been implemented yet, How will this work?

Thoughts:

It would be great to have a named paramater in modules to disable the default {module_webapp pagination="false"

It would be great to then either run a collection or specify a type of pagination collection for the module so you can code your own.

pagination="mypagination" which overides the default and allows you to form an each loop for the pagination.

What have you guys discussed and got to on this?

Collection & Json issues /questions.

Sample code:

{module_booking,a, collection="eventCollection"}

<script type="text/javascript" id="event-json">{{eventCollection.items | json}}</script>

Is fine because it will render the data in a script format.

I have a couple of questions/issues on this.

1. If you render a collection on the booking module, the collection works but the default module also still renders. I think this is a bug?  You must supply an empty template parameter (Maybe worth documenting this clearly)

2. As with 2, if you render this as JSON data the default module still renders. Is it that things may work but some modules are not full converted?

3. When you render Json data it will render the html of any field with html in it, such as the description area. You can render in script and that is ok, but if you wanted to store in html data for example... data-value="" then it will render out that html. Is it possible to offer an escaped version of the json data?

I think I have found a few issues as well with Json and pulling description content with speach marks etc and not coming out as valid json as well.

- EDITED -

Can I ask where you guys are at in terms of exposing more of the Data from things like the CRM?

A number of us have been providing information on modules and tags and what data output is missing for a while on the current developer reference comments.

Is getting access to information we can not (Billing address on CRM not order, 2nd email, 3rd email, POBOX... etc) ?

Thanks

Liquid Passing does indeed work now.

Shopping Cart and Registration:

Lucian, With Liquid, what will be available on the cart.

My Primary needs would be...

- Being able to access the product and ALL? (if possible) data via liquid

- Have the shipping options as a liquid or at least in a json format so we can form better custom solutions for this.

Same to with the checkout page. The Amount field is locked for good reason in terms of its value so you can not manipulate the price, even if you do BC will not take anything other then that current price.

I totally get why, but things like adding surcharges etc is a pretty much standard client request that BC developers can not do without going full API.

With liquid and being server side, is there something that can be offered here?

Further to these concepts:

Further to Liquid server side rendering, there must be some form of authenticated method or validation coupled with liquid to allow you to do a bit more or make requests and get information to do a bit more then just with javascript?

I know this sort of thing will be further down the line, but it is something that I think people will want going forward.

Thanks.