I am trying to show the value of a custom number field in the rating block within a view. Initially it seemed to work fine. Then I changed the default star icon to a thumbs up. The result was that the block was no longer visible in the frontend. Also, when going into page edit mode, it took extremely long before the view became visible.
Link to a page where the issue can be seen: hidden link
In Chrome, I don't see the block at all. The HTML is rendered but nothing is visible.
In Edge, I see "] only.
I think something is wrong with the rating block. On another page where I use the default stars (hidden link), all stars were grey while in edit mode they showed 4 or 5 out of 5 yellow as expected. After a long time and another page publish, this started to work though.
It would appear that there is a break in the block that is causing it not to render properly.
Would you mind allowing me to have admin access to the website so that I can have a more detailed look at this for you ?
I've enabled the private fields for your next response.
Thanks,
Shane
Thanks Shane. That does work for me both in the page edit mode and the frontend. However, then I changed it to the thumbs up icon again and the issue is back. I think doing that corrupts the block.
Thank you for the additional information. I managed to track down an internal ticket where this issue was already reported. Unfortunately there hasn't been any fix posted for the issue as yet.
I did however add your ticket to the issues tracker so the developers can be aware that multiple persons are having the issue.
My recommendation here is to use the default star icons temporarily as a workaround for the custom icons.
Ok thanks. My guess is that the problem is in the generated CSS. In the Chrome dev tool I can change "content: attr(data-star)" in ".tb-rating__star::before {" to this:
"content: 'test'"
That will make it display "testtesttesttesttest" (instead of the 5 icons that were supposed to be there)
I too suspect a css issue was well. However given the widespread issue the best thing is to wait for our dev team to properly investigate and resolve the issue.
