Hi Everyone, I have encountered an issue when depl...
# suitecommerce
k
Hi Everyone, I have encountered an issue when deploying a non-published theme after I fetched the theme from the server. When I attempt to deploy it, “gulp theme:deploy” prompts me for the Vendor, Name, Version, etc., even though I previously fetched it. I accept the default prompts. I then get an error that says “There is already a theme called: xxxxxxx. Vendor: xxxxxxxx.“. I have never encountered an issue fetching and deploying non-published themes before. I am using the latest version of SuiteCommerce Extension Management, version 2022.2.0.
c
@Keith Fetterman, I have seen this similar Issue with newer version 2022.2.0. I have encountered this Issue when I try to deploy the extension which is already in place.
k
@Charan, thank you for responding, so it might be a bug in 2022.2.0. Did you figure out a way to work around the issue without advancing the version #.
c
@Keith Fetterman we didn’t find any workaround yet. Mostly probably, will raise a support ticket on this Issue. Let me know If you are able to figure out the work around for this. Thank you!
k
@Charan, thanks for letting me know. I’ll let you know if I find a solution.
k
check to make sure "create" is no where in your gulp>config>config.json file
If you create the new theme using the tools it gets added but not removed after the first deploy...can't remember which tools version, but was recent
m
Have you tried: gulp theme:deploy --advanced
k
@Michelle Beutler,I did try it. No luck.
@kkennedydesign, you nailed it. In the gulp>config>config.json file there were the following properties near the end:
Copy code
"deploy_config": {
        "update": true,
        "chunk_size": 80,
        "create": true,
        "advanced": true
    },
When I removed “create” and “advanced”, I was able to deploy the theme without it prompting me to create a new theme. It successfully deployed the theme into the existing theme. Thank you. @Charan, this may also be the issue with your ability to deploy the extension.
😎 1
❤️ 1
c
Thanks @Keith Fetterman . I’ll give a try.
k
Glad it worked!!