Curtiss Grymala

You shouldn’t need to revert to any backups to solve this issue, you simply need to reactivate the plugin. The plugin is automatically deactivated because the name of the main plugin file changed, but you can still reactivate it under the new filename.

Hopefully, in the next release, the author will leave the new file in-place, but also create a copy with the old name that points to the new file (so that, if someone has already updated the plugin and reactivated it, it will continue to work; and if someone kept the old version of the plugin installed, an update won’t deactivate that, either).

It appears that this issue was actually introduced in Views 3 (when they started to add Gutenberg/Block support in the plugin). I rolled Views all the way back to 2.9.4, and SlideDeck started working properly again.

I have submitted a support ticket to Toolset to make them aware of the issue.

I have just updated the test version of this plugin on my GitHub repository. If you are able to, can you please attempt to install that version from https://github.com/cgrymala/post-content-shortcodes/releases/tag/1.0.1.2 and see if that fixes the issue you were experiencing?

Thanks for the feedback.

It looks like you should be able to start working on a proper translation for the plugin if you’d like. You should be able to go to https://translate.www.ads-software.com/projects/wp-plugins/post-content-shortcodes and choose your language to begin adding translation information there.

Theoretically, with the plugin now being translation-ready, you can also use language/translation utilities within your own site (for instance, if you’re running a multi-language plugin such as WPML) to translate individual strings locally on your site, as well. Thank you.

Well, that’s no good.

I’ve just pushed a small update to the GitHub repo for this plugin; if you are able to do so, would you mind testing that new version on your site to see if it fixes the issue? If it does, I’ll go ahead and push it out for release. Thanks.

Unfortunately, we probably need to include translation files within the plugin itself.

The string is translation-ready, but I haven’t generated translation files for the plugin yet. I will work on setting up the translation process in the next few days, so that the plugin will be properly internationalized and l10n-ready. I apologize for not handling that earlier.

In the mean-time, you can attempt to hook into the post-content-shortcodes-read-more filter and modify the HTML that’s output for the Read More link. Thanks.

I found one place that the plugin was outputting a message to the log where it shouldn’t have been. That should be fixed in the new version of the plugin that was released yesterday. If you see any other messages being output into the log when you don’t have WP_DEBUG enabled, please let me know. Thanks for the feedback.

Thanks for the tip. Fixing this, finally, and pushing out a new release soon.

Roy – To include the post date, you should be able to add the show_date parameter to the shortcode that you’re using. So, for instance, if you’re using something like [post-content id=7], you would change it to [post-content id=7 show_date=1].

There is no way to aggregate posts from multiple sites together. However, you can certainly include separate lists of posts from each subsite. So, if you wanted to include posts from your subsite with an ID of 2, and posts from your subsite with an ID of 3, you could use something like:

[post-list blog=2]
[post-list blog=3]

Like I said, though, there is currently no way to combine those into a single list. That may be something I look into in the future, but that would require a good bit of extra processing by the plugin (in order to sort the items appropriately after gathering them from multiple sources). Thanks for the question.

You are awesome. Thank you for handling this so quickly.

Thanks. I just pushed another update to GitHub today, fixing an issue with the way custom taxonomy filters worked in the shortcodes/widgets. If you notice any issues with the version you’re using, you can download the fixed version from GitHub.

Running a few more tests, and hoping to release the version officially this week.

The show_image parameter only works with the “Featured Image” for the post/page. If you’re trying to show images inside of posts, they’re handled a bit differently.

The biggest issue would be if you’re trying to display a gallery, since galleries are implemented with shortcodes. By default, this plugin strips out shortcodes before displaying the post content, because shortcodes can be tricky to handle across sites (where different plugins may or may not be active).

You can try adding shortcodes=true to the shortcode to see if that fixes the issue.

Also, if you’re still using this plugin, can you please try installing the latest development/test version of it from https://github.com/cgrymala/post-content-shortcodes? I am close to releasing it, but I am trying to test it a little more widely before doing so, and I want to make sure it addresses the issues that people have raised over the past few months. Thanks.

There is nothing natively inside of this plugin that would do that. I think, in the long run, this would probably be something better handled through use of JavaScript within your theme, that would find that div and remove all of the other content from within the PCS wrapper. Sorry.

If you’re still using this plugin, would you mind downloading the latest development/test copy at https://github.com/cgrymala/post-content-shortcodes and let me know if it works (and if it fixes the issue you’re running into)? I’m just about ready to release that new version, but I’d like to test it more widely and make sure it’s fixing the issues people have raised in the past few months. Thanks.

Not at this time, no, but it’s something I can look into. Thanks for the suggestion.