hi Erik
firstly thanks a lot for the fantastic work!
i have a joomla 1.5 install where i installed your component and module, they work smoothly on FireFox but cause the "cannot open the internet site - operation aborted" error on (any) Internet Explorer...
My joomla version is : 1.5.11
And my PHP version is : 5.0.41
And im using : com_communicator_2.0.0 and mod_communicatorsubscribe_2.0.0 Version : 2.0.x
I'm using translation : IT
Additional installed components/modules (incl. version #) : VirtueMart + modules, Joomulus, ARTIO Google Analytics, Custom Footer, Jumi
My homepage is :
http://www.tukulviaggi.it/tukul/the thing that baffles me is that on your fx%Test%.de site (which indeed works on all IEs) you use the Ja Purity template, which is what i've modified to use on my site, so i don't think it's down to a conflict with the template's javascript (those i did not tuch, i've only tweaked the template's html and css to suit my needs).
with the module i've also tried removing the javascript, just to test it, and the error still comes up.
i know under this conditions (same base templates, same modules and scripts, but different browser behaviours) it's nearly impossible for you to pass me a solution, but i wonder if you can give me any hint as to where to look for the problem (html tweaks? conflicts with other modules you have heard?), as the couple of mentions on this forum do not give any...
thanks in advance,
Max
=================
update:
if i create a module using Jumi and paste there the same output code of mod_communicatorsubscribe (copied from viewing the source on FireFox) i don't get the error...
of course it won't work anyway, as when i submit the subscription i get redirected to com_communicator and i get the error, and no new entry gets stored in the subscribers table...
on this page
http://blogs.msdn.com/ie/archive/2008/04/23/what-happened-to-operation-aborted.aspxTravis Leithead (Program Manager of IE8 Object Model) explains that the Internet Explorer error is triggered by an HTML parsing exception that occurs when all the following specific conditions are met:
1. The HTML file is being parsed
2. Script is executing
3. The executing script attempts to add, or remove an element from an unclosed ancestor in the markup tree (not including the script block's immediate parent element).
is anything of the sort happening with either your module or component?
(looking forard to a reply of some sort, i hate the idea of dropping something so nice and simple for what looks the usual IE crap at handling the web...)