[GeoNode-devel] [GeoNode-users] Changes to local_settings.py ignored [Windows, Apache]

Wed Nov 2 11:01:45 PDT 2016

On the first day of the Summit, we should decide on a new more moden method
for documentation and whiteboard a new UX flow for geonode.org.  I can
definitely see us having a "management commands" section of the website.

Regards,
Patrick Dufour

On Nov 2, 2016 1:11 PM, "Francesco Bartoli" <xbartolone at gmail.com> wrote:

> Surely, maybe we can handle that during the sprint at the latest
>
> Cheers,
> Francesco
>
> Sent from Nylas N1
> <https://link.nylas.com/link/43o9gzlmd58gqwkxv3di3wjcc/local-644a5635-880d/0?redirect=https%3A%2F%2Fnylas.com%2Fn1%3Fref%3Dn1&r=Z2Vvbm9kZS11c2Vyc0BsaXN0cy5vc2dlby5vcmc=>,
> the extensible, open source mail client.
>
> On nov 2 2016, at 1:07 pm, Alessio Fabiani <alessio.fabiani at geo-
> solutions.it> wrote:
>
>> Hi Francesco,
>> good catch. Those commands are not documented on the official GeoNode
>> documentation (as far as I can see).
>>
>> It would be good to have them documented.
>>
>> I'll try to find some time to test them and improve the documentation. I
>> have no much time in these days though, so if someone would like to do that
>> in the meantime it will be very welcomed.
>>
>>
>>
>> Best Regards,
>> Alessio Fabiani.
>>
>> ==
>> GeoServer Professional Services from the experts!
>> Visit http://goo.gl/it488V
>> <http://goo.gl/it488V&r=Z2Vvbm9kZS11c2Vyc0BsaXN0cy5vc2dlby5vcmc=> for
>> more information.
>> ==
>>
>> Ing. Alessio Fabiani
>> @alfa7691
>> Founder/Technical Lead
>>
>> GeoSolutions S.A.S.
>> Via di Montramito 3/A
>> 55054  Massarosa (LU)
>> Italy
>> phone: +39 0584 962313
>> fax:     +39 0584 1660272
>> mob:   +39 331 6233686
>>
>> http://www.geo-solutions.it
>> <http://www.geo-solutions.it&r=Z2Vvbm9kZS11c2Vyc0BsaXN0cy5vc2dlby5vcmc=>
>> http://twitter.com/geosolutions_it
>> <http://twitter.com/geosolutions_it&r=Z2Vvbm9kZS11c2Vyc0BsaXN0cy5vc2dlby5vcmc=>
>>
>> -------------------------------------------------------
>>
>> *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
>>
>> Le informazioni contenute in questo messaggio di posta elettronica e/o
>> nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
>> loro utilizzo è consentito esclusivamente al destinatario del messaggio,
>> per le finalità indicate nel messaggio stesso. Qualora riceviate questo
>> messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
>> darcene notizia via e-mail e di procedere alla distruzione del messaggio
>> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
>> divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
>> utilizzarlo per finalità diverse, costituisce comportamento contrario ai
>> principi dettati dal D.Lgs. 196/2003.
>>
>>
>>
>> The information in this message and/or attachments, is intended solely
>> for the attention and use of the named addressee(s) and may be confidential
>> or proprietary in nature or covered by the provisions of privacy act
>> (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
>> Code).Any use not in accord with its purpose, any disclosure, reproduction,
>> copying, distribution, or either dissemination, either whole or partial, is
>> strictly forbidden except previous formal approval of the named
>> addressee(s). If you are not the intended recipient, please contact
>> immediately the sender by telephone, fax or e-mail and delete the
>> information in this message that has been received in error. The sender
>> does not give any warranty or accept liability as the content, accuracy or
>> completeness of sent messages and accepts no responsibility  for changes
>> made after they were sent or for other risks which arise as a result of
>> e-mail transmission, viruses, etc.
>>
>> ---------------------------------------------------------------------
>>
>> On Wed, Nov 2, 2016 at 1:02 PM, Francesco Bartoli <xbartolone at gmail.com>
>> wrote:
>>
>> Hi Alessio,
>>
>> I think the geonode updatemaplayerip [1] might be of help
>>
>> Ciao,
>> Francesco
>>
>> [1] https://github.com/GeoNode/geonode/blob/master/geonode/
>> maps/management/commands/updatemaplayerip.py
>> <https://github.com/GeoNode/geonode/blob/master/geonode/maps/management/commands/updatemaplayerip.py&r=Z2Vvbm9kZS11c2Vyc0BsaXN0cy5vc2dlby5vcmc=>
>>
>> Sent from Nylas N1
>> <https://link.nylas.com/link/43o9gzlmd58gqwkxv3di3wjcc/local-56e8c7e4-998d/0?redirect=https%3A%2F%2Fnylas.com%2Fn1%3Fref%3Dn1&r=Z2Vvbm9kZS11c2Vyc0BsaXN0cy5vc2dlby5vcmc=&r=Z2Vvbm9kZS11c2Vyc0BsaXN0cy5vc2dlby5vcmc=>,
>> the extensible, open source mail client.
>>
>> On nov 2 2016, at 11:49 am, Alessio Fabiani <
>> alessio.fabiani at geo-solutions.it> wrote:
>>
>> Hello Nicolai,
>> I'm going to maintain the discussion on the mailing list so that it can
>> be useful for other users too in the future.
>>
>> The problem should be related only to the maps. I'm currently not aware
>> of a quick command to do this. At this point you have two options:
>>
>> 1. Delete only the old maps and rebuild them from scratch.
>>
>> 2. Manually update the GeoServer ip address on the database -> main
>> geonode database, table "maps_maplayer"
>>
>>
>>
>> Best Regards,
>> Alessio Fabiani.
>>
>> ==
>> GeoServer Professional Services from the experts!
>> Visit http://goo.gl/it488V
>> <http://goo.gl/it488V&r=Z2Vvbm9kZS11c2Vyc0BsaXN0cy5vc2dlby5vcmc=&r=Z2Vvbm9kZS11c2Vyc0BsaXN0cy5vc2dlby5vcmc=>
>> for more information.
>> ==
>>
>> Ing. Alessio Fabiani
>> @alfa7691
>> Founder/Technical Lead
>>
>> GeoSolutions S.A.S.
>> Via di Montramito 3/A
>> 55054  Massarosa (LU)
>> Italy
>> phone: +39 0584 962313
>> fax:     +39 0584 1660272
>> mob:   +39 331 6233686
>>
>> http://www.geo-solutions.it
>> <http://www.geo-solutions.it&r=Z2Vvbm9kZS11c2Vyc0BsaXN0cy5vc2dlby5vcmc=&r=Z2Vvbm9kZS11c2Vyc0BsaXN0cy5vc2dlby5vcmc=>
>> http://twitter.com/geosolutions_it
>> <http://twitter.com/geosolutions_it&r=Z2Vvbm9kZS11c2Vyc0BsaXN0cy5vc2dlby5vcmc=&r=Z2Vvbm9kZS11c2Vyc0BsaXN0cy5vc2dlby5vcmc=>
>>
>> -------------------------------------------------------
>>
>> *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
>>
>> Le informazioni contenute in questo messaggio di posta elettronica e/o
>> nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
>> loro utilizzo è consentito esclusivamente al destinatario del messaggio,
>> per le finalità indicate nel messaggio stesso. Qualora riceviate questo
>> messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
>> darcene notizia via e-mail e di procedere alla distruzione del messaggio
>> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
>> divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
>> utilizzarlo per finalità diverse, costituisce comportamento contrario ai
>> principi dettati dal D.Lgs. 196/2003.
>>
>>
>>
>> The information in this message and/or attachments, is intended solely
>> for the attention and use of the named addressee(s) and may be confidential
>> or proprietary in nature or covered by the provisions of privacy act
>> (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
>> Code).Any use not in accord with its purpose, any disclosure, reproduction,
>> copying, distribution, or either dissemination, either whole or partial, is
>> strictly forbidden except previous formal approval of the named
>> addressee(s). If you are not the intended recipient, please contact
>> immediately the sender by telephone, fax or e-mail and delete the
>> information in this message that has been received in error. The sender
>> does not give any warranty or accept liability as the content, accuracy or
>> completeness of sent messages and accepts no responsibility  for changes
>> made after they were sent or for other risks which arise as a result of
>> e-mail transmission, viruses, etc.
>>
>> ---------------------------------------------------------------------
>>
>> On Wed, Nov 2, 2016 at 10:15 AM, Nicolai Cryer <nkcryer at gmail.com> wrote:
>>
>> Dear Alessio,
>>
>> Thank you so much for your reply, this is really driving me nuts :)
>>
>> I just tested it out, and you were spot on - it's only the old maps that
>> have this issue. New maps created after changing the URL work perfectly.
>> THANK YOU!!! This is such a relief.
>>
>> Do you know if there's any way to update the configuration in the
>> database? Or should I re-upload all the data?
>>
>> 2016-11-02 9:41 GMT+01:00 Alessio Fabiani <alessio.fabiani at geo-solutions
>> .it>:
>>
>> Dear Nicolai,
>> is the problem related to the new layers also or just the old ones? Can
>> you please describe exactly your test-case?
>>
>> The thing is... if you are trying to expose your saved maps, consider
>> that the configuration is stored on the database. Therefore if you created
>> those maps with the old ip most probably the configuration still has the
>> latter recored on the DB.
>>
>> Best Regards,
>> Alessio Fabiani.
>>
>> ==
>> GeoServer Professional Services from the experts!
>> Visit http://goo.gl/it488V
>> <http://goo.gl/it488V&r=Z2Vvbm9kZS11c2Vyc0BsaXN0cy5vc2dlby5vcmc=&r=Z2Vvbm9kZS11c2Vyc0BsaXN0cy5vc2dlby5vcmc=>
>> for more information.
>> ==
>>
>> Ing. Alessio Fabiani
>> @alfa7691
>> Founder/Technical Lead
>>
>> GeoSolutions S.A.S.
>> Via di Montramito 3/A
>> 55054  Massarosa (LU)
>> Italy
>> phone: +39 0584 962313
>> fax:     +39 0584 1660272
>> mob:   +39 331 6233686
>>
>> http://www.geo-solutions.it
>> <http://www.geo-solutions.it&r=Z2Vvbm9kZS11c2Vyc0BsaXN0cy5vc2dlby5vcmc=&r=Z2Vvbm9kZS11c2Vyc0BsaXN0cy5vc2dlby5vcmc=>
>> http://twitter.com/geosolutions_it
>> <http://twitter.com/geosolutions_it&r=Z2Vvbm9kZS11c2Vyc0BsaXN0cy5vc2dlby5vcmc=&r=Z2Vvbm9kZS11c2Vyc0BsaXN0cy5vc2dlby5vcmc=>
>>
>> -------------------------------------------------------
>>
>> *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
>>
>> Le informazioni contenute in questo messaggio di posta elettronica e/o
>> nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
>> loro utilizzo è consentito esclusivamente al destinatario del messaggio,
>> per le finalità indicate nel messaggio stesso. Qualora riceviate questo
>> messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
>> darcene notizia via e-mail e di procedere alla distruzione del messaggio
>> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
>> divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
>> utilizzarlo per finalità diverse, costituisce comportamento contrario ai
>> principi dettati dal D.Lgs. 196/2003.
>>
>>
>>
>> The information in this message and/or attachments, is intended solely
>> for the attention and use of the named addressee(s) and may be confidential
>> or proprietary in nature or covered by the provisions of privacy act
>> (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
>> Code).Any use not in accord with its purpose, any disclosure, reproduction,
>> copying, distribution, or either dissemination, either whole or partial, is
>> strictly forbidden except previous formal approval of the named
>> addressee(s). If you are not the intended recipient, please contact
>> immediately the sender by telephone, fax or e-mail and delete the
>> information in this message that has been received in error. The sender
>> does not give any warranty or accept liability as the content, accuracy or
>> completeness of sent messages and accepts no responsibility  for changes
>> made after they were sent or for other risks which arise as a result of
>> e-mail transmission, viruses, etc.
>>
>> ---------------------------------------------------------------------
>>
>> On Tue, Nov 1, 2016 at 3:29 PM, Nicolai Cryer <nkcryer at gmail.com> wrote:
>>
>> Hi,
>>
>> We're trying to open our Geonode installation to the public, and have
>> done the necessary DNS stuff. As such, our Geonode is able to serve static
>> files (html etc.) to outside the internal network, but the url for WMS
>> services etc. still seems to be configured to the localhost.
>>
>> As such, users can view the Geonode front-end but cannot be served
>> WMS/WFS content from our geoserver (these show up as bad tiles in
>> geoexplorer).
>>
>> I tried to solve this by editing local_settings.py in
>> C:\GeoNode-2.4.x\geonode-2.4.x\geonode, specifically the
>> "PUBLIC_LOCATION" key in the OGC dictionary.
>>
>> The big problem is that no matter what I change in settings.py or
>> local_settings.py, how many times I restart Apache/Tomcat/the whole server,
>> delete .pyc files to be regenerated etc., the changes are never reflected
>> in the actual OGC configuration. I don't understand where the problem lies!
>>
>> I've even attempted to delete settings.py without incident, so it's like
>> the files are cached somewhere (perhaps in the bowels of Apache?)
>>
>> I would be most grateful for any ideas, because I've almost exhausted the
>> list of buttons to push :/
>>
>> Best,
>>
>> Nicolai
>>
>> _______________________________________________
>> geonode-users mailing list
>> geonode-users at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/geonode-users
>> <http://lists.osgeo.org/mailman/listinfo/geonode-users&r=Z2Vvbm9kZS11c2Vyc0BsaXN0cy5vc2dlby5vcmc=&r=Z2Vvbm9kZS11c2Vyc0BsaXN0cy5vc2dlby5vcmc=>
>>
>>
>>
>>
>>
>> _______________________________________________
>> geonode-users mailing list
>> geonode-users at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/geonode-users
>> <http://lists.osgeo.org/mailman/listinfo/geonode-users&r=Z2Vvbm9kZS11c2Vyc0BsaXN0cy5vc2dlby5vcmc=>
>>
>>
>>
> _______________________________________________
> geonode-users mailing list
> geonode-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/geonode-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-devel/attachments/20161102/9dc7f8ac/attachment-0001.html>