[Building Sakai] new web content tool error

[Cris J Holdorph]

If the new tool is working differently and has less "functionality" then 
the old tool, it does seem like a 'regression' and should have a jira 
created for it.

---- Cris J H

On 07/30/2014 08:55 AM, Adam Marshall wrote:
> I don’t dispute that URL should not contains spaces but the old Web
> Content tool did accept them. I would imagine a good solution would be
> to accept URLs with spaces but translate the space to %20 before storing
> in the DB. The same goes for other disallowed characters.
>
> Our users will go nuts (technical term) if they have to manually
> translate spaces to %20 in order to save a Web Content link.
>
> adam
>
> --
>
> ** Note change of email address to adam.marshall at it.ox.ac.uk
> <mailto:adam.marshall at it.ox.ac.uk> **
>
> Dr A C Marshall, WebLearn Service Manager, University of Oxford.
>
> IT Services, 13 Banbury Rd, Oxford. OX2 6NN.
>
> *From:*Sam Ottenhoff [mailto:ottenhoff at longsight.com]
> *Sent:* 30 July 2014 16:01
> *To:* Adam Marshall
> *Cc:* sakai-dev at collab.sakaiproject.org
> *Subject:* Re: [Building Sakai] new web content tool error
>
> Isn't a space invalid in a URL? http://www.ietf.org/rfc/rfc1738.txt
>
>
>
>
>
>     Characters can be unsafe for a number of reasons.  The space
>
>     character is unsafe because significant spaces may disappear and
>
>     insignificant spaces may be introduced when URLs are transcribed or
>
>     typeset or subjected to the treatment of word-processing programs.
>
>     The characters "<" and ">" are unsafe because they are used as the
>
>     delimiters around URLs in free text; the quote mark (""") is used to
>
>     delimit URLs in some systems.  The character "#" is unsafe and should
>
>     always be encoded because it is used in World Wide Web and in other
>
>     systems to delimit a URL from a fragment/anchor identifier that might
>
>     follow it.  The character "%" is unsafe because it is used for
>
>     encodings of other characters.  Other characters are unsafe because
>
>     gateways and other transport agents are known to sometimes modify
>
>     such characters. These characters are "{", "}", "|", "\", "^", "~",
>
>     "[", "]", and "`".
>
>
>
>     All unsafe characters must always be encoded within a URL.
>
> On Wed, Jul 30, 2014 at 10:52 AM, Adam Marshall
> <adam.marshall at it.ox.ac.uk <mailto:adam.marshall at it.ox.ac.uk>> wrote:
>
> You can't have a target URL that contains a space in the new Web Content
> tool.
>
> Is that deliberate? It's breaking loads of our pages. A blocker.
>
> adam
>
> --
>
> ** Note change of email address to adam.marshall at it.ox.ac.uk
> <mailto:adam.marshall at it.ox.ac.uk> **
>
> Dr A C Marshall, WebLearn Service Manager, University of Oxford.
> IT Services, 13 Banbury Rd, Oxford. OX2 6NN.
>
>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org <mailto:sakai-dev at collab.sakaiproject.org>
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org
> <mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject of
> "unsubscribe"
>
>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>