Showing posts with label debugging. Show all posts
Showing posts with label debugging. Show all posts

Monday, 5 May 2014

Google map rendering problem

To self: Next time google map tiles don't display properly in a Plone site page (or anywhere actually) - check to see if you have set the width and height for the map container.

*doh*

Friday, 4 October 2013

Getting autofs working on a Centos NeCTAR vm


So I have to set up a web server on a NeCTAR vm to allow public access to some research data that is sitting on RDSI storage in the QCIF UQ node. The node support team requested that instead of just NFS mounting the data storage to the vm, it would be preferable to use autofs to mount the filesystem.

I'm not a sys-admin type - mostly my linux environments are all set up for me so this was a bit of an adventure. I had quite a few problems so, with the aim of helping out future non sys-admin types in the same position, I thought I should document what I had to do.

Wednesday, 30 November 2011

Something for next time

Remember, if you change something in a buildout script - rerun buildout if you want the change to have efffect.

Tuesday, 30 August 2011

Plone debugging

To get an interactive debugger in your plone code:
  • add import ipdb; ipdb.set_trace() into the code
  • the set_trace function sets a breakpoint at the point in the code.

To reload the code you are debugging after you have made changes with out having to restart the service, to gohost:port/@@reload
this doesn't always work. If you get a complaint mentioning something to do with calling super then you will probably just have to live with restarting the service instead.