无法回滚到Google Tag Manager工作区的当前版本,如何删除草稿版本?

huangapple go评论49阅读模式
英文:

Can't roll back to current version of the Google Tag Manager workspace, how do I delete the draft version?

问题

我导入了标签到错误的工作区 ID 40,而不是最新的工作区 ID 38。

ID 40在导入之前不存在。

如果我访问 https://tagmanager.google.com/#/versions/accounts/xxx/containers/xxx/versions?containerDraftId=40
我看不到版本 40 以删除,即使我将版本 38 设置为最新版本(它已经是了),我仍然从 https://tagmanager.google.com/#/container/accounts/xxx/containers/xxx/workspaces/38/ 重定向到 https://tagmanager.google.com/#/container/accounts/xxx/containers/xxx/workspaces/40/

我应该从这个界面删除版本 40 吗?
无法回滚到Google Tag Manager工作区的当前版本,如何删除草稿版本?

还是这会删除所有内容?

我已导出工作区版本 38。

帮助赐教。

英文:

I imported tags into the wrong workspace ID 40, instead of the latest workspace ID 38.

ID 40 did not exist before the import.

If I visit https://tagmanager.google.com/#/versions/accounts/xxx/containers/xxx/versions?containerDraftId=40
I don't see version 40 to delete, and even if I set version 38 as the latest version (it already was) I am still redirected from https://tagmanager.google.com/#/container/accounts/xxx/containers/xxx/workspaces/38/ to https://tagmanager.google.com/#/container/accounts/xxx/containers/xxx/workspaces/40/

Do I delete version 40 from this screen?
无法回滚到Google Tag Manager工作区的当前版本,如何删除草稿版本?

or will this delete everything?

I've exported workspace version 38.

Help appreciated.

答案1

得分: 0

似乎你混淆了工作区和版本。这两者是无关联的。只有在发布时,版本号才会递增。工作区可以创建或删除而不会改变版本号。你可以将工作区视为 Git 分支,发布就相当于将它们合并到主分支。每当一个工作区被发布,而另一个工作区仍然存在时,它会提供更新另一个工作区的选项。这就像将主分支合并到你的分支中一样。

版本号只能递增,不能减少。所以当你出于错误发布了某个内容,从版本 38 到版本 39,然后想回滚到 38,你仍然可以。但当你回滚到 38 时,GTM 会创建版本 40。尽管版本号是 40,但其中的代码基础仍然是来自版本 38。

这可能看起来有点复杂,但它确保了你在 GTM 中发布的所有操作都被记录在版本历史中。

所以不要太关注版本号,而要关注版本中的代码基础,或者说你要部署的更改。

另外,不,你不能从工作区屏幕上删除版本。实际上,你不能删除版本。如果你需要管理版本,你可以转到版本管理页面。

英文:

Seems to me like you're mixing up workspaces and versions. These two are disassociated. Versions only increment when you publish. Workspaces can be created or deleted without changing the version numbers. You can treat workspaces as git branches and publishing would be just merging them with main. Whenever one workspace is published while another workspace exists, it will offer you to update the other workspace. This would be just pulling main into your branch, effectively.

Version id can only be incremented. It can't be reduced. So when you publish something by mistake and go from version 38 to version 39, and then you want to roll back to 38, you still can. But when you roll back to 38, GTM creates version 40. Even though the version number is 40, the codebase in it would be from 38.

It may seem overcomplicated, but it makes sure all you do in GTM in terms of publishing is accounted for and recorded in the version history.

So stop paying too much attention to version numbers. Pay attention to the codebase in versions or rather the changes you're deploying.

Also, no, you don't delete versions from the workspace screen. You don't delete versions at all. If you need to manage versions, you go to versions:

无法回滚到Google Tag Manager工作区的当前版本,如何删除草稿版本?

huangapple
  • 本文由 发表于 2023年6月8日 10:07:10
  • 转载请务必保留本文链接:https://go.coder-hub.com/76428146.html
匿名

发表评论

匿名网友

:?: :razz: :sad: :evil: :!: :smile: :oops: :grin: :eek: :shock: :???: :cool: :lol: :mad: :twisted: :roll: :wink: :idea: :arrow: :neutral: :cry: :mrgreen:

确定