Redone ImportScript table using K4 standards
Redone pre-Import Script
c_Meta tag, checking if module at least found before getting ItemTemplate (from mobiland_eshop to RC)
Default value changed to Comma sep. for Export script
Uncomment DIE(); before Releasing to public
Script adjusted to reflect migration of Writable folder
Show "System Cache" tool added with DIE(); restriction
Cosmetic changes for Agents, Speliing Dic., Thesaurus + Icons added
Version updated => 4.3.9
Added "Export button" to Grid
In-Portal now contains language pack combined from proj-base and in-portal modules (not including core phrases)
Constant "ITEM_FILES_PATH" moved to "core/kernel/constants.php"
In-Portal old kernel and scripts using it removed from RC.
Added default Icons (Custom) - used while new not ready
Show module background image only when "Proj-Base" module is not enabled (allows to preserve logo_bg.gif from in-portal inside "core" folder).
Phrases added.
Duplicate regional section templates removed from In-Portal.
Unused stylesheet removed.
Unused In-Portal templates removed: editor.tpl, translator.tpl.
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.
Got a suggestion or an issue? Discuss it on the Atlassian Community or visit Atlassian Support for other options.
