Support » Alpha/Beta/RC » wp_editor api a few observations

  • Using 3.3beta1 nightly.

    I am using the editor on the bbpress plugin and it works almost as expected with just a couple of issues.

    1. If you are on a really long page with the editor on the bottom of the page, click the media button to add media and notice the embed media popup is way up top out of view.

    Should it not center on the screen?

    **was trying it on an ipad and for a long time I thought it was broken, until I accidentally scrolled way up and found the editor… very confusing

    2. I as a super-admin in a multisite setup am the only one able to add images to the post and have them actually show up. Every other user sees the following behavior.

    – add image to editor
    – image shows up in editor when click add to post
    – publish post, no image shows up.

    3. There is no visual editor button on the ipad, no matter what account level I am logging in as, even super-admin.

    4. Is there any way to activate the visual editor as a default?

    – I allow guest posting on the bbpress side, so they get the editor, but enless logged in, there is no option to use the visual editor.

    Are these all bugs, or am I just missing something?


    gotta say, this is awesome having the new editor api, huge kudos to the devs on this one!

Viewing 7 replies - 1 through 7 (of 7 total)
  • I know it’s only been 4 days, but does no one have any ideas?

    Are there other channels I should be asking in?
    I tried both channels on freenode, stackexchange, and a number of other sites, but no answers or hints anywhere…

    Am I simply in uncharted territory?

    *do these questions deserve trac tickets?

    Moderator Ipstenu (Mika Epstein)


    Lead Plugin Wrangler

    Are you trying to activate the visual editor on the front end?

    Yes, I have the visual editor activated on the front end. The new api makes it incredibly easy to use.

    Basically I took the bbPress plugin and removed the textarea input for topics and replies and replaced it with the wp editor.

    $post = get_post($post_id, 'OBJECT');
    $tabindex = bbp_get_tab_index();
    $settings = array(
        	'wpautop' => true,
        	'media_buttons' => true,
        	'textarea_rows' => '15',
        	'tabindex' => $tabindex,
        	'editor_class' => 'tumble',
        	'tinymce' => true,
        	'quicktags' => true
    wp_editor( esc_html($post->post_content), 'bbp_reply_content', $settings );
    Moderator Ipstenu (Mika Epstein)


    Lead Plugin Wrangler

    Ah, okay, that makes a little more sense.

    I wouldn’t raise this as a bug, since it’s not a bug, it’s just you trying to do something that isn’t ‘normally’ done. Actually I don’t know anyone who’s doing it yet.

    I WOULD email this idea to hackers, though.

    Thnx so much for your time on this.

    I didn’t realize that I was doing something unusual, kind of thought the entire point of having the wp_editor api like it is being built was for the sole purpose of having the editor on the front end. Maybe it’s just so new that’s it is not yet mature enough to be used..

    I imagine that once people see the new api that these issues are going to come up a lot in the near future.

    I will email the hackers group for advice.

    I should add that other than the problems I note above, that the editor actually works pretty good. I think a lot of us have been waiting years to have this ability, and I’m excited to see what it will bring about.

    *didn’t want anyone think I was complaining, more to the point, I am overly excited to get this all worked out as it’s so awesome.

    created a couple of trac tickets for the 2 major issues:

    *I sure hope that I am not breaking any rules or protocols by creating trac tickets without patches.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘wp_editor api a few observations’ is closed to new replies.