no toolbar images on IE6 PLEEEAAAASE

thanks for trying, but right now my IE is wide open, with the lowest possible security settings - everything is enabled, so no alerts, no prompts - a hackers paradise. still no toolbar.

i've also cleared the cache many times.

do you know if the developers monitor this forum? i can't imagine they're not aware of this problem.

yeah...i love firefox too...and i wish IE would just magically vanish, but the project i'm working on has to work in IE...

looks like I'll have to use TinyMCE or something...

i gave up. i've tried it on 3 different computers, all with pretty standard configs, and it didn't work on any of them. i'll keep monitoring this forum in case somebody has a solution, but judging by the fact that this problem has been reported by many users for the last 8 months or so without any word, i'm not too optimistic. it just seems a bit strange to me, and unfortunately i just don't have time to debug the code.

also, i didn't save any of the links because i didn't find any useful information - just the same questions asked over and over again with no answers. but try a forum search for "toolbar", or "toolbar AND ie", you'll see what i mean.

well, in 15 minutes with tinymce i made more progress than 5 hours of struggling with fck (kinda makes me wonder what fck stands for). i don't want to start a flame war or anything, but tinymce just seems much better put together. clean hooks for customization, and full, well-organized documentation. unless i'm missing something, it just seems like a more modern top-down design. maybe a few less features than fck, but the design is clean and accessible enough that i can write stuff myself if i need it, without worrying too much about breaking anything - the fck code seemed a bit spaghetti-ish. most importantly, tinymce works in the most current version of the most popular browser.

i also discovered that the html source button in fck crashes firefox...hmmm...i'm running...

do you (or anybody, really) have experience with tinymce or others? why do you like fck? like i said, maybe i'm missing something...

if the developers are listening, and care to investigate these problems, i'll be happy to provide whatever info they might want - they're easily reproducible.

as far as the multiple browser thing goes...it doesn't really matter much, as long as browsers adhere to recommended standards...IE fails miserably on that...

take care.

hey, i really appreciate your great attitude, and sorry if i was a bit snotty in my last message - in my heart i truly appreciate all the work that folks put into open source projects, and i give back when i can - in the form of feedback, and code every once in a while...it can just get a bit frustrating sometimes, especially when you're on a tight deadline....and after i sent that last message i realized that the fck were inits...but you have to admit it sounds a bit similar to something else fcked(itor), but maybe it's just me...or maybe fred is really having a laugh on all of us...

where's the comparison that david mcnab posted? did you mean to show a link? i'd be interested in this.

also, the ff crashing thing is actually a known problem, and appears to be a ff bug, and is being discussed on the mozilla forums (https://bugzilla.mozilla.org/show_bug.cgi?id=291183)...so i won't let my setup take the blame on this one

i tried everything i found in the forums, but what i always come back to before i go too far with trying to rig a working toolbar from scratch is that i want the samples to work...a psychological comfort zone...i'm just baffled that 3 computers with really straightforward xp setups won't display the samples...it just makes me nervous about stability - especially knowing that i'll be rolling out a wysiwyg editor system to a bunch of users whose systems i can't control...

maybe 8 is not a big number out of thousands (and i think there were actually more), but i hope you agree that a problem like this really should be addressed in some way by the developers - so it made me nervous that there was no developer follow up on any of the reports of this problem...IE, love it or hate it, but we're all stuck with it for the moment.

and yeah implementation can't be ignored with standards, etc, but as you said, the result will always be 6...from a user perspective the implementation doesn't much matter...imps are for developers to worry about when they go to write extensions, apps, plugins, etc...

err, i didn't come through with the details of my setup, because err err, my invitation wasn't accepted by the developers, but as OS goes round and round sometimes because of enthusiastic users, here's what i'm working with:

setup 1: IE 6.0.2900.2180.xpsp_sp2_gdr.050301-1519
(funny, same as yours - have you tried loading pages from a local hard drive?)
setup 2: IE 6.0.2600.0000.xpclient.010817-1148
setup 3: IE 6.0.2800.1106.xpsp1.020828-1920

no toolbar with any of the samples, and no toolbar when creating a page with one only a few toolbar buttons included. i could dig deeper to see if i can get any toolbar buttons to display, but i've tried all the permutations that i have time for right now.

one of the requirements of the project i'm working on is no-server-interaction, it will all be run locally. my suspicion is that something gets out of whack with the setting of the base path when run locally. because it works fine in ff, i'm thinking that IE deals with file locations differently...just a guess...

see ya...

yep. the right click is disabled - no context menu at all when right-clicking on the buttons. the tooltips for the buttons work, and the actual buttons appear to work as expected when left-clicked.

my guess is that the line like:
"var sBasePath = document.location.pathname.substring(0,document.location.pathname.lastIndexOf('_samples')) ;"

in the sample files, is returning a path that gets munged somewhere in the code when the image path for the toolabr buttons is calculated..

i threw in a javascript alert to check the paths generated by FF and IE, and they do, in fact, differ. FF shows all forward slashes, and IE uses backslashes - with the exception that IE shows a path that looks like:

/C:\aFolder\anotherFolder\theRootFolder

notice the leading forward slash.

does this ring any bells for anybody? is this barking up the right tree?

i guess i could try stripping that leading '/' to see if it makes a difference...but i ran out of steam (and time)...and my basic javascript is pretty weak, except when it comes to the DOM and the XMLHttpObject...

thanks for the link, and thanks for all of your help. the comparison was pretty helpful, and confirmed some of my personal findings - and now that IE and FCK are playing nicely together for me, it looks like i'll go back to my original gut plan to use FCK for the project that i'm working on.

just goes to show how much of a difference a community can make.

thanks.

that fixed it! thank you, thank you, thank you!

i don't know what else to say...thank you. nice job.