You are here

aredn 3.15.1.0b04

9 posts / 0 new
Last post
wb6tae
aredn 3.15.1.0b04

On the Port Forwarding, DHCP, and Services page, under  Advertised Services:

If a space is entered into a service Name any attempt to Add or Save Changes clears the page and then hangs (no new screen is displayed) and no error is reported.

I believe if spaces are not allowed in service names, then attempts to define a service name with an embedded space should result in either the page being re-displayed with an error message or the space being replaced with a "-" or "_" .

 

K5DLQ
K5DLQ's picture
Can you post a screenshot of

Can you post a screenshot of the actual data that you entered?  I just tried it with "test test" as the service name and it added, then saved successfully.

Thanks

wb6tae
Very odd

I tested the problem several times and even rebooted, and kept getting the same problem. But, when I just tried, it didn't happen.

HOWEVER, try this, create a service test_test, add and save it.  Now, replace the "_" so you have "test test" and click save. That hangs and keeps hanging until you delete that entry and reenter it.

Ya, I realize we can't really edit names... But, then the GUI shouldn't let us, or should offer an update option.

KG6JEI
Haven't tested this yet, but

Haven't tested this yet, but incase it becomes relevant what browser (including version ) and operating system ?

wb6tae
Browser info

It was Safari 9.0.1 on MacOS 10.11.1.  

K5DLQ
K5DLQ's picture
I just tested on Safari 9.0.2

I just tested on Safari 9.0.2 on OSX 10.10.5 and cannot replicate.

Can you provide a screenshot with the exact data that you are entering?

 

wb6tae
screenshot

There is not much to take a screenshot of.  The input data is too long to display in the input text boxes and then once I click Add or Save, the screen just clears and never comes back until I click the back arrow, at which point I see the input is lost.  I will try again tonight to see if I can give you better instructions to create the error. I will also try another browser.

K5DLQ
K5DLQ's picture
ok thanks.  I've tried on

ok thanks.  I've tried on Firefox, Chrome, and Safari.

Are you using:  localnode.local.mesh:8080 or callsign-node-name.local.mesh:8080 or callsign:8080  ?

 

wb6tae
it was...

It was callsign-node-name.local.mesh:8080  But, I can no longer get it to break. Very odd.  Oh well, probably a complex set of circumstances that are no longer in place and, hopefully, hard to treplicate.

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer