sections.module, line 173

bad code
t('Are you sure you want to delete the section %name?', array('%name' => '<em>'. $ection->name .'</em>')),

fixed code
t('Are you sure you want to delete the section %name?', array('%name' => '<em>'. $section->name .'</em>')),

Please update your code.

Regards
quiptime

Comments

Patrick Nelson’s picture

Patrick Nelson commented

Thx quiptime

Bèr Kessels’s picture

Bèr Kessels commented
Status: Active » Fixed

committed, thanks. BTW: in future you might want to learn to make patches. It makes fixing bugs a lot easier for all of us:

http://drupal.org/diffandpatch

quiptime’s picture

quiptime commented
Title: small bug- bugfix » very small bug- post a patch file or not

@Bèr Kessels

Ok, i can post a diff or patch file. But, often my code contains also different changes. And these changes are not fixed a bug. Linux: diff compares 2 complete files. I would have to remove the other changes for one moment. That is for me too much stress, only around post a small bug.
In a situation with a large and more complex error or other extensive changes I produce a patch file. For memory, above I post an error with only one line.

Thank you for your tip.
quiptime

Bèr Kessels’s picture

Bèr Kessels commented

@quiptime
That means *you* must change your workflow and methods.
We, Drupal, agree on one system: patches. Please abide by these "laws".

Patrick Nelson’s picture

Patrick Nelson commented

quiptime,

I know what you mean because I change a lot of the default files too, but can you not keep a copy of the original file? And then, when you make a change that fixes a bug, perhaps you could also make it to your copy of the original and then post the patch / diff?

Regards

Patrick

quiptime’s picture

quiptime commented

Ok, I adapted my file system on that to use of patches.

Patrick Nelson’s picture

Patrick Nelson commented

Thx quiptime,

That will be a great help to everyone in the community.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)