Closed (fixed)
Project:
Broken Anchor
Version:
6.x-1.0-rc2
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
19 Jan 2009 at 14:58 UTC
Updated:
21 Feb 2009 at 19:30 UTC
After installed Broken Anchor it broke my whole website with some php code.
Tested on HeartInternet virtual hosting.
| Comment | File | Size | Author |
|---|---|---|---|
| Clipboard01.jpg | 590.26 KB | kenorb |
Comments
Comment #1
kenorb commentedSolution: Changing short_open_tag to <?php start worked.
Ignoring hundreds of errors similar to:
#354432: Many errors on insall--unusable
#354125: Broken Anchor SQL Error
#354430: Invalid PHP tag
WTF?!?!???
Disabling the module, until the next stable release. If there will be any.
Using short php tag is depreciated, most of the server doesn't support it anymore.
Please change it.
Comment #2
Yoran commentedKeep cool, It would have been nice to send me an email instead of getting mad at me.
Anyway, everything seems to be fine with RC3
Comment #3
kenorb commentedSorry:)
I like testing some nice new modules, but I'm always pessimist when installing some new modules, because 1/4 of it always breaking something with fatal errors and you never don't know why.
But it's good to know that this module is not suspended as many others:)
Thank you.
Comment #4
Yoran commentedNo and it will not :) I have many modules on my own site, when I put one here, it's to maintain them, not just for fun ;-) I'll just try to watch this issues page more often in the future :)
Comment #5
kenorb commentedBut some modules provides some nice solution which are very useful and sometimes you realize after than that you need that functionality and you can also improve those modules by testing it, so it's not only for fun.
But I wondering why there is no any test bot which will check the basic errors before you installing it. It will save lot of time and problems.
#362931: Automated testing for contrib modules
Comment #6
Yoran commentedBy "not for fun", I was meaning that as I choose those two modules of mine to put them in this forge, I realy don't want them to be dead code.
About testing, As I'm from Java world, I fully agree with your vision. specially when mistakes are like mine (short php tags or wrong mysql fields). As I am (as many module authors I think) a full time PHP dev, this can be really usefull.
With an higher point of view, the all Drupal project need QA Process soon or later. A real validation cycle for module with a recognized compliance label is the only way to compete with mambo/joomla people.