pbeckley

I’m also getting this exact error

Final follow-up (I wish I was more patient and gathered all this first): I think this issue is partly due to almost completely different rendering out the HTML and assigning CSS classes based upon switching %post_title_list% and %post_title_list_short%. The entire series box is rendered differently if I just make that one change.

I’ve verified with default WP theme and zero other plugins.

Follow up: This works as expect when %post_title_list% is used in the “Post list” field, but not when %post_title_list_short% is used.

As a follow up and clarification, for me this error is caused in the JSON output of the Event List block.

I’m also getting this error, but only for a page where I have the widget being used, not the calendar or event listing pages.

Provided historical info over on Git.

Would something like this in the “Series Post Navigation Template” do what you’re looking for?

%postcontent%<fieldset class="series-fieldset"><legend>Series Navigation</legend><span class="series-nav-left">%previous_post%</span><span class="series-nav-right">%next_post%</span></fieldset>

I believe you can update it from the same edit screen you initially assigned it. I think clearing the “series part” field and saving will remove it from the series.

Same, had to delete plugin to get back into site :/

Thank you for clarifying. I didn’t see that kind of information in the documentation, so this might be an opportunity to update it with this info.

I’ve never heard anything from the developer regarding it, but since it’s been almost a year since he last updated the plug-in, my guess is that it won’t be fixed by him.

This is still an issue, and it’s annoying that I keep needing to correct it after each update on every blog I have.

The first problem I’m referring to is that many self-hosted solutions make the root of their domain the ‘home’ even when the site is hosted in a subfolder (e.g. /blog).

The mobile support has nothing to do with log in, the front end looks horrible on my tablet, and cell phone. I suspect it has to do with lack of responsive design or poor implementation of it.

I stand by my rating, these are issues which prevented me from using this plugin when I needed. I no longer need this functionality, but I found a much better solution, but I will not use this review thread as an advertisement for them.

This info is actually in the plugin interface when setting up the Custom posts query with customizable template options:

“Relative path to the template file. Default templates is placed under the plugin directory (templates folder). You can copy it under your theme directory and modify as you want. You can use following default templates that already available in the plugin directory”

I still can’t seem to get it to recognize post formats through get_template_part, which seems like it should be a pretty basic thing, given that it’s core (and bragged about) functionality in WP.

Shaming and name-calling someone because of their review is pathetic.