Paul Menard

@mokhtar-taha,

So sorry to hear you have having issues. You are the first I’ve heard of any fatal errors. Can you advise what version of PHP you are running? I will look into the specific line item issue later this afternoon.

P-

@dc2010 & @jsnyder27,

Thanks for the post. And thanks for providing exactly no information about your WordPress site, your theme or even you settings for Simply Exclude. I can’t begin to help you without something to look into.

@megazip,

Is this still a mystery? Would need to know some specifics about your site. Such as what Theme, your Simply Exclude Settings, etc. Reply back and I see if I can assist.

I think this is resolve.

@bl59marie,

Probably not. Simply Exclude works to filter the main WP_Query executed by WordPress when you load any page on your site. It really doesn’t have anything to control mobile vs standard view. Might want to check with your theme provider.

@cspiegl,

Thanks for your thoughts but that is the current design. Most users will rarely need the option to control the Post at the individual level. Most users really need to filter post categories.

You can remove/hide this column. Here are two methods.

1. Assumed you are viewing the Posts > All Posts screen. In the upper-right corner see the ‘Screen Options’ tab. Click on it. It will expand to show the columns. Simply uncheck the one for Simply Exclude.

2. Second option go to Simply Exclude > Settings. Under the ‘Post Types’ tab scroll to the Posts section. Here you will see setting for ‘Show the extra columns on the Post Type listing and the Post Type edit form?’. Just set the ‘Hide’ option. See image. https://screencast.com/t/5r9bSBY2c

@ ntn09,

Why not just install it via your wp-admin > Plugins > Add New option. Otherwise I really can’t begin to help you as I have no control over why on your site you have uploaded the file. Nor have you provided any information like are you maybe running Multisite, etc.

@clane_workforce,

For your search do you actually use Simply Exclude on filtering search results?

@goldfingyr,

I’m the Media-Tags plugin author. Please let me know if there is anything I can do to help resolve this inter-plugin communications.

Appears somehow a beta version of the plugin was sent out instead of the simpler fix for 2.0.6.4 and 2.0.6.5. Hold tight. Trying to sort out the mess this morning. Will have 2.0.6.6 out shortly. Apologies.

Sorry about that. Somehow the fix did not get included. Just pushed 2.0.6.5. Let me know.

@naresh Vachhani

I have a patch for this but waiting on another user to confirm a different issue. should be released this coming weekend.

interesting note here on your comment

“Getting this error on the front end even if WP_DEBUG set to false.” this is not something controlled by Simply-Exclude. I know you know this so my comment is more for other users. If your hosting is displaying these PHP Warnings I would have them turn off PHP error_reporting as this can expose information about your hosting which can be used by others.

Another interesting issue on this reported fix. Per your correct suggestion the second function argument is optional and needs a default valid. What I find confusing is within the WordPress core there is only one call to the filter ‘get archives_where’. This is from wp-includes/general-template.php line 1374. It is this filter there Simply-Exclude hooks into and connects to the plugin function se_widget_getarchives_where().

If you view this this hook call (see below) you will see there is a second argument passed ‘$r’. So it is confusing as to why there is a need to have this set to a default value within the plugin code.

$where = apply_filters( ‘getarchives_where’, “WHERE post_type = ‘post’ AND post_status = ‘publish'”, $r );

P-

@angiwaters,

As suggested by @bdbrown please got to the plugin support forums. More specific to the Simply-Exclude support forum https://www.ads-software.com/support/plugin/simply-exclude and I’ll be glad to work with you there to get you to a resolution. More than likely it is your theme.

@juliedc,

I just did some testing on Simply-Exclude under WP 4.1.1 and there is no issue I can see which prevent the settings from saving.

Just a note all the Simply-Exclude settings are saved via AJAX not a traditional form submit. So when you click a change you should see the field background go yellow then fade to normal. If you see it red then you have some conflict with your AJAX calls. Normally this is some other plugin or script outputting a PHP Warning which is effecting the AJAX reply.

I can help debug but would need access to your site. Don’t post them here. If you want me to take a look please go to my contact form https://www.codehooligans.com/contact/ and provide the details.

Does 1.5.7 solve this error?

Fatal error: Call to undefined function flat_hook_page_before() in /home/code/public_html/wp-content/themes/flat/page.php on line 2