tgrblogger

@maybellyne the issue seems to have resolved itself. Not sure why, we did not make a change after posting. If I find out in a few days, I’ll update this thread to let you know.

Thank you for replying. Just to let you know that I had considered and checked on those things before making the post. I did fail to note that we recently dropped php 8.0 support, switching to php 8.1 and above. Could that be a possible source of this issue?

• This reply was modified 2 weeks, 1 day ago by tgrblogger. Reason: clarifyning

Confirming that it appears to be fixed. Thank you for the prompt response!

This has happened to a website I manage as well. Using the legacy version.

Also found that plugin WP Rollback works and successfully installs any of the previous versions.

OK, so spent the last few hours trying to resolve this and thank goodness someone posted here about it. No response from the authors yet apparently. Would also like to know how to rollback

That’s a problen as we have adjusted the upload & post size and execution as shown, and got the same result. I have tried negotiating your support and contacting them, not an easy task. Will try again contacting support again, but this whole process seems much harder to accomplish than it should be. This is WordPress and a plugin for it after all.

• This reply was modified 1 year, 1 month ago by tgrblogger.

You are probably right about that, but version releases / updates still matter to some setups where security is critical. thanks for the reply and the version bump.

I just did several tests, and it appears that the ticker title is what determines the size of the ticker when the Global Settings > Ticker Width is set to 0 (zero). According to the tool tip for that setting, zero is supposed to allow the width to be dynamic. Apparently, the title is required to be displayed in my situation. The only way I’ve found to get the ticker to display without a title is to create fixed width in that setting, which negates the advantages of being a responsive design element. I don’t know if you intended for it to work this way or not, but I’d appreciate it if you could look into it some more to allow the flexibility of responsive design.

• This reply was modified 3 years, 5 months ago by tgrblogger.

OK, when I remove that setting in the Ditty Ticker widget, the ticker no longer shows up. In other words, not only does the title disappear, but so does the ticker itself. If I reverse that and select the “Display Ticker Title”, the ticker displays, but so does the ticker title.

@metaphorcreations that is what I was trying to communicate, that the title is showing even though the “Display Title” checkbox is unchecked. I just noticed this behavior this week, not sure when it started doing it.

Health Check & Troubleshooting plugin reports that this plugin only supports up to PHP 5.6. It is running under PHP 7.3 on sites without incident, but having tested it with PHP 7.4, it does apparently fail for unknown reasons. Still looking into possible other causes for this.

FRom my research on this same subject, it appears to be that the new built-in sitemap function is very basic and does not do all that this plugin does. Example: there is not settings area for is where you can filter what is added to the sitemap, and what is not. IT also does not notify the search engines actively as this plugin can.

I found a simple way to disable the new built-in sitemap; I downloaded a new plugin named Disable WP Sitemaps. IT does not show up in the search for plugins inside a WordPress install as yet, but it is downloadable from the WordPress plugins website. DL the zip file and upload to your WordPress install using the new zip upload function in the Plugins area.

I have created another test where I have installed latest versions of plugins used, including the wordfence and Coming Soon plugins. I am not seeing any error at this time. and can start the wordfence scan without issue. I will monitor this and get back to you within a few days as to the results. IT may have been an anomaly with the way or order the plugins were installed as wordfence does do a check on what is presently installed and active when it is first activated.

The Wordfence error dialog did not specifically point to the Coming Soon plugin, but made a general statement regarding plugins that might have an effect of starting. I found that it was the Coming Soon plugin through standard testing process whereby all other plugins are tested against a given condition. The Coming Soon plugin was the only one that created the fail condition.