jackhowell

Hi @tigroumeow!

Nope, normal media scan. It removed the images it seems, but left the count.

Perhaps caching, but admin-side is rarely cached. It’s odd, because the number didn’t change after the scan and delete (including emptying the trash).

@adamwalter, the hero we needed.

The developer is clearly ignoring this issue as it was raised in another thread too only a week ago (with a “we will follow up” response).

Argh, this is the most annoying popup, guys! It’s plaguing a couple of my sites now. Would you please nudge its priority? ?? Of course, we like you, but the point is a little laboured now!

Post data, yes.

I might have confused the matter: this is strictly to do with importing data using WP Import/Export for posts, not CPTUI settings.

I meant if I had not been able to set the hyphen, I could have modified the data XML before import to use the “new” underscore format. So that when importing into the new site, WordPress recognised post_type_name (as it would be renamed in the data).

Thanks, @tw2113, yes, this is entirely trackpad driven on OSX.

It usually wouldn’t be a problem but, in this case, I have 250+ posts all using a series of categories and tags with hyphens in them to import.

I used Chrome to paused the DOM, pasted the text, resumed JS and saved. Temp fix, worked OK. Bit messy.

I expect using a different method of importing the posts I could rename them to use underscores, or even edit the XML to replace all the names with the more suitable underscore version. However, if the client wants to re-import again (and again) due to changes, that would be a repetitive task.

Thanks for looking into it!

I’ve attempted this, following the paste method correctly, but no matter how I try to sneak up on the input field it always changes to underscores.

My problem is: I’m importing custom post type data from another site, where they are hard-coded with hyphens. So even using the slug re-write, the CPT still has an underscore, so the import fails to find the categories.

I completely appreciate the technical reasons why this is in place. Please add an advanced setting to disable the keyboard hyphen to underscore function.

In the meantime, is there any other way around this?