Dashboard empty and non-manageable after update from 24.7 to 24.7.1

[rackenthogg]

I mean like, if you would like to signal that you have an issue, open it on github.

Maybe this change can be reverted for better browser compatability.

But without somebody raising the issue who uses alternative browsers, its harder to justify the need for it. So please raise your hand.

I am using only non-Microsoft and non-Chrome browsers. Same in company I work for (decided by IT higher-ups for security reasons).

OPNSense devs should not experiment with fancy gadgets which are aimed to be a weapons in war of Google with its competitors. And right now I can't even see the vital stats and states of OPNSense.

[Monviech (Cedrik)]

Well then explain your usecase in the ticket I have raised. Its up for discussion.

[cookiemonster]

I have just talked to the Palemoon core dev (yeah I know them, quite random that Palemoon pops up here) and the browser does not support this feature:

Code Select Expand

<script type="importmap">

It was added by the OPNsense in this commit:

https://github.com/opnsense/core/commit/c73f63c3fa7271f28192d66f8a6f1280e0ca0c2c

This makes the Dashboard totally incompatible with Palemoon in 24.7.1.

They lack funds to implement this feature since it is very complex and tricky. They need more monetary support. They have added an issue to their core repo. I'll link it here soon.

Please support this browser if you use and like it, there are not many alternatives out there anymore.

https://repo.palemoon.org/MoonchildProductions/UXP/issues/2556

I mean like, if you would like to signal that you have an issue, open it on github.

Maybe this change can be reverted for better browser compatability.

But without somebody raising the issue who uses alternative browsers, its harder to justify the need for it. So please raise your hand.

Hi, tickets are not my world, how about you raising the issue and link it with this thread? :-)

Have no paypal (and don't trust it), so have to find adifferent way to support palemoon project...

Well then explain your usecase in the ticket I have raised. Its up for discussion.

Wow. I'm not affected but thanks for doing this Moviech. You've gone well out of your way to help.
I imagine many would have understood if you had insisted on the issue/ticket being opened by the user in github.

[chemlud]

Discussion was ended with "won't fix". That's why I don't waste my time with "tickets" and alike.

My time is little...

[doktornotor]

My time is little...

Well I'd say the same is valid for OPNsense developers. These browsers have virtually non-measurable user base, (literally) a couple of developers and contributors. Keeping up with the web standards development is apparently not a realistic goal for such projects.

Dunno, maybe the Palemoon & co. guys should rebase their forks (of other forks) once again - since otherwise it's just reinventing the wheel and a lost cause... But this seems to be sort of religious topic everytime it comes up - not just here, see this reddit thread, e.g.  ;D  :o

[Patrick M. Hausen]

I am using only non-Microsoft and non-Chrome browsers. Same in company I work for (decided by IT higher-ups for security reasons).

That does not rule out Safari and Firefox so you still have two options supporting current standards.

[cookiemonster]

It wasn't ended with "won't fix" as far as I can see. (my emphasis). It seems more like "put something there official" so we have the official item for discussion amongst devs.

I mean like, if you would like to signal that you have an issue, open it on github.

Maybe this change can be reverted for better browser compatability.

But without somebody raising the issue who uses alternative browsers, its harder to justify the need for it. So please raise your hand.

Discussion was ended with "won't fix". That's why I don't waste my time with "tickets" and alike.

My time is little...

You see, this is where I find it strange. Opening a ticket in github takes a few minutes. That is the system used by the project. Strange for me is the view that tickets are a waste of time. I guess you've never had to deal with support services that require a ticket. Not optional, one must be raised, regardless if they have forum or not. Forums are for most companies not a support system, and if you were to comply with best practice -for example- ITIL, there must be a system of record with "requests", "incidents", "changes", and the rest. But if you haven't and all places you require your issue to have attention by someone in the organisation accept a forum post, fair enough.

Not picking on anyone, just honestly I find it hard to understand we're using a product, some of us for free. Then we have a very niche problem, we report/query it in the forum and when asked to spend a few minutes to log it in github, we say we have no time to waste with doing that.
So the new staffer goes and does it himself after hearing "Hi, tickets are not my world, how about you raising the issue and link it with this thread? :-)" . That is just taking whatever it is to a whole new level.
Moving on now, I sound too preachy now.

[franco]

I'll just leave this here. https://github.com/opnsense/core/issues/7777#issuecomment-2293192128

[franco]

Ok here we have it. Nobody bothered to report back on this. It really can't be that important.


Cheers,
Franco

[chemlud]

tbh, I simply don't use the Dashboard anymore. Have an empty landing page for GUI and that's about it. Most info can be retrieved from some other place, rest is gone with the wind.

No offence intended.

[franco]

I'll ship this when someone who asked for it tries it. Not before.


Cheers,
Franco

[doktornotor]

Did some testing. As for results, see the linked Github issue. I won't spend any more time on this. Who wants this working needs to produce some effort of their own to help with this.

[rackenthogg]

Dashboard is extremely important to me. How to test it? My current OPNSense build is the buggy one (OPNSense 24.7.2 "Kernel panic") reinstalled on UFS filesystem. How to install test build to check the dashboard? Is it in development repo?

Ok here we have it. Nobody bothered to report back on this. It really can't be that important.

Cheers,
Franco

[doktornotor]

Dashboard is extremely important to me. How to test it?

https://github.com/opnsense/core/issues/7777

No test build, no development repo, simple patch.

[rackenthogg]

Dashboard is extremely important to me. How to test it?

https://github.com/opnsense/core/issues/7777

No test build, no development repo, simple patch.

My eyes are full of tears of joy. Widgets works on older Firefox, Palemoon and Basilisk. They are also editable: I can add widgets.