sjohnso3

Yes, it is a pro feature and I am trying to do it with a Pro 7-day trial/demo site. Switching to another user isn’t quite what I want to do, either, as the whole point is I’m trying to manually register somebody who does not have an account and for whom I don’t necessarily want to create an account. We have lots of older customers who might call and want to register for an event (and then pay at the door).

Oh, and I’m trying to pull everything into the All In one Time.ly plugin.

I want to say how much I love this plugin and how much I hope recurring events are added to its functionality very soon. Otherwise, my event feed looks very slim.

I haven’t tried that Clone option. I will do that next time. The duplicator plugin uses that same terminology so I thought it was the same.

I ended up going into the WordPress tables and deleting the rows corresponding to the “ghost” events in the posts table. While mucking around, I noticed the table All-In-One created and uses and I *think* the problem was that the duplicator plugin simply didn’t create an entry in that table when it duplicated the event. (It only duplicated the rows in posts and postmeta.)

I’m probably not naming everything quite right as I’m working from memory and only know enough about the wordpress table structure to be dangerous.

Anyway, thanks for pointing out the “clone” option – I’ll use that in the future.

To clarify, I guess the problem is simply that the “Custom Message” is being retained when a post is cloned/duplicated. It would be nice if that wasn’t retained as that is hidden by default, and really the only time one should need to show it is if one wants a custom message, which usually we do not.

That is not a viable solution for me because I use the image elsewhere so I don’t want to delete it from the media library.

However, with a little trial and error and browsing in phpMy Admin, I figured it out. Here’s what I did for anybody else in the situation.

I went into the wordpress database and to the table _postmeta and looked in the meta_key for content with the word “header” and discovered two entries that had “_wp_attachment_is_custom_header” as the meta_key. As I had two images currently uploaded as “headers” this seemed promising. I looked at the post_id in the two entries and the post_id corresponded to the post_id of the two header images. Even more promising! I went back into wordpress, uploaded another image as a header, and voila! A third entry in _postmeta with “_wp_attachment_is_custom_header” appeared. I had it!

So, I simply deleted the table entry for the image I no longer wanted WordPress to consider a header, refreshed the header configuration page, and the image was no longer displaying as an uploaded image. I checked my media library and the image was still there (yippee!) but it no longer had “Header Image” noted next to the file name.

Not for the faint of heart, but worth it so I didn’t have to delete and re-upload the image and fix links to the old image across the site.

Happy to!

Here is the configuration page. You see two headers uploaded. I want to remove the first image, but I use that image in other posts on the site so I don’t want to delete it from the media library.

Config page.

And here is where I can see in the media library that the image file has been marked as a header.

Media Library

I’m using the Spacious theme. But I think the random header option is just part of the basic wordpress codex, isn’t it?

Having the same issue. Somebody said it was Jetpack issue, not that it helps. I’m using the Weaver II pro theme.