Download & Extend

RDFa setting breaks json output of some modules and ahah functionality of cck buttons

Project:Resource Description Framework (RDF)
Version:6.x-1.x-dev
Component:Settings
Category:bug report
Priority:normal
Assigned:Unassigned
Status:needs review
Issue tags:HTTP error 0, RDF, RDFa

Issue Summary

When uploading a file with the core upload module, the error An Http error 0 occured occurs. Browsing to upload/js returns:

{ "status": true, "data": "\x3cdiv class=\"messages error\"\x3e\nValidation error, please try again. If this error persists, please contact the site administrator.\x3c/div\x3e\n" }
      xmlns:dc="http://purl.org/dc/elements/1.1/"
      xmlns:foaf="http://xmlns.com/foaf/0.1/"
      xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">

which shows here the RDFa markup being added to the json response.

Turning off the setting Output an XHTML+RDFa DOCTYPE solves the problem.

Comments

#1

Title:RDFa settings breaks the upload module» RDFa setting breaks json output of some modules

marked #478884: Administration menu disappears as duplicate.

#2

I can confirm the problem.

Maybe it would be better to only use a replace strategy in _rdf_ob_handler() than the current remove and insert approach?

#3

this might be related but this doesn't work

test.php

<?php
require_once './includes/bootstrap.inc';
drupal_bootstrap(DRUPAL_BOOTSTRAP_FULL);
echo
"Test";
exit;
?>

Test is not outputted.

#4

above error happens when "Output an XHTML+RDFa DOCTYPE: " is enabled.

#5

This is also breaking the installation of Open Atrium. I am not sure it is for the same reason but it might.

#6

The issue #434394: 'HTTP error 0 occurred' on image upload might be related to this since fieldfield breaks when RDFa is enabled.

#7

Title:RDFa setting breaks json output of some modules» RDFa setting breaks json output of some modules and ahah functionality of cck buttons

Enabling RDFa is also breaking the AHAH functionality of CCK's 'add more items' button for me, at least with the modules that I have enabled.

I have added this to the title of the issue so people may find it more easily.

#8

where is this setting?
Turning off the setting Output an XHTML+RDFa DOCTYPE solves the problem.

#9

browse to admin/settings/rdf (Administer › Site configuration > RDF settings) and open the RDFa fieldset.

#10

When I enable rdf, I get WSOD

Fatal error: Call to undefined function ctools_include() in /sites/all/modules/contrib/purl/purl.module on line 631

#11

SocialNicheGuru, that is probably a different issue than the one here. This one is specifically related to javascript functionality and the Output RDFa setting of RDF module.

#12

@SocialNicheGuro you probably updated to the latest version of Purl and didn't read the instructions, Purl is now dependent from Ctools, and you probably don't have it installed. As @linclark said, that's a different issue than the one here.

#13

no, i have ctools installed and it works fine. It only gives me WSOD when I install RDF.

edit- i get no WSOD with an upgrade

#14

Status:active» needs review

I am using RDFa with FileField and was having the same problem. I created a small patch that should fix it for the FileField and the Add another item buttons.

After applying the patch, try enabling the Output an XHTML+RDFa DOCTYPE.

AttachmentSize
476280.patch 476 bytes

#15

I added an extra argument condition arg(1) != 'js', for the core upload.module, which has a menu callback for upload/js.

AttachmentSize
476280.patch 561 bytes

#16

Simply confirming this bug – I get an error on CCK 'Add another item' button (among other things) after enabling RDFa.

#17

Also confirming Filefield + RDF issue. With diff version of jQuery it fails differently, but still fails. Broken JSON data seems to be the problem

#18

Does it fail with the patch in #15?

#19

@vkareh: tnx for the patch!

solved the problem and saved my day :)

#20

The patch in comment 15 definitely fixes the problem, and makes perfect sense -- there's no need to use output buffering to add the RDFa headers on a javascript request. (For the record, this is *one* of the many causes of the infamous HTTP error 0!)

Any reason this patch can't be incorporated into RDF?