[Steven Zahm]

@ Nickolas

re: queries
Ahhh, ok, that makes sense! I missed that they were for the export from other tables.

re: automapping, partially translated
Yes, I’m not sure there’s a way around that. What happens in the background is that the fields types are pulled from Connections that way there are always current without having to update the CSV Import extension. What happens next is those field names are then concatenated with a field name in the CSV Import extension. These field names are hardcoded and not translated. Maybe they should be but that would require one to translate those strings. So that why you up with “Frenglish” (I think I just made up a word). But if you import with those field names, they should automap just fine. Looking at your CSV file, that appears to be exactly what you ended up with.

Even still you do not need to worry about the column header names at all, you only have to manually map the fields. Thats why there’s the mapping step, the automap is added as an added convenience. The CSV Import really does not care what the column headers are named it only cares what they are mapped to.

I hope that make sense! Good to hear you’ve got it imported and everything!

[Steven Zahm]

re: Colin

Yes, I received the reply.. sorry I’m a little backlogged with support issues.

What I read is you need several custom fields:

• A text input field for a link to a YouTube video.
• A repeatable text input field for links to MP3 files.
  • Still a repeatable field but instead of text fields for links, use the WP Media chooser.
• A textarea for Skills.
• A textarea for Experience.

The you need a custom version of Gridder which embeds the YouTube video in the right with the photo on the upper left.

The other custom fields look like they can be output using the core Content Boxes feature which would be built as part as the custom fields. These can be turned on/off and reordered on the Settings admin page under the Display tab. The new fields would show up there.

The email, there’s already the [Contact extension(http://connections-pro.com/add-on/contact/) available for that. The form is not hidden behind a button though.

Do I have all of that about right?

The last item I didn’t quite understand. What do you mean; “A shortlist that enables selection of people and placing them in an area for viewing later would be great too.“?

[Steven Zahm]

@ Ray

Adding the custom fields and rendering them on specific spots in a template is relatively easy depending on if the custom fields are already supported or the custom fields are, um, custom. Meaning, checkboxes, radio, text areas are supported, things that require repeatable fields would require additional coding to support.

Adding the custom fields can be done by creating an extension that has the fields you require. That would make it upda safe. To display the meta data would require a custom template. Something it appears you already have. So it would just need updated to display the data from the custom fields.

Now, the search, that is called faceted search. That is a bit more complicated … in part, because it is not something built into Connections. Core support is in my plans, but I have not given much thought on the best way to implement it. Off the top of my head … I plan on, very soon, to completely rewrite how Connections queries the entries to be displayed. Part of this would involve making sure, at this low level, results can be limited based on meta data. This alone is a major undertaking, but should pave the way for a decent faceted search which would still need built.

With that said, I think another viable solution would be to query the entry ID/s from the meta data that are being requested via the faceted search and then feed those ID/s into the code that already does processing for querying. This would even be forward compatible with the rewrite I have planned. This could be built as a separate extension.

Probably a bit more detail than what you wanted. I could do this … looking at my current schedule, not until mid March or even into late April though. That can of depends on some others who would be ahead of you if they decide to move forward with the customizations they want.

To give you an estimate on cost. I would needed to know what fields you want added. Where you want the meta data to be displayed in the template and how you want the fields to look. Mockups are great for this. I would also need greater detail on how you would want the custom fields to be shown in the faceted search and how the results should be displayed. Again, mockups would be good for this.

[Steven Zahm]

@ Alex

Not sure I follow, sorry!

Are you saying a duplicatory was created each time an entry was added with the category?

Was it just one particular category name … meaning were you importing other categories too?

Can I get a copy of the CSV file to see if I can duplicate the issue?

[Steven Zahm]

re: craig

If the features of the Gridder template meet your needs, then it would probably be a very nice fit. Maybe the Circled template too.

Hope that helps!

[Steven Zahm]

@ cheryl

Sorry, no. The Manage admin page is setup to display the image, not the logo. It is on my to do list to make that a configurable option but I honestly can not give you an eta one when this will be implemented.

[Steven Zahm]

@ Anna

If you do not enter data into the fields, they will not be shown at all. If you want to enter data manny fieldset, for example address and phone numbers, you can set the visibility to unlisted. With that set, those fieldsets will not be displayed.

As for the warning issued by Codestyling Localization, that can be ignored. Connections uses many strings which are translated by WordPress, so Connections will use them instead of requiring translators to translate the text again just for Connections. It also keeps resource useage down since multiple translations for the same string do not need to be loaded in the memory at the same time.

Opps… I did read the message clearly, I thought it was complaining about multiple text domains…

Any way, that message can be ignored as well. Connections does call the load_textdomain function, but only to load custom translations a user may have created for Connections. If custom translation does not exist, then it does call the load_plugin_textdomain function. This is a more advanced setup that provides more flexibility by allowing custom translations that are update safe. There is no danger of some filters and action not being run with the way this is setup.

Hope that helps!

[Steven Zahm]

@ Sam

Sorry, not easily doable until I release 8.2. There’s a brand new function I added specifically to do this. But if you want to give it go any way…

You would need to edit these two line:

• https://github.com/Connections-Business-Directory/Connections/blob/feature/term-meta/includes/entry/class.entry-output.php#L2467
• https://github.com/Connections-Business-Directory/Connections/blob/feature/term-meta/includes/entry/class.entry-output.php#L2475

You would replace the contents of the li and span tags with a call to this function:

• https://github.com/Connections-Business-Directory/Connections/blob/feature/term-meta/includes/class.terms.php#L4167

But since that function does not exist in the released version of Connections, you’ll have to create your own custom version of the function and call it instead.

Hope that helps!

[Steven Zahm]

re: Perhaps I should use another Char for delimiter then Comma, since there are some in my adresse fields (in French, address are formated as such “Civic numer COMMA Street name”)…

If the field values are not quoted, then yes, the comma in the road name can mess up the import.

YOu should still be able to use a comma, just make sure all the field values are quoted in the CSV file.

If you’re using Excel … that app creates poor CSV files. I suggest using LibreOffice.

[Steven Zahm]

@ jaime

Hmmm… the file naming looks wight. What folder did you put them in?

Can you attach the PO file again … just rename the .po to .txt first. I’ll compile a MO file using POedit so I can test it.

[Author]

Posts