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

Tokenizer broken since 19.7.5 #3760

Closed
mimugmail opened this issue Oct 12, 2019 · 16 comments
Closed

Tokenizer broken since 19.7.5 #3760

mimugmail opened this issue Oct 12, 2019 · 16 comments
Assignees
Labels
bug Production bug
Milestone

Comments

@mimugmail
Copy link
Member

Hi,

related to opnsense/plugins#1537 I checked the functionality of this field and as soon as I hit return, comma or whatever to tokenize the value, it's gone. I checked on different places like FRR BGP Networks field, also Whitelist filed in Maltrail plugin. Everywhere the value is gone (just in time when trying to tokenize, not saving).
Maybe it's related to this:

o ui: fix tokenizer reorder on multiple saves

I doublecheck with 19.7.4 where everything works fine, also when reverting back it works again.

Maybe worth considering a hotfix release :(

@fichtner fichtner added the bug Production bug label Oct 12, 2019
@fichtner
Copy link
Member

Which browser... all browsers?

@mimugmail
Copy link
Member Author

Chrome latest in Windows. I didnt test others as it was reproduceable via revert. I can test later today

@AdSchellevis
Copy link
Member

@mimugmail it's probably this a4217d8, strange it didn't popup on my end when testing, maybe it only has an issue if there's no content in the field. I'll have to check

AdSchellevis added a commit that referenced this issue Oct 12, 2019
a4217d8 calls tokenize2() before it seems to be inititalized, lets check for content before calling clear.
@AdSchellevis
Copy link
Member

@mimugmail can you try 7a5a271 ?

@mimugmail
Copy link
Member Author

@fichtner also happens to Firefox 69
@AdSchellevis patch works fine on my end, thx! :)

@mimugmail
Copy link
Member Author

opnsense-patch 7a5a271

For Forum linking

@AndyX90
Copy link
Contributor

AndyX90 commented Oct 12, 2019

After the patch i am not able to open the add-alias window.

@mimugmail
Copy link
Member Author

Can you switch browser? For me it works fine.

@AndyX90
Copy link
Contributor

AndyX90 commented Oct 12, 2019

I have tried with patch in Firefox and Chromium. Same result. Reverted to 19.7.4_1
It was a fresh installation.

@lazynooblet
Copy link

Using Chrome this patch worked, thanks :)

@P2AK
Copy link

P2AK commented Oct 12, 2019

The patch also doesn't work for me when using Firefox, Chrome or Safari on OS X. The alias I'm trying to edit also appears empty the first time I open it, but if I hit cancel and re-edit it, then the alias shows its content. I still can't add anything new to it after it shows its content though.

@lazynooblet
Copy link

I applied the patch to OPNsense 19.7.5-amd64. I manually adjusted opnsense.js using the diff page 7a5a271

@fichtner fichtner added this to the 20.1 milestone Oct 13, 2019
@fichtner
Copy link
Member

I'll reopen for now. It seems safer to issue a revert of the original fix for a hotfix release today and then reassess the situation, ok?

@fichtner fichtner reopened this Oct 13, 2019
@mimugmail
Copy link
Member Author

Revert and hotfix sounds good :)

@AdSchellevis
Copy link
Member

revert and hotfix is ok, but someone still should test master which reproducible issue 7a5a271 has (if any), Most of the time these reports come from improper installation or issues reloading the page. (I'm quite certain the patch fixes the original issue, leaving the issue open without new evidence likely wouldn't result in other outcomes).

@fichtner
Copy link
Member

Ok, closing and picking this back up for 19.7.6 backporting unless somebody points to an issue with the latest change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Production bug
Development

No branches or pull requests

6 participants