Post not showing up after 1.4.5 update

Hello – I’m sorry to hear about this. You can download previous versions of the plugin here: https://www.ads-software.com/plugins/custom-content-shortcode/developers/

I’ll go over the changes made since the last version, to see what could be causing this. I try to test every update thoroughly, but it’s possible I missed something.

If you have any more info that could help me solve this (the code you’re using, any warnings or other behavior), please let me know.

Reverting back to 1.4.2 solved the issue.

If I can offer any assistance in helping get to the bottom of this, I’d be obliged. Just let me know how I can serve you!

Thanks!

Thank you for letting me know. So it sounds like there was some change after 1.4.2 that is causing an issue.

Could you tell me the code that you’re using, which works in 1.4.2 but not later versions? That would help me to find which specific parameter is the problem.

Here is a list of the shortcodes used on the post, minus any additional HTML:

[content field="example-tab-textarea" meta="example_tab_meta_box"]
[loop type="post" category="example" count="5" pagination_type="simple"]
[field url]
[field title]
[field title]
[field author]
[field date]
[field date]
[field excerpt]
[/loop]
[display-posts post_type="post_events" events_item_types="example" include_excerpt="true"]
[display-posts category="thanks" tag="example" include_excerpt="true"]

Hmm, perhaps we can narrow down the problem further: could you try removing one part at a time — [content], [loop] block, [display-posts] — to see exactly which line is causing the issue? (Well, what I would do is duplicate the post to keep a backup first.)

For the first line, I assume you’re using the WCK plugin to create the metabox/field? Do things work if this line is removed? Looking at all the code, I think it could be this line where the issue is. In the last couple of updates, I did make a small change in how the metabox is handled.

For the second line, currently the [loop] shortcode doesn’t have a parameter for pagination. Still, it shouldn’t cause any issue.

I suppose there could be some interaction with [display-posts], which would be provided by another plugin. If you remove those lines, does the [content] and [loop] work as expected?

Same story here, the latest update broke all coding.

I had 1.4.5 update, and had to return to 1.4.2 before it wanted to work again.

Code was straightforward:

[loop type="post" category="i-want-to-ask-for-support"]
<strong>[content field="title"]</strong> (Requested on [content field="date" date_format="l, j F Y"] by <a href="[content field="author-url"]">[content field="author" meta="display_name"]</a>)
[content field]
[if category="i-want-to-ask-for-support"]I would need support <strong>[content field="for_how_long_will_support_be_needed_or_provided?"]</strong>.[/if]
This support can take place:
- By email: <strong>[content field="support_meetings_by_email_"]</strong>
- Face to face: <strong>[content field="support_meetings_face_to_face_"] [content field="if_face_to_face,_which_location_area?"]</strong>
- By video call: <strong>[content field="support_meetings_by_videocall_"]</strong>
- By phone: <strong>[content field="support_meetings_by_phone_"]</strong>
- By other means: <strong>[content field="support_meetings_by_other_means_"] [content field="if_by_other_means__please_say_how"]</strong>
<!--You can contact me <strong>[content field="you_can_contact_me"]</strong>.-->
[if empty]There are no requests for support.[/if]

<hr />

[/loop]

Any later update breaks the code and results in white screen. Great plugin though, but somewhere there is a bug I fear in the versions higher than 1.4.2. I run this on WP 4 installation.

Hello,

Thank you for the information – I was able to track down the issue to the meta parameter. It was conflicting with the WCK field metabox parameter. I added a check to prevent this.

Please try the latest update (1.4.6) to see if that solved it.

1.4.7 works as a charm. Thanks!

Great, thanks for the confirmation, I’m glad to hear it. I hope it will solve the issue for the original poster also.