Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 UTC on 18 March 2024, to get $100 off your ticket.
This breaks any attempt to send headers to the screen from any other module. Any chance you could remove that? It appears in both 7.2 and 7.2dev.
Thanks!
Comments
Comment #1
pedrofaria CreditAttribution: pedrofaria commentedHello elliot,
Sorry... I will release a new version with this fix soon.
Comment #2
Ronino CreditAttribution: Ronino commentedI can confirm this bug in 2.0 and that it's fixed in the latest dev version.
I noticed that XML exported by taxonomy_xml and Views RSS feeds head a leading space which made the XML invalid, resulting in XML parser errors like "XML declaration allowed only at the start of the document". Also Drupal's page markup head a leading space. Took me some time to trace it back to this module.
As I can imagine people out there struggling with the above behavior, I suggest not to wait too long with the next release so they get the fix automatically with an update. There's no obvious evidence that it's this module causing the trouble.
Comment #3
bropp CreditAttribution: bropp commentedJust ran into this one myself trying to create a googlenews sitemap (XML parser threw errors). Switched to the dev version and that fixed it. Please create a new release version as soon as you can.
Comment #4
rwinikates CreditAttribution: rwinikates commentedYes, the dev version fixed this for an issue I was having with another module. Having this as a tagged release would be very helpful!
Comment #5
rjacobs CreditAttribution: rjacobs commentedI just want to further advocate for pushing another release (even if it just captures this one fix). I don't personally use the Form API Validation module, but I have received a bug report in the issue queue for a module I maintain (Juicebox HTML5 Responsive Image Galleries) that's ultimately traced to this problem. See also: #1962548: Form API Validation module <= 7.x-2.0 breaks Juicebox (and probably many other modules)
Clearly the symptoms of this are causing lots of confusion for users.
Comment #6
melissavdh CreditAttribution: melissavdh commentedThis caused an erroneous space to be inserted into our WSDL, which thus rendered some SOAP calls invalid. Had to patch the module to sort this out - would be good to get a new version of this module released with this fix in place.
Comment #7
barraponto CreditAttribution: barraponto commentedThis is already fixed in the dev release.
This module will have a minor release ASAP (end of day).
Thanks for the feedback and support.
Comment #8
rjacobs CreditAttribution: rjacobs commentedJust wanted to check on this. Any word on a 7.x-2.1 release? It looks like things are still at 7.x-2.0. I know the fix is in dev, but most new users will not be using the dev version, so they will still be hitting this issue (which also impacts other modules).
Cheers!
Comment #10
rwinikates CreditAttribution: rwinikates commentedRe-opening since there still isn't a new tagged release. Please?
Comment #11
juampynr CreditAttribution: juampynr commentedPushing it up to critical. It took me 2 hours to figure out where was that empty space coming from.
Please release as soon as possible so this does not happen to anyone else.
Comment #12
pedrofaria CreditAttribution: pedrofaria commentedSorry guys... I am working a lot and I was trying to find some time to make a new release...
So... the 2.1 release is on the way...
Comment #13
juampynr CreditAttribution: juampynr commentedThanks!
Comment #14
Ronino CreditAttribution: Ronino commentedThank you!