Thanks, I've pushed the change.
Will try the text too long exception again today.
Regards,
Andriy
2016-04-21 4:07 GMT-04:00 Daniel Naber :
> On 2016-04-20 19:21, Andriy Rysin wrote:
>
>> I would argue that no matter when and how often it happens stack trace
>> is only useful for the site admin,
On 2016-04-20 19:21, Andriy Rysin wrote:
> I would argue that no matter when and how often it happens stack trace
> is only useful for the site admin, who can see the trace in the log
> anyway, for the thousands of the web-page users stack trace is not
> interesting (if not discouraging). Also the
I would argue that no matter when and how often it happens stack trace
is only useful for the site admin, who can see the trace in the log
anyway, for the thousands of the web-page users stack trace is not
interesting (if not discouraging). Also the stack trace may reveal
problems with site setup w
On 2016-04-20 17:48, Andriy Rysin wrote:
> Can I also suggest we make 500 message more user-friendly? E.g. with
> something like this
The common causes for 500 errors should all already have a friendly
error message. Something like ClassNotFound seems uncommon and should
only happen when settin
Cool, I've added error field in red like this:
And it now warns users (and me) if something is wrong and text hasn't
actually been checked.
Can I also suggest we make 500 message more user-friendly? E.g. with
something like this
diff --git
a/languagetool-server/src/main/java/org/languagetool/
On 2016-04-20 16:44, Andriy Rysin wrote:
> 4) if I submit a check via the web-page (directly to API, no proxy)
> there's no messages and text shows up as no errors
I see now - please add to your
page, it should display the error.
Regards
Daniel
-
Thanks David
I've adjusted --allow-origin and it works fine now.
The original problem is still there though:
1) remove server dependency jar (e.g. morfologik-tools.jar) and
restart the server
2) submit a request to the server
3) if I do it with dev tool I see the stack trace
(java.lang.NoClassDe
On 2016-04-20 15:02, Andriy Rysin wrote:
> this works if I point to https://languagetool.org/api/v1/, but I was
> not able to run with direct API pointing to the server running locally
> on my machine. I've added --public and it listens on *:8081 but it
> never returns a request.
> Is there some o
Thanks Daniel
this works if I point to https://languagetool.org/api/v1/, but I was
not able to run with direct API pointing to the server running locally
on my machine. I've added --public and it listens on *:8081 but it
never returns a request.
Is there some other config options I need to turn on
On 2016-04-18 21:25, Daniel Naber wrote:
> So you're using proxy.php, aren't you? Very soon (hopefully tomorrow)
> I'll update the documentation anyway, as the proxy.php isn't needed
> anymore as long as the server gets started with the proper parameters.
Done, everyone can now integrate LT on th
On 2016-04-18 21:11, Andriy Rysin wrote:
> I followed http://wiki.languagetool.org/integration-on-websites,
> although I set it up long time ago so my steps may have been slightly
> different.
So you're using proxy.php, aren't you? Very soon (hopefully tomorrow)
I'll update the documentation any
I followed http://wiki.languagetool.org/integration-on-websites,
although I set it up long time ago so my steps may have been slightly
different.
I don't have a URL that does not work, it works perfectly when it's
configured right (e.g. at http://r2u.org.ua/check).
The simplest scenario is when I u
On 2016-04-18 19:58, Andriy Rysin wrote:
Hi Andriy,
> I noticed that when I integrate LT on the website and some internal
> error occurs (e.g. missing jars, out of memory etc) there's no
> notification to the user and it comes back like text does not have any
> errors.
how exactly do you integra
I noticed that when I integrate LT on the website and some internal
error occurs (e.g. missing jars, out of memory etc) there's no
notification to the user and it comes back like text does not have any
errors.
Is it just for me and I need to adjust something or is it a behavior
we could improve?
14 matches
Mail list logo
