On 04/25/2012 04:24 PM, Thomas Tsai wrote: > Looks like the upgrade jacked up a few things here. Categories are no > longer there in the drop down menu when editing a node, but show up in > the general view page.
Category configuration has been moved away from under the Node tab to under the configuration tab. > > I get the error above after I completed the yum update upgrade to v3.3.2 > when I log into the management portal. It shows up on the dashboard > page. If I browse around and return back to the dashboard page, the > error is not there again until I log out, and then log back in. > > Should I treat this as cosmetic? If not, whats the fix I should consider? > The admin caches several values in session in order to be more efficient (in it's original inefficiency). Sometimes what is cached is changed during an upgrade. Logging out then restarting PacketFence before logging in are recommended step after upgrades. This admin is slated for replacement and the project already started, the next one will deal better in that regard. Cheers! -- Olivier Bilodeau [email protected] :: +1.514.447.4918 *115 :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
