Hello Lee

Following your tutorial regarding the FCK editor I have sucessfully used my own customised styles using my skin.css and incorporating the required styles in the fckstyles.xml file.

I have recently upgraded my FCKEditor to the latest version 01.00.07 and found that the dropdown styles menu was blank.

I created my own customised mystyles.xml file and mystyles.css file and uploaded them to the server.

Within the editor I have selected the following options:

Setting type:  Portal 

Style list generation mode:  Dynamic

Custom XML file:  file on site  =  mystyle.xml 

Editor General mode:  Dynamic 

Custom css file:  file on site  =  mystyle.css

Apply: Portal

But nothing happened, the styles did not reappear, the styles menu remained blank.

I have today sucessfully upgraded my DNN from v 4.3.5 to v 4.3.7.

Refreshed the page and editor

I reapplied the styles as above although the menu is now showing styles taken from my own skin.css instead of my custom style sheet as intended.  However, attached to each style is a SPAN element which has since appeared. 

Consequently all my styles from the skin.css or mystyles.css is not working and my site looks like it is having a bad hair day.

My menu bar relies on the styles from my custom style sheet and it is essential that they are made available, at the moment my site is useless, as I have no navigation bar.

What must I do in order to either:

 sucessfully upload and use my own custom styles 

or remove all the extra SPAN elements which have suddenly appeared on the FCKsyle menu and go back to using  the styles from my own skin?

Thanks.

Lynn

Hello

I now have the solution to the customs style problem.

I had previously set my style mode to Dynamic and I tried the URL mode with DNN 4.3.5 and found the neither of the style modes worked.

However, in 4.3.7 I have found that by selecting URL as the style mode and pointing to my custom xml and css files, housed in my site root, it works fine.

BTW the unwanted extra SPAN elements have also gone.

Panic over,  I now have my menu back.

I hope this solution helps someone else.

Lynn

Thanks Lynn,

Looks like I need to have a look at the new version of the FCKEditor. I will add it to the tutorials list, thanks,

Hi Lee

I will look forward to watching your updated FCKEditor tutorial.

BTW My problem of missing custom styles keeps re-occuring, it seems that currently the FCKEditor v 07 is not very stable with DNN 4.3.7 .

Suggestions from Boskone from FCKeditor:

"I have found that the URL control is not working as expected. If you make any other changes on the editor options page, re-select both the styles and css files again before applying changes."

"I am still trying to find out why this broke between versions. It should work but it one of those:They're not bugs...it's either un-defined features or exceptions to expected behaviour!!"

At the moment  I am finding myself in a hit and miss situation at to wether I can assign my custom styles or not.  Which is a big problem for me as my menu needs my custom css styles to work. 

However, I think I might have a solution, not perfect, but so far seems to work. Within my skin.css files I have my custom styles which is mirrored in  mycustomstyles.css and associated with mycustomstyles.xml files, housed in a specified folder within my site root.  I am now able to apply styles manually as the dropdown styles menu does not always display custom styles .

 However, I need to have the full list of style classes to hand in order to correctly insert classes.   I am not sure how anybody else has managed to overcome this problem as I have not seen any other posts expressing similar difficulties.  Or perhaps it is just me.

Thanks

Lynn

Hi Lynn,

If the previous version worked without any problems, it may be worth switching back to the old version.

I tend to hold back for at least a month before using a new release on a critcal site. This gives them time to iron out any new bugs.

I will probably wait for a couple of months before doing the tutorial just to see if they release any point  fixes.

Thanks,