Hi Nathan, Which version if 3.x exactly? You are speaking of a Magnolia Dinosaur, very long time ago it lived :)
Replacing the logo was never meant out of the box. I'm not even sure if from licensing point of view this was ok to do at this time, but I doubt that this is still relevant. I assume it is served form within the AdminCentral's JAR, there within located in the mgnl-resources. (All assumptions). The only way would be extracting this jar, and then: - Either replacing the logo (keeping the same name) - Or adapting the template/servlet which includes it, and include your own. Then "zip" it again as a JAR file. BUT: You will create by this a binary incompatibility. If you would like to do it more proper, you would check out the source. Replace the needed stuff, and then create with Maven a admin interface with a specific artifact ID. Then its clear that it is an separated jar and you could reference it specific in a project dependency. I hope this helps. Cheers Christian -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=333ff1f0-a101-4d26-8bca-3d5ee9c8e3bc ---------------------------------------------------------------- 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]> ----------------------------------------------------------------
