Promted text
After updating curlypage to version 3,3 there was one error. There is it at loading curlypage if to press to "continue" there is a second error. Screenshots of both errors are in attache.
This error repeats on different browsers. What is it? the Problem with Adobe Flash? Or a curlypage?
By the way, the same error arises on a site http://www.curlypage.co.cc/

Original text
После обновления curlypage до версии 3,3 возникла одна ошибка. Возникает она при загрузке curlypage, если нажать "продолжить" возникает вторая ошибка. Скриншоты обоих ошибок находятся в аттаче.
Эта ошибка повторяется на разных браузерах. Что это? Проблема с флешем? Или магическим уголком?
Кстати, эта же ошибка возникает на сайте http://www.curlypage.co.cc/

CommentFileSizeAuthor
Adobe_error_2.png3.96 KBalexeyal1
Adobe_error_1.png3.93 KBalexeyal1

Comments

manfer’s picture

Status: Active » Postponed (maintainer needs more info)

This is really strange, I have done a test on homepage http://www.curlypage.co.cc just now.

Firefox, Safari, IE and Chrome tested and on different OS, Windows Vista, Windows 7, Linux, OS X Snow Leopard. None of them has triggered those errors.

I even thinked of flash player configuration, I went into the adobe flash player admin panel and still didn't see any different config that could trigger the error.

The error is related with new code in action script 3 that is used by curlypage_clicks submodule instead of the previously used javascript code. But in the homepage curlypage_clicks is not being used and those functions on the code should not run at all. So even with an error on code (none that I can see yet) it should not be triggered at all.

I will continue looking for those two errors.

Thanks for the report.

manfer’s picture

Could you please test now the homepage http://www.curlypage.co.cc and report if same errors still triggering?

alexeyal1’s picture

I'm update flash player on http://www.adobe.com/products/flashplayer/ error gone.

manfer’s picture

It is a pity you didnt have the oportunity to test the homepage before the update.

It is posible that error comes from a bug in one version of FP10 that does not catch an IOError and I could know if the change I had made on code was enough to prevent that error from triggering.

Anyway I will include the change on code in next release and I'm going to try to include error handling too.

Thanks for the report.

alexeyal1’s picture

Promted text
I tested page for errors before updating and after, but only on the site http://millerovo.net/
After updating there was an error, and I have started to search, than it can be caused. At first has visited your site, and having come across the same error has written this message, in a consequence testing Curlypage in various browsers, I have started to update flash player. And it has helped...
Therefore I can unequivocally tell, that the error has arisen right after updatings Curlypage.

Original text
Я тестировал страницу на ошибки до обновления и после, но только на своем сайте http://millerovo.net/
После обновления возникла ошибка, и я начал искать, чем она может быть вызвана. Сначала посетил ваш сайт, и наткнувшись на ту же ошибку написал это сообщение, в последствии тестируя Curlypage в различных браузерах, я начал обновлять flash player. И это помогло...
Поэтому я могу однозначно сказать, что ошибка возникла сразу после обновления Curlypage.

manfer’s picture

Yes the error that is triggered is because of new AS3 code in curlypage 3.3 (URLVariables objects are not used until this version) but I made a little change to it and installed on homepage to test if that was enough to resolve that error.

That was why I wanted you to test again http://www.curlypage.co.cc with same flash player 10.x.x.x version. :)

For what I read about 2101 AS3 runtime error it should not appear on a code like the one in curlypage but it appears in some versions of FP10 that does not catch an error that should catch. What I'm confuse is why was triggered on homepage where the functions that include that URLVariables local objects should never run because that website is not using curlypage tracking at all.

Anyway I would try to include in next release runtime error handling in AS3 code to try to minimize this posible errors.

I don't know in what versions of FP10 the error appears but runtime error handling should resolve the issue even for FP10 versions with that problem.

manfer’s picture

Status: Postponed (maintainer needs more info) » Fixed

Error handling added to AS3 code in version 6.x-3.4. Besides, the code that triggers that error (which flash player 9 and most flash player 10 versions should be able to handled silently anyway with no effect on curlypage), has been changed.

So I set this to fixed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.