scmsteve (@scmsteve)

Forum Replies Created

Viewing 8 replies - 1 through 8 (of 8 total)

  • scmsteve
    Participant

    @scmsteve

    We are also seeing this, it took quite a while to track it down to this. Adding the code provided here seems to make the editor visible/work again.

    Another issue we are having, though, is the display of emoticons or whatever they are called that were inserted via TinyMCE…

    We get a 404 error on the URL formed like this:

    /forum/my-plugins/tiny_mce/plugins/emotions/img/smiley-smile.gif


    scmsteve
    Participant

    @scmsteve

    2.6.1 installed and everything is great! Thanks for your dedication and hard work, it is wonderful to see 2.6 available for everyone as an official release. The only other change we had to make (not to confuse this topic) was to undo the changes we made before for when the sub-forum list was changed from li to spans, seems they are now back as li elements, but it was easy to fix the CSS. Everything looks great from what I can see right now.


    scmsteve
    Participant

    @scmsteve

    Nothing to apologize for, glad you were able to get it fixed (or will), and that it wasn’t my fault. 🙂 Thanks for the quick reply and for taking care of it. Just testing before pushing this newer version to our live site, I’ll keep you posted on any other issues I find as well.


    scmsteve
    Participant

    @scmsteve

    Hi @sudar! Thanks for your great work in this regard, and I know this is *really* old now, but I am working on a site that has your bbpress-subscription-in-mandrill plugin installed and am trying to see if it is still necessary, hopefully without breaking anything.

    The site is sending things through Mandrill, using the Post SMTP Mailer/Email Log plugin. They are also running a beta of bbPress v2.6. I don’t know if it resolved any of these issues or not.

    I am just trying to understand your post above, that you switched to the asyncronous-bbpress-subscriptions plugin. Does that mean you are no longer using the one you wrote, and the above one solves all the issues? Any particular notes to be aware of in configuring that plugin vai filters/etc to accomplish the same thing yours has done?


    scmsteve
    Participant

    @scmsteve

    One other issue is how the forum list is generated, it seems it is invalid HTML having text in the

      that is outside the

    • elements.
      <ul class="bbp-forums-list">
      <li class="bbp-forum"><a href="forum-url" class="bbp-forum-link">forum-name (counts)</a>,</li>
      </ul>

      In 2.6 I am getting this:

      <ul class="bbp-forums-list">
      <li class="bbp-forum"><a href="form-url" class="bbp-forum-link">forum-name (counts)</a></li>,
      </ul>

      The seperator of a comma is being put after each li tag instead of inside of it.


    scmsteve
    Participant

    @scmsteve

    Realized part of it, it is looking for a .min.css version, and I only had bbpress.css. When I copied the bbpress.css file to bbpress.min.css in my child theme it found it.


    scmsteve
    Participant

    @scmsteve

    Noticed when migrating from 2.5.12 to 2.6 beta 2 (and also in RC1 and RC3), that my custom CSS file in mytheme/css/bbpress.css is no longer being detected.

    I am seeing that here as well… Since your post was never commented on, I don’t know if it was ignored or simply thought irrelevant. Or maybe missed. 🙂

    Looking at the HTML between the old site and a test site running the SVN pull of 2.6, it seems that previously as part of the enqueue_styles() call, it generated:

    <link data-asynced="1" as="style" onload="this.rel=&quot;stylesheet&quot;" rel="stylesheet" id="bbp-default-css" href="https://siteurl/wp-content/themes/mythemename/css/bbpress.css" type="text/css" media="screen">

    Now it is generating:

    <link data-asynced="1" as="style" onload="this.rel=&quot;stylesheet&quot;" rel="stylesheet" id="bbp-default-css" href="https://siteurl/wp-content/plugins/bbpress/templates/default/css/bbpress.min.css" type="text/css" media="all">

    So, it is not looking in the site css folder, but instead pulling from the plugin folder.

    Is this intentional? If not, is there a fix/workaround?


    scmsteve
    Participant

    @scmsteve

    I was searching on this problem and found that setting “Forum root should show” to “Topics by Freshness” instead of “Forum Index” seems to resolve a similar issue for our site. I don’t understand why, I haven’t dug into it yet.

Viewing 8 replies - 1 through 8 (of 8 total)