{"issue":{"user":{"id":326984,"login":"verrier","url":"https://api.github.com/users/verrier","gravatar_id":"0f4034ff0e6763c9cbd6420548813a55","avatar_url":"https://secure.gravatar.com/avatar/0f4034ff0e6763c9cbd6420548813a55?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"milestone":null,"title":"Odd bug when admin deletes a portal","created_at":"2011-10-07T03:42:54Z","labels":[{"name":"bug","url":"https://api.github.com/repos/Minecarts/PortalForge/labels/bug","color":"e10c02"}],"updated_at":"2011-12-20T23:19:54Z","state":"closed","id":1840279,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"html_url":"https://github.com/Minecarts/PortalForge/issues/7","closed_at":"2011-12-20T23:19:54Z","body":"This one is an odd one... when an admin /portal deletes a portal... and then user goes in later and ignites a nether portal at the exact same spot... the nether portal acts like their old sub portal\r\n\r\nThere's some kind of cache issue involved... the way to fix it is to re-create attach portal blocks to the portal and then set the old portal ID to a nether portal\r\n\r\nSo it's like a /portal clear # doesn't clear some cached portal to block mapping, but it does clear the portal object values itself (destination, type, etc)","number":7,"url":"https://api.github.com/repos/Minecarts/PortalForge/issues/7","comments":1,"assignee":null},"action":"closed"}