nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

New workarea wont deploy

shougom

Let me preface this by saying the original creator of our architecture is long gone and im in a position where we are incredibly under staffed support wise.

Were running teamsite 6.7.2 with multiple workareas.

Recently we have added a couple of new workareas. We have noticed that the files in the root of the workarea are not getting to staging when submitted.

Im sure this could be a number of reasons. But was hoping someone could steer us in the right direction as far as which logfiles or wfts to look for. I cant help but think its permissions related but not sure.

All the other/older workareas submit and deploy as expected. So creating a new workarea isnt enough a step must have been missed. Any clues are appreciated.

Find more posts tagged with

Comments

Adam Stoller

Let me preface this by saying the original creator of our architecture is long gone and im in a position where we are incredibly under staffed support wise.

Were running teamsite 6.7.2 with multiple workareas.

Recently we have added a couple of new workareas. We have noticed that the files in the root of the workarea are not getting to staging when submitted.

Im sure this could be a number of reasons. But was hoping someone could steer us in the right direction as far as which logfiles or wfts to look for. I cant help but think its permissions related but not sure.

All the other/older workareas submit and deploy as expected. So creating a new workarea isnt enough a step must have been missed. Any clues are appreciated.

Unfortunately you're talking about custom code - and custom code is difficult to debug without having access to it and the environment in which it is being run.

Let's try a little Q&A:

Frankly, at this point it's difficult to go on conjecturing without having gotten answers to the above.The ball's in your court now.

shougom

I figured out the issue. There was a permission missing at the folder level for the new workarea out on the Y drive for workarea and for staging.

Thanks.

shougom

Well I guess I half figured it out.

The files are now deploying to workarea and staging. But there is a deployment to production that isnt happening. We have a wft called direct deployment that sends it to staging and production in one shot. But its not doing the deploy to production.

Still looking.