Can't edit permalink

hrm, .. did you check the screen options tab in the upper right to see if the option is enabled for you to edit permalinks?

Sorry for the delay in reply, I’ve been away for a couple of days, yep I have all check boxes on.

I can’t see the edit box for the permalink even on a brand new comic, at any stage. I can quick edit, but that’s it.

Can you see the edit of permalinks on regular posts?

yes mate, can see and edit regular posts fine. ??

I can use the quick edit to change the link, just not in the main edit screen in Comic posts.

okay “mate”.

This would happen if a 3rd party plugin is running some scripts that is not being inclusive to their pages they’re supposed to be on. (i.e in the head/section of all the admin pages and not just the ones for the plugin it comes from) – – bad programming on their part.

Since I cannot duplicate it on the 7 sites with 5 different browsers that is the only logical conclusion.

So, disable all of your plugins except comic easel – clear your browser cache and give it a go; you’ll notice that you can edit it.

Phil,

I have deactivated all pluggins save Comic Easel and then I have cleared the cache on both IE and Firefox browsers.

I have emptied out my functions.php file and cleared the caches on both sites all over again.

I even cleared out the custom CSS. and cleared the cache on both browsers.
I cannot see the permalink edit box.

EDIT:
I also changed from the comic easel child theme I am on to the parent theme. No hope.

Incidentally, I have just activated the custom post types in Jetpack and have created a portfolio type. When I save to draft, I can edit the permalink.

This problem really does seem to be limited to comic post types only.

Just to be clear, we’re talking about this:

https://frumph.net/downloads/edit-slug-box-in-editor.jpg

—–

If you have the [x] slug checkbox from the screen options open up, it opens up ANOTHER box lower on the page that looks like this:

https://frumph.net/downloads/slug-screen-option.jpg

two different areas

—–

If you are not seeing the first one. The box itself is set to ‘not display’ .. not be seen at all because of this class=”hide-if-no-js”

If you are using a plugin or bit of code someplace that edits the tinyme editor and it wasn’t updated past 3.9 this would cause an issue.

If you have javascript disabled in your browsers, this would happen.

If another plugin de-enqueue’s jquery and re-enqueue’s their own jquery this could happen.

^ But in all of those cases it would happen to all of the places and not just the comic section.

If you were to use Chrome debug (F10 key pressed) or Firefox with Firebug (F10 again) and enable script debugging and load your editor, you can see if there’s any editor bugs that pop up and find exactly where it’s at.

But at this time, there’s no way for me to duplicate the particular issue where the edit-permalink box isn’t showing; so I am relying on you to go through the steps that I can think of – and the only one I can think of is that there’s something conflicting with the display of the box

Hi Phil,

Yes the slug edit box is there, but the permalink edit box is not.

As I said before I disabled all plugins, apart from comic easel, I removed all custom code from functions.php and still the box is hidden.

In the Chrome debugger, the only exception I can see is a complaint about the use of a deprecated function in TinyMCE. Which stinks of what you said above a bit. I can’t seem to trace that beyond the wp-admin post.php. Is there a way to trace what plugin is using that? As I said I have already disabled all my plugins before.

again to confirm, all other post types seem ok.

That tinymce complaint is probably what’s doing it ;/ do you get that same complaint on the regular post pages?

Yep it’s on the standard page too. Maybe a red herring?

BTW, sending you messages on Skype Phil. Not sure if you’ve seen? But wondered if you wanted to RDP \ webex \ team viewer over and I can show you the dashboard.

I have no idea what RDP \ webex \ team viewer is ;/ but loading skype now.

Okay this was fixed in the next release.

Turned out the method I was using to use chapters in the url line caused this to happen.

Rewrote it.