CMS Made Simple Forums

Hi,

We've updated our CMS-MS from 1.11 to 2.2.7 recently, step by step using the upgrade guides. After the upgrade, there is no WYSIWYG editor in Calendar Event Editor. (MicroTiny)

I'm not a content editor myself, but this is the feedback I received from the content editor. She doesn't know to write HTML. For that reason we would like to re-enable a WYSIWYG editor.

Any suggestions on how to do this? Thanks in advance.

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

Cms Version: 2.2.7

Installed Modules:

AdminSearch: 1.0.4
CGCalendar: 2.5.1
CGExtensions: 1.60.4
CGSimpleSmarty: 2.1.8
CGSmartImage: 1.22.2
CMSContentManager: 1.1.6
CmsJobManager: 0.1.2
DesignManager: 1.1.4
FileManager: 1.6.6
FilePicker: 1.0.2
MenuManager: 1.50.3
MicroTiny: 2.2.2
ModuleManager: 2.1.3
Navigator: 1.0.8
News: 2.51.3
Search: 1.51.4
SiteMapMadeSimple: 1.2.8
ThemeManager: 1.1.8


Config Information:

php_memory_limit:
max_upload_size: 15000000
url_rewriting: mod_rewrite
page_extension:
query_var: page
auto_alias_content: true
locale:
set_names: true
timezone: Europe/Amsterdam
permissive_smarty: false


Php Information:

phpversion: 7.1.16
md5_function: Aan (Waar)
json_function: Aan (Waar)
gd_version: 2
tempnam_function: Aan (Waar)
magic_quotes_runtime: Uit (Onwaar)
E_ALL: 22527
E_STRICT: 0
E_DEPRECATED: 0
test_file_timedifference: Geen tijdsverschillen gevonden
test_db_timedifference: Geen tijdsverschillen gevonden
create_dir_and_file: 1
memory_limit: 150M
max_execution_time: 60
register_globals: Uit (Onwaar)
output_buffering: 4096
disable_functions:
open_basedir:
test_remote_url: Succes
file_uploads: Aan (Waar)
post_max_size: 16M
upload_max_filesize: 15M
session_save_path: /tmp (1777)
session_use_cookies: Aan (Waar)
xml_function: Aan (Waar)
xmlreader_class: Aan (Waar)
check_ini_set: Aan (Waar)
curl: Aan


Performance Information:

allow_browser_cache: Aan (Waar)
browser_cache_expiry: 60
php_opcache: Aan (Waar)
smarty_cache: Aan (Waar)
smarty_compilecheck: Uit (Onwaar)
auto_clear_cache_age: Aan (Waar)

Server Information:

Server Software: Hiawatha v10.8.1
Server Api: cgi-fcgi
Server Os: Linux 4.9.95-gentoo Aan x86_64
Server Db Type: MySQL (mysqli)
Server Db Version: 5.6.39
Server Db Grants: Er is een "GRAND ALL" permissie gevonden, alles lijkt in orde.


Permission Information:

tmp: /var/www/patty/webroot/tmp (0755)
tmp_cache: /var/www/patty/webroot/tmp/cache (0755)
templates_c: /var/www/patty/webroot/tmp/templates_c (0755)
modules: /var/www/patty/webroot/modules (0755)
uploads: /var/www/patty/webroot/uploads (0755)
Bestandscreatiemasker (umask): /var/www/patty/webroot/tmp/cache (0755)
config_file: 0444

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

Attached another screen, from CGCalendar settings. The WYSIWYG column is emtpy, no possibility to select anything there.

The "Details" field is missing altogether, but shows in the editor.

I start to fear for data corruption? I have some other strange things happening, but I will open a separate thread for that as per forum guidelines.

My last message is still in review, but I want to revoke my statement around data corruption and having more problems. They where mistakes on my side and already resolved.

I think you just need to change it from a text field to a text area. Text fields are just one line <inputs> where text areas are multi-line <textarea>.

Edit: sorry, I realized it's the Details field you need the wysiwyg on. A few questions:
Does the wysiwyg work in other areas of the site, like editing content pages?
Does the user actually have a wysiwyg selected? (they can get reset after an upgrade)
Does it work if you choose MicroTiny instead of TinyMCE?
Is there anything in the javascript console?
Have you tried other browsers, and/or incognito mode? (rule out an old cached script)

DIGI3 wrote: Edit: sorry, I realized it's the Details field you need the wysiwyg on. A few questions:
Does the wysiwyg work in other areas of the site, like editing content pages?
Does the user actually have a wysiwyg selected? (they can get reset after an upgrade)

Darn, I'm punching myself real hard now. I didn't ask that first question to the editor, and your guess is right. The WYSIWYG editor didn't work anywhere in the site.

I did check the editor's permissions and settings, but apparently I can't see all the user settings, even as administrator. So I missed the setting of a WYSIWYG for that account.

Thanks for your time to respond!

Would it be realistic to file for a feature enhancement enabling the admins to view and/or modify all user settings? This would help in situations where the admin need to give tech feedback to the editors.

You can basically do that already. In the list of backend users, click the gear icon to assume that user's login. You can also copy settings from one user to another.

A bulk way to change multiple users's settings might be handy but I think the only time I've ever seen it come up is in this exact case - upgrade from 1.x to 2.x and losing the editor temporarily. I can't see it making its way to the core unless someone sponsored it, as it's fairly edge-case.