Wywsiwyg broken after packages upgrade

Squiz Matrix Support
1

I recently upgraded our premium packages to 3.10.3, which consequently my have broken our wysiwyg editor. However, I am unsure why this has happened as we don't have any custom plugins installed.


I get 8 'FIXME: Unknown toolbar item: undefined' alert boxes when i attempt to access simple edit mode.



Any help will be appreciated. Otherwise, I may have to rollback to 3.10.1 packages.



thanks



aleks

2

just confirmed that wysiwyg editor does work properly in _admin mode, just not in _edit mode

3

looks like my ajax addon to the simple edit interface is causing the problem :frowning:

4

[quote]looks like my ajax addon to the simple edit interface is causing the problem :frowning:
[right][post=“14099”]<{POST_SNAPBACK}>[/post][/right][/quote]



Ooh… aside from the fact that its causing issues, could you tell us more about this addon?

5

Looks like the prototype class of the leightbox ajax script (a lighter modified version of ParticleTree's lightbox) I used was clashing with the HTMLarea.prototype functions in fugde/wysiwyg/core/core.js


I'm using the leightbox script to show/hide contextual help in the simple edit interface.

6

[quote]Looks like the prototype class of the leightbox ajax script (a lighter modified version of ParticleTree's lightbox) I used was clashing with the HTMLarea.prototype functions in fugde/wysiwyg/core/core.js


I'm using the leightbox script to show/hide contextual help in the simple edit interface.[/quote]



Hi, I'm increasingly pushing our websites here towards decent cross browser JavaScript and one of the ways we're doing this is to use the poular mootools JavaScript framework. Unfortunately, this brings up the same problem as aleks was having - prototype is defined in mootools, so it prevents the /_edit interface from working. We're still on 3.10, so I realise this may be an issue that has been resolved but is there any way around this?



Thanks,

Adam

7

[quote]Hi, I'm increasingly pushing our websites here towards decent cross browser JavaScript and one of the ways we're doing this is to use the poular mootools JavaScript framework. Unfortunately, this brings up the same problem as aleks was having - prototype is defined in mootools, so it prevents the /_edit interface from working. We're still on 3.10, so I realise this may be an issue that has been resolved but is there any way around this?


Thanks,

Adam[/quote]



Just a tip for anyone adding additional js packages like mootools and having trouble. Use the following in the head of your parse file.

[codebox]<MySource_AREA id_name="logged_in" design_area="show_if">

<MySource_SET name="condition" value="logged_in" />

<MySource_THEN></MySource_THEN>

<MySource_ELSE><script type="text/javascript" src="mysource_files/mootools-release-1.11.js"></script>

<script type="text/javascript" src="mysource_files/slimbox.js"></script>

</MySource_ELSE>

</MySource_AREA>

[/codebox]



Its simple and allows you to edit pages using the simple edit interface. The only problem is that viewing pages while logged in will disable the javascript code.

8

Use "simple_edit_mode" as the condition instead. :)