Per the documentation, the name is correct. However, on startup it doesn't work, I rename to old.sipxplugin.beans.xml so the system doesn't find it, restart and GUI works again. Rename it back to sipxplugin.beans.xml and the plugin seems to work okay, with the customization applied.
http://wiki.sipfoundry.org/display/sipXecs/Customizing+Colors%2C+Layout+and+ Logo Look and Feel Create following files /etc/sipxpbx/sipxplugin.beans.xml From: sipx-dev-boun...@list.sipfoundry.org [mailto:sipx-dev-boun...@list.sipfoundry.org] On Behalf Of George Niculae Sent: Thursday, November 15, 2012 12:18 AM To: sipXecs developer discussions Subject: Re: [sipx-dev] Custom Skin plugin broken in 4.6 On Thu, Nov 15, 2012 at 10:08 AM, Todd Hodgen <thod...@frontier.com> wrote: I've found that after doing a yum update, that having a customized sipxplugin.beans.xml renders the GUI un-useable - with an error (404). Renaming the sipxplugin.beans.xml and restarting sipxecs allows the gui to work again. If I then rename the sipxplugin.beans.xml back to its correct name, restart, gui works again. This particular sipxplugin.beans.xml file has been used since 4.2.1 in its current configuration. Hm, it should be named sipxplugin.beans.xm, which name you think it is the correct one? George
_______________________________________________ sipx-dev mailing list sipx-dev@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-dev/
