MattM

You can change the FURLs if you wanted to, but really there is little point. The structure is proven to be spiderable. Adding ".html" at the end is almost pointless in this day and age as most of the internet is dynamically generated and Google knows this. Moving keywords around, etc has never been proven to substantially increase your ranking.

Personally, I would be incredibly wary of "Virtual HTML". This is where vBSEO replaces certain sections of text with dynamic javascript to cloak it from search engines. In my view, that is flawed because search engines parse and run javascript anyway to detect cloaked HTML and may penalize your ranking for doing so. Just a thought. :) I see elsewhere you say Bob's blog on switching to Invision Community Forum and that he's seen a rise in traffic since the switch. That tells me that maybe Google is wise to tricks that vBSEO employ. Either way, it proves that such measures aren't required for good placement.

David, Check in the Global skin, template bit "userInfoPane" Make sure it has this: <if test="authorcfields:|:$author['custom_fields'] != """> <foreach loop="customFieldsOuter:$author['custom_fields'] as $group => $data"> <foreach loop="customFields:$author['custom_fields'][ $group ] as $field"> <if test="$field != ''"> <li> {$field} </li> </if> </foreach> </foreach> </if>

If you look in admin/applications_addon/ips/blog/modules_public/display/list.php Function _showDash() Change /* Normal */ if ( count( $this->caches['blog_stats']['fp_entries'] ) ) { $this->DB->build( array( 'select' => 'e.*', 'from' => array( 'blog_entries' => 'e' ), 'where' => 'e.entry_id IN(' . implode( ',', array_keys( $this->caches['blog_stats']['fp_entries'] ) ) . ')' . $whereExtra, 'order' => 'e.entry_date DESC', 'limit' => array( 0, 20 ), 'add_join' => array(array( 'select' => 'b.*', 'from' => array( 'blog_blogs' => 'b' ), 'where' => 'b.blog_id=e.blog_id', 'type' => 'left' ), array( 'select' => 'bl.*', 'from' => array( 'blog_lastinfo' =>'bl' ), 'where' => 'b.blog_id=bl.blog_id', 'type' => 'left' ), array( 'select' => 'm.*', 'from' => array( 'members' => 'm' ), 'where' => 'm.member_id=e.entry_author_id', 'type' => 'left' ), array( 'select' => 'pp.*', 'from' => array( 'profile_portal' => 'pp' ), 'where' => 'pp.pp_member_id=m.member_id', 'type' => 'left' ) ) ) ); To /* Normal */ if ( count( $this->caches['blog_stats']['recent_entries'] ) ) { $this->DB->build( array( 'select' => 'e.*', 'from' => array( 'blog_entries' => 'e' ), 'where' => 'e.entry_id IN(' . implode( ',', array_keys( $this->caches['blog_stats']['recent_entries'] ) ) . ')' . $whereExtra, 'order' => 'e.entry_date DESC', 'limit' => array( 0, 20 ), 'add_join' => array(array( 'select' => 'b.*', 'from' => array( 'blog_blogs' => 'b' ), 'where' => 'b.blog_id=e.blog_id', 'type' => 'left' ), array( 'select' => 'bl.*', 'from' => array( 'blog_lastinfo' =>'bl' ), 'where' => 'b.blog_id=bl.blog_id', 'type' => 'left' ), array( 'select' => 'm.*', 'from' => array( 'members' => 'm' ), 'where' => 'm.member_id=e.entry_author_id', 'type' => 'left' ), array( 'select' => 'pp.*', 'from' => array( 'profile_portal' => 'pp' ), 'where' => 'pp.pp_member_id=m.member_id', 'type' => 'left' ) ) ) );

The query grabs featured items, etc and then one entry from each active blog. So, in your case, it'll only show two articles as you only have one blog.

Looks excellent!

PM sent!

Look forward to it. I believe I gave you my AIM? I have other messengers if need be.

Great news, Bob. You now how to reach me if you need anything.

Although the actual interface isn't changing much regarding creating hooks, Invision Community Forum 3.1. does introduce many enhancements in what you can do with them. Josh is taking the lead on this and will be posting a blog on our forums soon. We're quite excited about this as it opens up many more possibilities.

Just a few things: We run a stock Invision Community Forum. We don't have memcache/apc installed. We don't use Sphinx, we use normal MySQL FT searching. We also run everything on one machine, SQL and PHP on one VPS (it's not even on its own server). We do this because we want a fair test bed to work from. It's very useful for trying out new ideas and running queries to optimise them. We also run hundreds of hosting servers so we always keep on top of performance. There's no point in making an upgrade that means we have to double our hardware requirement overnight. :) There are two types of "View New Content": the default type is based on the topic marking system. This checks all the topics you've read against the last time you marked the board as read and displays any topics you've not clicked upon. This is a little slower than the other method which just shows all new content since your last visit. This setting is under "My Settings" > "General Settings". Regarding blog comments - this is an improvement I'm hoping to make for 3.1.0 or during the 3.1 branch. I want search to allow 'sub-apps'. Right now you can only specify one data source per application. Hope that helps clarify a few things.

I'll chat with Mark, our conversion guy, and see what we can do.

I can make an option to allow the member to hide their birthday. I'll have a think about that.