davekuhar

Hey TaxJar, any response to this?

Eh, it was an idea. I can see why you wouldn’t want to bother chasing Yoast spam everywhere. I just added this to my functions.php file:

// Tired of Yoast spam
function shut_up_yoast() {
   echo '<style type="text/css">
           #duplicate-post-notice {
           	display: none !important;
           }
         </style>';
}
add_action('admin_head', 'shut_up_yoast');

Sure: https://www.screencast.com/t/mdUUz8K5AW

Note that the ID of the div is duplicate-post-notice

My apologies – I misunderstood the issue my client is having. They’re using a different plugin to push their posts to Facebook, not pull their feed from it. For that, they use your plugin and it’s working fine.

Figured you’d say that. I’m trying to get support from them now. I may have to switch to SearchWP’s Modal Search Form instead.

Hi Vinod,

Yes, I’ve determined it’s a theme conflict issue. I was hoping you’d be able to give me some idea how themes commonly conflict with Ivory Search, as I can’t seem to find any evidence of an error in the console.

Thanks. I was pretty sure that was going to be the answer, I just wanted to verify before passing it on to my client.

That’d be fantastic. It’s hard to manage a long, complex set of categories with access to only two levels. Thanks!

Try this one.

Hey, plugin author: you need to remove this code permanently, since there’s no point in having it and it just breaks my fix every time you issue an update. You don’t need to hard code a port number.

Hey Dan, thanks for replying. I also reached out via your site’s contact form and have worked out the issue with tech support. It seems my client hasn’t yet set up ACH processing. I’m sure once that’s worked out the error will be corrected.

For reference, here are the lines to remove:

    $port = (isset($_SERVER["SERVER_PORT"]) && ((!$isHTTPS && $_SERVER["SERVER_PORT"] != "80") || ($isHTTPS && $_SERVER["SERVER_PORT"] != "443")));
    $port = ($port) ? ':'.$_SERVER["SERVER_PORT"] : '';

Thanks. It’s odd, I don’t think the update notice was working.

I tried deleting and reinstalling the plugin, then repairing permissions on the server, but I’m still getting these messages.

Warning: fopen(/nas/content/live/partnershc/wp-content/plugins/popup-maker/popup-maker.php): failed to open stream: Permission denied in /nas/content/live/partnersintl/wp-includes/functions.php on line 4782

Warning: fread() expects parameter 1 to be resource, boolean given in /nas/content/live/partnersintl/wp-includes/functions.php on line 4785

Warning: fclose() expects parameter 1 to be resource, boolean given in /nas/content/live/partnersintl/wp-includes/functions.php on line 4788

Any other ideas?

Any chance you worked this problem out? I’m getting the same error messages:

Warning: fopen(/nas/content/live/partnershc/wp-content/plugins/popup-maker/popup-maker.php): failed to open stream: Permission denied in /nas/content/staging/partnersintl/wp-includes/functions.php on line 4782

Warning: fread() expects parameter 1 to be resource, boolean given in /nas/content/staging/partnersintl/wp-includes/functions.php on line 4785

Warning: fclose() expects parameter 1 to be resource, boolean given in /nas/content/staging/partnersintl/wp-includes/functions.php on line 4788

I deleted and reinstalled the plugin from the repository. Upon activation I get the same PHP warnings, plus this message:

The plugin generated 602 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.