Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Changing server name shows button "failure" instead of "saving..." #1551

Open
reloxx13 opened this issue Jul 5, 2020 · 11 comments
Open

Comments

@reloxx13
Copy link

reloxx13 commented Jul 5, 2020

When i edit a server name and hit save, instead of "saving..", the button shows failure till the server page gets reloaded.

The save is successfull, just the button text is wrong.

grafik

@reloxx13 reloxx13 changed the title [BUG] Changing server name show button failure instead of saving... [BUG] Changing server name shows button "failure" instead of "saving..." Jul 5, 2020
@Safihre
Copy link
Member

Safihre commented Jul 5, 2020

I can't reproduce it on my machine. Are you on 3.0.0?
Does this also happen on a different browser?

@reloxx13
Copy link
Author

reloxx13 commented Jul 5, 2020

Heya,
Checked chrome and edge, both work fine.

Just happens in latest Firefox 🙄

disabled theme and adblocker in ff and still happens.

sabnzbd 3.0.0rc1

@thezoggy
Copy link
Contributor

thezoggy commented Jul 6, 2020

I can confirm this happens as well with firefox 78.0.1 and windows binary 3.0rc1
I suspect this is fallout from upgrading to jquery 3.x as our version of jquery-form is a bit dated and needs updating to support 3.x -- https://github.com/jquery-form/form

Hard to confirm however since I'm not running from source on this box just yet so I cant just swap it out and confirm myself

@Safihre
Copy link
Member

Safihre commented Jul 10, 2020

The update of jquery-form didn't fix it.
Probably have to lower the jQuery version again..

@Safihre
Copy link
Member

Safihre commented Jul 10, 2020

Oh, seems this was broken for 3 years already since we started using jQuery 3.

@thezoggy
Copy link
Contributor

do you know why we even use it? (as it seems like its just for lazy coders to do ajax)

@Safihre
Copy link
Member

Safihre commented Jul 10, 2020

No clue, it's been there before I joined SABnzbd 😃 Last I can find is when you copied it from the submodule
https://github.com/sabnzbd/sabnzbd/blame/102eaa966ba1c1fd0c1c26838653a7115fb16145/interfaces/Config/README.txt#L7-L21

@Safihre
Copy link
Member

Safihre commented Jul 10, 2020

Seems you added it 😉
https://github.com/thezoggy/sabnzbd-uni_Config/blame/master/templates/_inc_header_uc.tmpl#L66-L70
And now, I am too lazy to remove it.. true 😃

@thezoggy
Copy link
Contributor

i know i used it in the universal config.. but i could have sworn that it was just a carry over from whatever skin I copied some stuff from. back in the day each skin had its own config.. it got annoying to update all of them anytime you wanted to make a change.

if it really was me, damn i should be slapped :P but right now the page just re-loads which funny enough was the 'fix' about the last time this utility was mentioned: #398

so if its broken we might as well just remove it and call it a day until everything gets re-written to be proper ajax handling

@Safihre
Copy link
Member

Safihre commented Jul 11, 2020

We only refresh the page if the name or priority changes, otherwise it's the ajax-form. So since this bug has been there for 3 years I'm fine to leave it for now.
I also don't think the backend has changed much since you made the Config, it's such a mess in interface.py it's scary... 👻

@stale stale bot added Stale Issues automatically closed because they became stale and removed Stale Issues automatically closed because they became stale labels Aug 1, 2020
@sabnzbd sabnzbd deleted a comment from thezoggy Aug 2, 2020
@sabnzbd sabnzbd deleted a comment from stale bot Aug 2, 2020
@Safihre
Copy link
Member

Safihre commented Aug 2, 2020

@thezoggy feel free to fix 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants