[Resolved] Add custom field value to View Loop item contener

[Author]

Posts

[diyanK]

Hi team,

I need a way to change the background of a table row in a specific View Loop.

Best case scenario is if I can set a class that has the value of the a specific custom field from the current post in the loop.

Worst case scenario is I have to come up with a jQuery solution to do that on the front-end.

Any help is appreciated.

Thanks!

[Minesh]

Hello. Thank you for contacting the Toolset support.

First of all, I would like to know are you using classic view or block view.

Can you please share the screenshot of your view, once I review that I would be able to guide you in the right direction.

In addition to that, I would like to have debug information that will help us to debug and investigate your issue:
- https://toolset.com/faq/provide-debug-information-faster-support/

[diyanK]

Hi Minesh,

I'm using blocks, screenshot attached.

Note the last custom field that says PO Status – values from this field I'd like to use as classes.

PS. Please note how bad looks the view in a Table format when previewed in Gutenberg, and when there are more than the default amount of rows. I guess you need to address this issue separately as well. It's quite annoying. I planned to report it, but it never turned into a show stopper for me, but since now we're at it - it's worth mentioning the issue as well.

Thanks in advance!

[Minesh]

As you are using the block view - there is no way to adjust the table row class using the custom field value.

The workaround would be if you go with classic view there you will have more control on output as you can adjust the HTML code and assign the dynamic custom field values using row.

PS. Please note how bad looks the view in a Table format when previewed in Gutenberg, and when there are more than the default amount of rows. I guess you need to address this issue separately as well. It's quite annoying. I planned to report it, but it never turned into a show stopper for me, but since now we're at it - it's worth mentioning the issue as well.
==>
We know that and the GUI is not that so impressive for the table based view. We will try to improve that but in future and there is no ETA on it.

[diyanK]

OKay,

Classic view is fine, I can perfectly deal with that.

I stopped using the classic view in order to move faster to an all-blocks stack, and to be on the safe side in the future.

Do you have a plan on turning off support for the classic views? Is it safe to use for a project that is planned to last for another 5 years or so?

Thanks!

[Minesh]

Do you have a plan on turning off support for the classic views? Is it safe to use for a project that is planned to last for another 5 years or so?
==>
We are not going to stop supporting classic views so you should use it without any concerns.

[diyanK]

Awesome!

My issue is resolved now. Thank you!