K2 Hook Up v1.3 Released

I’ve updated my K2 Hook Up WordPress plugin to include support for two of the latest K2 Hooks: template_primary_begin and template_primary_end. You need to be running the latest version of K2 to take advantage of it, but once you are, K2 Hook Up will help you target over 10 regions in your theme with the content of your choosing – without having to edit any files. Current Users will be able to auto-update from wp-admin. New Users can get started here.

For developers looking to contribute to the plugin, K2 Hook Up is now on GitHub, so fork the project and send me a pull request with your changes.

9 Responses to “K2 Hook Up v1.3 Released”


  • I am running k2 815 with K2 Hookup. Have those hooks that you mention been implemented in that version. Also, is there any documentation regarding these hooks (template_primary_begin and template_primary_end)? Thanks.

    • You should be okay, there are only a couple of commits after that. There really isn’t any documentation, except on the plugin’s homepage: K2 Hook-UP about where the different hooks are in the template. I would experiment with it and see where it prints out the contents.

  • So I experimented with the latest nightly of k2 (817) and k2 Hook Up 1.3 and neither Primary Begin nor Primary End will hold the basic html code I entered. I typed in a basic paragraph (with p tags), pressed Update Options and the code disappeared. No php – just html. I tried it in other hooks and it works fine. Am I missing something? Thanks!

  • Hi Eric,
    Version 1.4 has two sets of “Before Content” and “After Content”. The second set seems to target the template_entry_head and template_entry_foot hooks. The labels are a bit confusing.
    Loren

    • Thanks again for the great feedback. v1.5 fixes the labels. They should have read ‘Entry Head’ and ‘Entry Foot’.

      The update has been submitted and you should receive an notification in wp-admin shortly.

      -e

  • Hi Eric,
    I hate to do this to you but there is still an error in the programming. Now the “Before Footer” block shows
    `Before Footer’); ?>:
    It seems there is a tag that is missing – I didn’t look at the code.
    Loren

Leave a Reply