From c32b452772e47d11cf6e4a34a5091dc23efeccdf Mon Sep 17 00:00:00 2001
From: =?utf8?q?Tim=20D=C3=BCsterhus?= <duesterhus@woltlab.com>
Date: Tue, 13 Oct 2020 11:58:01 +0200
Subject: [PATCH] Update defaultStyle after migrating styles

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 | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/com.woltlab.wcf/package.xml b/com.woltlab.wcf/package.xml
index 1672b5822b..ee933824b3 100644
--- a/com.woltlab.wcf/package.xml
+++ b/com.woltlab.wcf/package.xml
@@ -87,14 +87,14 @@
 		<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>
-- 
2.20.1