Update defaultStyle after migrating styles
authorTim Düsterhus <duesterhus@woltlab.com>
Tue, 13 Oct 2020 09:58:01 +0000 (11:58 +0200)
committerGitHub <noreply@github.com>
Tue, 13 Oct 2020 09:58:01 +0000 (11:58 +0200)
It appears that importing the defaultStyle causes the style specific asset folder to be created, leading to issues with the style migration.

com.woltlab.wcf/package.xml

index 1672b5822b52208c13674a386679201172c5dde3..ee933824b38a30a66e85f4959d7a75f7e52dce78 100644 (file)
                <instruction type="userNotificationEvent" />
                <instruction type="userOption" />
                
-               <instruction type="style" run="standalone">defaultStyle.tar</instruction>
-               
                <instruction type="language" />
                
                <instruction type="script" run="standalone">acp/update_com.woltlab.wcf_5.3_invalidateMailForm.php</instruction>
                
                <instruction type="script" run="standalone">acp/update_com.woltlab.wcf_5.3_style.php</instruction>
                
+               <instruction type="style" run="standalone">defaultStyle.tar</instruction>
+               
                <!-- This SQL step purges the legacy package servers, this must come last to make sure that an early
                     abort of the core upgrade does not brick the installation. -->
                <instruction type="sql">update_5.3.sql</instruction>