Actually deleting from GeoNode and GeoServer should be accomplished automatically when you delete through the Django app, no matter whether you use the admin interface or not. This pre-delete hook is supposed to handle it: https://github.com/GeoNode/geonode/blob/master/src/GeoNodePy/geonode/maps/models.py#L1528
(delete_from_geoserver and delete_from_geonetwork are higher up in the same file). This implementation is pretty naive (there's no retry and no reporting if the deletion fails), definitely room for improvement. It would be nice to add some infrastructure for retrying deletes in cases like this one. We also don't have a way to automatically check for records in GeoNetwork that don't sync up with GeoNode. If you're technically inclined I could point you in the right direction to produce such a script, which would make a nice addition to the GeoNode project. -- David Winslow OpenGeo - http://opengeo.org/ On Mon, Jan 31, 2011 at 3:02 AM, Smitha V <[email protected]> wrote: > Sure, i shall try and get back to u > > > On Mon, Jan 31, 2011 at 10:42 AM, Jeffrey Johnson <[email protected]>wrote: > >> Hi Smitha, >> >> In GeoNode, references to the layers are stored in 3 different places >> (GeoNode, GeoServer, GeoNetwork). Deleting them from the admin only removes >> the reference in the GeoNode database. The is some code (in gsconfig.py I >> believe) that will remove from all three places at once, but it is not >> linked into the interface because it doesn't work perfectly yet. >> >> You *should* be able to remove the layer from GeoNode and then run the >> updatelayers management command to remove the other refefences. But, I >> havent tested it this way myself, so let us know how it goes. >> >> Jeff >> >> On 2011-01-31 at 11:24:26, Smitha V wrote: >> >> Hey, >> >> I have problem while i try to delete the layers. I deleted them from admin >> account. Even after deleting them, it appears when u search for them. Why is >> it so? >> >> On Thu, Jan 27, 2011 at 12:16 PM, Smitha V <[email protected]> wrote: >> >> Thanks a lot Jeff, its working :) >> >> On Thu, Jan 27, 2011 at 11:03 AM, Jeffrey Johnson >> <[email protected]>wrote: >> >> Can you paste the current error please. >> >> Jeff >> >> On 2011-01-27 at 12:11:03, Smitha V wrote: >> >> I have done that too.. >> >> On Thu, Jan 27, 2011 at 10:35 AM, Jeffrey Johnson >> <[email protected]>wrote: >> >> Sounds like you need to edit src/geoserver-geonode-ext/jetty.xml to >> listen on all interfaces (thought you had done this before) >> >> change this line to look as follows (replace localhost with 0.0.0.0) >> >> <Set name="host"><SystemProperty name="jetty.host" >> default="0.0.0.0"/></Set> >> >> Jeff >> >> On 2011-01-27 at 11:53:34, Smitha V wrote: >> >> After changing the urls of Geoserver and Geonetwork, its throwing internal >> server error.. >> >> @David: Can u pls specify the link from where to d/w the new version. >> >> On Thu, Jan 27, 2011 at 10:13 AM, Jeffrey Johnson >> <[email protected]>wrote: >> >> Yes, please try changing the GEOSERVER_BASE_URL and GEONETWORK_BASE URL >> to http://<my-ip>:<port>/geoserver and http://<my-ip>:<port>/geonetwork >> respectively in settings.py >> >> Jeff >> >> On 2011-01-27 at 11:40:04, Smitha V wrote: >> >> These are the changes i have made in order to get Geonode up and running >> so that others are able to access the Geonode runnin on my machine. >> >> In shared/dev-paste.ini >> host=<my-ip> >> port=8000 >> >> In settings.py >> SITENAME = "GeoNode" >> SITEURL = "http://<my-ip>:8000/" >> >> >> In web.xml >> <context-param> >> <param-name>GEONODE_BASE_URL</param-name> >> <param-value>http://<my-ip>:8000/</param-value> >> </context-param> >> >> Am i supposed to change the Base_Url of Geoserver , Geonetwrok from >> localhost to my IP? >> Are there any more changes to be made? When i upload a new data, it it by >> default getting uploaded to localhost instead of my IP. Even while >> downloading the data, it is connecting to localhost instead of connecting to >> my IP. How do it solve this? >> >> On Tue, Jan 25, 2011 at 6:38 PM, David Winslow <[email protected]>wrote: >> >> Your jetty.log file shows an error (the line about the unrecognized >> command line parameter) which was fixed on master last week. I would >> recommend using 'git pull' to get the latest version of the code. (This is >> probably not the source of your current trouble but will become a problem >> once you get Django and GeoServer communicating properly.) >> >> -- >> David Winslow >> OpenGeo - http://opengeo.org/ >> >> On Tue, Jan 25, 2011 at 3:49 AM, Smitha V <[email protected]> wrote: >> >> No, its running on 8000 itself. >> >> >> On Tue, Jan 25, 2011 at 1:40 PM, Jeffrey Johnson <[email protected]>wrote: >> >> It looks like you changed the host in web.xml, but not the port? It is >> trying to connect to http://192.168.0.116:8000/ but I believe your >> geonode is now running on a different port? >> >> < span class="Apple-style-span" style="border-collapse: collapse; >> font-size: 12px; line-height: 17px; white-space: pre; >> -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: >> 2px;">Jeff >> >> On 2011-01-24 at 23:43:17, Smitha V wrote: >> >> I am getting Internal server error only while i try to search data or >> download data. But explore maps is working fine. >> >> On Tue, Jan 25, 2011 at 1:10 PM, Smitha V <[email protected]> wrote: >> >> Hey i have got the error here.. Pls help.. >> >> http://dpaste.de/MkWx/ >> >> >> On Tue, Jan 25, 2011 at 12:54 PM, Smitha V <[email protected]> wrote: >> >> Nope, i am getting that Internal server error even after adding to >> web.xml >> >> >> On Tue, Jan 25, 2011 at 12:26 PM, Jeffrey Johnson >> <[email protected]>wrote: >> >> It is the GEONODE_BASE_URL that is not being set properly ... NOT the >> GEOSERVER_BASE_URL. >> >> GeoServer delegates its authentication to GeoNode, so it (GeoServer) needs >> to know where to connect to the GeoNode. This GEONODE_BASE_URL variable >> needs to be set in the GeoServer web.xml. >> >> Please add the snippet below to your web.xml and try it that way. >> >> Jeff >> >> On 2011-01-24 at 22:53:54, Smitha V wrote: >> >> That is because the Geoserver's base url is specified >> in /geonode/src/GeoNodePy/geonode/settings.py. I have changed it to >> http://<my-ip>8001/Geonetwork >> and http://<my-ip>8001/Geoserver.. >> >> Is there a mistake it that? >> >> On Tue, Jan 25, 2011 at 12:19 PM, Jeffrey Johnson >> <[email protected]>wrote: >> >>> GEONODE_BASE_URL is still not being configured correctly, and therefore >>> GeoServer is using http://localhost:8000/ (the default) >>> >>> You can try setting this value in >>> >>> src/geoserver-geonode-ext/src/main/webapp/WEB-INF/web.xml with this >>> snippet. >>> >>> <context-param> >>> <param-name>GEONODE_BASE_URL</param-name> >>> <param-value>http://localhost:8080/</param-value> >>> </context-param> >>> >>> Replace localhost:8000 with the your servers configuration (IP address >>> and port) >>> >>> Jeff >>> >>> On 2011-01-24 at 22:21:14, Smitha V wrote: >>> >>> IIITB >>> >>> >>> >> >> >> -- >> Regards >> Smitha V >> MT2009149 >> IIITB >> >> >> >> >> >> -- >> Regards >> Smitha V >> MT2009149 >> IIITB >> >> >> >> >> -- >> Regards >> Smitha V >> MT2009149 >> IIITB >> >> >> >> >> -- >> Regards >> Smitha V >> MT2009149 >> IIITB >> >> >> >> >> >> -- >> Regards >> Smitha V >> MT2009149 >> IIITB >> >> >> >> >> >> -- >> Regards >> Smitha V >> MT2009149 >> IIITB >> >> >> >> >> >> -- >> Regards >> Smitha V >> MT2009149 >> IIITB >> >> >> >> >> >> -- >> Regards >> Smitha V >> MT2009149 >> IIITB >> >> >> >> >> >> -- >> Regards >> Smitha V >> MT2009149 >> IIITB >> >> >> >> >> -- >> Regards >> Smitha V >> MT2009149 >> IIITB >> >> >> > > > -- > Regards > Smitha V > MT2009149 > IIITB > >
