dave nicosia

I don’t use WP Category Permalink myself. I was just making sure it was compatible for a customer of mine using it along with my plugin.

My only suggestion is to make it clear in the install instructions that you have to use /%category%/%postname%/ for it to work properly.

okay. so version 1.6 and your latest version work properly when I use: /%category%/%postname%/ for my custom permalink – which I did not see anywhere in your documentation.

I also confirmed that it works properly with my plugin, WP ComPEAR installed. Both versions worked along with WP CopMPEAR just fine.

Same result Jordy. When I look at my wp_postmeta database table – I see that the correct category ID I saved as the permalink is there with the correct post ID, but it is not bold anymore on my post after updating, and my permalink does not change.

I don’t have any javascript errors on the front end while viewing the page, or on the back end when editing a page.

Here’s the issue I experience. When I click to set a category for a permalink on a post, it turns bold. Then when I update my post, it is no longer bold and does not save it.

I don’t use this plugin myself, but I wanted to clarify it is not a conflict with WP ComPEAR, as I experience the issue on two websites that have never had WP ComPEAR installed.

This is Dave here, author of WP ComPEAR. I tried the current version of this plugin on two different websites NOT running WP ComPEAR, and my chosen category for the permalink does not save at all when I update a post.

I tested on a fresh install of WordPress and this plugin, and it does not add my category to the permalink or save my category permalink choice.

I’m almost positive WP ComPEAR does not conflict with this plugin at all.

No that didn’t work.

I’ll describe the issue a bit more.

So I have a plugin that creates a slider. There are multiple instances of the wp_editor in them and they are run through the content filter: apply_filters(‘the_content’, $wysiwyg_content);

The plugin need to do this to make shortcodes work in the fields.

When I remove that content filter from the plugin code – the issue goes away but this is not an option since the wysiwygs in the plugin need to run through the content filter.

Another note is that the slider created by the plugin is inserted into the post via shortcode.

Any other ideas?

Ahh you were correct. The issue was with the Simple Share Buttons Plus Plugin. I apologize and mark this resolved or remove it.

Thanks!

Dave

I found this article that explains the exact problem and the solution:

https://pippinsplugins.com/playing-nice-with-the-content-filter/

Here is the part that applies:

In order to solve this problem, we can use one more conditional tag. The is_main_query() function was introduced in WordPress 3.3 and allows us to check whether we are currently inside of the main post query. The main post query can be thought of as the primary post loop that displays the main content for the post/page or archive. By using this tag, our filter will NOT get applied to any custom loops in sidebars, footers, or elsewhere, even if they use this:

So, my question is, can you please update your plugin to accommodate this? I’m sure it will solve this issue in many plugins compatibility issues.

Thanks!