Publishing to a different place file publishes to the current place file instead

Using the usual “Publish to Roblox As” menu, with team create & collaborative editing enabled (in both source and destination, though nobody is in the destination place’s team create server at the time of publishing).

Output (note the usual “you published to DEST but you are still editing SOURCE” message is missing):

The source place which is open in studio (notice how the version we published just now is present under this place file, not the specified destination):

The destination place (notice how the newest version is not the one we just published):

Also, I’ve been getting a lot of publish failures recently. The bug here is happening regardless of whether a fail actually occurred then succeeded on subsequent retry for the publish action.

Also, on subsequent “Publish to Roblox” actions (different from “Publish to Roblox As”), the output displays the wrong place:

EDIT: The bug seems to start happening after a “Publish to Roblox As” fails. A popup displays informing me that the publish failed, and then after clicking retry things are broken. I’m not sure if it’s clicking retry that causes things to break, or if just having the publish fail is the thing that does it.

3 Likes

Are you completely overwriting the other place?

1 Like

Yep, that’s what I’m trying to do.

Well, you can always try to save it to your file, open that one up, and overwrite it on the other place with that file, or simply just restart, you’ve already accidentally published it to the test place so you won’t be losing progress!

I am reporting a bug, not asking for help :slight_smile: I know other ways to achieve the goal

4 Likes

Still good to help remind of the other options, this never has happened to me, so I can’t really say much, but good luck on whatever it is you’re doing!

1 Like

This bug is happening to me too. I try to publish as to my main game and get failing as well as saying success- but it just publishes to my place.

Thanks for the report we are looking at this now.

1 Like

This is now fixed. Please let us know if this issue recurs.

2 Likes