pavel.simecek

sorry, my fault – i was watching a wrong page

Like… giving you access to my administration? No, there must be another way ??

What exactly you want me to send you and where?

jayarjo, I had the same problem as Vitzkrieg (in ‘init’). But I solved it with moving taxonomy registration to ‘after_setup_theme’. And I proposed this solution also to Vitzkrieg (my first post). Unfortunately, he did not get it.

Btw. I have just tried order of hooks in debugger and no, after_setup_theme comes before init. At least in WordPress 3.6.1

Vitzkrieg, it is just the opposite – you need to register the taxonomy as early as possible so that the plugin could take it into account when its hooks are applied.

Maybe, jayarjo changed hooks in 1.2.2 – I have not tried that.

But for the version 1.2, you can easily work around the problem by registering your taxonomy in ‘after_setup_theme’ hook (as I proposed above), which is the earliest possible in a theme. It works and does not break anything. So no reason to stick to the ‘init’ hook.

It happened to me too with WordPress 3.6.1 and plugin version 1.2 (have not tried 1.2.2 yet). It was caused by the strange behavior of TinyMCE that did not copy its content into a hidden textarea before submitting.

I have fixed that by registering event listener on a submit button like this:

wp_enqueue_script( 'tinymce-trigger-save-fix', get_template_directory_uri() . '/js/tinymce-trigger-save-fix.js', array(), false, true );

where tinymce-trigger-save-fix.js contains a event handler registration:

jQuery('#submit').on('mousedown', function() {
        tinyMCE.triggerSave();
    });

This is a more general problem, not just a bug in this plugin. It affected all plugins that allowed creation of tinyMCE editor in taxonomies.

Yes, you are right. My colleague just showed it to me this morning.

Nevertheless, I still think if it couldn’t be set also in settings of the plugin itself. This way it is kind of hidden option. Moreover, I would prefer if users could not change the option in administration.

Otherwise, the plugin is great. Thanks!

It happened to me too. I have solved it by registering custom taxonomies earlier:

previously I used:
add_action( ‘init’, ‘create_taxonomy_short_course_type’ );

now I use:
add_action( ‘after_setup_theme’, ‘create_taxonomy_short_course_type’ );

Hopefully, it helps.