Re: [oxid-dev-general] Oxid AJAX Bug?

2011-12-09 Thread Frank Zunderer 
Hello Mitch,

i stumbled into the same error:
https://bugs.oxid-esales.com/view.php?id=3405

There is hope that errors will be shown in next version:
https://bugs.oxid-esales.com/view.php?id=3375

Regards,
Frank Zunderer



> -Ursprüngliche Nachricht-
> Von: dev-general-boun...@lists.oxidforge.org [mailto:dev-general-
> boun...@lists.oxidforge.org] Im Auftrag von Mitch Köhler
> Gesendet: Freitag, 9. Dezember 2011 19:08
> An: dev-general@lists.oxidforge.org
> Betreff: Re: [oxid-dev-general] Oxid AJAX Bug?
> 
> Hello list,
> 
> I found the root of evil.
> It is a line in the details-page's ajax-files:
> [{oxscript add="$( 'ul.js-articleBox' ).oxArticleBox();"}]
> 
> This method has no (included) source-file and will therefore produce an
> error.
> 
> I would really appreciate it, if you don't uncomment console.log()-
> statements that only trigger if an error occurs (as it is currently the
case in
> oxajax.js).
> 
> Best Regards,
> Mitch
> ___
> dev-general mailing list
> dev-general@lists.oxidforge.org
> http://dir.gmane.org/gmane.comp.php.oxid.general

___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general

Re: [oxid-dev-general] Oxid AJAX Bug?

2011-12-09 Thread Mitch Köhler 
Hello list,

I found the root of evil.
It is a line in the details-page's ajax-files:
[{oxscript add="$( 'ul.js-articleBox' ).oxArticleBox();"}]

This method has no (included) source-file and will therefore produce an
error.

I would really appreciate it, if you don't uncomment
console.log()-statements that only trigger if an error occurs (as it is
currently the case in oxajax.js).

Best Regards,
Mitch
___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general

Re: [oxid-dev-general] Oxid AJAX Bug?

2011-12-08 Thread Mitch Köhler 
Just read what I wrote.
The problem is not restricted to the code from example.js, but also
occurs for the alert-statement as shown in my example.
> [{oxscript add="alert('Hello World!');"}]

Kind Regards,
Mitch
___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general

[oxid-dev-general] Oxid AJAX Bug?

2011-12-08 Thread Mitch Köhler 
Hello list,

I got the following JS-code:

(function($, undefined) {
$.widget('Example.example', {
_create: function () {
console.info('hello world!');
},_init: function () {
console.info('hello world!');
},
})
})(jQuery);

As well as
[{oxscript include='js/example/example.js'}]//file for the code above
[{oxscript add="alert('Hello World!');"}]
[{oxscript add="$('#testelement').example();"}]

I included these code-snippets on the details-page. All works fine when
loading the content for the first time. However, as soon as one chooses
a variant of an article, an ajax call is sent to the server. When the
callback arrives, nothing is happening (no call to _create nor _init,
however the oxid internal plugins work as far as I can verify this),
allthough all the neccessary JS-code is part of the server's response.

During investigation I found out that oxArticleVariant() can't be found
in oxajax's eval-method (un-uncomment the console-output), *although*
its functionality is provided and works (i.e. you can go on and choose
another variant, everything works as expected for variant-handling).

Are there any ideas of what might be wrong or is this an unknown bug?
I emphasize that problems only occur when an ajax-call was made.

Kind Regards,
Mitch
___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general