[ckan-discuss] problem implimenting WMS preview

[Adrià Mercader]

Hi Andrew,

This js error should not affect the preview, see eg [1]. For WMS I
suspect the proxy request is currently broken on ckanext-spatial, I'm
not sure what could happen with the geojson files, perhaps they are
too big?
If you open firebug or the chrome developer tools you should  see a
failed request to the proxy that might give you a better idea of what
happened.


Adrià

[1] http://master.ckan.org/dataset/ckan-instances/resource/cfe5802d-12c8-49c7-8cd6-6d57de2954a0

On 14 November 2013 18:59, Koebrick, Andrew (MNIT)
<andrew.koebrick at state.mn.us> wrote:
> I ended up doing a full reinstall of CKAN on our devel server and the WMS / geojson preview gets a little further along, but still fails.  Now, when attempting to preview, the word "Loading...: appears and a javascript error throws:
>
> TypeError: jQuery(...).popover is not a function
> jQuery('[data-target="popover"]').popover();
>
> This sounded a bit like  this error:
> https://github.com/okfn/ckan/issues/1305
>
> So I added a comment to the issue thread.  I also tried to load bootstrap.js via our extension so that it would be the last module loaded in case it was somehow bumbing into a namespace collision or getting overwritten by other javascript.  No improvement.
>
> Any assistance would be appreciated.
>
> Andrew
>
> -----Original Message-----
> From: Adrià Mercader [mailto:adria.mercader at okfn.org]
> Sent: Wednesday, October 30, 2013 8:49 AM
> To: Koebrick, Andrew (MNIT)
> Cc: ckan-discuss at lists.okfn.org
> Subject: Re: [ckan-discuss] problem implimenting WMS preview
>
> On 30 October 2013 13:10, Koebrick, Andrew (MNIT) <andrew.koebrick at state.mn.us> wrote:
>> Our spatial extension is 0.2 which seems to match the version number here: https://github.com/okfn/ckanext-spatial/blob/master/setup.py  But we did install ours back on June 19, and I see that there have been various commits to the github repo since then so perhaps updating it would be good.
>
> I would recommend check out the "stable" branch of ckanext-spatial and update to the latest version, to make sure we are not running in an already fixed issue.
>
> Adrià
>
>