[Steven Zahm]

@ Jeff

Yes, the entries would still have the duplicated data because that is saved to the database already. Resetting the roles capabilities can not remove data saved to entries.

If this fixes it like it did last time, editing entry will no longer produce duplicates. Please give it a try. If that fixes it up, I suggest trying to figure out which plugin is not-so-helpfully altering capabilities that do no belong to it. Seeing as this is very intermittent for you, that could prove to be extremely challenging.

[Steven Zahm]

@ Eric

Oh, I want to point out … with Link 2.0, if Form 2.0 is installed and activate, that’ll allow front-end editing for users’ entries.

[Steven Zahm]

@ Eric

Pre-population, I like it… I just added a filter to both Form 2.0 and Link 2.0 that will easily allow this to be accomplished.

Assuming you’re using Link 1.0.5, change line 37 to this:

$entry = apply_filters( 'cnl_admin_add_entry_object', new cnEntry() );

Now you’ll be able to hook into the cnl_admin_add_entry_object filter for pre-population and be ready for Link 2.0 to boot.

Here’s an example on how to use the filter:

add_filter( 'cnl_admin_add_entry_object', 'cnl_alter_add_entry_object' );
add_filter( 'cnf_add_entry_object', 'cnl_alter_add_entry_object' );

function cnl_alter_add_entry_object( $entry ) {
	
	// Add the filters necessary to save data in the cache.
	add_filter( 'cn_email_cached', '__return_true' );
	add_filter( 'cn_address_cached', '__return_true' );
	
	$entry->setFirstName( 'First' );
	$entry->setLastName( 'Last' );
	
	// Setup the email data to prepopulate.
	$email = array();
	$email[1] = array();
	$email[2] = array();
	
	$email[1]['type'] = 'personal';
	$email[1]['address'] = 'personal@email.add';
	
	$email[2]['type'] = 'work';
	$email[2]['address'] = 'work@email.add';
	
	// Store the email address in the cache.
	$entry->setEmailAddresses( $email );
	
	// Setup the address data to prepopulate.
	$address = array();
	$address[1] = array();
	
	$address[1]['type'] = 'home';
	$address[1]['city'] = 'Reading';
	$address[1]['state'] = 'PA';
	$address[1]['country'] = 'United States of America';
	
	// Store the address data in the cache
	$entry->setAddresses( $address );
	
	return $entry;
}

Of course you’ll need to add the code necessary to pull the data from your source for pre-population and some conditional to determine when the to pre-populate because you would want to do it for every single entry with the same data.

Can you tell me where exactly you added the code that renders the instruction text? If it makes sense from a big picture view, I can add an action that can be hooked into to render anything one could dream of before the form.

[Steven Zahm]

@ Lisa

re: first question
If you want the users to maintain their own entry, you need to use Link, not Form. using Link will prevent the possibility of duplicate entry and allow the user to maintain their own entry. Using Link, yes, the user will require a login.

re: login module
I do not have any that I can recommend but any plugin that has a shortcode for a login form or a widget should work just fine.

re: second question
I would not expect that they would need double entries. Parts of the entry such as addresses and phone numbers can be marked as private. When marked as private, those details will only be exposed to users that are logged in if that there user role has been setup to allow the viewing of private details.

Hope that helps!

[Steven Zahm]

@ Deepanshu

1. Yes, Link will link the past registered users and their entry, when they next log into the site as long as the email addresses match in both the user account and in the entry.

2. Right now this is not possible. I’m nearing completing Link 2.0 which will enable front-end editing as long as Form 2.0 is installed and active. Form 2.0 is also under development and nearing completion.

I hope that answers your questions!

[Steven Zahm]

@ mary

Please do no reply to the email auto-responder, replay back here in the forum. Thanks!

Slim Plus will automatically create images from the source image that are
120px x 100px. It does not use the pre-cached image sizes created when you add a new image. You will have to pre-process the image, scale and crop. If you upload a pre-cropped image using the same ratio (6:5) that would work too. For example, images with the dimension of 200px x 167px or 110px x 92px. Here’s the math…

( width / height ) * new-height = new-width

OR

( height / width ) * new-width = new-height

Hope that helps!

[Steven Zahm]

@ Kera

Long explanation short … the server is properly configured to check file types. If found in these instances if you change the file extension from .csv to .txt the upload and import will work fine. Not related, but I recommend following this FAQ too.

Hope that helps!

[Steven Zahm]

@ John

Please see these doc pages, they’ll explain exactly what you need to do.

• str_bio_head=’Biography’
• str_bio_show=’Show Bio’
• str_bio_hide=’Close Bio’
• str_note_head=’Notes’
• str_note_show=’Show Notes’
• str_note_hide=’Close Notes’
• str_contact=’Contact’

Hope that helps!

[Steven Zahm]

@ Steve

Do you mean something more like what Slim Plus offers?

[Steven Zahm]

@ Jeff

Did you try resetting the role capabilities like I mentioned in this reply. If not, go to the Connections : Roles admin page, add a check beside “Reset All Role Capabilities” and click Update button. If that fixes it again, then something keeps deleting a core capability that Connections requires.

[Author]

Posts