[Resolved] Blocks missing settings in content editor and views block

[Author]

Posts

[SteveR6772]

I discovered while building a site that toolset blocks for image, audio and views at times fail to show settings. After some playing around I discovered this happens when the field is not populated.

I created hidden link to verify the problems occur with a minimal wordpress site, only toolset blocks have been added.

To recreate the problem I

Created a new content type.

Add fields for the content type, including image and audio fields.

I then created a content template for the new type.
When adding either an image or audio toolset block the settings do not show.
Adding a "Single Field" block seems to work.

Adding a instance of the content type without the fields populated and then editing the template did not resolve the issue.

After adding an image to content and then editing the template, selecting the image block now shows the settings. (Note the image does display even without editing the template)

It would be nice is the settings show even if the field is not populated, if not practical, it would be nice if the block interface when it can not display the settings, display a message instead of nothing.

It would also be handy if it was possible to search for content to "View with", instead of being limited to those in the dropdown.

Thanks

[Minesh]

Hello. Thank you for contacting the Toolset support.

This is known to us and the current behaviour would be:
- If you are creating a template for posts and want to include an image from the post, then to specify the settings for the image, you should make sure your preview post has an image.

However, we want to improve the things and we file a internal ticket to improve the 'View With' search dropdown. Other things will work as it for now. We will have talk with our Devs again in near future and we will see what we can do to improve the missing fields.

[SteveR6772]

Regarding

"- If you are creating a template for posts and want to include an image from the post, then to specify the settings for the image, you should make sure your preview post has an image."

I have two issues with this
a) Since it is a silent "error", unless you know about this, you simply see a misbehaving block.
b) This was discovered on a site ported from Drupal, and the field in question is sparsely populated. Since there is no control over which content is available for preview, this may not be practical.

Thanks

[Minesh]

I know this is not practical and we will try to improve this and we do have internal tickets for that. Improving blocks will be the continuous process and we will try to serve the best we can.

You can still share your ideas how/what you want to improve with screenshots or could be a video will do, and we are eager to take look at that and share your concern with our devs.