Plugin causes post/page editor crash

Just coming to add that I just had the same issue and the only resolution was to disable the plugin, as the post above says.

I’m having the same issue. Their site, scriptburn.com is down. My guess would be that it has something to do with the check to see if you have a pro version or not. When their site comes back up, it will probably work fine again.

I just had the exact same thing happen. When I went to edit posts, the layout of the admin was so garbled that it was impossible to edit posts. I deactivated all plugins and the problem went away. Then I activated the plugins again one by one and checked to see if the problem returned. The problem returned when I activated this plugin.

I depend on this plugin for a variety of reasons but unfortunately it’s unusable right now.

I’m running WP 4.9.4 with the latest version of the Florence theme, and the latest version of this plugin.

For now I have changed @line 1081 to avoid printing the erroneous remote resource parsing.

file:
/wp-hide-post/admin/class-wp-hide-post-admin.php

line 1081
return null;
//return $info;

Thanks Dbrossa

But what does this mean for the future of the plugin? I’d start looking elsewhere if the developer doesn’t fix his own site in a decent amount of time.

I have implemented this plugin in it’s place: https://www.ads-software.com/plugins/ultimate-category-excluder/

Work flow is a little cleaner. It has a main settings page that allows you just exclude the categories you don’t want listed rather than having to do it per page. I find that easier to use. Now on my feed I can show only the categories I want.

found this plugin: https://www.ads-software.com/plugins/super-hide-post/

It hasn’t been updated in a while, but whoever made it must have used some of the same code from WP Hide Post because when I activated it, it already had all my hidden posts still hidden.

It may not be a long-term solution, but it will buy some time until WP Hide Post figures things out.

@dbrossa

One suggestion: your solution is still doing the remote post to scriptburn.com and then sidestepping the error that is returned. Would be better to exit the function earlier and skip the remote post entirely (for now. obviously this is not a good long-term solution)

public function default_info($page)
{
    $info = get_transient('wphp_notices_' . $page);
    return $info; // ADD THIS HERE... LINE 1032 OF PLUGIN VERSION 2.0.10

edit: also, wanted to mention that while these fixes will make the edit screen work, it looks like it will NOT enable pro features to anyone who has a pro license, so those users are kind of stuck at the moment. The remote post is validating the license and setting something locally if it is confirmed.

• This reply was modified 6 years, 9 months ago by Dave McHale. Reason: adding note re: pro licenses

@dmchale

Yes, that would probably be safer in case someone nefarious purchased ‘scriptburn.com’ and returned an even worse payload for parsing. I was just leaving the office last night when I came up with that quick fix. Hopefully the developer is aware and will release a real fix soon.

@dbrossa I hadn’t even thought of that, but you’re not wrong. I was mostly thinking that the extra curl post was a waste if we were going to ignore it anyway ?? Agree, hopefully the dev gets his domain back in order soon. Registration dates and DNS all appear to be fine on the surface, but who knows. Cheers!

Note that @dmchale’s solution does not work if you’re trying to recompile the code from their github repository (version 2.1.11)