I've tried specifying something different from 'Default Map' as format for 'Teaser' and 'Full node' in 'display fields' tab of content type configuration.

Getting NO map in node view mode when doing so.

Comments

strk’s picture

strk commented

Uhm, _another_ non-default preset works fine, so sounds like a problem with a specific preset.
This specific preset (I called it 'project_view') has been created by _cloning_ the one that works
(called 'project_edit') and adding my own WMS as an overlay (non-active).

strk’s picture

strk commented

I've found that 'theme_openlayers_cck_formatter_map' function, defined in includes/openlayers_cck.theme.inc,
is not even called in the non-working preset case.
It is with the preset that works.

strk’s picture

strk commented

_none_ of the functions in includes/openlayers_cck.theme.inc are called, when the non-working preset is used!

strk’s picture

strk commented

I checked DB definition of the two presets (working and non-working) and found them actually equal (the 'data' field).

The name, title and description differ:
Working one:
name: project_edit
title: Project edit
desc: Projects edit

Non-working one:
name: project_view
title: Project view
desc: Projects view

strk’s picture

strk commented

'drush cc all' fixed this.
Anything we can do from the module to do better (auto-cleaning when troubles detected or print/log an error or the like) ?

pavithran’s picture

pavithran commented

@strk : something similar happpened in my case .

The default preset loads only mapnik . Hence i created a preset(pre1) with osmarender and google maps . It was not working and sometimes only showed the default preset .

I created a new preset(pre2) with same layers + more google layers .

Now the old one magically started working while the new one is not working . Added to that this time for the new one nothing is shown . not even the default preset .

This behaviour is only shown in views. Its not shown when the node is edited .

strk’s picture

strk commented

did cleaning the cache work for you ?

zzolo’s picture

zzolo commented
Category: bug » support

The cache should be cleared on any update (even without DB changes). This is true of any module. Is this still an actionable ticket?

strk’s picture

strk commented

can be closed for me.

zzolo’s picture

zzolo commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.