@cagatay sorry for late response. This looks too be one of the widgets, and I’m wondering if you have custom code that targets this.
Had this recently happened after an upgrade or other changes?
@cagatay sorry for late response. This looks too be one of the widgets, and I’m wondering if you have custom code that targets this.
Had this recently happened after an upgrade or other changes?
@DownPW the FA library was missing with no paths defined. I’ve set these in the headers and uploaded the source, including necessary shim files which resolves the issue.
@cagatay Just looking at this now. Do you have a FA Pro 6 license, or are you trying to use the free version? It’s not immediately clear, and the directory structure on your server is a mess to be honest. Not sure what has happened here.
EDIT - I have it working. DM me.
@cagatay if you look in the console (developers console in browser) do you see any error messages being returned?
Linux is case sensitive, and it’s possible to have the same filename and folder name in upper and lower case.
I suspect this might be the issue, but I could be wrong.
@cagatay The most reliable way to upgrade Node.js on Ubuntu depends on how you originally installed it.
If you already use Node Version Manager (NVM), upgrading is simple. NVM allows you to keep both versions and switch between them if needed.
nvm install 22nvm use 22nvm alias default 22node -vIf you installed Node.js via apt using the NodeSource repository, you need to update the repository script to point to the new version.
sudo rm /etc/apt/sources.list.d/nodesource.listcurl -fsSL [https://deb.nodesource.com/setup_22.x](https://deb.nodesource.com/setup_22.x) | sudo -E bash -sudo apt-get install -y nodejsnode -vIf you have npm installed, you can use the n interactive manager.
sudo npm cache clean -fsudo npm install -g nsudo n 22hash -rsudo.node -v still shows version 20 after upgrading via NVM, restart your terminal or run source ~/.bashrc.apt to nvm, it is best to sudo apt remove nodejs first to avoid path conflicts.@DownPW I tend to stay at least one release behind intentionally to ensure maturity before upgrading - unless there is a good reason to do so immediately - such as identified vulnerabilities
@cagatay what is in the nodebb log?
@crazycells I did see something similar to that article, yes. I never fully understood why anyone would want to give unfettered and complete access to AI without first understanding exactly what it had control of, and what it intended to do with that access.
This isn’t the first “horror story” and it won’t be the last.