WYSIWYG Editors Fail to Display Styled Text

[jlkane]

I can't coax either TinyMCE or MicroTiny to show the effect of a selected Design or any of its attached stylesheets. The result is shown in these screenshots:

Calendar page (typical rendered page):
http://simply-effective.com/WGR/calendar.html

How the content looks in TinyMCE:
http://simply-effective.com/WGR/editor.html

This makes content editing an unpleasant experience, and the only significant source of dissatisfaction with an otherwise-likable CMS system.

Has anyone been able to get TinyMCE to display the content styled in a way that reflects your own stylesheets?

Thanks in advance for your help,
Jim

----------------------------------------------
Cms Version: 2.1.6
Installed Modules:
AdminSearch: 1.0.2
CMSContentManager: 1.1.4
DesignManager: 1.1.1
FileManager: 1.5.2
ModuleManager: 2.0.5
Navigator: 1.0.3
News: 2.50.6
Search: 1.50.2
Snippet: 0.2.2
TinyMCE: 3.1.4

Config Information:
php_memory_limit:
max_upload_size: 128000000
url_rewriting: none
page_extension:
query_var: page
auto_alias_content: true
locale:
set_names: true
timezone: America/New_York
permissive_smarty: false

Php Information:
phpversion: 5.6.30
md5_function: On (True)
json_function: On (True)
gd_version: 2
tempnam_function: On (True)
magic_quotes_runtime: Off (False)
E_ALL: 22519
E_STRICT: 0
E_DEPRECATED: 0
test_file_timedifference: No time difference found
test_db_timedifference: No time difference found
create_dir_and_file: 1
memory_limit: 512M
max_execution_time: 30
register_globals: Off (False)
output_buffering: On
disable_functions:
open_basedir:
test_remote_url: Success
file_uploads: On (True)
post_max_size: 128M
upload_max_filesize: 128M
session_save_path: /tmp (1777)
session_use_cookies: On (True)
xml_function: On (True)
xmlreader_class: On (True)
check_ini_set: On (True)
curl: On

Performance Information:
allow_browser_cache: Off (False)
browser_cache_expiry: 60
php_opcache: Off (False)
smarty_cache: Off (False)
smarty_compilecheck: Off (False)
smarty_cache_udt: Off (False)
auto_clear_cache_age: On (True)
Server Information:
Server Software: Apache
Server Api: cgi-fcgi
Server Os: Linux 3.10.0-427.36.1.lve1.4.44.el7.x86_64 On x86_64
Server Db Type: MySQL (mysqli)
Server Db Version: 5.6.34
Server Db Grants: Found a "GRANT ALL" statement that appears to be suitable

Permission Information:
tmp: /home/weaver20/public_html/tmp (0755)
tmp_cache: /home/weaver20/public_html/tmp/cache (0755)
templates_c: /home/weaver20/public_html/tmp/templates_c (0755)
modules: /home/weaver20/public_html/modules (0755)
uploads: /home/weaver20/public_html/uploads (0755)
File Creation Mask (umask): /home/weaver20/public_html/tmp/cache (0755)
config_file: 0440
----------------------------------------------

[calguy1000]

The steps for implementing styled WYSIWYG editors are different in TinyMCE as compared to MicroTiny. So they are essentially different problems.

For MicroTiny in CMSMS 2.x You must select the stylesheet that will be used to style the editor when editing a profile. Additionally, IIRC the styling requirements for tinymce are fairly specific, and have to be from the body down. This may require a different stylesheet than you normally use for your design. I admit that I have only verified that it works. Because I rarely use WYSIWYG editors in my work, I never completely style the editor.

I have verified that stuff like this works:
body * {
color: red;
}

[jlkane]

Thanks for your prompt reply, Calguy.

I'm focused on TinyMCE, as my editors will need several features that it provides beyond MicroTiny's feature set.

So to test, I did the following:

- created a simple stylesheet that contained *only*:
body * {
color: red;
}

- created a Design and attached only that simple stylesheet

- in Extensions > TinyMCE, I modified the custom profile I've been using. On the CSS tab, I selected my just-created simple Design from the "Design to use for CSS stylesheets" dropdown.

- cleared the CMSMS cache

- opened a page for editing, hoping to see red text

- saw black text

For the record, every other change I've made to my custom TinyMCE profile has worked as expected, so I don't have a generalized problem with configuring the editor. My failure seems completely specific to getting the editor to pull in a stylesheet.

Your thoughts?
Jim

[calguy1000]

Okay, so since this is an issue with the third Party TinyMCE module it is not a core issue... and I will move it to the proper forum.

Clarity and specifics when posting your questions prevents us all from wasting time.

[jlkane]

Okay, so since this is an issue with the third Party TinyMCE module it is not a core issue... and I will move it to the proper forum.

Since TinyMCE has been integrated into CMSMS in such a way as to pull stylesheets from a designated Design, I felt that the issue belonged here. If that's wrong, I'm sorry!

Jim

[jlkane]

I'm also wondering whether others are experiencing this problem, or whether this bit of functionality works smoothly for everyone else?

Jim

[jlkane]

I can't figure out whether no one else is affected by this problem, or whether everyone has just stopped expecting the WYSIWYG editors to pick up their stylesheets.

In either case, here's what I did to resolve the problem to my satisfaction:

[REMOVED]

edit: we do not allow posting code hacks

[jlkane]

In either case, here's what I did to resolve the problem to my satisfaction:

[REMOVED]

edit: we do not allow posting code hacks

Wow. If someone had acknowledged the problem and pointed me in this direction as at least a temporary workaround, I would have been very grateful. As far as I can tell:
- No one is willing to acknowledge this problem
- No one is interested in solving this problem
- Moving this thread to the backwaters of "The Lounge" is an effort to sweep it under the rug

I'm disappointed.

Jim

[calguy1000]

Wow. If someone had acknowledged the problem and pointed me in this direction as at least a temporary workaround, I would have been very grateful. As far as I can tell:
- No one is willing to acknowledge this problem
- No one is interested in solving this problem
- Moving this thread to the backwaters of "The Lounge" is an effort to sweep it under the rug

The rules of this forum and all CMSMS communication channels are well documented in our code of conduct. Your continuing unwillingness to read and/or follow them does not constitute a problem on the part of the community.

And... you did receive a constructive response to this topic.

Additionally, I tested a second time and could not reproduce an issue.