Skip to:
Content
Pages
Categories
Search
Top
Bottom

3.3 compatibility

  • Profile photo of sboisvert
    sboisvert
    Participant

    @sboisvert

    I might be wrongly diagnosing this, But I thought I might as well leave this note for anyone else who might come across it. While using 3.3 Beta 2, I had to change :
    add_action( ‘wp’, ‘ass_update_group_subscribe_settings’, 4 );
    to:
    add_action( ‘wp’, ‘ass_update_group_subscribe_settings’, 3 );
    If not your changes did not get saved. Again take this with a grain of salt, I didn’t try it on a clean 3.3 beta 2 install with nothing else running. so its more of a, if you have this problem, try this solution kind of post.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Profile photo of Boone Gorges
    Boone Gorges
    Keymaster

    @boonebgorges

    Good point. You can avoid the whole issue by switching the hook from ‘wp’ to ‘bp_actions’ (assuming you’re running BP 1.5+).

    Profile photo of sboisvert
    sboisvert
    Participant

    @sboisvert

    Perfect, I wasn’t sure exactly of the order and what is the preference of what to use. I found 5 instance of ‘wp’ used in actions, do you want me to submit an svn diff or is it just as easy for you to do it yourself since you’re maintaining the plugin?

    Profile photo of Boone Gorges
    Boone Gorges
    Keymaster

    @boonebgorges

    It’s easy for me to do. I need to find a decent backward compatible way to do it, anyway. Thanks though!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘3.3 compatibility’ is closed to new replies.
Skip to toolbar