Comments on: SPAW2+Firefox+HTTPS Quick Fix http://blog.solmetra.com/2007/02/27/spaw2firefoxhttps-quick-fix/ Events in the lives of developers Tue, 2 Dec 2008 08:15:42 +0000 http://wordpress.org/?v=2.0.4 by: php cart http://blog.solmetra.com/2007/02/27/spaw2firefoxhttps-quick-fix/#comment-363 Sat, 19 Jul 2008 04:36:41 +0000 http://blog.solmetra.com/2007/02/27/spaw2firefoxhttps-quick-fix/#comment-363 Firefox 3.0 is now out and those bugs are now fixed. :) Firefox 3.0 is now out and those bugs are now fixed. :)

]]> by: ailon http://blog.solmetra.com/2007/02/27/spaw2firefoxhttps-quick-fix/#comment-104 Sat, 24 Mar 2007 18:52:42 +0000 http://blog.solmetra.com/2007/02/27/spaw2firefoxhttps-quick-fix/#comment-104 Use stripslashes() on the server. This is not related neither to firefox nor to this bug or anything at all. It's your php setting Use stripslashes() on the server. This is not related neither to firefox nor to this bug or anything at all. It’s your php setting

]]> by: Kirill http://blog.solmetra.com/2007/02/27/spaw2firefoxhttps-quick-fix/#comment-103 Sat, 24 Mar 2007 17:49:02 +0000 http://blog.solmetra.com/2007/02/27/spaw2firefoxhttps-quick-fix/#comment-103 Very strange bug - in Mozilla Firefox 2.0.0.3 SPAW send text but not send html tags: editor engine save back-slashes near quotation marks. Very strange bug - in Mozilla Firefox 2.0.0.3 SPAW send text but not send html tags: editor engine save back-slashes near quotation marks.

]]> by: Derk http://blog.solmetra.com/2007/02/27/spaw2firefoxhttps-quick-fix/#comment-87 Sat, 03 Mar 2007 15:00:23 +0000 http://blog.solmetra.com/2007/02/27/spaw2firefoxhttps-quick-fix/#comment-87 Nevermind, I just upgraded:D thnx anyway Nevermind, I just upgraded:D thnx anyway

]]> by: ailon http://blog.solmetra.com/2007/02/27/spaw2firefoxhttps-quick-fix/#comment-86 Sat, 03 Mar 2007 14:39:13 +0000 http://blog.solmetra.com/2007/02/27/spaw2firefoxhttps-quick-fix/#comment-86 I will send you my thoughts about this via email. Also there was a thread in the forum with someone posting a workaround. I will send you my thoughts about this via email. Also there was a thread in the forum with someone posting a workaround.

]]> by: Derk http://blog.solmetra.com/2007/02/27/spaw2firefoxhttps-quick-fix/#comment-84 Sat, 03 Mar 2007 14:27:10 +0000 http://blog.solmetra.com/2007/02/27/spaw2firefoxhttps-quick-fix/#comment-84 I have this bug also in v.1, I don't want to upgrade because it works good except the ssl bug and I have to change everthing again in oscommerce. Is there also a workaround for v.1? regards I have this bug also in v.1, I don’t want to upgrade because it works good except the ssl bug and I have to change everthing again in oscommerce. Is there also a workaround for v.1?

regards

]]> by: ailon http://blog.solmetra.com/2007/02/27/spaw2firefoxhttps-quick-fix/#comment-83 Wed, 28 Feb 2007 07:28:50 +0000 http://blog.solmetra.com/2007/02/27/spaw2firefoxhttps-quick-fix/#comment-83 Hmm.. that's strange. Have you cleaned your cache, restared browser, etc. after applying the patch? I think it would be better to move this discussion to the forum http://forums.solmetra.com/viewtopic.php?t=2042&start=45 Hmm.. that’s strange. Have you cleaned your cache, restared browser, etc. after applying the patch?

I think it would be better to move this discussion to the forum
http://forums.solmetra.com/viewtopic.php?t=2042&start=45

]]> by: Jeff http://blog.solmetra.com/2007/02/27/spaw2firefoxhttps-quick-fix/#comment-82 Wed, 28 Feb 2007 01:20:15 +0000 http://blog.solmetra.com/2007/02/27/spaw2firefoxhttps-quick-fix/#comment-82 Thanks for being on top of this. Just a heads-up that I don't think the issue is entirely resolved. I've applied the patch to our SPAW instance and although our data fields render w/o any problems on Safari (no wysiwyg of course), they come up blank in Firefox when the server is running HTTPS, HTTP is fine. We're instantiating the wysiwyg as follows: $sw = new SPAW_Wysiwyg('generalnews_e' /*name*/, $overallStatus /*value*/, 'en' /*language*/, 'mini' /*toolbar mode*/, '' /*theme*/, '325px' /*width*/, '50px' /*height*/); $sw->show(); Jeff Thanks for being on top of this. Just a heads-up that I don’t think the issue is entirely resolved. I’ve applied the patch to our SPAW instance and although our data fields render w/o any problems on Safari (no wysiwyg of course), they come up blank in Firefox when the server is running HTTPS, HTTP is fine. We’re instantiating the wysiwyg as follows:

$sw = new SPAW_Wysiwyg(’generalnews_e’ /*name*/, $overallStatus /*value*/,
‘en’ /*language*/, ‘mini’ /*toolbar mode*/, ‘’ /*theme*/, ‘325px’ /*width*/, ‘50px’ /*height*/);
$sw->show();

Jeff

]]>