Printing completely broken in 1.2b1

[jj0hns0n]

from @cholmes "Printing didn't work at all. Always got The server returned an error: 500 Internal Server Error (tried a few times on different types of layers)"

[cholmes]

I don't think this is critical for 1.2. But if it's not working at all we should probably remove that gxp button from map composer.

[jj0hns0n]

I think this may still have to do with the MapFish whitelist etc. I will
check into it.

On Fri, Jul 27, 2012 at 12:44 PM, Chris Holmes <
reply@reply.github.com

wrote:

I don't think this is critical for 1.2. But if it's not working at all we
should probably remove that gxp button from map composer.

---

Reply to this email directly or view it on GitHub:
#340 (comment)

[ingenieroariel]

This is documented in the post-install notes [1] so we can leave it as is. I think this is a fix for the geoserver printing module, to at least print from the local the geoserver without adding it to the whitelist.

[1] http://docs.geonode.org/en/latest/deploy/production.html#configure-the-printing-module

[jj0hns0n]

I seem to be running into problems with the normal set of base layers we
have, even after adding the entry for the local one. I think we need to
make sure that any thing we have set in the base layers by default is
whitelisted in this yaml.

That said, we are moving toward replacing this mapfish module with
something more 'standards based' in the near future, so I think it may be
ok to just disable the print button and leave this for 2.x.

On Fri, Jul 27, 2012 at 7:05 PM, Ariel Núñez <
reply@reply.github.com

wrote:

This is documented in the post-install notes [1] so we can leave it as is.
I think this is a fix for the geoserver printing module, to at least print
from the local the geoserver without adding it to the whitelist.

[1]
http://docs.geonode.org/en/latest/deploy/production.html#configure-the-printing-module

---

Reply to this email directly or view it on GitHub:
#340 (comment)

[ingenieroariel]

Re-enabling the print button is harder than just fixing the printing
template. (Seems like it would require fetching the js sources,
recompiling them and putting them in the right place).

I am -1 on disabling the print button. And +1 on adding entries for
the default base layers, we have this as one of the required steps
after installation (along with creating a superuser and setting
SITEURL) [1].

[1] http://docs.geonode.org/en/latest/deploy/production.html#required-steps

On Fri, Jul 27, 2012 at 11:14 PM, Jeffrey Johnson
reply@reply.github.com
wrote:

I seem to be running into problems with the normal set of base layers we
have, even after adding the entry for the local one. I think we need to
make sure that any thing we have set in the base layers by default is
whitelisted in this yaml.

That said, we are moving toward replacing this mapfish module with
something more 'standards based' in the near future, so I think it may be
ok to just disable the print button and leave this for 2.x.

On Fri, Jul 27, 2012 at 7:05 PM, Ariel Núñez <
reply@reply.github.com

wrote:

This is documented in the post-install notes [1] so we can leave it as is.
I think this is a fix for the geoserver printing module, to at least print
from the local the geoserver without adding it to the whitelist.

[1]
http://docs.geonode.org/en/latest/deploy/production.html#configure-the-printing-module

---

Reply to this email directly or view it on GitHub:
#340 (comment)

---

Reply to this email directly or view it on GitHub:
#340 (comment)

[jj0hns0n]

I still Ran into problems even after adding all the base layers. I think
it's not respecting sub domains porperly. @ingenieroariel if you can get it
to work by modifying the yaml, I'm happy to leave it in, if not, no sense
including a broken feature.

On Saturday, July 28, 2012, Ariel Núñez wrote:

Re-enabling the print button is harder than just fixing the printing
template. (Seems like it would require fetching the js sources,
recompiling them and putting them in the right place).

I am -1 on disabling the print button. And +1 on adding entries for
the default base layers, we have this as one of the required steps
after installation (along with creating a superuser and setting
SITEURL) [1].

[1]
http://docs.geonode.org/en/latest/deploy/production.html#required-steps

On Fri, Jul 27, 2012 at 11:14 PM, Jeffrey Johnson
<reply@reply.github.com javascript:;>
wrote:

I seem to be running into problems with the normal set of base layers we
have, even after adding the entry for the local one. I think we need to
make sure that any thing we have set in the base layers by default is
whitelisted in this yaml.

That said, we are moving toward replacing this mapfish module with
something more 'standards based' in the near future, so I think it may be
ok to just disable the print button and leave this for 2.x.

On Fri, Jul 27, 2012 at 7:05 PM, Ariel Núñez <
reply@reply.github.com javascript:;

wrote:

This is documented in the post-install notes [1] so we can leave it as
is.
I think this is a fix for the geoserver printing module, to at least
print
from the local the geoserver without adding it to the whitelist.

[1]

http://docs.geonode.org/en/latest/deploy/production.html#configure-the-printing-module

---

Reply to this email directly or view it on GitHub:
#340 (comment)

---

Reply to this email directly or view it on GitHub:
#340 (comment)

---

Reply to this email directly or view it on GitHub:
#340 (comment)

[ingenieroariel]

Jeff can you share the error you get and the modifications to made to the yaml?

-a

On Sat, Jul 28, 2012 at 4:28 PM, Jeffrey Johnson
reply@reply.github.com
wrote:

I still Ran into problems even after adding all the base layers. I think
it's not respecting sub domains porperly. @ingenieroariel if you can get it
to work by modifying the yaml, I'm happy to leave it in, if not, no sense
including a broken feature.

On Saturday, July 28, 2012, Ariel Núñez wrote:

Re-enabling the print button is harder than just fixing the printing
template. (Seems like it would require fetching the js sources,
recompiling them and putting them in the right place).

I am -1 on disabling the print button. And +1 on adding entries for
the default base layers, we have this as one of the required steps
after installation (along with creating a superuser and setting
SITEURL) [1].

[1]
http://docs.geonode.org/en/latest/deploy/production.html#required-steps

On Fri, Jul 27, 2012 at 11:14 PM, Jeffrey Johnson
<reply@reply.github.com javascript:;>
wrote:

I seem to be running into problems with the normal set of base layers we
have, even after adding the entry for the local one. I think we need to
make sure that any thing we have set in the base layers by default is
whitelisted in this yaml.

That said, we are moving toward replacing this mapfish module with
something more 'standards based' in the near future, so I think it may be
ok to just disable the print button and leave this for 2.x.

On Fri, Jul 27, 2012 at 7:05 PM, Ariel Núñez <
reply@reply.github.com javascript:;

wrote:

This is documented in the post-install notes [1] so we can leave it as
is.
I think this is a fix for the geoserver printing module, to at least
print
from the local the geoserver without adding it to the whitelist.

[1]

http://docs.geonode.org/en/latest/deploy/production.html#configure-the-printing-module

---

Reply to this email directly or view it on GitHub:
#340 (comment)

---

Reply to this email directly or view it on GitHub:
#340 (comment)

---

Reply to this email directly or view it on GitHub:
#340 (comment)

---

Reply to this email directly or view it on GitHub:
#340 (comment)

[jj0hns0n]

Copying in info from #329 which was closed as a duplicate.

How can i sent geonode to print using both IP address . The following address is beiong displayed when I try to print a map

Error while generating PDF: DocumentException: org.mapfish.print.InvalidJsonValueException: spec.layers[0].baseURL has an invalid value: http://tile.openstreetmap.org/ (http://192.168.0.116/) at org.mapfish.print.map.readers.HTTPMapReader.checkSecurity(HTTPMapReader.java:64) at org.mapfish.print.map.readers.HTTPMapReader.(HTTPMapReader.java:55) at org.mapfish.print.map.readers.TileableMapReader.(TileableMapReader.java:40) at org.mapfish.print.map.readers.OsmMapReader.(OsmMapReader.java:41) at org.mapfish.print.map.readers.OsmMapReader.create(OsmMapReader.java:78) at org.mapfish.print.map.readers.MapReader.create(MapReader.java:56) at org.mapfish.print.map.MapChunkDrawer.renderImpl(MapChunkDrawer.java:98) at org.mapfish.print.ChunkDrawer.render(ChunkDrawer.java:55) at

[ingenieroariel]

I had no trouble with this on a snapshot from current master after setting the local ip and adding.

In order to be able to fix this ticket I did three things:

• Implemented geonode-updateip, an script that takes in an ip address or dns and updates SITEURL in local_settings.py and printing/config.yaml adding the configured ip address. (Already in master)
• Moved printing config out of gs-data directory and into the data dir (previous attempt to add open layers and others by default had failed because config.yaml was not in the right place and a default version was then written by geoserver
• Added maps.opengeo.org, OSM, Mapquest imagery and Mapquest OSM (the default layer) to the whitelist, so people have better chance of not running into trouble.

Ariel.