FreePBX 2.10 Beta – Lots of Credit to the team!

There’s lots of exciting stuff and for those of you who follow the activity going on in the trac timeline then you should be well aware of how busy things have been and how much activity has been going on by the team over at Inc., who have contributed the bulk of all the super great work to this next and very exciting 2.10 release! On the Schmooze side mbrevda has been going nuts with all sorts of great contributions though they are not the only ones as mickecarlsson has been keeping quite busy himself and tm1000 (Andy) continues to plug forward on his continuous effort to keep the endpoint manager module up to date and moving forward!

For starters, a hats off to all of these guys who have been carrying so much of the load these last few months. With all that said, the [url=/freepbx-distro]FreePBX Distro[/url] work has been going strong as well which again is a major contribution by Schmoozecom and driven by tonyclewis with lots and lots of background help from GameGamer43 (Bryan) who all to often sits silently in the background.

Ok … enough of the credits, I just want to make sure that all of you keep in mind that this project is successful because it is very much a community effort whose direction and results are a direct product of those who get involved and help make it happen!

So what has been going on? Well let me warn you that when you load the 2.10 beta be prepared for a lot of great things and some really big changes on the “look and feel” front. Let me also precede this by saying WE WANT TO HEAR YOUR FEEDBACK! This is not a “done deal” but we need to hear from you now to affect change, not 3 months after final release! (and if you do scream then, we are going to point you right back to this blog post!)

Upon loading the beta you are going to find that the whole GUI has gone though a MAJOR facelift. Kudos to some awesome work by mbrevda whose efforts started back in 2.9 to make this a reality and here we are today with a MUCH NEEDED modernization of the interface. With that said we are well aware that this sort of change may not suite everyone and further more, with a large community like we have, there is probably NO single solution that will make everyone happy. So let me talk you through this a little bit, here is a screen shot to get a taste:

First you will notice that the left navigation bar is gone and in its place is a series of top navigations with a handful of categories that now store all the GUI displays. No more tool vs. setup tab and those clunky top menu tabs as we had before! At this point I know that some of you are probably THRILLED for the refreshing new look and feel of the GUI while others of you DO NOT LIKE IT and want something closer to what we already had. As such, I want to make it VERY CLEAR that this is NOT A DONE DEAL! The re-architecting that mbrevda has done has lent itself to allow for different GUI layouts and although we have started with the proposed layout, we are not adverse to providing more than one layout if a significant portion of the community tells us it is really needed. Please keep in mind that we are looking for REAL feedback! Let’s keep the drama out of it as we have just stated this is not a done deal, and instead have some real community discussion to determine if the resources are better spent on more new and exciting phone features vs. developing and supporting a second layout more similar to the “left navigation bar” format in 2.9 and earlier releases!

In the meantime, we realize that this new layout most certainly has rough edges and we are very much looking for feedback to further improve it whether color shading suggestions or more fundamental. Another place we expect we will NEVER satisfy everyone is the menu layout on top. That includes both the names that we have currently chosen, and what modules go into which of those buckets. Trust me when I say it’s not a done deal because within the development team we are very much at odds with some of the tab names and what should go where. So … with that said, please speak up but I would request that you try to do it in a format that we can digest. Have some great ideas? – propose a full solution. Want to have a discussion? – kick off a thread with your ideas on the forums. There is time to change this so let’s make sure your input is heard!

So … despite the “eye candy” what else has happened on this release. Some of the major changes include a completely rewritten, template driven and extremely flexible backup module that dedicated many months of mbrevda’s time to create. Trying to describe the level of flexibility you have with this would be a pointless effort, go load up 2.10 and have a look. For those of you who love to add your own stuff and install various projects from around the web, you will be thrilled that you can now tell FreePBX about those so they not only get backed up but also restored with this module!

As if the Backup module was not enough, mbrevda largely rewrote the IVR module which was in bad need of some serious improvements despite its outwards appearance that made it look like it was in decent shape. The interaction and understanding of it should also be more straight forward. Yet another major component that was falling apart from the inside out was the CDR reporting engine that originally came from another project and was barely maintainable depending on outdated and no longer maintained libraries that we packaged with FreePBX. So thanks to the wonderful world of open source and the great efforts on mickcarlsson’s part for digging up a new engine that we were able to turn into a full fledge module and provide much of the needed CDR reporting functionality that is important to most users! Last to mention is the call recording capabilities of FreePBX which have been plagued by ambiguity and lack of ability to control what would be recorded and what would not. We’ve re-architected the controls that determine what to record and what not at both the extension level as well as higher levels such as ring groups, queues, conferences, etc. We’ve also replaced the builti-in automon capability (on-demand recording) provided by Asterisk with our own implementation of on-demand call recording so that we can make more attempts at controlling and honoring settings when a call gets recorded and not. So all an all, we should be well on our way to a more deterministic call recording capability!

What next? Well first of all I guarantee you that there will be bugs to flush out and feedback to listen to so that we can take this beta and really clean it up and drive it to a real release! We NEED YOUR help to start testing and providing feedback whether it be isolating the bugs or helping with the guidance on the changes that we asked you about above! The easiest way to get started will be to pull beta version with the complete FreePBX Distro that will install everything for you! Details are on this forum post.

However, for those of you wanting to get your hands dirtier or using other Distro’s out there, you can load up the tarball and upgrade as you always have. Which ever way you do it, come help us shape this release to something that is a joint effort between your feedback and those of us and you who can contribute coding, patches, testing, etc. to drive this to completion!

Philippe – On behalf of the FreePBX and Team!

56 thoughts on “FreePBX 2.10 Beta – Lots of Credit to the team!

  1. Suggestions:

    1. Add a link to the Flash Operator Panel in the FreePBX UI. I can’t find it now, except on the home page before you get to the GUI. On a related note, FOP doesn’t seem to work, even thougn it is enabled…

    2. Add tooltips to the feature codes page, for each feature code. Some of them are not obvious. For example, a tool tip that explains that *85 doesn’t work because of an asterisk bug would be nice.

    3. Add a pull-down to block caller ID (on trunks, outbound routes, and extensions), instead of relying on users to understand the tooltip about adding the word “hidden”.

    Alternatively, add that same tip to the tooltips for the Caller ID field in outbound routes and extensions. Right now, the tip about using the word “hidden” only appears in the trunk caller ID tooltip.

    4. Add a home page icon that links to the freepbx system status page.

    5. Add IVR brought me to a blank screen (same with add a backup job), but I’d done a lot of messing by then.. for example I had installed and removed the 2.9 FOP Framework, and that may have messed things up.

    Otherwise, great job. I’m old and I usually don’t like new things anymore, but this is really, really nice.

  2. 1. FOP is essentially borked. The question is how far back will FreePBX bend over to support it vs. putting those resources towards a more productive use
    2. its B E T A, there is only one way to find out…
    3. the goal of the new gui was to to increase performance, as a whole, in FreePBX. We are continuing to examine our options and see how we can make thins work even better/faster
  3. 1. I think the plan here in the next week is to remove FOP completely since it does not work with Asterisk 1.8 very well anyways.

    2. If you want to propose text for each one I would be happy to add them. Just never had the time to do this. Email them and I will get them added.

    3. I like that idea and think you should open a feature request and I will advocate it for you.

    4. Yes I agree with this. Same as option 3 I would say,

    5. Works fine for me. Just tested it again.

  4. #2- I’ll e-mail you privately on this one.

    #3- There already is a feature request on this. See Ticket 5249.

    #5- I probably need to reinstall. As I said, I loaded FOP Framework 2.9 (hoping it would fix probem #1) and so there’s a good chance that messed everything up.

  5. Custom Contexts should work in 2.10 but I have not tried it so someone will need to play with it. The only way at this time Custom Context would become a core module is for it to be really re-written as it has lots of gotchas. We cleaned it up a bunch a year or so ago but it needs a re-write from my understanding of what Moshe and Philippe have said.

    As far as FOP it will be removed from the status page and a few other places before 2.10 goes final.

  6. OK please open a bug ticket and we can take a look. We do all of our testing on Chrome and Firefox since none of us have or use IE.

    Moshe should have fun with this one. I know how much he loves IE issues.

    [i]update: We only support the latest iteration of every major browser. Please test with IE 9 before opening a ticket. –Moshe/mbrevda[/i]

  7. Looks pretty good! Takes some getting used to, but looks nice and easy to get around.

    Suggestions –

    1) Suggest Voicemail Admin to the Admin menu (since it has Admin in the name). Perhaps it should be split into two parts with voicemail settings in the settings menu, but I assume that would be much harder for little ROI.

    2) Online support & Freepbx support in the admin menu are confusing. I understand they are different, but to a newbie it may not make sense

    3) the menu item being displayed is shaded. Would it be possible to shade the active menu as well?

    4) Icon on upper left isn’t showing up on the “User Portal” screen. (using the distro iso build)

  8. Perhaps you could create a poll if people would prefer top/horizontal drop down menus, or already expanded left/vertical menu.

    While the interface is certainly more ‘clean’ and the bublier look is more modern, it really feels a lot more cumbersome to operate… menus are no longer expanded, requires a lot of mouse clicks, and the organization I agree seems very arbitrary. My opinion is that most modules are very long vertical pages, and therefore offer alot of blank unused realestate on the sides… this to me begs a fully expanded left/vertical menu.

    If you are ultimately determined to ‘clean things up’ with a top/horizontal menu, I would at the very minimum beg for the menus to appear on mouseover and NOT mouseclick. Just compare FreePBX w/ a program like Microsoft Excel or Word, where there is an inordinate number of menu items… you’re effectively burying all modules in a *long* file menu, as opposed to having (at the very least) the most often used modules available w/ a direct single-click of the mouse on a toolbar (or in this case an already expanded menu).

    Pretty form, but lacking function
    – J

    +1 Vertical Expanded

    [i]yay – Microsoft design! –mbrevda[/i]

  9. I just ran the upgrade procedures as outlined on the site, and everything is showing as 2.10, but I still have the old look and feel. I’ve restarted AMPORTAL, and cleared my browser caches. Did I miss something?
  10. I’ll download beta freepbx distro from your site, then install, but in installation process don’t ask me any password, where is a default password?

    UPD: Sorry, it’s my bug.

    UPD 2: But in the DB don’t exists any users, and I don’t login from web gui.

    UPD 3: I’m adding user to mysql, and then authorized, but I see blank page.
    This syntax:
    INSERT INTO ampusers (username, password_sha1) VALUES (‘admin’, ‘d033e22ae348aeb5660fc2140aec35850c4da997’);

    is correctly?

    UPD 4 (Final): Ok! I was decided my problem, this is a fully sql query from correct functional freepbx:
    INSERT INTO ampusers (username, password_sha1, sections) VALUES (‘admin’, ‘d033e22ae348aeb5660fc2140aec35850c4da997’, ‘*’);

    Thanks for help me. ))

  11. When I did the install, I was prompted for the root password during the install. Then after it was all done, there was a login prompt on the screen. At that point, I went to a different computer, opened up chrome, and went to (IP address of the machine I just built). That prompted me to setup the admin user, email address, and FOP user.
  12. I think that he means that he did a module update. I’ve noticed that module update on the beta includes a lot of 2.9 modules, which I assume you definitely shouldn’t process.

    Beta means beta. As Uncle Ward would say, “Remember the Pioneers!” Fiddle with it. Report the bugs. Don’t count on it working.

    Also, if you want the web interface to work right on the beta, don’t use IE 8. Use Chrome or Firefox.

  13. I wish and hope for a stable streaming MOH in 2.10. I manage PBX’s for a radio station group, and as of yet I always have problems with streaming music on hold. clunky, crashes, etc. Dahdi has always been a pain for conferencing to work, and if a yum update is ever ran it nukes the dahdi. I am a Huge FreePBX fan and I love the new gui screenshot. I just would love a stable solution for shoutcast,Icecast streaming MOH I would even go as far as to say that I would purchase a module if it meant that it would work and be maintained.

    Thanks for all the hard work!!


    [i]Josh – the MoH module definitely needs some TLC. For sponsorship opportunities (including getting your favorite features in!) you can contact us via Professional Support. –mbrevda[/i]

  14. Josh

    The issue with streaming MoH is not FreePBX but asterisk. It has to transcode that audio in real time and asterisk struggles with it and puts a huge load on your server. I would never run streaming MoH on any production server for this reason.

    Also with our Distro you can yum update all you want and it will not break DAHDI as long as you do not modify the yum repos or add your own yum repos.

  15. It seems crazy that Asterisk still chokes on streaming MOH. isnt Asterisk designed for audio? anyway enough ranting. Just irritating when customers which happen to be radio stations want their stations as the MOH.


  16. Josh,

    If you allow any customer to use a radio station as their MOH, you open them up to a significant risk that one day a letter will arrive from ASCAP and their lawyers demanding significant royalty payments, civil penalties, and attorney fees for copyright infringement.

    Even if it ever becomes technically possibly, I recommend, in the strongest possible terms, that you never, ever, ever allow a radio station to be used for MOH. Ever.

  17. @bucasia. Thanks.
    @FreePBX. I am not crazy about the new menu structure and I think you need to reorganize things a bit so that it makes sense. e.g.

    1. The connectivity tab is a good idea but IMHO it should include extensions, follow me, ring groups, queues and anything that affects the call flow.

    2. The FreePBX system status should be in the Admin tab or alone since it’s the HOME button.

    3. In the end I am much more comfortable with the old interface and would miss it if replaced with the new menu structure.

    4. If this is a done deal maybe include a menu.conf file that allows users to customize the interface so if I want Asterisk CLI in reports I could move it there by simply changing a setting in the menu.conf file.

  18. It’s not a done deal and the hardest and most difficult discussion has been what to call the top level menu tabs and what to put in them, as I said in the blog.

    The menu.conf is a good idea. Most people do not know it but in 2.9 and some earlier releases there actually is an ini file (I forget the name) that lets you do such changes as well as change the name and which tab (tool vs. setup) they go into, or even create a new one such as Favorites. This was not done on this new layout mostly because no one got to it yet and also because of our fantasies of having a module that let you do that via drag-and-drop.

    So … I do plan on adding back that ability at least to some extent assuming it is not too complex which I assume it will not be. However, that does not mean that the current buckets and categories are a done deal. It would still be really helpful for some people who have great ideas on how we may re-bucket the display pages and/or re-label the categories to maybe present a full proposal. What you presented is much appreciated and I do see some of the logic in it as well. It’s the beginning of what we are looking for so we can come up with something that makes logical sense.

    Another issue we struggled with is how many tabs to have. The fewer tabs, the more menu items under each which can become a problem. The more we have, the more horizontal space it takes of which I don’t have a good feel how many is too many, as I have a 27″ monitor and often have a very wide browser window open. There’s also the consideration that when localized, the category headers can get much longer in some languages thus taking up more space. However, feedback on if we can/should have more tabs would be useful. I’m guessing less would be a problem no matter what?

  19. Personally I like the menu on the left. Without it the screen looks empty. I just think that “TOOLS” should have been on top with the old menu structure instead of a tab on the left.

    Here is how I would organize the new menu, regardless on where the actual tabs end up but I would put “CALL CONTROL” on the left and the other menu options on top. This structure is based on how I navigate the existing menu. What I use and what I don’t use. E.g. My home screen is “System Status” so it deserves a stand alone tab. My other (most used) screen is CDR Reports so it deserves a tab too.

    ADMIN = System Status

    Inbound Routes
    Outbound Routes
    Ring Groups
    Queue Priorities
    Time Conditions
    Time Groups
    Zap Channel DIDs
    Follow Me

    REPORTS = CDR Reports

    System Admin
    Module Admin
    Voicemail Admin
    Advanced Settings
    Asterisk Sip Settings
    Fax Configuration
    Asterisk API
    Asterisk CLI
    PHPAGI Config
    Custom Destinations
    Custom Extensions
    Feature Codes
    System Recordings
    Music on Hold
    PIN Sets

    Custom Contexts
    Custom Contexts Admin
    Extension Settings
    Backup & Restore
    Asterisk Phonebook
    Asterisk Logfiles
    Online Support
    FreePBX Support
    CallerID Lookup Sources
    Asterisk Info
    Weak Password Detection
    Dundi Lookup
    Misc Applications
    Misc Destinations


  20. Thanks for the input!

    As mentioned, everyone will have differing ideas on what makes sense and there will never be a ‘right’ solution. However, there are more and less intuitive ones for sure.

    The System Status screen I do agree needs to be more obvious. We are currently discussing if we can make the icon to the left of the navigation screen be a link as well that would take you there by default (but re-configurable in Advanced Administration if so desired).

    In the meantime, I have returned the freepbx_menu.conf ability back to this new menu structure though nothing has been published yet. You can see the changes in r12718 and grab the latest copy of menu.php if you want. I’m hoping that with this we can get some people to start up a thread (or multiple) in the forum and you can use the freepbx_conf.ini file to communicate what makes sense and visualize it on a real system. In any event, it will be available as it has for the last few releases to do your own customization regardless of what we come up with as a final for this layout.

    We’ll get that published within the next few days but it can be grabbed for now if anyone wants to play with it.

  21. 1. Will FOP continue to work?

    2. Are there dangers to upgrade to beta? Is there anything going not to work probably?

    3. Menu should be like in the past on the left. Having to click each time to open drop down menus are a waste of time. It is faster if you see all the options in front of you.
    Moreover, javascript menus do not work well and fast, If i had to connect from my smart phone to make a setting. Even it worked, I would have to scroll up and down and most probably the menu would get autoclosed till I reach the option I want.

  22. As stated in my post, the “customers” are AM and FM radio stations and they are set up with ASCAP BMI, etc In this rare occurrence they are legal as they pay all applicable fees associated with the content. I do agree that this would not be a good idea in most instances. However it would be a used feature among many radio station clusters providing Asterisk could ever do this reliably.


  23. Recently I’ve been searching for a web GUI for Asterisk that is much simpler than FreePBX to be able to offer customers as an alternative, for those that do not need all of the functionality.

    I really like FreePBX but it can be overwhelming when starting out as there is just so much of it.

    However, thinking about it some more, I’m wondering if FreePBX could be adapted to provide a much simpler interface quite easily.

    With a master BASIC/ADVANCED switch at the top of the screen it could be possible to switch a lot of the advanced features off to provide a simplified interface.
    I would see the BASIC interface to have the goal of allowing users to get extensions, incoming and outgoing calls working.

    It could include the Extensions, Trunks, Inbound Routes, Outbound Routes and CDR menu options only. Also, within those menus a lot of the options could be hidden. For example in the Extension menu page there would be maybe 5 or 6 options – extension number, secret, voicemail on/off and not much more.

    This would give new starters a real chance at getting calls going in and out of the system quickly. Once they were comfortable with how FreePBX worked they would switch it in to ADVANCED mode and get all of the options.

    I’m not sure how easy this would be to implement, or if the underlying architecture allows for menu options within pages easily allows options to be flagged as advanced, and hidden.

    Does anyone have any thoughts?

    [i]great idea, and we’ve been pondering it ourselves for some time. The main problem is that there isnt any pluming for it and adding some would be rather complex… –mbrevda [/i]

  24. 1. We originally had a “call flow” tab in there, which contained just that – anything that affects call flow. Personally, I’m all for it, but we figured well let the peoples add some weight to the decision.
    2. system status is actually just a module – like any other. It just so happen to shown by default if no other module was selected, but it is by no means the homepage or default page.
    3. Most people are more comfortable with the home-y tried-and-tested. Our goal here was not to undermine that comfort and security, but rather to make some significant backend changes that greatly improved the performance of FreePBX. The gui changes were just collateral (which – dont get me wrong – were pretty please with and proud of!)
    4. While that would partly affect performance (not in a huge way, but every little bit counts) that is something that we can look in to
  25. CSS would work great, if there was pluming in place to generate said css in a sane and efficient manner. In the mean time, some module (like extensions) can have certain sections collapsed/hidden by default. At the moment, this must be hardcoded, but I think there are sections that we can all agree that dont always need to be shown. Feel free to campaign for that
  26. I have Asterisk 10.0 Beta loaded on a test machine and thought I’d start flushing out potential issues both with Asterisk and FreePBX 2.10. However, 2.10 won’t allow installation on Asterisk 10.0. Do you expect to allow this in the near future?

    [i]FreePBX does not currently support asterisk 2.10, but that doesn’t mean that we won’t try to if it means adding just a few tweaks. Feel free to open a feature request –mbrevda[/i]

  27. kenn10,

    I think there should be a switch if you use install_amp to force it to install with 2.10. We plan on supporting it and I think there have been some who have tested it. Try that route as I expect there will probably be minimal issues.

  28. Have not had a chance to play with the beta GUI yet. But, from the screen capture above showing the Lateral menu, I would place a ‘yeah’ vote for it. I tried unsuccessfully to find a way to hide the left menu bar in 2.9 in order to print Peers, SIP Info, Subscriptions, etc. under the Asterisk Info, WITHOUT the last 4 columns being cut off by the printer. This would help in that end.

    Also, as with ANY change, there comes with it responsibility of us recipients of a FREE product to make “some” effort to learn a different (and most likely improved) way of doing things (ie location, names) than the way they’ve “been use to doing them.” I’m sure we are capable of picking up new habits just as we did the old ones. As has been already stated, there is not going to be a perfect solution for all (there are just to many of us). I do like the idea of a condensed number of possibilities of where the items could be searched for, however. For us that are limited to screens smaller than 27″ (hahaha), eight might be the max you’d want to span across the top. There is just SO much good stuff, it’s hard to decide how best to condense it! ;]

  29. Just a few quick updates on things we are doing or thinking about doing to streamline the menu…

    First off, I know mbrevda is revisiting what it would take to make hovering over the top menu items allow them to drop down. I don’t think there is anyone who wouldn’t like that, I just know it is something discussed well before this blog post and we knew that it was non-trivial given the jquery library being used to generate it.

    Another thing I just did to manage the valuable real estate up there was get rid of the “User Panel” button. Still want it, no problem, I just made a trivial module that will reinstall it right where it previously was. The reason I removed it by default is that most Distro’s including our own provide a direct path to it when first entering the distro.

    Want it as a sub-menu, just use the freepbx_menu.conf configuration file I mentioned above to move it elsewhere.

    Now there have been requests for other top level menu items. I modified my recent changes so any category that has only a single entry under it will be transformed into a top level button just like “User Panel” is at the moment. So if you want CDR reports or FreePBX System Status up there by themselves, you can just use freepbx_menu.conf to do it.

    Another thing we are discussing in real time is where we can move the Languages menu that is also taking valuable real estate. It’s something that you change once when bringing up FreePBX since after that it is retained in your session. Advanced Settings won’t work as that would changes it system wide, but I’m sure we will find somewhere to put it that will make it easy to get to but not take up all that real estate. Other suggestions are welcome.

    Anyhow … all these changes will be pushed out soon in a Framework update, there’s just currently something broke in svn that we need to track down before pushing out an update. If you want to play with the above though, just grab menu.php as it’s all contained in there.

  30. I have no great love for FOP specifically, but we heavily depend on having some sort of call status display at each user’s desk. (Some call control functions would be nice, too, but not essential; we never got those working right on FOP.) Is there a recommended alternative (preferably free or very affordable) that is expected to be able to work with 2.10 (and Asterisk 1.8)?
  31. Hi I updated a 2.9 install that was loaded from your ISO. Did it from teh update links provided herein. cat /etc/asterisk/freepbxdistro-version shows

    When I try to create an IVR and make one of the options to go to another IVR (sub IVR), when you push the option for the sub IVR it just repeats the message of the Parent IVR.

    The IVRs that came over on the update, that heretofore worked, exhibit the same behavior.

    If you dial the number of the sub IVR twice you also get teh message, “Sorry you are having trouble. Goodbye.” Then it hangs up.

  32. franklin,

    please either start a new thread with the issue and provide a CLI trace going through this so we can see what is going on, or file a bug and provide the same trace.

    There was a recent change to IVR that might be related. Checking the code I don’t see how the change would not be operating properly but a trace of your issue would help determine that or not.

  33. I have moved this question/comment to general question area in a new post.

    I recently upgraded to 2.10 with all the updates from 2.9 and am struggling with the new CDR report. It is hard to read, the columns in the old CDR included the “name” of the caller. I had to change the color of my screen so that it was not just white background with tiny black letters. At least now I get some contrast between the columns and lines, it is not all white. If I increase the size of the print the rows will double in size. Is there a way I can choose the columns in the cdr report that I want displayed? I would add caller name and remove “system”, “userfield”, “account” columns.

    I am sorry for complaining, but the old system gave me exactly what I wanted in clear to read columns and graphs if I wanted them.

  34. just playing with 2.10 and freepbx_menu.conf
    I am trying to move the “Freepbx system status”
    to Favorites with menu.conf but it does not move.
    Seems to be the only item that can not be moved.

    My entry is:

  35. Yes. That works. Thanks.

    I guess it confused me that [dashboard] does not use the same naming convention as the other modules i.e. it should be [index].

    Why not use the tango.png image to link to dashboard?

  36. Same problem to move around module admin. The name “modules” does not work. Do you have a list of names for the different modules? Most seem to use the display=names e.g. “findmefollow” but some like dashboard and modules don’t so we need the actual names to move them around in freepbxmenu.conf
  37. dcitelecom,

    well to a large extent you happened upon a couple of the “special case displays” that would appear to not follow more of a norm for reasons that are not worth getting into here.

    However, to answer your question, the name usually is the “display” name if it weren’t for these two exceptions. Authoritatively you can determine the correct name by looking in the module.xml module. In the case of the System Status page you will see:
    FreePBX System Status
    so in that case it is the “dashboard” xml tag which get’s mapped to “index” based on the above attribute. In the case of Module Admin, not really being a module, it is controlled by the “module-builtin.xml” file and in there you will notice:
    Module Admin
    so you would use “modules1” for your section. There used to be module1 and modules2 because this used to be on both the tool and setup tabs, when we took away that concept we never renamed it to simply “modules” which we could (and maybe will) do.

    I hope that helps.

  38. Thanks.
    That solves my issue.

    Many thanks also for freepbxmenu.conf
    My menu is now exactly the way I want it
    with all the day to day stuff right where I need it
    and the other modules out of the way or completely removed.

Leave a Reply