Best online gambling sites.Enjoy Free 888+200 Daily Legal Bonus

ClassicPress support

aquasp — Sun, 03 Apr 2022 18:51:08 +0000

Hey team,

Hope you are doing fine. I was searching the perfect translation plugin, and this seems to be the one

However, I’m using ClassicPress on my blog instead of WordPress. Classicpress is a fork of WordPress 4.9.x that focus on simplicity, security and stability. It is also community driven.

So, my question is: Will this plugin support classicpress in the future? Or in the future it will drop support to ClassicPress?

Thanks!

WordPress 5.1 required?

?eslav Przywara — Fri, 22 Feb 2019 12:34:21 +0000

Hi Andrew,

I just updated to the latest version of this plugin from WordPress 4.9 backend and just then noticed that advertised required WP version is 5.1. Should I expect problems on 4.9 then now that I have the latest version?

Btw. I thought that WordPress won’t offer plugin update if minimum WordPress version is not met?

Also, you forgot to update Stable tag in readme.txt – it still says 5.0.1.

Unable to Edit PHP files

earncrafty — Thu, 12 Jul 2018 13:21:42 +0000

Hi there,

I am freelance PHP Developer and new to WordPress(First Project) and need your guidance in following issue:
My initial installation was WordPress 4.9 Version. Since the installation of theme, I am unable to edit .php files in the editor. Now I read forums and came to know that I am not the only one struggling. So I read their discussions and tried the very common first step in all of the topics to install health-checkup plugin. Which I did, an dnow the error changed from

Unable to Communicate back with site to check fatal error,so the PHP can be reverted.You will need to upload your PHP file change by some other means, such as by using SFTP.

So now after installing the health -Check up plugin the error changed from the above one to the bottom

Something went wrong. Your change may not have been saved. Please try again. There is also a chance that you may need to manually fix and upload the file over FTP.

Kindly let me know if you can guide me through the solution. Thank you. Because my client needs an ETA.

Not receiving new comment and forgot password emails

Brijesh Gohil — Tue, 23 Jan 2018 05:56:22 +0000

I am not receiving any email notifications of my wordpress website. I use contact form which used to send email to me when it is submitted but now I am not receiving any email.

Even I tried commenting and forgot password but I am not receiving any email from my wordpress site.

Earlier it used to work fine but after updating wordpress to 4.9 this is the problem that I am facing and not able to fix after lot of different tries.

How to disable wordpress 4.9 Syntax Highlighter by default?

rayorlana — Mon, 08 Jan 2018 03:41:40 +0000

I am on wordpress 4.9 and the new syntax highlighter features seems to be causing issues for editors and admins. So, there’s some false positive detected as errors on WordPress and those errors are automatically fixed which is actually not what i wanted.

I’ve found out that this feature can be disabled for each editor manually from edit profile > disable syntax highlighting. Is it actually possible to disable it by default so that future editors on my site don’t need to set it again.

WordPress 4.9.x: Editing Themes/Plugins (Unable to communicate error) temp fixes

Douglas "BearlyDoug" Hazard — Wed, 20 Dec 2017 16:06:34 +0000

Ever since WordPress 4.9 (and 4.9.1) have come out, I’ve seen multiple complaints about people getting the following error message, when trying to use WP Admin’s Plugin and/or Theme Editors:

WordPress editor Unable to communicate back with site to check for fatal errors, so the PHP change was reverted. You will need to upload your PHP file change by some other means, such as by using SFTP.

WP announced changes to Theme/Plugin editors in version 4.9.

I installed the WordPress Health Checker, and did the whole troubleshooting thing on one of our customer sites. I was unable to identify any plugin that would cause a conflict with the known session_start() issue outlined in this bug report.

A bit further down, I did see someone recommend that two files be replaced inside the wp-admin file folder (wp-admin/theme-editor.php and wp-admin/includes/file.php). I took it a step further and replaced wp-admin/plugin-editor.php, as well… all from the WordPress 4.8.3 release.

While I know this is absolutely not the preferred way to “fix” this issue, I am happy to report that by replacing these three files with ones from 4.8.3, the error message has gone away.

The WordPress Team needs to get this issue addressed, and the issue affecting the “loopback” issue, as identified in the Health Checker:

The loopback request to your site took too long to complete, this may prevent WP_Cron from working, along with theme and plugin editors.

Result from testing without any plugins active: The loopback request to your site took too long to complete, this may prevent WP_Cron from working, along with theme and plugin editors.

There’s a separate manual workaround available for that (WP Cron, and having it run at the server level), but that’s for another topic, for another day.

How to handle WordPress leftovers?

Marc Bijl — Thu, 14 Dec 2017 14:57:40 +0000

Scanning a brand new website, I get a bunch of warnings. It seems these are generated by leftovers of a WordPress 8 version, since the same issue occured here:

https://www.ads-software.com/support/topic/worrying-flagged-issues/

What is the best way to clean the WordPress core structure and files? Just deleting all the mentioned leftover files (and should I delete other files as well, may be)? Or ignore them and wait for a new WordPress version to clean these files? Something else; may be there’s a Wordfence option that handles these WP 4.8 to 4.9 update issues?

This is my list of warnings:

This email was sent from your website “FoodLab Limburg” by the Wordfence plugin.

Wordfence found the following new issues on “FoodLab Limburg”.

Alert generated at Thursday 14th of December 2017 at 02:31:12 PM

Warnings:

* Unknown file in WordPress core: wp-admin/css/press-this-editor-rtl.css

* Unknown file in WordPress core: wp-admin/css/press-this-editor-rtl.min.css

* Unknown file in WordPress core: wp-admin/css/press-this-editor.css

* Unknown file in WordPress core: wp-admin/css/press-this-editor.min.css

* Unknown file in WordPress core: wp-admin/css/press-this-rtl.css

* Unknown file in WordPress core: wp-admin/css/press-this-rtl.min.css

* Unknown file in WordPress core: wp-admin/css/press-this.css

* Unknown file in WordPress core: wp-admin/css/press-this.min.css

* Unknown file in WordPress core: wp-admin/includes/class-wp-press-this.php

* Unknown file in WordPress core: wp-admin/js/bookmarklet.js

* Unknown file in WordPress core: wp-admin/js/bookmarklet.min.js

* Unknown file in WordPress core: wp-admin/js/press-this.js

* Unknown file in WordPress core: wp-admin/js/press-this.min.js

* Unknown file in WordPress core: wp-includes/js/mediaelement/background.png

* Unknown file in WordPress core: wp-includes/js/mediaelement/bigplay.png

* Unknown file in WordPress core: wp-includes/js/mediaelement/bigplay.svg

* Unknown file in WordPress core: wp-includes/js/mediaelement/controls.png

* Unknown file in WordPress core: wp-includes/js/mediaelement/controls.svg

* Unknown file in WordPress core: wp-includes/js/mediaelement/flashmediaelement.swf

* Unknown file in WordPress core: wp-includes/js/mediaelement/froogaloop.min.js

* Unknown file in WordPress core: wp-includes/js/mediaelement/jumpforward.png

* Unknown file in WordPress core: wp-includes/js/mediaelement/loading.gif

* Unknown file in WordPress core: wp-includes/js/mediaelement/silverlightmediaelement.xap

* Unknown file in WordPress core: wp-includes/js/mediaelement/skipback.png

* Unknown file in WordPress core: wp-includes/js/plupload/plupload.flash.swf

* Unknown file in WordPress core: wp-includes/js/plupload/plupload.full.min.js

* Unknown file in WordPress core: wp-includes/js/plupload/plupload.silverlight.xap

* Unknown file in WordPress core: wp-includes/js/swfupload/plugins/swfupload.cookies.js

* Unknown file in WordPress core: wp-includes/js/swfupload/plugins/swfupload.queue.js

* Unknown file in WordPress core: wp-includes/js/swfupload/plugins/swfupload.speed.js

* Unknown file in WordPress core: wp-includes/js/swfupload/plugins/swfupload.swfobject.js

* Unknown file in WordPress core: wp-includes/js/swfupload/swfupload.swf

WP 4.9 Plugin Problem No Edit Link

montanan — Tue, 28 Nov 2017 17:55:15 +0000

Yesterday I updated my plugins and they all failed. This happened after the site was automatically updated to 4.9. It appears they are all updated because there are no updates available. However, all of the edit links are missing. I am getting a few red bars with errors on failing to load parts of plugins. Not sure if this is related.

I cleared the cache. I tried new browsers with no change. I also tried a different install with a backup installed (WP Migration). The same thing happened only after I updated to 4.9.

Last I did a new install on my localhost with the newest download of WP 4.9. and did nothing else but install Jetpack and still no edit button.

Needs urgently to be updated

oekom — Tue, 28 Nov 2017 13:33:38 +0000

Please update the plugin to make it compatible with WordPress 4.9

Zip Recipes Not Working with WordPress 4.9

rbennett — Sat, 25 Nov 2017 20:30:47 +0000

Not working with wordpress 4.9. Just get dark screen when trying to EDIT posts. Have tried several different posts.

See screenshot – https://snag.gy/sycAWf.jpg