Hi,

It’s the same as in this thread.

There is an issue in the logic of checking for the WP version in order to update deprecated or new option:

function compatible() {
    return (
        intval( explode( '.', get_bloginfo('version') )[0]) >= 5
        && intval( explode('.', get_bloginfo('version') )[1]) >= 5
    ) ? true : false;
}

This is checking for the two first numbers in the version, and returning true if both are bigger or equal 5 which makes no sense:

5.6.0 -> true
but
6.0.1 -> false (because 0 < 5)

So then the below causes the issue:

# 'Comment author must have a previously approved comment' (checked)
if ( compatible() ) {
    update_option( 'comment_previously_approved', 1 );
}
else {
    update_option( 'comment_whitelist', 1 ); # deprecated since WP 5.5.0
}

Deprecated: Function update_option was called with an argument that is deprecated since version 5.5.0! Zmieniono nazw? opcji z “comment_whitelist” na “comment_previously_approved”. in /Users/dawid/Local-Sites/pyrkonpanel/app/public/web/wp/wp-includes/functions.php on line 5663

Ideally function compatible should use version_compare() to identify compatible WP version.

version_compare( get_bloginfo('version'), '5.5', '>=' )

In Site health showing error as follows…
“The REST API encountered an unexpected result”

So this has been reported here before, to no avail as near as I can tell. The other disable blogging plugin had the same problem according to their support forum but they apparently found a fix. Should I switch to them?

• This topic was modified 2 years, 6 months ago by Anonymous User 17976131.

Hello.
File functions-general.php must be updated to (lines 305 to 310)

if ( compatible() ) {
update_option( 'comment_whitelist', 1 ); # deprecated since WP 5.5.0
}
else {
update_option( 'comment_previously_approved', 1 ); # deprecated since WP 5.5.0
}

To get rid of DEPRECATED message

We use Gravity Forms on our site along with this plugin. I was having issues not being able to save a form i was trying to create. After some trial an error, when disabling this plugin I was finally able to Save the form.

/wp-json/oembed/1.0/embed

etc

is still being added

Using the Health Check plugin, I discovered that the problem I was having where adding or editing posts or pages loads an empty browser tab is being caused by the Disable Blogging plugin. Anyone else having the same?

Errors on every page load:

Deprecated: update_option was called with an argument that is deprecated since version 5.5.0! The “comment_whitelist” option key has been renamed to “comment_previously_approved”.

Any chance we can get this fixed soon? This issue has been around for almost a year now.

Good afternoon!

Thanks for a great plugin! I get the following error message in my Site Health tool when I activate your plugin:

<strong>The REST API encountered an unexpected result</strong>

The REST API is one way WordPress, and other applications, communicate with the server. One example is the block editor screen, which relies on this to display, and save, your posts and pages.

The REST API call gave the following unexpected result: (403) {"code":"rest_cannot_read_type","message":"Cannot view post type.","data":{"status":403}}.

I think another user reported the same/a similar issue some months ago. For the time being the error doesn’t seem to cause any functional issues across my site, but I thought I should let you know anyway in case you’re still working on a solution. I’m using version 2.1.0 of the plugin, by the way.

Cheers!

/jenny

Seemingly disables WP’s Feed widget in Widgets even with Feeds enabled in the plugin’s settings.

Could be a WP limitation but isn’t noted in plugin’s settings anywhere.

Hello,

After updating to WP 5.6 there are severals issues seen.

Permalink edit button doesn’t work. Also, setting page is not being loaded.

It’ll be awesome if you could fix this.

I have installed the plugin and activate it.
Choose disable option in General tab in Blogging Settings.
Still not working,
“Oops! That page can’t be found.
Return to home page
It looks like nothing was found at this location. Maybe try a search?” on the screen.

In the Reading tab in Blogging Settings there is not “Front Page Displays” option

Please see screenshots:

View post on imgur.com

After updating to 5.5, it generates the following errors on every page load.

Deprecated: update_option was called with an argument that is deprecated since version 5.5.0! The “comment_whitelist” option key has been renamed to “comment_previously_approved”.

Hi there,
really appreciate the ability your plugin offers and all the additional side options too – thanks a lot for this great piece of work!

Found out, that – when activated – suddenly a lot of entries in the dashboard are missing. – Looked up and down the settings in the ‘blogging’ settings, tried a lot with these options, but couldn’t figure out, which might be the culprit …

Only disabling the entire plugin helped.

Even a complete fresh WordPress test installation in a new database directory didn’t help.

Any help is highly appreciated.

Thanks in advance and best regards,

Hubertus

Wordpress V. 5.4.1
Disable Blogging V. 2.0.4

Hi there.
Using last wordpress update we see as almost in every admin page this line on top:
“Deprecated: contextual_help” and “Use get_current_screen()->add_help_tab(), get_current_screen()->remove_help_tab() instead.”

I know you are aware of it, but .. meanwhile … what can we do to get rid of it?

Thanks!

Hello.

Are you planning update this plugin?

Thank you in advance.

this is the error:

The REST API encountered an unexpected result

The REST API call gave the following unexpected result: (403) {“code”:”rest_cannot_read_type”,”message”:”Cannot view post type.”,”data”:{“status”:403}}.

Love the plugin but hate the icons in the plugin page! Any chance you can get rid of them? They disrupt the nice minimalist flow going on there.

I tried to disable the visual editor and toolbar, same as few other profile fields. It just dooesn’ work.

Thanks.

The Meta widget has been wipe out from all available widgets, I cannot add this to the sidebar to let user click on login link.

Please add an option to show/hide Meta widget (or maybe other widgets if it is not necessary to hide).

In WordPress Multisite, for sub sites that activated this plugin and have option set.
On uninstall the plugin the options name that contain factmaven_ are left in options table for sub sites. It is already clean on main site.

Please cleanup options on delete for sub sites.

Thank you.

Hey,

I like the idea of being able to disable the blog if it isn’t needed. But the “Blog” page still shows up in the pages list within widgets ect.

Could you maybe have it hide the blog page from everything?

When clicking it it also seems to use the search page instead of issuing a 404 or redirecting to the homepage.

Good idea though!!

Hi,

I’m trying to create a pretty huge CMS with wp and I like the non-blogging idea. But i still need a specific homepage (home.php).

Is it possible to select the home.php template file as the homepage? Or do I have to set an actual “static” page?

Thanks!

If I have this plugin enabled CSS changes made to a child theme do not take effect. If I disable the plugin, the CSS changes are displayed correctly. With the plugin renabled, a cached version of the CSS file is used. How can I resolve this?

Clearing browser cache does not fix when the plugin is enabled.

Thanks,
Paul.

Installed your Disable Blogging plugin.
Now. Instead of the usual “Nothing Found…..Apologies, but no results were found for your request. Perhaps searching will help you to find a related content”,
I now get:
“Oops! That page can’t be found.
It looks like nothing was found at this location. Maybe try a search?”
Different, but no improvement! How can I remove these messages altogether? I am trying to set up a website not a blogging site! No input required except by admin.

Hello @ethanosullivan ??

I just wonder if this plugin is compatible with the current version WordPress Multisite?`

Thanks!

Kind regards
AngryWarrior

Would it be possible to also include hiding category? I can hide the author pages, but the category pages are still there…

Thanks!

I installed Disable Blogging and now my home/front page shows a 404 page only. It was working before installing the plugin. In Settings>Reading, my home/front page is not listed, although all the other pages are. The theme I’m using is Enigma Parallax. As an experiment, I tried deactivating Disable Blogging and it didn’t solve the problem. Neither does uninstalling it. Please help! Thanks.

My home page now is 301 redirect to a post after installed your plugin.
It’s working very well at earlier wordpress version

Hi Fact Maven,

We activated your plugin about a month ago and it does exactly what you say it does and what we wanted.

There’s just one problem: since upgrading to the latest version of Visual Composer, your plugin now interferes with it in an ever so slight but crucial manner: when Disable Blogging is activated, the row and column tags disappear from front-end editing on VC, which makes it extremely difficult to use VC properly (I wish I could show you a screenshot of what I’m talking about, but WordPress doesn’t appear to offer this).

This was the response I got from VC’s support team regarding the conflict:

“Unfortunately, the disable blogging is a third party plugin and we are not aware of the code used in it. We checked it further and it looks like some CSS and Js code from the plugin is altering the visual composer causing this issue.”

Do you have any idea what could be causing the issue in your plugin’s code? I’ve disabled your plugin temporarily as we absolutely must have the full functionality of Visual Composer. However, once we go live, we need both their plugin and your plugin activated.

Thanks.