Your are absolutely right in principle. However in this particular case I need the styles to be loaded to the front-end, and not just in the admin area.
The all point is letting people use and apply custom styles trough the WYSIWYG editor so they can be “interpreted” in the front-end to the general public.
If my styles or scripts were only to be used in the admin area, then, admin_init (or eventually admin_head) were indeed the correct hooks to use.
Thanks!
MAC 
Thanks for your warnings.
I’ve updated the code to your suggestions, except for point 1, where I haven’t had the time, yet, to check.
Thanks!
MAC
Nice guide, still i think there are some proablems.
1. the line below is useless, and should be deleted.
add_filter( ‘mce_css’, ‘tdav_css’ );
2. the following line:
wp_enqueue_style( ‘myCustomStyles’, get_bloginfo(‘template_url’).’/mycustomstyles.css’, ”,”’,’all’ );
would work better if changed in:
wp_enqueue_style( ‘myCustomStyles’, get_bloginfo(‘stylesheet_directory’).’/mycustomstyles.css’, ”,”’,’all’ );
3. the following line should be added. it helps make the editor look like the custom css.
add_editor_style(‘mycustomstyles.css’);
Your guide plus my changes worked graite for me. I hope it will help others.
Thx for the guide.
Any idea what I can do to get this working?
Thanks! ]]>
After adding the code to my functions.php file, i get this at the bottom of my editor pages.
Warning: call_user_func_array() expects parameter 1 to be a valid callback, function ‘tdav_css’ not found or invalid function name in C:\xampp\xampplite\htdocs\websites\wordpress\wp-includes\plugin.php on line 170.
Also, all the TinyMCE buttons have disappeared, and the page layout has gone a bit funny and out of place.
What’s gone wrong? ]]>
admin_init
rather than
init
for things that you want to happen only in the Admin area.
Then WP isn’t bothering to load extra code when just displaying a regular page for non-admin.
add_action(‘admin_init’, ‘mycustomStyles’); ]]>
/**/
]]>