<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[how to show groups separately]]></title><description><![CDATA[<p dir="auto">In the display, there is nice box labeled EXTENSIONS and then each of the extension buttons is below. I want to group the extensions into 3 piles (groups). I noticed that if I enable my user (say 500) to include 3 groups, all the extensions in those groups are sorted together into one pile, labeled EXTENSIONS. How can I set it up so that I see 3 groups, such as MEENY, MINEY, MOE.  It seems that if you go multi-tenant it does break them into piles, but by creating multiple event streams coming in that will slow the system down considerably.</p>
]]></description><link>http://localhost:4567/topic/1062/how-to-show-groups-separately</link><generator>RSS for Node</generator><lastBuildDate>Tue, 27 Oct 2026 09:34:08 GMT</lastBuildDate><atom:link href="http://localhost:4567/topic/1062.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 24 Feb 2012 22:00:19 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to how to show groups separately on Mon, 05 Mar 2012 22:34:46 GMT]]></title><description><![CDATA[<p dir="auto">spaces are not stripped. not sure what versions you have or what you did.</p>
]]></description><link>http://localhost:4567/post/4740</link><guid isPermaLink="true">http://localhost:4567/post/4740</guid><dc:creator><![CDATA[nicolas]]></dc:creator><pubDate>Mon, 05 Mar 2012 22:34:46 GMT</pubDate></item><item><title><![CDATA[Reply to how to show groups separately on Mon, 05 Mar 2012 22:14:38 GMT]]></title><description><![CDATA[<p dir="auto">you didn't address why spaces are being stripped out in group names. I will try using   to see if that HTML escape sequence works okay.</p>
]]></description><link>http://localhost:4567/post/4739</link><guid isPermaLink="true">http://localhost:4567/post/4739</guid><dc:creator><![CDATA[voicecarrier]]></dc:creator><pubDate>Mon, 05 Mar 2012 22:14:38 GMT</pubDate></item><item><title><![CDATA[Reply to how to show groups separately on Tue, 28 Feb 2012 02:24:07 GMT]]></title><description><![CDATA[<p dir="auto">You sort groups by dragging the box to where you want it to be shown in the FOP2 UI. The order is per user, not global.</p>
<p dir="auto">Best regards,</p>
]]></description><link>http://localhost:4567/post/4738</link><guid isPermaLink="true">http://localhost:4567/post/4738</guid><dc:creator><![CDATA[nicolas]]></dc:creator><pubDate>Tue, 28 Feb 2012 02:24:07 GMT</pubDate></item><item><title><![CDATA[Reply to how to show groups separately on Mon, 27 Feb 2012 20:50:45 GMT]]></title><description><![CDATA[<p dir="auto">By filling in the "groups' field I was able to get FOP2 to show various groups. I noticed that it put my OPERATOR group first. How did it know to do this? How does one set the order of the groups... they appear to be in alphabetical order except for the magic "operator" group.  And how come when I put in a group name of "BMW Dealership" the space gets stripped out. How does one put a space inside a group name? minus signs work of course, but a minus is not the same as a space....</p>
]]></description><link>http://localhost:4567/post/4737</link><guid isPermaLink="true">http://localhost:4567/post/4737</guid><dc:creator><![CDATA[voicecarrier]]></dc:creator><pubDate>Mon, 27 Feb 2012 20:50:45 GMT</pubDate></item><item><title><![CDATA[Reply to how to show groups separately on Sat, 25 Feb 2012 02:52:14 GMT]]></title><description><![CDATA[<p dir="auto">If you have fop2admin installed, go to the fop2 buttons page and fill the "group" field with whatever group name you want for each extension. After apply/reload , you will see the extensions grouped as you want.</p>
]]></description><link>http://localhost:4567/post/4736</link><guid isPermaLink="true">http://localhost:4567/post/4736</guid><dc:creator><![CDATA[nicolas]]></dc:creator><pubDate>Sat, 25 Feb 2012 02:52:14 GMT</pubDate></item></channel></rss>