because you could have created node in both instances programatically, so just the fact that node is not set as activated is not enough to be sure it doesn't exist in public. Therefore if there is public instance configured, Magnolia will try to reach it to notify it about content deletion ... and if that public is unreachable ... well you get told that it can't be reached. IF you have configured nodes to be automatically published after creation or modification, you would get the same error for those ops as well.
-- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=7af0abb6-e6b3-47c4-9218-6fb58953dbf3 ---------------------------------------------------------------- For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
