Did a test build locally and the problem doesn't appear, so I think someone already fixed it. It will be fixed in the next release automatically, but perhaps webmaster Kevin could manually fix on the site for now? Assigning to him. Kevin, kick it back to me if you want.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I could possibly fix this with clever use of the command line, but I think there's only one copy to do it on: the live version. I don't want to screw it up. Isn't Council planning to do a new release soon? If so, I'd just as soon wait till that happens and we overwrite it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is only on the Guidelines part of the site. Looking at it now...
Did a test build locally and the problem doesn't appear, so I think someone already fixed it. It will be fixed in the next release automatically, but perhaps webmaster Kevin could manually fix on the site for now? Assigning to him. Kevin, kick it back to me if you want.
I could possibly fix this with clever use of the command line, but I think there's only one copy to do it on: the live version. I don't want to screw it up. Isn't Council planning to do a new release soon? If so, I'd just as soon wait till that happens and we overwrite it.
This seems to be fixed -- should have been closed after the last release,