Hi,

I have the following problem:

In a content type I have created, I am using a node reference field where the "Node: Title" for each node is presented with HTML symbols intact. For example, where the original node has a title of "Under 9's (Tackers)" the version in the drop down menu becomes "Under 9& # 039 ;s (Tackers)" (the spaces have been added to the html code to make sure drupal.org doesn't try and convert it back to an apostrophe).

The list of Node Titles is fed to node_reference from a view i have created and specified in the "Advanced - Nodes that can be referenced (View)" section of the node_reference configuration page. I am supplying "Node: Title" from the view, filtered on published and parent node ID, in the form of a block with List view. I have checked the view in Page format and the node titles are intact.

The apostrophes are intact in the nodes in the database - the big problem being that when this new content type is written to the node table, the new, fugly, html symbol gets written into the field...

Does anybody know if the handling of embedded HTML symbols is working in cck.node_reference?

Thanks,

BlueSquare.

CommentFileSizeAuthor
#5 noderef.jpg24.45 KBemilyf
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

yched’s picture

Could you check latest CVS from DRUPAL-5 branch (or wait a few hours and grab the 5.x-1.x-dev tarball in http://drupal.org/node/98656)
I committed a change that should fix this.

bluesquare’s picture

Status: Active » Closed (fixed)

Hi,

Downloaded cck-dev and copied to my site. Clicked "save" and I'm now looking at apostrophes.

Thanks!

BlueSquare.

bluesquare’s picture

Status: Closed (fixed) » Active

Hi,

Looks like there are a few issues after the change.

This seems to have stopped one of my views working. This view uses a node reference to determine the node set and visibility. I'm using a combination of techniques described in the forums and found on paul resnick's page. I am using a "Node Reference:" argument and adding;

$args[0] = arg(1);

to the "Argument Handling Code:" section.

I'm then using;

<?
$visible = FALSE;

if (arg(0) == 'node' && is_numeric(arg(1)) {
   $visible = TRUE;
}

return $visible;
?>

in the visibility block for the block generated by the view.

This was working fine before the change. Now I get no blocks generated by this view.

Do I need to be running a particular version of views/cck?

Thanks,

BlueSquare.

yched’s picture

The specific changes I committed to fix the original issue above should have no effects like the one you mention. The affected code is only executed for the noderef widget rendering on the node's edit form.

Maybe this is a side effect of other changes between the version of cck you used and the new 5.x-dev release you updated to.
Could you please specify what version of cck you used to run ?
Also, did you update anything else ? Views module ?
Did you run update.php ?
You could also try re-saving the incriminated view.

emilyf’s picture

Version: 5.x-1.5 » 5.x-1.6-1
FileSize
24.45 KB

This appears to be happening again in the 5.x-1.6-1 release. In the "View" tab, the node reference will display apostrophes correctly, but in the "Edit" tab the select box renders the apostrophe wrong. See attached image for example.

anthonym’s picture

I've got incorrect display of apostrophe's as well using CCK 5.x-1.6-1. And because I'm using token module to create a node title automatically from various fields, including a node reference field, the title contains the the raw html rather than the apostrophe. Any fix for this?

yched’s picture

Status: Active » Fixed

I think we fixed that in current 5.x-1.x. Please reopen if not.

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

james.wilson’s picture

Status: Closed (fixed) » Active

I'm having this same issue, but with version 5.x-1.9 and also using the token module to automatically generate the node title. I'm getting a title that contains the raw html rather than the apostrophe. As I also Pathauto to generate a path, the raw html is also being generated in the path.

jenlampton’s picture

Still an issue for me too, it would be nice if the patch was posted here originally so we could compare to the current version and see what's missing. Does anyone know what the original fix was?

Jen

kenorb’s picture

KarenS’s picture

Status: Active » Closed (won't fix)

The D5 version is no longer being supported. Sorry.