<@U8X7E86M6> Steve - we have fetch a theme that ap...
# suitecommerce
k
@Steve Goldberg Steve - we have fetch a theme that appears to have a skin applied. The skin does not come with the fetch....is there documentation on how the skins are supposed to work? I assume you can only have one active skin per website record like SMT content? Or is the skin per domain? I would think if it was per website record it would be applied to our dev domain as well.....we can't access it either via SMT
s
So, is this a skin that's been built in the SMTs and saved?
k
thats my guess...looks to be a NS skin that has then been altered
s
These are the docs for skin management https://developers.suitecommerce.com/chapter1512491665
if it is a valid skin then I would expect it to turn up in the SMTs
as for downloading it after a fetch, I've not tried that yet
k
ok...I should clarify....we have the skins but not the custom edits done in SMT.....would you expect those would come down too? They appear not to have....
s
OK I can't see anything in the docs (internal or external) to suggest that a custom skin created in the SMTs should be fetchable into the developer tools. As far as I can tell, they are considered separate use cases
However, there should be a new custom skin custom record which saves the key info in your NetSuite account
k
Thanks - we saw that record and trying to edit it....no luck yet but could be cached somewhere - appreciate the help
so now our problem is the fetched theme is missing templates from some of the extensions.....sigh
s
That's bizarre
k
its related to the posh theme extension....we deactivated this extension and no errors, but will need to backfill anything we're missing
s
SC.PoshThemeExtension.1.0.0.ShoppingEntryPoint?
k
yes.....I tested in an SCA account with summit theme....the extension did not come down in the fetch either, but there were no errors....perhaps its because SC vs SCA timing/load order
s
OK. I'm unsure what exactly that extension is meant to do, or if it has templates
I will need to check that out
k
As we looked closer, there were template errors, but I think those were not the main issue...this one..... ErrorManagementPageNotFoundView.addExtraContextProperty(...) I know it said, in so many words, that addExtraContextProperty is not a function.
that same function is in the summit extension that I ran perfectly in SCA
s
OK, so it looks like that the themes have companion extensions that change some of the behaviour
For example, one module changes the page not found view file
Therefore, strictly speaking, when you get the theme provisioned to an account you should also get the extension
The person who provisioned the theme to your account may not be aware of this
I think you will need to request that the companion extension bundle is provisioned to you
k
well, the interesting thing is that it is in the account and activated...
but its sc so thinking its a load order.....
s
oh
I would be surprised
k
are we the first to report this lol
its just running local thats the issue
s
It seems you are. I can't seem to find any cases near this
I mean, you are a trailblazer when it comes to bug hunting 😄
k
my lot in life ;>(