lowe_22

Have you had any more thoughts about how to make this work? I’m still keen to get this implemented if possible. What actions or filters are associated with media edit screen? Is there an action ‘view edit’ or something? Or am I just going to have to copy a lot of functionality from wp-admin/media-upload.php into File Gallery?

Thanks

Hey,

I’m actually already using Advanced Post Types. How can i set this up using the Advanced plugin?

Cheers

Hey,

Sorry it’s taken me so long to get back to you on my own post! I didn’t really know where to start with filters or actions. I was thinking about trying to replicate the form from wp-admin/media.php in the file-gallery but haven’t had much luck so far.

Do you have any ideas?

O

Ah, my bad. Sorry for the confusion – I stumbled on this post searching for issues with the Simple Events plugin didn’t notice the title!

Great plug-ins by the way, I think I’m using most of yours on my WP sites.

Thanks, Olly

Steve,

Just to clarify, I’m referring to the Simple-Events plugin, not Developers Custom Fields plugin.

Sean seemed to be having issues getting Simple Events to work and all his symptoms fitted mine exactly, and as I’d managed to sort those out with this fix I assumed it was relevant.

Adding a priority of 10000 seems like a good idea. Will be happy to submit an issue on the Simple-Events GitHub for you

Cheers,
Olly

Hi Sean and Steve,

I was having the same issue with the plugin. I installed it, check for any namespace conflicts and after discovering no issues started debugging.

I noticed both the plugin and your register_post_type functions are called on ‘init’ action.
You need to make sure that WordPress calls your register_post_type function before the plugin ‘init’ action so that the post type exists before the plugin is activated.

Do this simply by adding a priority of ‘1’ to your register_post_type function, thus:

function create_my_post_types() {
	register_post_type( 'event',
		array(
			'labels' => array(
				... labels here ...
			),
			'public' => true,
			'supports' => array( 'title', 'editor', 'thumbnail' ),
			       ... more options ...
		)
	);
}
add_action( 'init', 'create_my_post_types', 1, false );

It works for moe now, so I hope that helps.
Might be worth putting that as a note in your plugin readme, Steve? Or just add a lower priority to the plugin init action.

Olly

Sorry, I should have clarified a bit – I’d like /showreel/this-project-name essentially to redirect to /showreel#234 so that entering the first address would have the same effect as the second, if you see what I mean?

Not sure of the best way to achieve this. I just need a pretty way for a client to be able to skip down to an individual post rather than using a # in the url if possible.