Forum Replies Created

Viewing 15 replies - 136 through 150 (of 261 total)
  • I would say that this was meant to be as simple and easy-to-use as possible. There’s not going to be anything to distinguish between an “author” or “source” — This would all just be the “Quote Source” (i.e. whatever text string you want to display below the quote)

    Thread Starter Jason

    (@themeblvd)

    @esmi Thanks for taking the time to give me your take on this.

    I’ve digging through core a bit more and have noticed some things on this.

    1) When you add theme support for “post-formats”, it gets registered globally, but in searching through 3.6 with my text editor, I don’t see any places where this support is actually checked to do anything. (In WP 3.5 you can see it checked in many places)

    2) When you add theme support for “structured-post-formats” it seems that the only real purpose here is that the fallbacks of post_formats_compat() on those registered formats don’t get applied with using the_content().

    … All kind of interesting. Seems that if you’re a theme author and you don’t look into post formats with all of your themes, users are going to be quite confused when updating to 3.6. Things will kind of, sorta work OK with post_formats_compat, but not fully. I’m sure post_formats_compat will get improved a bit as we move a long, as well.

    Thread Starter Jason

    (@themeblvd)

    I guess where I’m confused is with what actually add_theme_support is doing now with the post-formats/structured-post-formats in 3.6. Why put this in your theme at all if they are on by default? Something just seems off to me here. I must be missing something.

    When I comment out these add_theme_support uses in TwentyThirteen, I can’t figure out what changes in terms of the the WP admin in editing posts or the frontend display of the posts. Everything seems to be the same whether support has been added by theme or not.

    Thread Starter Jason

    (@themeblvd)

    Hey Chris,

    Thanks for responding. You’re totally right on the snippet I posted, however I believe I am still seeing the issue I was trying to point out.

    Here’s how to reproduce the issue:

    With v3.6-beta1 and TwentyThirteen activated, open up TwentyThirteen’s functions.php and comment out lines 76-81 where it adds theme support for post formats (where you copied from previously).

    add_theme_support( 'structured-post-formats', array(
    	'link', 'video'
    ) );
    add_theme_support( 'post-formats', array(
    	'aside', 'audio', 'chat', 'gallery', 'image', 'quote', 'status'
    ) );

    After doing this, I see that post formats are still available in the WordPress admin panel when editing posts.

    And if I activate any themes that I’ve created that do not support post formats, I also see post formats in the Edit Post page of the WP admin.

    Is this not the case for you?

    Plugin Author Jason

    (@themeblvd)

    Aw, you’re talking about this: http://ww.wp.xz.cn/support/topic/resolved-custom-post-types-compatible

    I can’t really speak to what’s going on there unfortunately, as it’s just something a random user posted.

    Plugin Author Jason

    (@themeblvd)

    Hello,

    I apologize, but custom post types are not a feature that this plugin supports. I’m not quite sure what you were copying, but it wouldn’t have been from us.

    Plugin Author Jason

    (@themeblvd)

    Try out the updated version of the plugin.

    I’ve totally re-tooled how the code formatting happens. Escaping of special characters now happens while saving the topics and replies, opposed to attempting to save the topics/replies and then displaying the code.

    Plugin Author Jason

    (@themeblvd)

    Hello,

    I’m not quite sure how you ended up posting in the support forum for this bbPress plugin, but here’s our support forum if you need any theme support from us: http://support.themeblvd.com

    Plugin Author Jason

    (@themeblvd)

    Perfect. The trick to bypass WP’s kses and stripping of the HTML tags without removing any security-related things was to apply htmlspecialchars() all content between pre and code tags before saving each topic and reply. — So if you ever switch to some other plugin that uses some sort of code formatting on the topics/replies after they’re displayed (as I was trying to do before), there might be some issues, but I’m not sure how else this could have been done.

    Plugin Author Jason

    (@themeblvd)

    Thanks bearing with me on this one. This is such a tricky plugin to code for bbPress. Try out v1.0.3 of this plugin, and let me know if you’re still having problems.

    I would imagine it’s still not perfect. So, feel free to let me know if you come across any other odd things. And as always, any specific examples where you’re running into issues are really helpful.

    Plugin Author Jason

    (@themeblvd)

    Hello,

    I’ve actually been using this plugin awhile on my own support forums. So, I’ve seen some of the odd issues you’re trying to describe, as well. I’m trying to tackle some of them. It’s just very difficult with the way bbPress sanitizes the content of topics and posts.

    Would be able to give me some more specific examples of things you’re doing that aren’t working? Also any examples you give, make sure to let me know if you’re doing in them pre or code tags.

    Here’s one main thing I’ve noticed that plays a big roll:

    1) If a normal non-moderator user posts anything with > or < that is not part of a standard HTML tag (like maybe in a PHP code snippet) it will get changed in the HTML special character conversion like & g t ; (without spaces)

    Plugin Author Jason

    (@themeblvd)

    Hello,

    This plugin only works if you’re using a compatible theme. You cannot use it with the Twenty Twelve theme. — Currently the only compatible theme is Jump Start and soon these themes will also be compatible.

    Plugin Author Jason

    (@themeblvd)

    Hello Nick,

    The map gets pulled in with javascript, and you’ve got javascript errors on the page. So it makes sense that no map is showing.

    Have you gone through and disabled all of your plugins? If it just started happening, it most likely means that some sort of plugin you’ve installed recently or something you’ve done with your javascript (maybe a caching plugin you’re using or something?) has caused this to happen.

    Plugin Author Jason

    (@themeblvd)

    Hello,

    it would be great if the user could also start navigation from within that plugin.

    Can you tell me what you mean by this?

    Plugin Author Jason

    (@themeblvd)

    Hello,

    I noticed you marked this as resolved. Were you able to discover some sort of issue on your end?

Viewing 15 replies - 136 through 150 (of 261 total)