@gtj0

This should clarify:
Screenshot of Object Model from DWC

8f83b5fe-4bcc-4c0d-a6eb-593c6e4afc24-image.png

Relevant setting on config.g (global.zprobe_index = 1)

;Setup BLTouch as probe 1. This is to allow probe zero to be free for analogue sensor e.g. simple piezo echo "Setting BLTouch" ; K = probe number P= probe type R=Settle time before probing H=Dive Height F=Probe Speed ; T=Speed between probes A=Max probes at each pont S=Repeat deviation M558 K{global.zprobe_index} P9 C"io2.in" R1 H10 F120 T6000 A5 S-1 ;probe 5 times and average M950 S{global.zprobe_index} C"io2.out" ; This is the mod probe - used for deploy and retract G31 K{global.zprobe_index} P25 ; set trigger threshold M280 P{global.zprobe_index} S160 ; reset any error conditions```

@stuartofmt said in Possible Issue with v3.5.0-beta1:

As a side note, I have noticed that naming the config file xyz.js (instead of xyz.json) makes no difference. Or at least it seems to make no difference.

Now that I think of it, yeah. Originally, I was fetching the config using the old javascript Ajax calls which forbade retrieving code "for security reasons" and required the awful JSONP workarounds. When I did the big refactor a few years ago, I switched to dynamically updating the DOM with a "script" element which caused the browser to just retrieve the config file like any other javascript file. I forgot all about that until I just looked at the code. 🙂

@gtj0
If it's any consolation ... err ... what was I going to say?

@stuartofmt said in v3.2.5-beta3 not recognizing themes:

I just got a chance to look at the beta3. While it now mostly recognizes the configFileSettings - it ignores the theme_name setting and defaults to Cuerulian.

P.S. I only tried Darkly.

I've been using beta2 without any issues in other areas - so the rest of the beta does look solid. I'll continue with beta 3 but using the full url invocation method.

Heh. The bootswatch folks actually changed the Darkly theme to be not so Dark.
Anyway, I thought I fixed that but I guess not.

@garis That's bizarre...
85aa5f0e-124f-4e5b-8cbf-86ef79e106b7-image.png
That URL should look have the password appended like
http://192.168.1.202/rr_connect?password=reprap

I'm investigating.

@stuartofmt Yeah that's kind of the logic I use but there's a chicken and egg thing going on because you have to find a config file before you can get the settings out of it but you have to have some settings already to know where to look.

I think I have it working now but I'm going to wait until tomorrow and test it again before doing a beta3.

@Nathan116 I've done it with both the same and different configs. This issue isn't something I've seen before. Might need a tweak to the DSF web server. Let me investigate.

@jnofsinger No problem!

@stuartofmt Gotcha. It's not really insecure since you control both resources.

I very much appreciate all the hard work.

Thanks for the clarification on the two versions.

What happened was that I copied the index.html file from the prior version over and that's where it picked up the back rev label 🙂

Gotcha. Let me investigate.

@stuartofmt Yeah, I'm really sorry about the name changes. It was work I did back in May that I never released and I just lost track of it.

I'll get that bug fixed this afternoon.