[Steven Zahm]

@ Xavier

Ok, I found the issue and have fixed it. I’ll be releasing a bug fix release in the next few days that addresses this ans several other bugs.

Apologies for the trouble!

[Steven Zahm]

@ Colm

Did you network activate Connections? If you did, please deactivate the network activation and only activate it on the individual sites you intend to use it on.

Hope that helps!

[Steven Zahm]

@ kevin

The custom metabox and field API support was release back in the end of March. I’ve released several plugins that utilitize it:
http://wordpress.org/plugins/connections-business-directory-hours/
http://wordpress.org/plugins/connections-business-directory-income-levels/
http://wordpress.org/plugins/connections-business-directory-education-levels/
and coming soon:
http://wordpress.org/plugins/connections-business-directory-languages/

There not a point and click method of adding custom fields. The API is a dev level resource. If you need something specific, I can recommend a dev that has plenty of experience working with the API.

Hope that helps!

[Steven Zahm]

@ Tim

re: Does this mean that it will no be backwards compatible with past entries?
Yes, but only when you edit. Any existing entries will continue to show what was entered. Any new entries or entries updated would show the state abbr. The abbr is what is actually save to the DB.

The array returned from cnGEO::US_Regions() is array("AL"=>"Alabama","AK"=>"Alaska", ...

So, you could array_flip( cnGEO::US_Regions() ). That would meet your requirements, I believe. Just when editing an entry you would see a select list with the state abbr instead of the full name but the inverse would be that the full state name would be displayed and saved to the DB and would work with search too.

I do have a dev I can recommend. The only issue I can see with doing this might be forward compatibility with Connections … meaning updates to Connections could break your customization.

[Steven Zahm]

@ gary927

Good to hear you have it resolved … sounds like the may have been code/pre tag in the field.

If you have 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]

@ gary927

Edit the page where you inserted the [connections] shortcode, click the Text tab in the upper right corner of the post editor. Remove the <code> and/ <pre> tags from around the shortcode. If there are none, ensure when pasting the text, you are pasting with in to the Text tab of the bio/notes field. For entries having this issue, switch to the Text tab and make sure there are no <code> and/ <pre> tags.

If you’ve checked all those and they’re fine … then it is being caused by CSS from the theme or another plugin. Without a link to the directory there’s no way I’ll being able to tell you what the fix would be because it is not originating from Connections.

I hope this helps, let me know!

[Steven Zahm]

@ Wendy

That is just an internal debugging message. To turn this off, go to the Connections : Settings admin page, click the Advanced tab and then uncheck the Debug Messages option and click the Update Changes button. There’s no need to have that option enabled.

The logo that you’re having trouble with, please save it as a jpeg or png and reupload it. It seems there a bug with the new image processor when it comes to gif.

That should fix you up.

[Steven Zahm]

@ Axel

I see the issue … you’re using the Default permalink structure the core WP function that I’m using does not take that into account like I thought it would.

The correct path for your setup would be this:
http://chungmoo.dk/?cn-image&src=http://chungmoo.dk/wp-content/uploads/connections-images/frederik-madsen/Frederik_Sejr_Madsen_original.jpg&cn-entry-slug=frederik-madsen&w=160&h=108&zc=2

A subtitle, but important difference.

I’ll fix this bug and release a bug fix this weekend/monday … I’m still triaging/fixing some other bugs that made their way through testing.

[Steven Zahm]

@ Deniss

Looking at the page the most likely cause is the memory allocated to PHP has been exhausted causes PHP to stop running. My suggestion is to try increasing this amount. Try 128MB.

See this excellent blog post on how to do it. Since every host is different, which method that will work is unknown. My suggestion would to be start at the top and work your way until the issue is, hopefully, resolved.
http://dailyblogging.org/wordpress/increase-wordpress-memory-limit/

Let me know how you make out.

Oh, any reason, could be max_execution_time
https://www.youtube.com/watch?v=M2IqW-43Sr4

Try increasing this too.

[Steven Zahm]

@ Xavier

Are you perhaps using a translation other than English? If yes, which one?

[Author]

Posts