Search Results for 'test'
-
Search Results
-
Just a small cosmetic issue I noticed after installing the Version 1.0-alpha-1 zip file: after activating a few plugins, I noticed that the cells were not alternating classes correctly (or at least, what I’d think of as correctly).
To test this, simply go to the Plugins page and activate a plugin. If the plugin row had a white background, it changes to green to show it’s active. If it had a gray background, it stays gray whether it is active or not. It seems to me that we’d want there to be either one or two shades of green to show the active plugins.
The cause between this seems to be the CSS classes of the active rows alternated between
<tr class="active">and<tr class="active alt">; this means that the row with ‘active alt’ takes the properties of the ‘alt’ row, which overrides the background color of the ‘active’ class as it is lower in the style.css template. This derives from the function get_alt_class(), as defined in bb-includes/template-functions.php, which can assign two classes to one element.Topic: latest topics?
Is it possible to only get shown the last 5 topics on the main page, and still list more topics when you go into a category on the forum?
Or just switch them around so the categories will be listed first, and then the latest topics below the categories?
Thanks
I thought it might be helpful; I tried the following popular plugins with the latest release of bbPress and they seem to work perfectly:
– bb-smilies
– bbcode-buttons
– mini-track
– my-views
– post-count-plus (with some minor changes)
– support-forum
– bb-reputation (to some extent)
– bb-signatures
– bb-topic-views
– bbcode-lite
– hidden-forums
– report-post
– unread-posts
what is missing most is the working plugin for quotes…
Topic: when NOT to use 1.0 alpha
The following is just my personal opinion but there seems to be a growing misunderstanding around here that makes me want to petition Sam and Michael to take 1.0 alpha off the download section and limit it to people who know how to use the SVN.
“Alpha” means “NOT ready for regular use”
I don’t know how to explain that any more clearly.
It only exists for people to test and report problems for eventual repair.
Do NOT use the Alpha:
1. on a forum with active members
2 on a forum that you would care if it’s down for a week
3. if you expect it to be trouble-free
4. if you expect immediate fixes for your troubles with it
5. just because you insist on using WP 2.6 and it’s the only version that will work with it
About 1 out of 5 of my plugins has some kind of unforseen problem with 1.0 alpha because of extensive internal changes with how it does things
Last but not least, even I do not run 1.0 on any of my public forums yet, only for testing. If that doesn’t discourage you from insisting on using it, well then you’ve been warned.
A month from now 1.0 might be perfectly stable and lovely. Right now it is NOT. You’ve been warned.
Topic: Upgrade Path Suggestions
I am currently running the following:
WP 2.3x (using due to theme limitations)
BBPress 0.8.3.1
I am planning to upgrade the theme to be compatible with the latest version of WordPress. Once I do this I need to upgrade BBpress. Given the availabiltiy of the Alpha and the 2.5 restriction of BBpress 0.9 I was looking for suggestions on how to go about things.
Option 1 – Is this a valid path?
1. Upgrade to WP2.5 & BBpress 0.9
2. Wait for stable 1.0 Beta of BBpress
3. Upgrade to WP 2.6x and BBpress 1.0
Option 2
1. Upgrade to WP2.6 & BBpress Alpha
Questions:
1. Is a 2.5 version of WP still being distributed?
I hope this was clear. Thanks.
I have an installation of bbpress 0.9 (installed independent from WordPress).
When I pull the rss feed, I get code that looks like this:
<item>
<title>Anonymous on "Hello"</title>
<link>http://forums.brynmawr.edu/topic.php?id=2#post-8</link>
<pubDate>Fri, 29 Aug 2008 21:45:22 +0000</pubDate>
<dc:creator>Anonymous</dc:creator>
<guid isPermaLink="false">8@http://forums.brynmawr.edu/</guid>
<description><p>test
</p></description>
</item>The <p> is a <p> tag that is entity-encoded (I presume so that <p> won’t be parsed as an XML tag by an XML parser).
This is causing an issue with the feed parser that I am using (lastRSS): the parser is passing the <description> contents through unchanged, and so I’m getting literal “<p>” and “<p/>” on the pages that use lastRSS.
I believe that the standard method of embedding HTML into an XML feed (or any XML document) is to use CDATA blocks:
<description><![CDATA[<p>test
</p>]]></description>and this is the way feeds from wordpress, blogger, etc are formatted. bbpress should really do the same thing so that feed parsers like lastRSS will pass through correct HTML (in this example, text wrapped by a paragraph tag, rather than text with character entities that cause the browser to display the literal characters)
Can the feed generator code be changed to use CDATA blocks?
Thank you.
Check the new project here.
Thanks to GSoC student Dan Larkin for his work over the Summer.
BBXF is now available for review and testing in bbPress trunk and we plan to make it a bundled plugin in bbPress 1.0
)