Tarmo Toikkanen

We haven’t tested it. There’s no reason why it would not work, it’s just a few custom content types. Let us know if you test it.

More specifically: in the imagemapper_script.js file, line 87 has the function that reacts to a click and closes the active tooltip. Copy that content to a mouseleave even handler.

Hi. Not sure what you mean. The plugin should not have any explicit https requirement. Some other plugin may be altering callback protocols via hooks.

The hot spots are scaled relative to the image size, which is always dependant on what the theme does to images. In this case, some dynamic update to the layout parameters (js being loaded) is affecting this, and the timing of the imagemapper when looking for the current display size happens at the wrong time. Not sure how to fix that, unfortunately. Try a different theme?

You can enter an imagemap manually, by adding the proper shortcode:

[imagemap id=”1479″]

where the number is the one you see when editing the image map.

Hi. The tooltip can contain images and links (basically, ane html content), so people may want to interact with it. That’s why automatic mouse out is a bit of a problem. The tooltip will go away when you click anywhere outside it.

Of course, if you want the tooltip to fade away automatically, you can just edit the javascript file to get that effect.

We haven’t looked at that. Basically creating image maps entails creation of both imagemaps and imagemapareas. Usually you’d need author rights to do those.

I suggest you test some good plugins for access management, like RoleScoper, where you should be able to allow or disallow authoring of specific custom content types.

You can have only one imagemap on a page at a time. Placing image maps in widgets may be a bad idea, since you easily end up with more than one being displayed, if image maps are also used in the content.

The image map is mostly tested in content where it has the whole width of the post to use. Columns is VC may be too dynamic for the image map to properly detect and handle. In general, it’s a bit tricky finding out the dimensions of the image that’s finally displayed to a user. All the hot spots need to be relatively placed to match those dimensions, so any dynamic readjustments that happen later in the render process may mess things up.

If anyone can figure out a fix, patches are accepted. ??

Quite often real popups are blocked in browsers. That’s why we have the inline popup that is less of a problem.

Hi. Can’t see the image on the site. ImageMapper code seems to load ok.

Not sure about the error you have. Can you be more specific? How does it appear and disappear?

OK, by creating a new user, I was able to see the forms again. For some reason, my existing test user was not seeing the forms, even though they did not have the achievement.

And I think I figured this out by reading some other threads, where it was explained that having a future achivement in a chain of steps will disable the earlier ones. Chaining achievements together created this situation. Sorry for the noise, but maybe someone with a similar problem finds the answer here.

Right, sorry about that. I had left some debug messages in there. They work on Chrome and on Firefox 3.x, but older Firefoxes and IE seem to get upset by them. Version 0.5.2 is now tagged, and has this fixed.

I still need to further optimize the sorting code – it does way too many jquery queries while sorting. When you have nearly 100 comments, things start getting way too slow…

Hi Johnny. The comment field is disabled until you first select a knowledge type from the drop-down list above it. And press the button next to it. You’ll then get scaffolding information, and the comment box will be enabled.

If you can’t see a drop-down list above the comment box, then your theme is probably messing with the plugin. You should only use plugins that use the WordPress normal Walker method of displaying comments.