Original folder name for FCKEditor was "/core/fckeditor/editor" and it was hardcoded in "fckedtor_php4.php". All stopped working after folder was renamed to "/core/editor/editor"
Unused template removed, have more advanced copy in "core" anyway.
We are using nlsMenu instead of fw_menu.js for quite some time. Remove unused copy from "in-portal" (still have copy in "core" folder).
In-Portal's unused templates removed. Their copy from "core" is used.
Images and stylesheets moved from "in-portal" to "core" for template "sections_list.tpl".
Incorrect toolbar icon was used for disabled primary theme button.
"in-portal/no_permission.tpl" removed, because it's copy from "core" is used.
In-Portal's configuration templates removed, because we actually use ones from "core" folder.
Some sections still used configuration templates from in-portal, but core equivalents were already available. Fixed.
Ban Rules section's name was incorrect in unit config and templates, and old section was used in tree instead of new one!
In-Portal's Visits List (+ it's variation in In-Commerce) adapted to use "combined_header" and new grid filters (for each column).
clean.sh added to /system/cache
New tag <inp2:m_PrintCurrentParams/> for printing parametes at current deep level (useful for debugging purposes).
More support for K3 tables without TABLE_PREFIX.
Minor corrections (fix for prev. Commit)
Minor corrections to match programming standards in In-portal
Monir corrections to match programming standard in In-portal
Denying "unwanted" file types to Show in Browser
Minor fix in template
Fatar Error after last changes of <inp2:cms to <inp2:st - changed back
Disabled OLD "Summary Log" and "Session Log" sections
Enabled NParser for Everyone by default
New FCK Editor
New FCK Editor, small session expiration fix
Empty option added for users editing form in admin (Platform only), because all users were originated from Afganistan before
Both spelling dictionary fields made required, because there is no logic in creating suggestion for empty string and otherwise.
Got a suggestion or an issue? Discuss it on the Atlassian Community or visit Atlassian Support for other options.