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; } } }

Unpublsh files

System

Is there a command/way to remove or unpublish an xml file previously submitted to a server?

I'm want to do it in a custom action calling a.cgi.

Find more posts tagged with

Comments

Adam Stoller

Is there a command/way to remove or unpublish an xml file previously submitted to a server?

I'm want to do it in a custom action calling a.cgi.

Assuming you mean to delete a file that was previously deployed with OpenDeploy - yes, there is a way to do that. A file list deployment in which you make sure the file(s) in the list do not exist on the source side, and make sure you have enabled doDeletes in the deployment configuration file.

Assuming you properly write the deployment configuration file with respect to options and parameters, your CGI should be able to initiate the deployment with the desired parameters to perform the desired action (would recommend significant testing in a DEV environment first though)

Migrateduser

Assuming you mean to delete a file that was previously deployed with OpenDeploy - yes, there is a way to do that. A file list deployment in which you make sure the file(s) in the list do not exist on the source side, and make sure you have enabled doDeletes in the deployment configuration file.

Assuming you properly write the deployment configuration file with respect to options and parameters, your CGI should be able to initiate the deployment with the desired parameters to perform the desired action (would recommend significant testing in a DEV environment first though)

What I'd like is to remove the xml file from the server folder (where the file was previously deployed) but keep it on the cms. Is that possible just using the "doDeletes"?

nipper

If you know what you are doing, yes. This is a big gun, and you can easily shoot yourself in the foot. However, you can change the area in the deployment config XML to another location, use a filelist that points to a non-existent file and use doDeletes. That will remove the XML. Of course if you do it wrong, it could delete everything.

Migrateduser

If you know what you are doing, yes. This is a big gun, and you can easily shoot yourself in the foot. However, you can change the area in the deployment config XML to another location, use a filelist that points to a non-existent file and use doDeletes. That will remove the XML. Of course if you do it wrong, it could delete everything.

What I want is exclude a complete file list that I send to the deploymentConfiguration file

( ... ...)

Migrateduser

If you know what you are doing, yes. This is a big gun, and you can easily shoot yourself in the foot. However, you can change the area in the deployment config XML to another location, use a filelist that points to a non-existent file and use doDeletes. That will remove the XML. Of course if you do it wrong, it could delete everything.

My previous quote may be confusing, the point is I have some xml files already published on the server (using filelist deployment), what I want is from teamsite check N files, click in a custom action (that calls a cgi) and remove those files from the serverm, but keep the files on teamsite.

nipper

Again, it can be done, but it won't be simple. There is some development to be done. You can do what I suggested to remove files from the OD receiver.

I would start slowly and may certain everything works right.

Adam Stoller

Create everything you think you need and then run OpenDeploy in simulation mode (iwodcmd start ... -sim) and look carefully at the micro logs to verify that it would do what you want, when satisfied, run the same command without the -sim flag and re-verify (you might want to make backups or snapshots of the file systems beforehand... Better would be to create the same scenario in your DEV environment (you do have a DEV environment, don't you?) and run it there first.