User Tools

Site Tools

:: Version 2.7.0 ::

2_7_0:install:260_to_270_migration_notes

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
2_7_0:install:260_to_270_migration_notes [2019/12/20 09:37]
vdumas [System]
2_7_0:install:260_to_270_migration_notes [2020/01/08 16:41] (current)
Line 8: Line 8:
   * For an exhaustive list of changes check the [[2_7_0:​release:​change_log|Change Log]]   * For an exhaustive list of changes check the [[2_7_0:​release:​change_log|Change Log]]
  
-====== ​To know before upgrading ​======+====== ​Impact on Users ======
  
-===== Custom extensions on Portal =====+===== Portal ​behavior changes ​=====
  
-In order to ensure better securitysupport ​and sustainability;​ we migrated ​the portal's framework ​from Silex 2.x to Symfony 3.4. Even though we managed ​to keep backward compatibility for most of the code, if you made a custom extension for the portal, you are most likely ​to rework part of it.+  * In iTop 2.7any forms which **only** propose transitions,​ are now automatically read-only. This can break a customized user portal. The workaround is usually to add the ''​always_show_submit''​ tag on the form definition or to split forms to make them more specialized between creation ​and edition. 
 +  * External key display in forms are now clickable, if you rather keep the previous behavior replace the //xxx_id// attribute code in your form with //​xxx_id_friendlyname//​. 
 +  * We have update Font Awesome from v4 to v5.9.0, check that your icons in portal ​are still displayed as expected. Some [[https://​fontawesome.com/​how-to-use/​on-the-web/​setup/​upgrading-from-version-4#​name-changes|icons names have changed]] between the versions, old name will still work except if you have used aliases from the version 4, which will need to be changed. 
 +  * For security reasons, LinkedSet displayed in forms, such as for example contacts associated ​to a User Request, are now by default limited to the scope of the portal user. A typical example therewas that portal user could see on his User Requests, IT department associated contacts, even if in theory his Contact scope was limiting him to contacts of his own organization. If you want to keep the previous behavior, you need to modify the forms in your portal displaying those linksets as explained in the [[2_7_0:​customization:​portal_xml#​xml_version_17|2.7 new features in the Portal XML reference]]
  
-Read [[2_7_0:​install:​portal_270_migration|this page]] ​ to check if your extension is concerned.+===== Change of Administrators users =====
  
-===== Incompatible Extensions =====+  * //Admin tools// has been modified and some of its entries moved to new //​Configuration//​ and //System// menus.
  
-Because of the silex to Symphony migration, the following extensions are **not compatible with the iTop 2.7**. A new version will be published within the coming months and you will have to upgrade those extensions as well.+====== To check before upgrading ====== 
 + 
 +===== System ===== 
 +  * Ensure that you have ''​php-gd''​ installed on your iTop server. It is now enforced at setup, as it is mandatory for handling correctly images within caselogs and description. 
 +  * If you use php-memcache,​ migrate to php-memcached 
 + 
 +===== Setup can take time ===== 
 + 
 +With the new attachments display and the addition of the //creation date// and //user// columns, the DB schema must be modified accordingly. This operation can **take a long time** if you have an **big number of attachments**. 
 + 
 +It could be good to run that SQL query before upgrading. FIXME Provide the query or PHP page. 
 + 
 +===== Portal ===== 
 + 
 +==== Incompatible Extensions ==== 
 + 
 +Because of the Silex to Symphony migration, the following extensions are **not compatible with iTop 2.7 Portal**. A new version will be published within the coming months and you will have to upgrade those extensions as well.
  
   * [[https://​store.itophub.io/​en_US/​products/​combodo-customized-request-forms|Customized request forms]]   * [[https://​store.itophub.io/​en_US/​products/​combodo-customized-request-forms|Customized request forms]]
   * [[https://​store.itophub.io/​en_US/​products/​combodo-approval-process-automation|Approval process Automation]]   * [[https://​store.itophub.io/​en_US/​products/​combodo-approval-process-automation|Approval process Automation]]
-  * [[https://​store.itophub.io/​en_US/​products/​itop-iframe-dashlet|iFrame Dashlet]] 
  
-===== End of Legacy Portal ​=====+==== Custom extensions on Portal ==== 
 + 
 +If you have custom extensions bringing new bricks in your portal, you will need to get/write a new version of those extensions. 
 + 
 +Because, in order to ensure better security, support and sustainability;​ we migrated the portal'​s framework from Silex 2.x to Symfony 3.4. Even though we managed to keep a backward compatibility for most of the code, if you made a custom extension for the portal, you are most likely to rework part of it. 
 + 
 +Read [[2_7_0:​install:​portal_270_migration|this page]] ​ to check if your extension is concerned. 
 + 
 +==== End of Legacy Portal ====
  
 As announced, the Legacy portal is no more available in iTop 2.7 As announced, the Legacy portal is no more available in iTop 2.7
  
-====== To check before upgrading ====== 
  
-===== System ​===== +===== XML Datamodel changes ​=====
-  * Ensure that you have ''​php-gd''​ installed on your iTop server. It is now enforced at setup, as it is mandatory for handling correctly images within caselogs and description. +
-  * If you use php-memcache,​ migrate to php-memcached+
  
 +If you have custom extensions on your iTop, the Setup with an 2.7 version of iTop may fail due to one of the Datamodel changes that we have made:
 +
 +  * Datamodel now includes the default theme in ///​itop_design/​branding/​themes/​theme[@id="​light-grey"​]//,​ so if you altered the //​branding//​ node, make sure to put the alteration flag (eg. //​_delta="​define"//​) on the subnodes.
 +  * Some of the //Admin tools// sub-menus have been moved under the newly created group-menus //​Configuration//​ and //System//. If you have redefine those menus, it may not work as expected.
  
-===== Portal behavior changes ===== 
  
-  * In iTop 2.7, any forms which **only** propose transitions,​ are now automatically read-only. This can break a customized user portal. The workaround is usually to add the ''​always_show_submit''​ tag on the form definition or to split forms to make them more specialized between creation and edition. 
-  * External key display in forms are now clickable, if you rather keep the previous behavior replace the //xxx_id// attribute code in your form with //​xxx_id_friendlyname//​. 
-  * We have update Font Awesome from v4 to v5.9.0, check that your icons in portal are still displayed as expected. Some [[https://​fontawesome.com/​how-to-use/​on-the-web/​setup/​upgrading-from-version-4#​name-changes|icons names have changed]] between the 2 versions, old name will still work except if you have used aliases from the version 4, which you will need to change. 
-  * For security reasons, LinkedSet displayed in forms, such as for example contacts associated to a User Request, are now by default limited to the scope of the portal user. A typical example there was that portal user could see on his User Requests, IT department associated contacts, even if in theory his Contact scope was limiting him to contacts of his own organization. If you want to keep the previous behavior, you need to modify the forms in your portal displaying those linksets as explained in the [[2_7_0:​customization:​portal_xml#​xml_version_17|2.7 new features in the Portal XML reference]] 
  
  
  
2_7_0/install/260_to_270_migration_notes.1576831065.txt.gz · Last modified: 2019/12/20 09:37 by vdumas

";