Thanks Howard, the hint really helped.
I've double checkes page initialization and immediately found the problem:
for non-Russian locales template logic were hiding one form which was
referred from addInit ().
Shoudln't be there any kind of console error in such a case?
On Sun, Mar 21, 2010 at 5
I suspect you have some other JavaScript error on your page that is
keeping Tapestry from initializing correctly. Use FireBug and debug
it.
I know you're thinking that's a cop out and it should just work ...
but experience has shown that when things don't work for one user that
do work for other
Any ideas yet?
On Fri, Mar 19, 2010 at 12:30 AM, Ilya Obshadko wrote:
> No, the problem is that I don't see any request on the server side.
>
> No request is being sent at all. After clicking on linksubmit component it
> calls waitForPage() which is handling form submit event.
> Then, inside this
No, the problem is that I don't see any request on the server side.
No request is being sent at all. After clicking on linksubmit component it
calls waitForPage() which is handling form submit event.
Then, inside this function, it terminates right after checking whether
Tapestry.pageLoaded is true
Do you see the request on the server side? I.e., use FireBug Net
panel to see what request is being sent, what response is coming down.
There shouldn't be any difference between normal and localized pages.
Is it possible that some intermediate server is mangling the query
path in some way?
On T
I have a very strange blocker bug: linksubmit component doesn't work at all
on localized pages.
I have an AJAX form in a sidebar that processes user login and logout.
Basically I'm on 5.1.0.5, but I am using LinkSubmit code from 5.1.0.6 (with
a bugfix for working in zone-based forms).
To make it
