Could you restart with logging make some selections and attach the log file as described in:
Bug report filed with logging…
@Brad, when you are ready to upgrade your machine please send me a price and keep me in mind, looks like an awesome machine with the four Thunderbolt 3 ports. I want her.
Brad I meant attaching the log files… not necessary creating a bug report post
Brad,
Is the page your are working on maybe from a remote site/remote target? Using HTTPS?
Can you open it again with local target? Or try some different local projects.
Hmmm, it appears to be at the site level. Also appears to be an issue with sites on one server. The two sites I have on our main server do not work. Unfortunately that is the server that 99% of my work is done on.
Works fine on my personal site or sample sites. Why would it not work on our server? It was working before the update.
Using Bootstrap local as the framework.
1 Like
Any reason why it is not working on a particular server? Even doesn’t work when set to local.
well it seems all related to the new web security context … and your remove sites aren’t being detected as secure 
Maybe if you had an SSL (HTTPS) connection it should work directly.
Temporaly solution
if you start Wappler with an extra argument that includes your domain name it should work:
--unsafely-treat-insecure-origin-as-secure="http://example.com"
where http://example.com is your remote site address.
for Mac OSX:
- Quit Wappler fully by choosing the tray icon and then Quit
- Start the Terminal and type:
open -a "Wappler.app" --args --unsafely-treat-insecure-origin-as-secure="http://example.com"
So this should work as a temporally solution, till we find a better solution.
If you are interested in the Secure Contexts, read:
1 Like
Temporary solution worked. Hope this can be fixed.
1 Like
Just to add - if your remote host is going through HTTPS instead of plain old HTTP, you won’t have this problem at all.
So make sure your remote sites are secured with SSL and address starts with https://
This is a requirement this days as Google Chrome even bans sites using just http without encription.
if you don’t have a certificate, you can always get one for free from:
So what you are saying is that this will not be fixed? this creates an issue for me going forward as our dashboards are all internal and no need for SSL at this time. I don’t see the connection between SSL and selecting elements in Design View. What is the danger of having things selectable in Design View when not SSL?
Also, I looked into this the other day, it does require a business license so not free for everyone, especially a person like me doing this to learn and help others as part of a hobby.
1 Like
Hi Brad,
see:
and:
So, there will be a solution. And no, it is not a restriction by us.
But I’m looking for a clear answer ti if there will be a fix for this. I am aware of the workaround but to start Wappler like that every time is a bit of a pain. I totally get that Google has a thing for SSL. My point is that not all projects are public websites and not meant to be searched. I also quite often do up temporary sites to test something before I do it live on a dashboard. I can’t have SSL set up for every little temporary site that might only be up for a few hours. Or even minutes …
Of course Brad, temporary solution means that is a solution until we release a fix for this…
1 Like
Fixed in version 1.5.1
2 Likes