CSS for microTiny in Admin

[MantaPro]

Hi - I'd like the WYSIWYG experience when my user-editors edit page content within the Admin to better approximate the front end styling.

I have read the MicroTiny module help; plus the Support Document here; plus searched these forums and wider on Google.

I can't seem to get it working - what I have done so far is:

• Created a new style sheet called Admin Editor
• Created a new Design called Admin Editing
• Assigned the Admin Editor stylesheet and the 2 main page layout templates to the design Admin Editing
• In Admin/Extensions/MicroTiny WYSIWYG Editor/Settings/Admin Editor I have selected the Admin Editor stylesheet

From the docs I expected that to work, at the moment the only commands in the style sheet are:

Code: Select all

body#tinymce {
background-color: #616161;
color: #fff;
}

Using my browser's web tools inspector and/or doing view-source there is no evidence that the Admin Editor style sheet is even loading - the body tag within the MicroTiny iframe is being styled by content.min.css which is part of the OneEleven admin theme

No errors shown in either the Admin log or PHP error logs.

Where I am going wrong - suggestions appreciated - thanks in advance ..

Code: Select all

----------------------------------------------

Cms Version: 2.2.9

Installed Modules:

    AdminSearch: 1.0.4
    CGBetterForms: 1.9
    CGExtensions: 1.61.4
    CGGoogleMaps2: 1.1.1
    CGSimpleSmarty: 2.2.1
    CMSContentManager: 1.1.7
    Captcha: 1.0
    CmsJobManager: 0.1.3
    DesignManager: 1.1.5
    FileManager: 1.6.8
    FilePicker: 1.0.3
    Gallery: 2.3.2
    LISE: 1.3.1
    LISEActivities: 1.3.1
    LISETestimonials: 1.3.1
    LISEVacancies: 1.3.1
    LinkMgr: 2.2.1
    MicroTiny: 2.2.3
    ModuleManager: 2.1.5
    Navigator: 1.0.9
    News: 2.51.4
    Search: 1.51.6
    SitemapMgr: 1.5.4


Config Information:

    php_memory_limit:
    max_upload_size: 10000000
    url_rewriting: none
    page_extension:
    query_var: page
    auto_alias_content: true
    locale:
    set_names: true
    timezone: Europe/London
    permissive_smarty: true


Php Information:

    phpversion: 7.3.0
    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: 32M
    max_execution_time: 60
    register_globals: Off (False)
    output_buffering: 1
    disable_functions:
    open_basedir:
    test_remote_url: Success
    file_uploads: On (True)
    post_max_size: 10M
    upload_max_filesize: 10M
    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: On (True)
    browser_cache_expiry: 60
    php_opcache: Off (False)
    smarty_cache: Off (False)
    smarty_compilecheck: Off (False)
    auto_clear_cache_age: On (True)

Server Information:

    Server Software: Apache
    Server Api: cgi-fcgi
    Server Os: Linux 3.16.0-ui18135.21-uiabi1-infong-amd64 On x86_64
    Server Db Type: MySQL (mysqli)
    Server Db Version: 5.5.60
    Server Db Grants: Found a "GRANT ALL" statement that appears to be suitable


Permission Information:

    tmp: /homepages/38/d242029264/htdocs/menwinnion_cmsms2/tmp (0705)
    tmp_cache: /homepages/38/d242029264/htdocs/menwinnion_cmsms2/tmp/cache (0705)
    templates_c: /homepages/38/d242029264/htdocs/menwinnion_cmsms2/tmp/templates_c (0705)
    modules: /homepages/38/d242029264/htdocs/menwinnion_cmsms2/modules (0705)
    uploads: /homepages/38/d242029264/htdocs/menwinnion_cmsms2/uploads (0705)
    File Creation Mask (umask): /homepages/38/d242029264/htdocs/menwinnion_cmsms2/tmp/cache (0705)
    config_file: 0444

----------------------------------------------

[DIGI3]

Did you clear the cmsms cache after making the changes?

[MantaPro]

Hi Digi3 - thanks for the reply

Yes after I set up the editor style sheet and design I cleared Cache in System Maintenance

Having checked and tried everything again, including clearing cache, I now notice that in the Admin/Extensions/MicroTiny/Example screen I do get a "failed to load content css: ......" withn the MicroTiny iframe

and in the admin log the message "No stylesheets matched the criteria specified"

(ps. within the tabs for the stylesheet: I do not have any media queries set; I have tried it with all media types unset and also tried it with a media type of "all" set - in case this was filtering its selection)

The two messages above make me think it knows what it wants to load but the reference is getting mangled somewhere along the way so that it is not found when the MicroTiny iframe loads

The only articles I found regarding CSS for MicroTiny in CMS-MS pre dated the {cms_stylesheet} - I wonder about the Stylesheet/Design set up - currently I have linked the templates (for the pages the users need to edit) to both my front end Design and the Admin Editng Design (which the Adim Aditor stylesheet is linked to) - I will try unlinking and deleting the Admin Editing design - just have the Stylesheet as an unassigned orphan see if that works - otherwise I'll have to look at the code for MicroTiny/CMSMS-Admin to see where the load instruction is getting corrupted

Regards ... Phil

[MantaPro]

I have tried detaching the Editor stylesheet from the Admin design, and deleting the Admin design then clear cache again - still doesn't work; I'll trace through the code later ..... !

[DIGI3]

This is a bug, and has now been fixed in svn.

[MantaPro]

Excellent many thanks Digi3

I have picked up revision 11851 from the SVN;

It is a step in the right direction; but still not right

I know next to nothing about the coding under the surface of CMSMS but here is my theory (a guess!!) and observations (factual).

After creating the Admin stylesheet; assigning via Extensions/MicroTiny Settings then clearing cache : -

• if the next thing I do is edit a page via content manager then the revision 11851 fixes are NOT working. I presume having edited a page I have created some cache; when I then go to edit News or LISE module text areas then the WYSIWYG styling still isn't loading - the styling loaded style.php (i.e. OneEleven) + skin.min.css + content.min.css only

• alternatively, if the FIRST WYSIWYG iframe is accessed by going to Extensions/MicroTiny/Settings Sample then both my Admin editor stylesheet and all of the assigned Frontend stylesheets are loaded and the WYSIWYG looks correct; being the first WYSIWYG it creates the cache, if I then go to edit pages via Content Manager; News items or LISE module text areas then they now display correctly

So I am guessing that the way the MicroTiny WYSIWYG iFrame loads in extensions is subtly different to Content Manager; News etc

Sorry about the guessing but I hope the scenario results help narrow the issues

Thanks for your help

[DIGI3]

Another update has been made if you want to test. I haven't had a chance yet.

[MantaPro]

Got the additional fix - now working perfectly - excellent - many many thanks for your help