Rick Hellewell

The issues is with 2 sites (out of about 20) that daily want to upgrade to version 1.9.9, which does not exist. Version 1.9.8 is what is installed on all of the sites (not just the 2 that are complaining).

So daily I get the notice that those two sites want 1.9.9. And even when I let it update those two sites, the next day those same sites complain about needing 1.9.9. The other sites are not complaining nor requiring the update.

I have uninstalled the plugin on those two sites, deleted them from the dashboard, reinstalled the plugin, and re-added the two sites to the dashboard.Did another refresh to make sure the plugin was current.

And the next day, those two sites will still complain about wanting 1.9.9. This has been going on for several weeks. Ignoring the update request for the two site, and the next day the complaint about needing 1.9.9.

Screenshots of the messages are in my original message here.

No response to this question after 4 months. Still a valid question.

But related to it – can the plugin use whatever editor is in use for the comment box? Like the standard comment box, or any comment editor that replaces it through proper filters?

Right now, I get an HTML coded box. Not very user friendly.

Thanks for the reply.

I decided to go in a different direction. First, added an ‘up/down’ voting plugin.

Second, wrote my own plugin that will add ‘spam/trash/delete’ links to the comment list display when admins are logged in. This allows admins (or anyone with moderate comment roles) to immediately spam/trash/delete a comment without needing to get into the comment admin screen. One click and it’s done.

This plugin allows the admin/comment moderator to quickly get rid of unneeded comments. It’s called “CellarWeb Instant Comment Moderation”, and is available here.

Thanks again for your response.

I use the basic blog page template (usually page.php, but depends on the theme), and modify that to strip out all CSS classes and header/sidebar/footer. The result is just the post heading and content, for all of the posts.

The query I use sorts by oldest first. You could modify that query to select certain categories or date ranges … which is basically what this plugin does. The settings are used to build the query, then the ‘plain’ page is generated.

Still in progress. Other projects keep getting in the way. Thanks.

(On my site, I just created a new template with only output of headers and content. Used a copy of the page.php file in your theme. Doesn’t have all the options – you would have to hard code the query you need, but works well.)

BTW, @duplicatepagesupport – it is not necessary to release a new version when all you have done is update the WP version texted.

All you need to do is update the plugin’s readme.txt file with the new WP version, which doesn’t require a new version.

Also, if you put the “Tested to” to “6.0”, that keeps you current for all WP 6.0x versions. Again, no need to release a complete new version.

Just doing some final testing on the upgrade. But had a sudden thought – would an option to include comments on each post in the output be useful? Or not useful?

Any other new features that you think would be useful?

Thanks…Rick…

Actually, you motivated me to work on the upgrade. Currently testing now.

As for choosing which post to convert, you can do that by assigning the desired posts a unique category, then selecting that category on the Settings page.

The update should be finished by the end of the week; possibly sooner. Takes a while to test.

PHP 7.4 starts issuing error ‘warnings’ if a variable doesn’t exist and you use a statement like your example. Code still works, though, although the error warnings are in your error.log file.

I haven’t updated that plugin for a while. Instead, for my use case, I just built a bare-bones template based on my theme. So I am not surprised that there are issues. Probably even more in PHP 8+.

I might try to update the plugin for PHP 8.x, which will take care of those errors. But I have no ETA, due to other projects that have a bit more demand (I’m a one-person shop). If I do find time, it may take at least a month to squeeze it into my schedule.

Your issue has made me more aware of the need to update the plugin for PHP 8, though.

Although @swekarl (Karl ANdersson) extra CSS will fix the issue, the issue is still there in the plugin version 4.00.

Hiding a field that shouldn’t be there with some CSS is not a fix. It’s a bandaid.

The field shouldn’t be there – this is still an open and non-resolved issue.

As I continue testing, just noticed that there is a ‘we’ll look into it” message on clicking.

And, good feature that prevents multiple votes. You might add an option to customize those messages (including the ‘flagged’) one.

…Rick…

I just did a fresh install on my test site. Made no changes other than required during setup. Did not change any forms.

Then added the subscribe form to the right widget area. Here’s a screenshot of that area: (can’t put the screenshot here, but will be sent privately)

Here is the code for that area:

</widget><h3 class="widget-title"> Subscribe to Get Notified </h3><div class="emaillist" id="es_form_f1-n2"><form action="/development/sample-page/#es_form_f1-n2" method="post" class="es_subscription_form es_shortcode_form " id="es_subscription_form_62a37b0ab5743" data-source="ig-es"><div class="es-field-wrap"><label>Name*<br /><input type="text" name="esfpx_name" class="ig_es_form_field_name" placeholder="" value="Rick " required="required" /></label></div><div class="es-field-wrap"><label>Email*<br /><input class="es_required_field es_txt_email ig_es_form_field_email" type="email" name="esfpx_email" value="[email protected]" placeholder="" required="required" /></label></div><input type="hidden" name="esfpx_lists[]" value="4b96a698f5a3" /><input type="hidden" name="esfpx_form_id" value="1" /><input type="hidden" name="es" value="subscribe" />
			<input type="hidden" name="esfpx_es_form_identifier" value="f1-n2" />
			<input type="hidden" name="esfpx_es_email_page" value="2" />
			<input type="hidden" name="esfpx_es_email_page_url" value="https://cellarweb.com/development/sample-page/" />
			<input type="hidden" name="esfpx_status" value="Unconfirmed" />
			<input type="hidden" name="esfpx_es-subscribe" id="es-subscribe-62a37b0ab5743" value="ecaf19ec53" />
			<label style="position:absolute;top:-99999px;left:-99999px;z-index:-99;"><input type="email" name="esfpx_es_hp_email" class="es_required_field" tabindex="-1" autocomplete="-1" value="" /></label><input type="submit" name="submit" class="es_subscription_form_submit es_submit_button es_textbox_button" id="es_subscription_form_submit_62a37b0ab5743" value="Subscribe" /><span class="es_spinner_image" id="spinner-image"><img src="https://cellarweb.com/development/wp-content/plugins/email-subscribers/lite/public/images/spinner.gif" alt="Loading" /></span></form><span class="es_subscription_message " id="es_subscription_message_62a37b0ab5743"></span></div>            </div><!-- .widget-area -->

I can send the URL of the test page separately and privately via email.

Thanks for the response.

I’d like to be able to
– directly (via code) add items to a specific list.
– have a form that the user could access on the front end to enter a message/text
– use that message/text to send out a template (that would include the message/txt) to a specific list
– access a lists’ data for use in my own code
…Rick..

Update: FormSpammerTrap for Comments (FST4C) version 4.00 was released today. Lots of chnages; see the readme for the change log.

As to usage, and it’s relationship to our Block Comment Spam Bots (BCSB):

– use BCSB for basic comment spam protection
– use FS54C for additional customization of the comment form elements and content. Note that not all themes support full customization of the comment form elements.

Both plugins use the latest FormSpammerTrap (version 14) which was released last week. FST version 14 includes a ton of features, including improved instructions for creating a FST template page for WP sites. See https://www.FormSpammerTrap.com for details.

Hope this helps….. Thanks for your support!

…Rick…

NOte: version 4.00 released; 3.10 didn’t process well into the plugin repository. Version 4.00 is the latest version, and has all of the fixes in 3.10.