Not working with WP 4.2

Hi lklawless,

I suspect your issue is caused due to plugin conflict.

Please try disabling all plugins and lets see if this behavior appears.

Thanks,
Yaniv

For now though, until we figure out what’s happening – try installing this version of the plugin – https://downloads.www.ads-software.com/plugin/wp-category-permalink.1.6.zip

Hi Yaniv,

Thanks for responding. I don’t use WooCommerce.

I haven’t added any new plugins lately, only upgraded to the latest version of WP, and that’s when the permalink option went away.

I installed the old version of WCP and still have the same issue. ??

I’m getting this error in FireFox’s web console:

TypeError: jQuery(…).sCategoryPermalink is not a function post.php:2691:0

Here’s my site, if you want to take a look: https://www.lawlessfrench.com

Hi lklawless,

I still suggest you try disabling your plugins as perhaps an update to one of them is causing a conflict.

Nevertheless Iv’e asked Jordy to pitch in and try to seek for a solution.

Best,
Yaniv

I’ve tried disabling all the plugins and I even downgraded to version 1.4 per Julie’s suggestion, but no matter what, I don’t have the option to set the permalink and I get the same error: TypeError: jQuery(…).sCategoryPermalink is not a function post.php:2691:0

All the permalinks I’d set previously are still ok, but I can’t do any new ones, and I guess I have to live with that. ??

Thanks for trying to help.

Hi lklawless,

I’m sorry to hear that it still doesn’t work.

Lets try replacing your theme, and also try deleting your browser’s cache / surfing from a different browser.

Yaniv

Hi Yaniv,

I’ve cleared my cache and tried different browsers, no luck. I’m not going change my theme.

I went back to the Hikari plugin and that works. I know yours is better, but right now, I just need it to work, so I’m going to stick with Hikari.

Thanks again for trying to help.

Ugh. Well, I’m glad there’s another option for you!

Just by chance, did you try it with Chrome? It seems like you are using Firefox. Would love to know if that bug happens on a certain browser only, that might be the case.