I'm trying to deploy a theme and at the end of the...
# suitecommercel
LC
07/08/2022, 4:29 AMI'm trying to deploy a theme and at the end of the process it shows the error: There is already a theme called xxx
anyone knows why is not allowing me to deploy the existing theme? I already tried deploying targeting the account, using --advanced, --to, etc.
c
Christopher Dembek
07/08/2022, 1:17 PMI have had this happen before. Within your Theme folder --> Gulp --> config.json --> around line 71 look for “deploy_config”. You might have the value of “update” set to “false”.
Hope this helps.
l
LC
07/08/2022, 1:39 PM@Christopher Dembek I just reviewed the config file and the update value is set to true. 😞
f
Flo
07/08/2022, 2:21 PMwhat´s the exact error you are getting?
l
LC
07/08/2022, 2:24 PMAfter the prompt checks if the Theme is a published theme I get the following:
[112358] Error in task gulp theme:deploy
Error Message
There is already a theme called: NAMEOFTHEME_Theme - 22.1.0. Vendor: SuiteCommerce.
Error Details
[112358] 'theme:deploy' errored after 32 s
f
Flo
07/08/2022, 2:24 PMand if you go to the record list that entry does not exist?
Flo
07/08/2022, 2:28 PMI´ve seen issues related to deploy or activation actions being blocked by the File Cabinet Antivirus but that issue has already been fixed
l
LC
07/08/2022, 2:28 PMwhat record list?
the Theme does exist since I managed to deploy it the first time.. but for some reason I can't re deploy it
f
Flo
07/08/2022, 2:31 PMwhen you deploy a theme the SC ExtMech Extension record creates a new entry
Flo
07/08/2022, 2:31 PMmy question is if that entry is actually created
l
LC
07/08/2022, 2:31 PMI can check
f
Flo
07/08/2022, 2:33 PMand have you changed the theme version?
l
LC
07/08/2022, 2:35 PMYes, it did created a new entry for the SC ExtMech Extension and no, I did not changed the theme version.. I usually don't change it unless the theme presents big changes or milestones
f
Flo
07/08/2022, 2:38 PMI have not worked with Themes for a long time, but per what I recall you can not redeploy a theme that already exists if you do not change the version
Flo
07/08/2022, 2:39 PMI mean something needs to change, name, version or vendor
l
LC
07/08/2022, 2:46 PMThis is the first time I'm getting this time of error... I don't usually never change the name, version or vendor unless there is a milestone new for the theme.
That's why I find this error so strange...
f
Flo
07/08/2022, 2:47 PMdon´t know then
Flo
07/08/2022, 2:47 PMbut that´s what I would try
l
LC
07/08/2022, 2:49 PMyeah.. I created a support case to see if there is any type of fix
thanks both for your help!
k
kkennedydesign
07/11/2022, 4:49 PMI found if you use the --create command it adds something to the config….. like “create”: true…. then you have to manually remove it for subsequent deploys. I would scour your config.json
l
LC
07/12/2022, 5:28 PM@kkennedydesign I'm going to test changing that value of the create to see If I manage to override the theme.
LC
07/12/2022, 9:35 PM@kkennedydesign worked perfect! I changed the value of create: false and I managed to re deploy the theme without any issues. Thanks!
👏🏻 1
4 Views