opentype

I see the usefulness of this on my site. People can easily create a club by filling out one form. But if they stop there and don’t instantly look for the link to add apps, they create a club that makes no sense,  because you can’t do anything in there. (I am sceptical about adding one of each though, especially since there currently is no delete option for the club owner.) 
Maybe it should rather work like this:
In the club creation form you get checkboxes for each app for your initial setup – so you get a fully working club as soon as it was created. That would streamline the process and avoid confusion among club owners and people joining (potentially empty) clubs. You just check “topics” and a forum is created. Name and description can be changed/added later. 
And if selecting at least one app is required, the site owner can make sure that all clubs are fully functional instantly. 

I see the usefulness of this on my site. People can easily create a club by filling out one form. But if they stop there and don’t instantly look for the link to add apps, they create a club that makes no sense,  because you can’t do anything in there. (I am sceptical about adding one of each though, especially since there currently is no delete option for the club owner.) 
Maybe it should rather work like this:
In the club creation form you get checkboxes for each app for your initial setup – so you get a fully working club as soon as it was created. That would streamline the process and avoid confusion among club owners and people joining (potentially empty) clubs. You just check “topics” and a forum is created. Name and description can be changed/added later. 
And if selecting at least one app is required, the site owner can make sure that all clubs are fully functional instantly. 

This?
 

It was shown in this picture in january 2016 how to do this already:
 

Looking forward to purchasing this once 4.2 officially is released! 

It’s your theme. It makes the background layer of the text block invisible. If you link the actual page, I can check the CSS styling and probably provide a manual override to fix that. 

Look at what is going on there. Instead of CSS, there is a whole website calling Github files and whatnot. It breaks my 4.2 site (I tested it on) completely. It’s not just Pages templates. 
 

Look at what is going on there. Instead of CSS, there is a whole website calling Github files and whatnot. It breaks my 4.2 site (I tested it on) completely. It’s not just Pages templates. 
 

That’s expected. The new 4.2 reputation calls aren’t in there. I will update it close to the release of 4.2 and then replace the 4.1 version with the 4.2 version. I can’t do that now of course, or it would break for customers who are not running the 4.2 beta. 

That’s expected. The new 4.2 reputation calls aren’t in there. I will update it close to the release of 4.2 and then replace the 4.1 version with the 4.2 version. I can’t do that now of course, or it would break for customers who are not running the 4.2 beta. 

I recommended it too a while ago. Makes perfect sense to support these Twitter meta tags along with the ones Facebook looks for. Tweets with images are so much more likely to get clicks than just plain links. 
If you can’t wait: it’s surprisingly simple to add it to certain templates. For example, I added this to my video database in Pages:
{{\IPS\Output::i()->metaTags['twitter:card'] = 'summary_large_image';}} {{\IPS\Output::i()->metaTags['twitter:site'] = '@TypographyGuru';}} {{\IPS\Output::i()->metaTags['twitter:title'] = $record->_title;}} {{\IPS\Output::i()->metaTags['twitter:description'] = 'Watch this video in the collection of the best typography videos on Typography.Guru';}} {{\IPS\Output::i()->metaTags['twitter:image'] = (string) \IPS\File::get( 'cms_Records', $record->record_image )->url;}}  

{{\IPS\Output::i()->metaTags['keywords'] = implode(',',$record->tags());}}  

I recommended it too a while ago. Makes perfect sense to support these Twitter meta tags along with the ones Facebook looks for. Tweets with images are so much more likely to get clicks than just plain links. 
If you can’t wait: it’s surprisingly simple to add it to certain templates. For example, I added this to my video database in Pages:
{{\IPS\Output::i()->metaTags['twitter:card'] = 'summary_large_image';}} {{\IPS\Output::i()->metaTags['twitter:site'] = '@TypographyGuru';}} {{\IPS\Output::i()->metaTags['twitter:title'] = $record->_title;}} {{\IPS\Output::i()->metaTags['twitter:description'] = 'Watch this video in the collection of the best typography videos on Typography.Guru';}} {{\IPS\Output::i()->metaTags['twitter:image'] = (string) \IPS\File::get( 'cms_Records', $record->record_image )->url;}}  

My widget haven't layout for horizontal section. So I used 
if ($this->orientation != 'vertical') { return ''; } It's a better for performance.
I think I'll add new setting for "Grid" style/theme

With horizontal it will looks like

It's a core issue and related with "orientation".
applications/cms/sources/Blocks/Block.php
public static function display( $block, $orientation=NULL ) When you use {block} tag you can't pass orientation variable.
Solution
Open plugins/nb41socialcountfans/widgets/nbSocialCountFans.php
Find and comment
if ($this->orientation != 'vertical') { return ''; } or change to 
if (isset($this->orientation) and $this->orientation != 'vertical') { return ''; }  

You have set .ipsAreaBackground_light to “transparent” in your CSS. That hides everything. 
You should remove that styling. If you really don’t want the light grey, which is set by default, set it to white, not transparent. 

Yeah, that’s not ideal. Your thumbnail will be super small and your large images can get super large in terms of file size. 
I prefer something like 600 to 800 as max size for the thumbnail and 1500 to 2000 for the large images. But that depends on what you are doing on your site. 
If the thumbnails are too small or the large ones too big, there is a setting to choose which ones to use for the grid view. Of course if both have problems, I can’t help you. 
If you change the image settings for the database you would have to upload the image again. 
  
The images are centered and scaled up or down to fill the container in both direction. So you want the aspect ratio of your uploads close to the aspect ratio you set for SuperGrid. So try to set it that way and try to keep all uploads similar. The more you deviate from the default aspect ratio you set, the more will be cut off from the image. 

{{\IPS\Output::i()->metaTags['keywords'] = implode(',',$record->tags());}}  

{{\IPS\Output::i()->metaTags['keywords'] = implode(',',$record->tags());}}  

In the Pages template your database uses for the “record view”. 
It isn’t. It’s an application of the Twitter code. You can’t just paste the Twitter code. It’s just an example. The fields need to be populated with the dynamic content from the database record. Also, don’t just copy my code above. That’s also just an example. 
My Pages template include Twitter card support. You don’t need to do anything else than add your Twitter handle to the template. 
 

I recommended it too a while ago. Makes perfect sense to support these Twitter meta tags along with the ones Facebook looks for. Tweets with images are so much more likely to get clicks than just plain links. 
If you can’t wait: it’s surprisingly simple to add it to certain templates. For example, I added this to my video database in Pages:
{{\IPS\Output::i()->metaTags['twitter:card'] = 'summary_large_image';}} {{\IPS\Output::i()->metaTags['twitter:site'] = '@TypographyGuru';}} {{\IPS\Output::i()->metaTags['twitter:title'] = $record->_title;}} {{\IPS\Output::i()->metaTags['twitter:description'] = 'Watch this video in the collection of the best typography videos on Typography.Guru';}} {{\IPS\Output::i()->metaTags['twitter:image'] = (string) \IPS\File::get( 'cms_Records', $record->record_image )->url;}}  

What do you mean by “find” the topic? Through the search function? Access in the browser URL bar? Or from within a script? …?
Regarding the address bar, you can just access the topic through /00000-something
Which means: the ID followed by a hyphen and something else. Example to access this topic:
https://invisionpower.com/forums/topic/436181-doesn’t-matter https://invisionpower.com/forums/topic/436181-x https://invisionpower.com/forums/topic/436181-hello All forwards to the same topic. 

That’s the IPS template. 

Thank you! Looks great now.

My mistake. But don’t worry about it. If you use a recent download, you will have the recent version.