Hi

I just added a Image marker style (medium) in the image field settings on a content type.

When I create a new content with that content type and add an image on the image field, I get this error:

Notice: Undefined index: nb i imagemarker_widget_submit() (linje 209 av /home/lmb/public_html/modules/imagemarker/imagemarker.module).

Any help is much appretiated
Bstrgds
Tor

Comments

swentel’s picture

Status: Active » Postponed (maintainer needs more info)

Can't reproduce this on the dev version, can you test and see if this also the case with that version.

domik’s picture

+1

I get the same message after posting a node
I can add a description on the image though... but then i can't see it on the frontend

amango’s picture

I think this might help - I had the same problems with the undefined index!
I did the following steps: content_type >Publishing options > Multilingual support > ENABLE

And now when you add an image you should choose "Language neutral" as language!
It may still show an undefined index error, but I don't know why - it works (for me)!

I used the dev version

wayne57’s picture

I am getting the same issue:

Notice: Undefined index: width in _imagemarker_load_imagestyle() (line 307 of /websites/123reg/LinuxPackage21/60/10/_o/mysite/public_html/sites/all/modules/imagemarker/imagemarker.module).
Notice: Undefined index: height in _imagemarker_load_imagestyle() (line 308 of /websites/123reg/LinuxPackage21/60/10/_o/mysite/public_html/sites/all/modules/imagemarker/imagemarker.module)

I think it has something to do with the virtual host and with the .htaccess but not entirely sure

swentel’s picture

@wayne57 That's something completely different, you should pick a style which has a width and height, otherwhise it won't work.

wayne57’s picture

Many thanks for that. Quite right, I created a new style e
With width and height and it now works a treat. I only wish the markers could be a little larger, but a great module.

ilfelice’s picture

Per comment #3 by amango, enabling multilingual support in the content type and setting the node to neutral language does the trick. Would be great if this could be fixed, so that this workaround is not required.

webmatter’s picture

@amango #3
thank you for so much your tip. Worked like a charm. I guess I would never found out without your help.