Deployment stops on a document that is a node reference for one of the nodes we selected. The following message is returned: "The path is already in use." This seems to occur in every case where there already exists a node on the live server that has the same URL Path Settings. The workaround is to give the node a new URL Path Setting.

Should this work? Does the Create a New Revision setting affect things (it's turned off)? Any hints/suggestions would be appreciated.

Comments

gippy’s picture

gippy commented
Title: Error: "The path is already in use" » Log: "date(): it is not safe to rely on the system's timezone

I don't know if this is significant, but we are getting the following error on the live server each time we run deploy:

date(): It is not safe to rely on the system's timezone settings ...You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /home/www/vhosts/bazaarvoice.com/subdomains/developer/httpdocs/includes/xmlrpcs.inc on line 114.

Reported by php.

gippy’s picture

gippy commented
Title: Log: "date(): it is not safe to rely on the system's timezone » Error: "The path is already in use"

changing the Issue title back to "the path is already in use"

gippy’s picture

gippy commented

One more piece of information:
We unchecked "Automatic Alias" and also removed the setting for those nodes on the staging and the live servers. After that the deploy process seems to be working okay.

druvision’s picture

druvision commented

Yes, but we also need automatic alias!

Suggested logic:

IF alias is the same THEN update ELSE add-new

Will it work??