What? When did I do that? I’ve been working with users all day on this. I even provided solutions. Fixes and wrote out the cause.
This issue was actually resolved 24 hours ago. Someone said that 12 hours ago. I worked alongside two other users who had similar similar issues but the grand issue was resolved 24 hours ago. Where did I not provide assistance.
The solution is even marked as the first response.
Messages like this discourage developers from developing in open source when they’ve clearly been trying to help all day.
Please consider your words before posting in the future. Perhaps read the thread before blindly making a statement.
Andrew - your help is greatly appreciated. Please just ignore Ralph. As you mentioned, he probably replied before reading the whole thread, and seeing that there was a fix already.
I apologise if my choice of words was inappropriate. My point though was that the solution offered assumed a good deal of further knowledge.
I implemented the solution successfully but further separate research about the method was required by me.
For example: Use an access program to get SSH to the system like Putty and enter the following commands etc as described by Pitzkey
This is probably of no interest to skilled developers but of immense value to those trying to develop skills and have come very late to the freepbx party.
I would add that I have placed a question elsewhere that has never had a reply so that frustration spilled over into this thread.
I am absolutely delighted with the entire system and the learning I have had to do to get it installed and implemented.
I ran the commands bellow and that got the Admin dashboard up and going. I am still having the class pico feed error under UCP. Is there a different fix for that?
fwconsole ma upgrade dashboard
Once done, run
fwconsole reload
Clear your browser cache and try accessing the GUI
Bug report in, but wondering if somebody can suggest CLI downgrade method. Need to get back to at least 14.0.3.3 but GUI is inaccessible after most recent update last night.
PLEASE NOTE: THIS ERROR HAS APPEARED ON 5 PRODUCTION SYSTEMS ON THREE SEPARATE CLOUD ENVIRONMENTS (AWS, Vultr, DO) AFTER THE MOST RECENT FRAMEWORK AND/OR DASHBOARD UPDATES - PROBABLY DASHBOARD.
Module(s) requiring upgrades: dashboard
Upgrading module ‘dashboard’ from 14.0.4 to 14.0.4.1
Asterisk is still processing calls but GUI is inop. Checked OS and fwconsole - all modules and apps up to date.
Over five people opened bug reports on this in the Jira Bug system. All the bugs were closed saying that they were duplicates of each other, that the bug has been fixed, gave no indication how we can fix our installations, and referred us to this forum.
For me, this is a showstopper. I cannot install my system or do anything with it.
@hjbtyvv was this post a rant, or are you still stuck? Did you not review the linked thread immediately above you which contains the fix in a few places?
SOLVED - there seems to be a problem with the consist when you fwconsole ma updateall. Doing this gets you framework 15.0.1.19 which is broken. However, when Andrew finally stopped being snarky and just telling people to search and sent fwconsole ma update framework dashboard ucp the problem was fixed. Issuing the update command specifically for individual modules caused the current modules to load while updateall did not.
Users are not always ranting lunatics. Frequently, predominantly, but not “always.” Until the consist for updateall is fixed, issued the explicit module upgrades and everything will be okee dokee.
11 people have open tickets on this. All duplicate tickets. I can’t keep track of putting resolutions in each of those tickets so I bounce them back to the original issue. Which now has a resolution and a link to this forum thread.
If you upgrade all of your modules you’d not run into this issue. It’s only when one is upgraded like framework or dashboard by itself. Exception on 15 where this was not published yet.
I downloaded the iso and installed it, then did raspbx-upgrade and ran into this problem. So now I have done fwconsole ma upgradeall, which seems to upgrade things that raspbx-upgrade doesn’t upgrade. What is the difference between the two?
Anyway, after doing fwconsole ma upgradeall, the framework and dashboard are at the right version, but ucp seems to be missing. Is this a problem?
root@raspbx:~# fwconsole ma list | grep framework
| framework | 14.0.4.1 | Enabled | GPLv2+ |
root@raspbx:~# fwconsole ma list | grep dashboard
| dashboard | 14.0.4.1 | Enabled | AGPLv3+ |
root@raspbx:~# fwconsole ma list | grep ucp
root@raspbx:~#
Let me tell you a story. A little over 48 hours ago I talked with my boss @GameGamer43’s about what we can do to work on performance in FreePBX. Along with the wonderful Zulu team we discussed different ways to get past our bottlenecks, one of the ideas we brought up was to attempt to start using caching.
So to achieve this we added a single library Doctrine Cache. When adding this library to 13 we had to merge it into 14. To do that we had to rebuild composer (a library autoloader we use) and there is where it all went wrong. Mainly because the library Pico Feed was deprecated but not only that it was removed entirely from packagist. A few of you clever folks figured out you could find a fork of Pico Feed and put it into the PHP include folder and it would work, we thought about doing this for FreePBX but forks can have malware in them so we didn’t want to risk it, along with it also wouldn’t be part of Composer which is what we wanted.
So we went looking for a new RSS feed reader and came to SimplePie. To get this to work we had to add SimplePie to Framework and also reference it in Dashboard and UCP. Since I can’t go back in time and make an older version of dashboard and ucp depend on a newer version of framework I have to accept that this will unfortunately blow up in people’s faces because either framework will be too high a version or dashboard/ucp will be too low a version.
Then I ended up dealing with duplicate tickets yesterday. Over 11 of them all the same without referencing the oldest ones or cross referencing and so I incorrectly and wrongly shutdown and close two related tickets dealing with FreePBX 15. While the issue was related it was not the same as yesterday and I incorrectly closed the two tickets as duplicates and asked the two users to search the ticket tracker. Once I realized it was actually because the Framework fix wasn’t in FreePBX 15 I immediately went to resolve that. When I did I posted in both of the tickets, then I came here asking people are more information, if anyone else was having any errors.
From there it has spiraled so out of control and for that I am closing this thread. If anyone has any issues related to this feel free to open a new thread but I think we are done here