yes

On Fri, Oct 14, 2011 at 2:49 PM, Joe Larson <[email protected]> wrote:
> Thank you Andreas and Ariel!
>
> Am I right in this planned workflow? Clone
> https://github.com/GeoNode/geonode-client > run `ant zip` > move
> archive to /var/lib/geonode/src/GeoNodePy/geonode/maps/media/geonode/
>> run `sudo geonode collectstatic -v0`
>
> On Fri, Oct 14, 2011 at 11:18 AM, Andreas Hocevar <[email protected]> 
> wrote:
>> Fixed with 
>> https://github.com/GeoNode/geonode-client/commit/899f291d37f84a510435f5210ff150d57f0bf41c.
>>
>> Andreas.
>>
>> On Oct 14, 2011, at 20:13 , Joe Larson wrote:
>>
>>> I forgot to include that the Firebug error also mentioned:
>>>
>>> GeoExplorer.js (line 13)
>>>
>>> On Fri, Oct 14, 2011 at 11:09 AM, Andreas Hocevar <[email protected]> 
>>> wrote:
>>>> Hi,
>>>>
>>>> I'll give this a look shortly. Will keep you posted.
>>>>
>>>> Andreas.
>>>>
>>>> On Oct 14, 2011, at 20:07 , Joe Larson wrote:
>>>>
>>>>> I am getting this error (Firebug console output) when clicking the
>>>>> Print button in GeoNode; occurs both when using 'no background' and
>>>>> 'OpenStreetMap' Base Layers:
>>>>>
>>>>>
>>>>> invalid 'instanceof' operand OpenLayers.Layer.GoogleNG
>>>>> [Break On This Error]
>>>>> setScale.call(this);this.mapPanel.map....tadataForm){this.initMetadataForm();}
>>>>>
>>>>>
>>>>> I have no custom entries in my settings.py or local_settings.py for
>>>>> other Base Layers.
>>>>>
>>>>> dwins and I (larso) chatted briefly about it on IRC, it was mentioned:
>>>>> "GoogleNG is no longer a valid layer type" & "it's possible that a
>>>>> lingering reference to it exists..."
>>>>>
>>>>> I have asked in #geoext without any leads - wondering if other
>>>>> installs of 1.1+RC1-ariel6 experience this or if anyone on this list
>>>>> can help us move forward to enable printing.
>>>>>
>>>>>
>>>>> -JLarson
>>>>
>>>> --
>>>> Andreas Hocevar
>>>> OpenGeo - http://opengeo.org/
>>>> Expert service straight from the developers.
>>>>
>>>>
>>
>> --
>> Andreas Hocevar
>> OpenGeo - http://opengeo.org/
>> Expert service straight from the developers.
>>
>>
>

Reply via email to