[Resolved] More than 9 images inside my conditional output shows shortcode
The Toolset Community Forum is closed, for technical support questions, please head on to our Toolset Professional Support (for paid clients), with any pre-sale or admin question please contact us here.
This support ticket is created 6 years, 10 months ago. There's a good chance that you are reading advice that it now obsolete.
This is the community support forum for Types plugin, which is part of Toolset. Toolset is a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients and people who registered for Types community support can post in it.
Display my single "property image" and the additional "property gallery images" as thumbnails under the large "property image"
Link to a page where the issue can be seen:
hidden link
I expected to see:
The series of thumbnails.
Instead, I got:
The shortcodes from the layout that should display the <img> tags
Additional Info:
This only happens when I have a total of 10+ images. So 1 property photo and 9 property gallery images or no property photo and 10 property gallery images. When less than 10 total, the thumbnails display perfectly as shown here - hidden link
Not sure if you've tried this as yet but would you mind temporarily disable all the non-toolset plugins and check again to see if the issue still remains?
If it does would I be able to get admin access to your website so that I can investigate the issue further ?
The private fields will be enabled for your next response.
Thanks for confirming, also sorry i didn't notice the credentials in the first post.
I would also like to verify that this isn't an issue with the server so I would like to create a duplicate of your website locally so that I can test without affecting your live site.
It seems that there is too much data for the [wpv-conditional if="( $(wpcf-property-gallery) ne '' ) OR ( $(wpcf-property-photo) ne '' )"] conditional to process.
What I would suggest is to restructure this. Is there a case where you allow users to upload a property without a photo ?
Making at least one of these fields required should resolve this issue.