Closed (fixed)
Project:
Location
Version:
6.x-3.x-dev
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
13 Apr 2009 at 13:26 UTC
Updated:
27 May 2010 at 13:42 UTC
Jump to comment: Most recent file
Comments
Comment #1
seanrComment #2
seanrComment #3
yesct commentedTagging
Comment #4
yesct commentedcould this be related to #769094: locations.tpl.php bug
?
this patch might be a candidate for a quick review... good for someone who has never tested a patch before... *grin* come on, you know you want to! I'll help you, just reply or contact me.
Comment #5
hutch commentedNo, not the same template file.
As you suggest, let someone else review this, nice and simple, gotta start somewhere ;-)
Comment #6
yesct commented:)
Comment #7
yesct commentedtagging
Comment #8
eporama commentedI tested the patch in #2, it applied fine (but the line numbers were off). Works as advertised and location-cck and node locations both worked fine. The map link is now within the div.
I rerolled the patch against current dev to get line numbers right, but other than that, no change.
Comment #9
eporama commentedYesCT also thought I should mention that we had some back and forth re: the "No newline at end of file" which I couldn't figure out why my ".new" file was without a newline. I noticed that the original patch in #2 also had the "No newline at end of file", which I take to mean that it actually removed the newline when I applied the patch. Just thought it should be mentioned since it was another "difference" in the two patches.
Comment #10
hutch commented#8 rerolleddiv.patch works fine, RTBC as far as I'm concerned.
In #9, "No newline at end of file" means that the 'changed' file that the patch was built from did not have a newline (eg did not have an empty line at the end of the file), so the patch reflected that but provides a warning in case that was not the intention. Just goes to show that all files should have a newline on the end, at least when working with scripts in drupal.
Comment #11
yesct commentedeporama, what was that trick you said in IRC you used to see the characters in a file? something -c?
Comment #12
eporama commentedod -c
octal (or hex, decimal, ASCII) dump but with "Output C-style escaped characters". This shows \n and/or \r for linefeeds, carriage returns, etc. Also handy for telling if \t or " " is used... Not a pretty output, but at least it's relatively plain.
Comment #13
yesct commentedupdating tags.
Comment #14
rooby commentedCommitted to D5, D6 and HEAD. Thanks.
Comment #15
hutch commentedAnd with the map link in its own div, excellent! That makes theming much easier.
Comment #16
yesct commentedhttp://drupal.org/cvs?commit=360998
http://drupal.org/cvs?commit=361000
http://drupal.org/cvs?commit=361002
Comment #18
rooby commentedJust realised I committed to the DRUPAL-5 branch instead of the DRUPAL-5--3 branch :(
Committed to DRUPAL-5--3 - http://drupal.org/cvs?commit=372110