<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div>Hi Toni,<br></div><div>I spotted those and fixed them by refreshing the statistics. Is WPS enabled? It seems that the feature catalogue info is not written properly on those instances.<br data-mce-bogus="1"></div><div>I was not able to reproduce that kind of behaviour, yet.<br data-mce-bogus="1"></div><div>yours,<br data-mce-bogus="1"></div><div>Florian</div><div data-marker="__SIG_PRE__">-- <br>MSc Florian Hoedt<br>Head Geoinformatics | OpenData Representative<br>Thünen Institute, Centre for Information Management<br>Bundesallee 44<br>38116 Braunschweig<br><br>Tel: +49 531 596-1428<br>Mobil: +49 162 92 50 275<br>Fax: +49 531 596-1499<br>Mail: florian.hoedt@thuenen.de<br>Web: www.thuenen.de<br><br>The Johann Heinrich von Thünen Institute, Federal Research Institute for Rural Areas, Forestry and Fisheries – Thünen Institute in brief – consists of 14 specialized institutes that carry out research and provide policy advice in the fields of economy, ecology and technology.</div><div><br></div><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><b>Von: </b>"Toni Schönbuchner" <toni.schoenbuchner@csgis.de><br><b>An: </b>"geonode-devel" <geonode-devel@lists.osgeo.org><br><b>Gesendet: </b>Montag, 8. Februar 2021 09:17:12<br><b>Betreff: </b>[GeoNode-devel] Upload layer on migrated 3.1 missing attributes<br></div><div><br></div><div data-marker="__QUOTED_TEXT__">Hi Devs,<div class=""><br class=""></div><div class="">I’m fighting with a strange problem on an instance which has been</div><div class="">migrated from 3.1-dev to 3.1 (final) on docker. </div><div class=""><br class=""></div><div class="">Every uploaded layer is missing attributes.</div><div class="">This leads to an empty attributes table on layers detail page</div><div class="">and an unstyled response in mapstores feature window. </div><div class=""><br class=""></div><div class="">No errors can be spotted in log output during upload.</div><div class="">The django and geoserver container have already been rebuild. </div><div class=""><br class=""></div><div class="">Has anybody run into something similar or has an idea</div><div class="">what could prevent the Attributes model to be filled?</div><div class=""><br class=""></div><div class="">Thanks,</div><div class=""><br class=""></div><div class="">Toni</div><div class=""><br class=""></div><div class="">PS: These issues come close but should already be resolved:</div><div class=""><div class=""><a href="https://github.com/GeoNode/geonode/issues/4713" target="_blank" rel="nofollow noopener noreferrer">https://github.com/GeoNode/geonode/issues/4713</a><br data-mce-bogus="1"></div><div class=""><a href="https://github.com/GeoNode/geonode/issues/5577" target="_blank" rel="nofollow noopener noreferrer">https://github.com/GeoNode/geonode/issues/5577</a><br data-mce-bogus="1"></div></div><div class=""><br class=""></div><br>_______________________________________________<br>geonode-devel mailing list<br>geonode-devel@lists.osgeo.org<br>https://lists.osgeo.org/mailman/listinfo/geonode-devel<br></div></div></body></html>