Mailing List Archive: Bricolage: users

WYSIWYG Issues in 2.0

Index | Next | Previous | View Threaded

mattrolf at me

Jun 1, 2010, 4:36 PM

Post #1 of 5 (764 views)
Permalink

WYSIWYG Issues in 2.0

While poking around Xinha tonight I found out the link functionality in the latest version doesn't work with 2.0. I remember testing it at Denison a *long* time ago, but they don't use the link functionality, so I wouldn't have necessarily spotted the problem. Most other functions appear to work just fine.

FCKeditor didn't work at all for me. I noticed it's now renamed "CKeditor" as well, so it's possible it has gone through some iterations that have broken the compatibility.

JS-Quicktags appears to work like a charm. Sure, it won't give you that WYSIWYG layout that makes you feel all warm and fuzzy. But from what I can tell, it still does its thing without complaint.

I wanted to bring this up to the user list so others with WYSIWYG editors knew what was up in the event of a migration. I also want to solicit user input from those on 2.0 to verify what I've seen and add in anything else that's out there so we can get the right bugs in the bug tracker.

-Matt

fulekia at denison

Jun 7, 2010, 7:26 AM

Post #2 of 5 (704 views)
Permalink

Re: WYSIWYG Issues in 2.0 [In reply to]

Matt,
We're seeing different WYSIWYG failures on pretty much every
browser/OS combo we've tried (using Xinha on bric 2 cloned from our
1.10.9 install). IE8 on Windows XP is the only pair that's actually
working as expected. It could be a problem in our configs, but
Michael has triple-checked them. It looks like this will need some
pretty serious testing to nail down what's up.

Has bric 2 changed how WYSIWYGs are attached to textarea elements?

-Aaron

---------------------------------
Aaron Fuleki
Senior Web Architect
Denison University
740.587.5752
---------------------------------

On Jun 1, 2010, at 7:36 PM, Matthew Rolf wrote:

> While poking around Xinha tonight I found out the link functionality
> in the latest version doesn't work with 2.0. I remember testing it
> at Denison a *long* time ago, but they don't use the link
> functionality, so I wouldn't have necessarily spotted the problem.
> Most other functions appear to work just fine.
>
> FCKeditor didn't work at all for me. I noticed it's now renamed
> "CKeditor" as well, so it's possible it has gone through some
> iterations that have broken the compatibility.
>
> JS-Quicktags appears to work like a charm. Sure, it won't give you
> that WYSIWYG layout that makes you feel all warm and fuzzy. But
> from what I can tell, it still does its thing without complaint.
>
> I wanted to bring this up to the user list so others with WYSIWYG
> editors knew what was up in the event of a migration. I also want
> to solicit user input from those on 2.0 to verify what I've seen and
> add in anything else that's out there so we can get the right bugs
> in the bug tracker.
>
> -Matt

mattrolf at me

Jun 7, 2010, 8:56 AM

Post #3 of 5 (704 views)
Permalink

Re: WYSIWYG Issues in 2.0 [In reply to]

Well, at least you were able to get 1 combination working right. Maybe it would be good to catalog the things you saw on the bugs I opened (179 & 180).

Has bric 2 changed how WYSIWYGs are attached to textarea elements?

Yes. If you take a look at git, you'll see that David had to do some work to get the WYSIWYGs working in 2.0 a year ago. But there have been a lot of commits and browser releases since then.

-Matt

mattrolf at me

Nov 10, 2010, 12:25 PM

Post #4 of 5 (405 views)
Permalink

Re: WYSIWYG Issues in 2.0 [In reply to]

So I did some brief checking on the Xinha issue today, and the problem in regards to the link functionality appears to be a css class name collision. The link box for Xinha has the "dialog" class, and we're using that class in /widgets/dialog_box/dialog_box.mc.

Is that the warning box? If we change that to a new class we should eliminate the problem.

Also, if Denison could further report on the weird behavior's they've been seeing, that would be a great help.

-Matt

On Jun 7, 2010, at 10:26 AM, Aaron Fuleki wrote:

> Matt,
> We're seeing different WYSIWYG failures on pretty much every browser/OS combo we've tried (using Xinha on bric 2 cloned from our 1.10.9 install). IE8 on Windows XP is the only pair that's actually working as expected. It could be a problem in our configs, but Michael has triple-checked them. It looks like this will need some pretty serious testing to nail down what's up.
>
> Has bric 2 changed how WYSIWYGs are attached to textarea elements?
>
> -Aaron
>
> ---------------------------------
> Aaron Fuleki
> Senior Web Architect
> Denison University
> 740.587.5752
> ---------------------------------
>
>
>
> On Jun 1, 2010, at 7:36 PM, Matthew Rolf wrote:
>
>> While poking around Xinha tonight I found out the link functionality in the latest version doesn't work with 2.0. I remember testing it at Denison a *long* time ago, but they don't use the link functionality, so I wouldn't have necessarily spotted the problem. Most other functions appear to work just fine.
>>
>> FCKeditor didn't work at all for me. I noticed it's now renamed "CKeditor" as well, so it's possible it has gone through some iterations that have broken the compatibility.
>>
>> JS-Quicktags appears to work like a charm. Sure, it won't give you that WYSIWYG layout that makes you feel all warm and fuzzy. But from what I can tell, it still does its thing without complaint.
>>
>> I wanted to bring this up to the user list so others with WYSIWYG editors knew what was up in the event of a migration. I also want to solicit user input from those on 2.0 to verify what I've seen and add in anything else that's out there so we can get the right bugs in the bug tracker.
>>
>> -Matt
>

phillip at communitybandwidth

Nov 10, 2010, 1:46 PM

Post #5 of 5 (405 views)
Permalink

Re: WYSIWYG Issues in 2.0 [In reply to]

Maybe add it to this ticket?
http://bricolage.lighthouseapp.com/projects/29601/tickets/179-fckeditor-does-not-work-in-20#ticket-179-2

On 2010-11-10, at 3:25 PM, Matthew Rolf wrote:

> So I did some brief checking on the Xinha issue today, and the problem in regards to the link functionality appears to be a css class name collision. The link box for Xinha has the "dialog" class, and we're using that class in /widgets/dialog_box/dialog_box.mc.
>
> Is that the warning box? If we change that to a new class we should eliminate the problem.
>
> Also, if Denison could further report on the weird behavior's they've been seeing, that would be a great help.
>
> -Matt
>
>
>
> On Jun 7, 2010, at 10:26 AM, Aaron Fuleki wrote:
>
>> Matt,
>> We're seeing different WYSIWYG failures on pretty much every browser/OS combo we've tried (using Xinha on bric 2 cloned from our 1.10.9 install). IE8 on Windows XP is the only pair that's actually working as expected. It could be a problem in our configs, but Michael has triple-checked them. It looks like this will need some pretty serious testing to nail down what's up.
>>
>> Has bric 2 changed how WYSIWYGs are attached to textarea elements?
>>
>> -Aaron
>>
>> ---------------------------------
>> Aaron Fuleki
>> Senior Web Architect
>> Denison University
>> 740.587.5752
>> ---------------------------------
>>
>>
>>
>> On Jun 1, 2010, at 7:36 PM, Matthew Rolf wrote:
>>
>>> While poking around Xinha tonight I found out the link functionality in the latest version doesn't work with 2.0. I remember testing it at Denison a *long* time ago, but they don't use the link functionality, so I wouldn't have necessarily spotted the problem. Most other functions appear to work just fine.
>>>
>>> FCKeditor didn't work at all for me. I noticed it's now renamed "CKeditor" as well, so it's possible it has gone through some iterations that have broken the compatibility.
>>>
>>> JS-Quicktags appears to work like a charm. Sure, it won't give you that WYSIWYG layout that makes you feel all warm and fuzzy. But from what I can tell, it still does its thing without complaint.
>>>
>>> I wanted to bring this up to the user list so others with WYSIWYG editors knew what was up in the event of a migration. I also want to solicit user input from those on 2.0 to verify what I've seen and add in anything else that's out there so we can get the right bugs in the bug tracker.
>>>
>>> -Matt
>>
>

--
Phillip Smith // Simplifier of Technology // COMMUNITY BANDWIDTH
www.communitybandwidth.ca // www.phillipadsmith.com

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads