Transporter:
We spawned a blueprint of a station. The station then got centered within the sector by a server admin. All transporter 'stopped' working, insofar they tranported to the sector coordinates of the other transporter modules, which were valid before the station got centered. Deleting the transporter modules and placing new ones in the same position reproduces the same result. If you put transporter modules in a different place, then it would work again. The sector coordinates related to the transporter module seem to be stored in the space the module occupied and remains unchanged even if the block gets replaced within the very same point in space.
~~Rail:~~
~~A encountered a similiar behaviour with rail blocks. I use a button adjacent to a rail block, then link the button to a sequence of rails, such that the trigger of the button changes the orientation of the rail within the sequence according to the rail that is adjacent to the button. If the rail block adjacent to the button the gets replaced with a rail block of a different orientation, the orientation of the former block remains. It is as if the meta-information like block-orientation is been safed in the space the block originally occupied, and remains unchanged after replacement. ~~
~~Since those two encounters are similiar, I post them togehter in one bug report. ~~
@Lancake: Can't reproduce the rail issue and it looks like the duplicate meta links issue we had before (which should be fixed now), might explain why I don't get it anymore.