[Mitch]

Yep. Adding the a :hover css with color/underline changes helped highlight the title/link to single page. Just makes it more obvious for users mousing around the page that they can click to open another page. All good here.

Thanks.

[Mitch]

That didn’t resolve it so I just took a big leap in another direction.

I installed a plugin I’ve been testing on the sandbox – Plugin Organizer – awesome stuff. I set the MapPress plugin to NOT work on the url/connectionshome/ page and all children pages, then excepted the one specific URL/child page that contained the MapPress code mashup in the connections info box so it worked. Voila.

Good stuff.

Thanks.

[Mitch]

No problem at all. I always appreciate your feedback.

I think I just need to somehow make sure people understand to click the title. Maybe some css of the text/color/font/underline. Like Google does in SERPs, where when you hover over the title, it adds an underline, that sort of thing. (or maybe I’ll make it change color).

Bottom line, its something I can do here that emphasizes the link, not necessarily a defect in the plugin structure.

Thanks.

[Mitch]

woot!

Looking for it now. Good things take time, right? Should we pull from github or wait for the WP repository?

By the way, know what’s funny, no one can accuse you of version jumping… it’s been right at four years since I downloaded 0.7.0.1… and you’re only now at 0.8. Looks like you’ve had only one release (0.7 to 0.8) in four years, LOL.

We know better. :)

Congrats, excited to see the changes.

[Mitch]

Easiest explained in the link I re-found. It is here:

http://docs.woothemes.com/document/jquery-cookie-fails-to-load/

WC blames it on host. Host says it will not modify for security reasons. Best way is for me to just mod code.

Your comment about js fatal error triggered my memory of having to do this previously.

Thanks.

[Mitch]

OK, so this was bugging me too much to wait for the final release. I found the old code, and applied the mod to the WC RC1, and it worked to resolve the error.

This was an across the board js error, based on the host’s conflict with the naming of a js file in WC. Silly stuff, really.

This error had nothing to do with Connections or CMap.

Keep up the good work! :)

[Mitch]

If I recall, there was a security conflict between WC and my host based on the naming of some files, throwing the 406 and creating havoc in other items. I had hoped they’d fix it in 2.1, but it looks like I’ll need to find and insert the code mods so the host and WC play nice together.

I’m going to wait until final release, load it on the sandbox, and see if that resolves. At that point, I’ll know more.

I had just forgotten about this mod being needed, and I am hoping that is what caused the Connections error. They are supposed to release a final 2.1 this month, so I’ll let you know as soon as I do.

Thanks again for your prompt reply.

[Mitch]

I’m not sure exactly what it means, but I recognize an error (406) from a previous problem with WooCommerce. Their integration with Genesis isn’t even working right right now. I’m going to wait until they move past beta and RC1 to try and resolve this issue.

I’ll then make the code change that fixed the old version, and see if it fixes this issue too.

I will update here if/once I get it resolved.

Thanks for pointing me in the right direction.

[Mitch]

I wanted to jump back into this. I updated to 3.1 and cleaned up some stuff. So now, when I am on a single company view page (clicked open from the listing), the facebook og:image seems to pull properly, and the link – while it SAYS the main website name – does actually go to the proper specific Connx entry page, but the og: description is that of the connections ‘homepage’ itself, NOT of the description that is placed in the Bio of the specific listing entry.

Am I forgetting how to get that info from the Bio to be the og: description?

Thanks.

[Mitch]

Yeah, I’ve been periodically following along over on github. Notice though, that I didn’t mention the original goal date, you did. :)

Wow, two more months, must have turned into much more than you originally thought. Looking forward to what you have when you have it. Thanks for the update.

[Author]

Posts