zymeth25

Hi,

This is possible and is well documented:

posts_morelink – Include a “read more” link after each post. It receives a string of characters as a parameter which will be used as the text of the link. Example: [catlist id=38 posts_morelink=”Read more about this post”]

No, sorry for being unclear, it’s close to what you wrote but the exact scenario is:

1. You post as a subscriber on the front-end and two emails are sent – one to the subscriber and one to the admin (which contains a non working edit post shortcode).

2. If you post as an admin still on the front-end, the notifications are sent and the admin notification does contain a working edit post shortcode.

If I create a “Pending review” post via WP Admin everything also works. Subscribers don’t (and I don’t want them to) have access to WP Admin post editing so that’s not an issue.

• This reply was modified 7 years ago by zymeth25.

Thanks for your reply @voltronik

Yes, that’s what I’ve already implemented. Whenever the form is submitted two emails are sent: the author (usually a Subscriber) receives a simple confirmation notification and the admin receives another one with the edit link. The thing is in that admin notification the edit link doesn’t appear. Only when I submit the form while logged in as admin (which is not intended) the [edit_post] shortcode works.

This is now included in 0.76 so you can just update to the latest version of the plugin

Please update to the latest version of the plugin. It restores compatibility with your versions of PHP. However, we will be dropping support for PHP pre 5.4 soon so do contact your hosting providers and ask for updating PHP.

• This reply was modified 7 years, 1 month ago by zymeth25.

This is because your host uses PHP version older than 5.4. Any chance you can upgrade?

Please update to the latest version of WordPress and check if it resolves the issue.

Hi,

Can you give some more details?

I created a “list-category-posts” folder in my child theme and put the default.php file inside and renamed it “template_test_01.php”.

This is all fine, this is what you are supposed to do. Can you share your template code and say exactly what you wanted to achieve and what failed?

The search parameter seems to be working fine on my end. It returns nothing when no posts match the “search term”.

But dynamic dates do seem to be broken, we’ll have to look closer at this.

Hi @manillons

It is a very good feature request and I hope it can be included in the future.

But there’s another way you can accomplish what you want right away if you don’t mind using tags. If you add a tag “news” to all relevant posts you could do this:
[catlist categorypage=yes tags=news] which would display posts from the current category if and only if they have a “news” tag.

I have just checked your shortcodes and they all work and produce expected results on my end. I had another look at your initial post and I think the problem is quite different – what you want to achieve is not what this plugin is meant to be used for.

You want to display a list of categories with number of posts for each category, not a list of posts. The LCP plugin is for listing posts only. All shortcode parameters are used to select or display post-related data.

Have a look at this plugin, I think it is closer to what you are looking for.

Cheers

• This reply was modified 7 years, 1 month ago by zymeth25.

Templates are well documented so if you follow the docs you should be able to create your custom template.

Unfortunately this is not possible at the moment.

Hi @lucio7

Sorry, but what you described is not possible only with the shortcode. It can be easily done with CSS and JavaScript but you would have to add the necessary code yourself.

The LCP plugin doesn’t come with any styles or scripts out of the box, the idea is that users get the html markup with the shortcode and then do whatever they want with it on the front end.

We try to make sure the docs cover 100% of the code so if something is not mentioned there’s 99% chance it is not supported.

As per the documentation, to list pages post_type=page needs to be specified.

To list only children of a given post id post_parent has to be specified. It doesn’t support automatic detection of current post’s parent and the documentation doesn’t mention it.