[Steven Zahm]

@ Dennis

Sorry, no, there is no support for printing labels or exporting the data in an excel at this time. If those are absolute requirements then Connections will not be a good fit for your needs. As for annual cost, yes, the premium templates and extensions do have an optional annual renewal fee for continued support and updates. I hope that answers your questions thoroughly.

[Steven Zahm]

@ Marco

Yes, but not easily like in the premium templates.

Install the Code Snippets plugin:
https://wordpress.org/plugins/code-snippets/

Add the following code as a new snippet:

add_filter( 'cn_output_default_atts_address', 'cn_remove_label_separator' );
add_filter( 'cn_output_default_atts_phone', 'cn_remove_label_separator' );
add_filter( 'cn_output_default_atts_email', 'cn_remove_label_separator' );
add_filter( 'cn_output_default_atts_im', 'cn_remove_label_separator' );
add_filter( 'cn_output_default_atts_socialmedia', 'cn_remove_label_separator' );
add_filter( 'cn_output_default_atts_link', 'cn_remove_label_separator' );
add_filter( 'cn_output_default_atts_date', 'cn_remove_label_separator' );

function cn_remove_label_separator( $atts ) {
	
	$atts['separator'] = '';
	
	return $atts;
}

SAve and activate the new snippet.

Hope that helps!

If I have not asked and if you have a moment, I would truly appreciate a review as they really do make a difference. Many thanks in advance!
http://wordpress.org/support/view/plugin-reviews/connections

[Steven Zahm]

@ Mitch

A curiosity question … how do the links get wonky? Shouldn’t they point t the same page set as home_id?

The Widget Pack is being worked on indirectly via some very important changes to core Connections code. I did take a little break from rewriting the terms class for the categories. That’s just part of how I work. Sometimes I need to take a break from one project and focus on another and then go back. At this very moment I’m writing a completely new method to handle images. Currently, none of that be actually being handled by core WordPress which is inefficient now that WordPress has decent image processing code to work with. The benefit you’ll see from this work is reduced server memory requirements and server CPU load being used by Connections. And true HTML5 responsive image support, serving the right image size for current device. Many claiming responsive image support are simply server a large image and using CSS image scaling via media queries. Any way, this is just one of many projects I have going into 8.1. I’m guessing the end of summer is when it’ll drop.

[Steven Zahm]

@ Mitch

Unfortunately, that’s about all the can be done. You said Relevanssi can adjust character counts … can you do three character searches with it? If you can, maybe I’ll have to dig into their code and figure out how they managed that.

[Steven Zahm]

@ Shonna

Looks like you have Connections 0.8.5 installed… you need at least 0.8.11. I recommend updating to the latest, version 0.8.14.

After you update, I image you would not receive any more errors. Let me know. Hope that helps.

[Steven Zahm]

@ Mitch

If you convert the Connections tables to MyISAM using phpMyAdmin and the disable/reenable FULLTEXT, you should be able to turn off keyword search and enjoy the better search results that FULLTEXT will provide. fyi, in >= 0.8 I finally figured out how to choose the right DB storage engine by default based on PHP and the MySQL version so new user install should always support FULLTEXT. Older user that got stuck with keyword has to manually convert the tables, sorry!

[Steven Zahm]

@ Kristina

Sure send the CSS my way, I’ll take a look at it. Look forward to receiving the translation too, thanks!

If I have not asked and if you have a moment, I would truly appreciate a review as they really make a difference. Many thanks in advance!
http://wordpress.org/support/view/plugin-reviews/connections

[Steven Zahm]

@ Meg

This is very likely a DOCUMENT_ROOT issue which will resolve itself when you take your site to a live domain. If you would like to fix it now, try this:

The document root can not be determined automatically. So you have to manually set the DOCUMENT_ROOT here’s how:

Add the following to the timthumb-config.php file found here:

../wp-content/plugins/connections/vendor/timthumb/

This is what you need to add, make sure to change the doc root accordingly:

define ( 'LOCAL_FILE_BASE_DIRECTORY', '/my/doc/root/' );

What /my/doc/root will be will depend entirely on the server setup. If you go to the the Connections : Dashboard admin page and look at the the System widget; there will be a constant named CN_PATH. The doc root should be the beginning portion of that path. What I can tell you is that from the wp-content and on will NOT be part of the doc root.

That should fix it.

[Steven Zahm]

@ Meg

It sounds like you have HTML tags in and around the Connections shortcode. That’ll break the WordPress shortcode parser. To fix, edit the page where you entered the shortcode and the category option. Switch the page editor to the Text tab, remove any stray HTML in and around the shortcode and save the page. That should fix it.

[Steven Zahm]

@ Mitch

You should be able to use the home_id shortcode option. Set it to the page ID where the clear search should redirect to.

[Author]

Posts