Hi guys can you make Internet Explorer more compatiable with Wiccle Software since more then half the Users on the Net use it.

WIccle does NOT like Internet Explorer :(

Even Youtube does not show up on Internet Explorer browsers inside wiccle

Most of my friends who will sign up once wiccle is ready to use on a live wiccle site will leave if they see errors at bottom of page , the error is  "object required" on all pages of wiccle software :(

firefox does not give errors

I have not tried opera and chrome

maybe someone else can try

I intend to do a full IE specific debug, both with 7 and 8, and with Smart URLs on and off. In the meantime, if you have any specific problem reports, please feel free to indulge.

The alert you see at the bottom is a harmless javascript warning over an undefined variable in some admin-specific builder functions. I'll fix it for the next update.

thanks for addressing the fix in the next relaease that comes

I expect we'll have version 1.11 as a minor update out in a couple of days time, say a week at the most, containing fixes to the issues we've encountered post 1.10 release (keep those reports coming) --- and I hope also the language pack support, which unfortunately didn't go in yet.

ok so the next release 1.1.1 will be more updates on the fixxes that we have discussed with Internet Explorer also languages as you mentioned.

Since you will be working with the cross browser situation all the stuff you have told me to do will be fixxed in the next update sometime next week ?

------------------

edited ....

We won't upgrade the version number over this, because when 1.11 comes (whenever it becomes relevant), it'll have more fixes. There will be a full IE support patch available tomorrow. I'll update the full download zip and also provide a quick fix file with the changed files. We do need to have it (7 & 8) fully supported.

Marcus wrote:

full support patch available tomorrow. I'll update the full download zip and also provide a quick fix file with the changed files.

 Now the question is are we gonna upgrade the number in this version to 1.10A since its a full patch for IE.

Well the A would usually indicate Alpha...

While we're at it, and as I have a bit of spare time today, I'm also going to include language pack support (for Iggy and other non-English-project folks) and some minor tweaks, and just call it 1.11. Coming up sometime after midnight Euro time.

so from what I see now is the final version will not be 1.11 correct ?

A minor update addressing a few things, and it is enough to be now called 1.11 when the update is done.

Oh Markus! Language packs! 

I'm putting iWiccle 1.1 under a lot of test routines here and I'm really impressed with it. It's a beautifull work all of you've done.

There's some little buggy things and other things I think could be made better along the way, but I'll collect my ideas first to make a more significative review.

For now, thanks a lot.

Yes, I really wanted to have them in, but just ran out of time with 1.10. Great to hear it's working for you! Do keep track of all the little quirks you come across (though only after this release is up), we want to get them all fixed.

Hi I am very impressed with the kit and adapting it well, I have a couple of conccerns though, I have found that when you try and bring the login box up it will not in IE8 and Chrome, is there some reason for this, even after I have installed the latest version.

I have also noticed the small error appearing on the bottom right corner.

Any plan on resolving these issues?

Other than that it's a fantastic piece of kit.

Hi atrades and welcome onboard!

It's all coming up fixed with iWiccle 1.11. Release was meant to be done already this morning, but I had to divert to some Wiccle presales related sites --- we need income too --- but it's being wrapped up now.

What's the bug with Chrome though? Can you repeat it and tell me what steps lead to the problem? (Or mail me a link where I can test it.)

www.intofitness.co.uk

This error called "Object Required" is caused by this bit of code:

    if (IE) { // grab the x-y pos.s if browser is IE
        tempX = event.clientX + document.body.scrollLeft;
        tempY = event.clientY + document.body.scrollTop;
    }

Now, what makes this patently humorous is that the missing object is actually "document.body", which should be provided by the browser itself! IE is, then, effectively reporting that it forgot all about the document.body element... I used to get this error on average every 8th pageload or so --- 7 out of 8 were "no errors", 1/8 produced "object missing". The current fix validates whether document.body is defined or not (!), and if not, just sets the scroll value to zero. Curious enough, IE still seems to find and understand document.body.scrollTop without problems... 

With their sub-standard but market-leader browser series (IE8 is the first decent browser as far as standards go), Microsoft costs the world in the hundreds of millions of dollars in added developer costs, just because it can't behave like the rest and requires all sorts of extraordinary hacks to work properly. We developers are the ones who suffer hands-on, they CEOs are the ones who suffer with up to 20% added expense, and you end-users are the ones who suffer with the add in the price tag.

If it were a possibility to skip IE < 8 altogether, the time spent doing HTML and CSS work would reduce dramatically. If you spend 8 hours doing standards-compliant HTML+CSS that displays exactly as it ought to on a standards-compliant browser, you can easily spend another 2 hours hacking and fixing it to display (and function, pray tell, if you also used javascript) right on IE. I don't even want to imagine how iWiccle may look like on IE6 right now (I should dust off my old laptop and see!), I am only too glad to have it working right with IE7 now.