[Steven Zahm]

@ Serge

Looking at the SQL file…

The source DB on WAMP, the table engine in InnoDB which only supported FULLTEXT starting in MySQL 5.6. The host is likely on an older version.

On you WAMP install, drop the FULLTEXT indexes manually in phpMyAdmin on the following tables:

• wpeig_connections
• wpeig_connections_address
• wpeig_connections_phone

OR

Like I said before, manually edit the SQL file to remove the lines that begin with:

FULLTEXT KEY search

They are still in the sample file you attached.

Also, as mentioned, make sure to also delete the trailing , from the previous line otherwise you will end up with an invalid SQL statement.

[Steven Zahm]

@ Kelly

You do not need to set anything when editing an entry. You tell the template to use the SiteShot image. Here’s a link to the doc page. Follow the sample shortcode.

Hope that helps! Let me know.

[Steven Zahm]

@ Serge

Sorry, it seems the FULLTEXT indexes are not dropped when disabling that option on the Connections : Settings. That is a bug. I just fixed it.

The first solution should work just fine though.

Another way to deal with this is to open the SQL files you exported and remove the lines that begin with FULLTEXT KEY search. There should be three instances if you exported all tables as a single export. If you exported the tables as individual SQL files then there will only be one instance in three of the connections table SQL files. Make sure to also delete the trailing , from the previous line otherwise you will end up with an invalid SQL statement.

[Steven Zahm]

@ Serge

That would make sense. If your import failed in any way, then the required tables and data might not exist.

[Steven Zahm]

@ Serge

re: Is there something I’m doing wrong or is there no way to import the connections files from my localhost/WAMP?

The default table engine in your WAMP install supported FULLTEXT and the default table engine that your web host provides does not. Likely the web host running an older version of MySQL.

What you likely need to do is make sure the tables are set to MyISAM before you import.

Alternatively, on your WAMP install, disable the FULLTEXT search on the Connections : Settings admin page under the Search tab. Then export again. You should be able to do the import now because the FULLTEXT indices will not exist.

Hope that helps!

[Steven Zahm]

@ Kasper

re: I have tried adding the function, but it didn’t change anything for me.

Please try again. It seems there was a small bug which I just fixed.

re: I don’t understand why you don’t have a “default-category” argument to the shortcode.

Too niche. I already provide probably too many options. Between the core shortcode options and ones that template enables, there are over 60 already.

re: Also i notice i have another problem, when doing a search it changes all the connection shortcodes on the page, and it looks pretty silly when it does 4 searches

Yes, if you put the direct shortcode on the page multiple times, you’ll get the directory multiple times. Each shortcode instance is not aware of the other.

Here’s a few shortcode options which you can utilize to work with this:

• lock
• home_id
• force_home

You would not use home_id and force_home at the same time but you could use either to define a second page for the links to resolve to. You could use the force_home option to create “Results” page where all links and the form post would resolve to the Directory Home Page defined on the Connections : Settings admin page under the General tab. On this “Results” page you would only have the [connections] shortcode with no other options.

Hope that helps you out.

[Steven Zahm]

@ Mike

re: Searching for “510” versus “(510)” yields are different set of search results.

This is not surprising as they are completely different strings.

How is your search setup (Connections : Settings admin page, Search tab)? What fields are you letting the search, search? Just the phone numbers? If is more than just the phone numbers, results from the other fields will also be included.

Something else will influence results too…

The string (510) is 5 characters. The a FULLTEXT search would be applied so you would get weighted results that would include both (510) and 510. If no results are found with a FULLTEXT query, then it’ll try a LIKE query. Following the same rules as explained in the next paragraph the with exception of the results being returned will be those that start with (510). This would not include any results for 510 because that is not what is being search for for by the user.

The string 510 is 3 characters the database will not perform a FULLTEXT search with just 3 characters. There’s nothing I can do about that. What happens instead, Connections will fallback to a LIKE query. This will return results that begin with 510 and not (510 because that is not what is being search for by the user.

All that said… I really do not have any recommendations other than maybe you could create predefined links that search by area code. The link would really be true areacode searches but it would provide your users constant results since they would be searching for the same string.

Hope that helps!

[Steven Zahm]

@ Alan

I’m unable to answer that because I have not tested with any.

[Steven Zahm]

@ Serge

Did you somehow delete the Uncategorized category? That could break thing in quite unexpected ways. Please try deactivating and reactivating Connections. It should be recreated.

Let me know if that fixes it.

[Steven Zahm]

@ Serge

I suspect that you might have copy/pasted the shortcode from a webpage into the WordPress visual editor. When this is done, the underlying HTML is also pasted. This is a feature of WordPress and is not a bug with Connections or cMap. If you wish to copy/paste from a web page, make sure to always switch the WordPress post editor to the Text tab before you paste. The underlying HTML will not be pasted.

Here’s a link to the relevant FAQ.

To fix, edit the page where you pasted the shortcode, switch the editor to the Text tab and then delete any HTML tags from within and around the shortcode especially the code and/or pre tags.

That’ll fix it right up.

Hope that helps!

[Author]

Posts