Simple change in error message about jatos

[kristian-lange]

There are several error messages in the component edit page. You mean the
one for the html file path?

On Sat, Nov 29, 2014 at 11:50 PM, elisafilevich [email protected]
wrote:

The error message in the edit component can be a bit confusing. It's a bit
too focused on the path. It would be nice if it could also say something
like: 'make sure that the .html extension is included'

—
Reply to this email directly or view it on GitHub
#45.

[elisafilevich]

Yes, exactly

[kristian-lange]

So what wording would you like. How about:
"Not a valid path. Remember to use '/' as the separator. You can leave it
empty for now."
I can't enforce a file suffix. HTML files might have htm or html suffix or
whatever the user chooses.

On Sun, Nov 30, 2014 at 1:33 AM, elisafilevich [email protected]
wrote:

Yes, exactlyOn So., Nov. 30, 2014 at 12:57 vorm., JATOS/JATOS <
[email protected]> wrote: There are several error messages in the
component edit page. You mean the

one for the html file path?

On Sat, Nov 29, 2014 at 11:50 PM, elisafilevich [email protected]

wrote:

The error message in the edit component can be a bit confusing. It's a
bit

too focused on the path. It would be nice if it could also say something

like: 'make sure that the .html extension is included'

—

Reply to this email directly or view it on GitHub

#45.

—Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
#45 (comment).

[elisafilevich]

How about:

Not a valid path or filename. Remember to use '/' as the separator, and to include the file extension. You can leave it
empty for now.

On 30 Nov 2014, at 19:19, Kristian Lange [email protected] wrote:

So what wording would you like. How about:
"Not a valid path. Remember to use '/' as the separator. You can leave it
empty for now."
I can't enforce a file suffix. HTML files might have htm or html suffix or
whatever the user chooses.

On Sun, Nov 30, 2014 at 1:33 AM, elisafilevich [email protected]
wrote:

Yes, exactlyOn So., Nov. 30, 2014 at 12:57 vorm., JATOS/JATOS <
[email protected]> wrote: There are several error messages in the
component edit page. You mean the

one for the html file path?

On Sat, Nov 29, 2014 at 11:50 PM, elisafilevich [email protected]

wrote:

The error message in the edit component can be a bit confusing. It's a
bit

too focused on the path. It would be nice if it could also say something

like: 'make sure that the .html extension is included'

—

Reply to this email directly or view it on GitHub

#45.

—Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
#45 (comment).

—
Reply to this email directly or view it on GitHub.

[kristian-lange]

Yes, done!

On Sun, Nov 30, 2014 at 8:17 PM, elisafilevich [email protected]
wrote:

How about:

Not a valid path or filename. Remember to use '/' as the separator, and to
include the file extension. You can leave it
empty for now.

On 30 Nov 2014, at 19:19, Kristian Lange [email protected]
wrote:

So what wording would you like. How about:
"Not a valid path. Remember to use '/' as the separator. You can leave
it
empty for now."
I can't enforce a file suffix. HTML files might have htm or html suffix
or
whatever the user chooses.

On Sun, Nov 30, 2014 at 1:33 AM, elisafilevich [email protected]

wrote:

Yes, exactlyOn So., Nov. 30, 2014 at 12:57 vorm., JATOS/JATOS <
[email protected]> wrote: There are several error messages in
the
component edit page. You mean the

one for the html file path?

On Sat, Nov 29, 2014 at 11:50 PM, elisafilevich <
[email protected]>

wrote:

The error message in the edit component can be a bit confusing. It's
a
bit

too focused on the path. It would be nice if it could also say
something

like: 'make sure that the .html extension is included'

—

Reply to this email directly or view it on GitHub

#45.

—Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
#45 (comment).

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
#45 (comment).