Skip Navigation

[Resolved] wpv-post-featured-image behaving odd

This thread is resolved. Here is a description of the problem and solution.

Problem:

[wpv-post-featured-image] does not work as expected.

Solution:

It should be a compatibility issue, you can check these:

https://toolset.com/forums/topic/wpv-post-featured-image-behaving-odd/#post-1366051

Relevant Documentation:

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

This topic contains 2 replies, has 2 voices.

Last updated by Sammut 11 months, 1 week ago.

Assigned support staff: Luo Yang.

Author
Posts
#1365747

Did something change with the [wpv-post-featured-image] tag?

As of yesterday, any shortcode using custom, e.g.,

[wpv-post-featured-image size="custom" width="58" height="58" crop="true"]

does not display.

If I use

[wpv-post-featured-image size="custom" width="58" height="58" crop="true" output="url"]

it does display but does not resize correctly and also adds a version number, for example image.jpg?v=3453452345

I fuse something like

[wpv-post-featured-image size="large"  class="single-post-image"]

it does work. Any thoughts? I am quite confused.

Thank you!

#1366051

Luo Yang
Supporter

Languages: English (English ) Chinese (Simplified) (简体中文 )

Timezone: Asia/Hong_Kong (GMT+08:00)

Hello,

I have tried all three shortcodes you mentioned above in my localhost, with a fresh wordpress installation + the latest version of Toolset plugins, all three shortcodes work fine.

I suggest you try these:
1) Make sure you are using the latest version of Toolset plugins, you can download them here:
https://toolset.com/account/downloads/

2) In case it is a compatibility problem, please deactivate all other plugins, and switch to wordpress default theme 2019, and test again

3) If the problem is fixed, you can activate other plugin/theme one by one, find and locate the problem plugin/theme.

#1366195

My issue is resolved now. Thank you!