[Steven Zahm]

@ Eve

Please see my reply here.

[Steven Zahm]

@ Eve

You could, but the result would be anything but pretty. Others have successfully added it only to remove it again. The design of Tile is based around the fixed width and height. Adding a variable height to the mixed will create undesirable effects. Tile Plus instead relies on the user to simply click thru to the single entry view of the template where both the bio and notes are displayed without requiring further user interaction.

If you’d like to give it a go anyway… I’m not sure which post you’re referring to, but yes the template structure has changed a few times throughout the years. The next release of Connections take the current iteration of the structure a step forward by easily allowing one to override the template files in an update safe manner. Any back on topic … the 2012 instruction probably still apply, just that you need to make the changes to the card.php file rather than the template.php file. And that the template files are now in the plugins folder rather than the connections_templates folder since template are now full fledged plugins. So, the folder for Tile Plus will be connections-tile-plus.

I hope that helps.

[Steven Zahm]

@ Timothy

Many thanks for the review! Every now and again the multi-level visibility trips up people. I added because it is a great way to have public info while keeping more sensitive data behind a login.

[Steven Zahm]

@ John

re: http://connections-pro.com/support/topic/category-sub-category-question/#post-289193…

See my 1/. topic from my reply above.

[Steven Zahm]

@ Eve

Actually this is quite easy as I built changing the gradient right into the template as options. See this doc page. The doc page is for cMap, but the same instructions apply to Tile Plus.

[Steven Zahm]

@ bobbyau

The caption [meta page description] that Google is extracting from the page is what I would expect since all the roasters for the separate regions are single pages. To my knowledge, Google is not going to parse out each entry as a single search result. This meta page description can be set to something you desire instead of one Google creates from the page content. Use a plugin Such as WordPress SEO by Yoast to do this.

Ticking the name link option should help because now each entry will have its “own” page, as far as Google is concerned…

I went back to site to take a look, even though you have the name link option enabled, the roaster names are not links as they should be. You should be able to click on a link and be taken to a virtual page where only the entry which was clicked exists. That option can be overridden [disabled] at the shortcode level. What is the exact shortcode you are using on the directory pages? If you have link=false set as an option, remove that.

With the name link option set the meta page description for each individual entry should be an excerpt of the contents of the bio field. It will not be the address and such. Maybe when Google supports organization rich snippets it will. There’s nothing I can do about that. I can only do my best to ensure the micro data is properly setup for Google.

[Steven Zahm]

@ Eve

Tile Plus uses a fixed with in pixels. Currently percentage based widths are not supported. When settings it as 50% you are actually creating an invalid CSS width so the width becomes just big enough to fit the content.

I’ve started to see a few instances where the content does not show. It has always been due to the theme globally setting the box-sizing from the default of content-box to border-box. This messes up the width calculations for anything expecting the browser default.

What needs to be done is to change the box-sizing back to the default by overriding the theme. Do this by adding the following to theme’s custom CSS area to to the end of the theme’s styles.css file:

#cn-tile-plus .cn-entry {
	-moz-box-sizing: content-box;
	-webkit-box-sizing: content-box;
	box-sizing: content-box;
}

This will not affect anything other than the Tile Plus template so it is safe to add.

Hope that helps!

[Steven Zahm]

@ jon605

You add the enable_search and the enable_category_select shortcode to each instance of the shortcode, not individually in separate instances of the shortcode; like:

[connections enable_search=false enable_category_select=false category='4']
[connections enable_search=false enable_category_select=false category='5']
[connections enable_search=false enable_category_select=false category='6']
[connections enable_search=false enable_category_select=false category='7']
[connections enable_search=false enable_category_select=false category='11']
[connections enable_search=false enable_category_select=false category='12']
[connections enable_search=false enable_category_select=false category='13']
[connections enable_search=false enable_category_select=false category='14']
[connections enable_search=false enable_category_select=false category='15']
[connections enable_search=false enable_category_select=false category='16']
[connections enable_search=false enable_category_select=false category='17']
[connections enable_search=false enable_category_select=false category='18']
[connections enable_search=false enable_category_select=false category='19']
[connections enable_search=false enable_category_select=false category='20']
[connections enable_search=false enable_category_select=false category='21']
[connections enable_search=false enable_category_select=false category='22']
[connections enable_search=false enable_category_select=false category='23']

Since an instance of a shortcode is unique, you need to apply options each time.

Hope that makes sense!

[Steven Zahm]

@ John

1/. Sorry, nothing officially supported. However, see this support topic reply. It offers a method that can be used to enable this.

2/. The issue is that, likely the theme, has included an HTML shim script. The purpose of these shim scripts is to enable HTML5 features in browsers that do not support them. They work pretty well … but, there seems to be a bug in this shim script.

When you click on a category, the “Search” placeholder string in the search box is being sent too. So you’re actually searching for “Search” within the category being clicked. Obviously not what we want to do.

The fix will be to remove the “Search” placeholder text. To do this easily, we can use another plugin.

Changing the search string can be done with the Say What? plugin.

It’ll add a new Text Changes menu item. Click Add New, enter the string exactly as shown in Connections, Search. Next enter connections [notice the lack of capitalization, that's important!] as the domain and then enter your new text. The new text you want to add will be nothing, leave it blank. That should fix it.

Hope that helps!

[Steven Zahm]

@ Ian

Any changes made to actual PHP/CSS/JS files will be lost in the event of an update. I looked back thru the topics you started and I see only one instance of me suggesting a file being edited and that would be the CSS to add the one label. You will only loose this change in the even you update the cMap template. The next version of Connections comes with a built in method to override core template files including the CSS file. The plus would be these overrides will be update safe. The negative is that if a new feature is implemented in an overridden file, one might not be able to take advantage of the new feature because it does not exist in the override file. Hope that makes sense and helps!

[Author]

Posts