Have a look in the ITaaU blog at this post.
See how the metadata is rendered.
Cause is excessive escaping, probably in prop_blog.php line ~116
We will keep this as a known issue.
If we fix it we will break any Trove that already has /'s turned to -'s.
We will address this issue in a future release when we migrate key/value from XML strings to tables.
The / in - has been fixed as URLs can now be handled as metadata values because of the use of URL encoding and decoding on the metadata key-value index pages. Problems with escaping of single quote marks has been dealt with and double quote marks (like angle brackets) are not permitted for metadata values.
Tim: Can you confirm you are happy with this fix on aurora.
Seems to work properly now on Aurora.
Made a new post with an URL as a key value which was stored and rendered and remembered upon edit correctly.
Went back and edited the original test case where '-' had been substituted for '/' and put the '/'s back successfully.
The changes were saved and remembered upon re-edit.
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.