Welcome to the nuBuilder Forums!
Register and log in to access exclusive forums and content available only to registered users.
Register and log in to access exclusive forums and content available only to registered users.
4.5 issues
4.5 issues
Hello all, got my new server up and running Ubuntu 20.04, php 7.4 and mariadb. Well there seems to be a major installation with my system. None of the windows open as expected. For example if trying to open the debug screen from the hamburger menu on the main screen I get a greyed out screen, same when clicking on a lookup and and it seems anything that tries to make a popup window. HELP. I just updated to the latest files from source forge.
-
- nuBuilder Team
- Posts: 4307
- Joined: Sun Oct 14, 2018 6:43 pm
- Has thanked: 71 times
- Been thanked: 448 times
- Contact:
Re: 4.5 issues
Hi,
Do you see any error messages in the developer console or in the server log file?
And is this a new installation or did you update a previous version?
Do you see any error messages in the developer console or in the server log file?
And is this a new installation or did you update a previous version?
Re: 4.5 issues
Error from console:
Uncaught SyntaxError: Unexpected token '<'
[Violation] Forced reflow while executing JavaScript took 78ms
(index):1 Refused to display 'https://dbs.winecountry-bbq.com/index.p ... e&iframe=1' in a frame because it set 'X-Frame-Options' to 'deny'.
I'll be looking into x frame options. This is a new installation and the dataset was updated from the previous version. Also the first time I saw this behavior was when testing the email setup.
Uncaught SyntaxError: Unexpected token '<'
[Violation] Forced reflow while executing JavaScript took 78ms
(index):1 Refused to display 'https://dbs.winecountry-bbq.com/index.p ... e&iframe=1' in a frame because it set 'X-Frame-Options' to 'deny'.
I'll be looking into x frame options. This is a new installation and the dataset was updated from the previous version. Also the first time I saw this behavior was when testing the email setup.
-
- nuBuilder Team
- Posts: 4307
- Joined: Sun Oct 14, 2018 6:43 pm
- Has thanked: 71 times
- Been thanked: 448 times
- Contact:
Re: 4.5 issues
Your link rel in the header is in the wrong place. Try placing it like this:
Code: Select all
function nuHeaderTest() {
console.log('Functions placed here are available anywhere in nuBuilder Forte.');
}
// nuOnLoad() will be run after each Browse and Edit Form loads.
function nuOnLoad() {
if(nuFormType() == 'edit'){
// Edit Form loaded
} else
if(nuFormType() == 'browse'){
// Browse Form loaded
}
}
</script>
<!-- Define your own styles, override styles from nubuilder4.css -->
<link rel='shortcut icon' href='http://dbs.winecountry-bbq.com/favicon.ico'>
<style>
/*.nuActionButton {background-color:#0073aa;} */
</style>
<script>
Re: 4.5 issues
Ah, the plot thickens and I left out some critical information I am trying to run the site under SSL and when changing the header setup it won't save and I get the message Use SSL cannot be left blank. I think that is the root of the issue.
Also how do you make those nice code windows???
Also how do you make those nice code windows???
-
- nuBuilder Team
- Posts: 4307
- Joined: Sun Oct 14, 2018 6:43 pm
- Has thanked: 71 times
- Been thanked: 448 times
- Contact:
-
- nuBuilder Team
- Posts: 4307
- Joined: Sun Oct 14, 2018 6:43 pm
- Has thanked: 71 times
- Been thanked: 448 times
- Contact:
Re: 4.5 issues
Ok, that resolved the saving issue, still working on the x-frame issue. I changed the setting in the apache config file and it said there were conflicting settings and it was defaulting to deny.
Re: 4.5 issues
Well it only took half of my day, but I've got it! The solution was:
Code: Select all
What did it for me was the following, I've added the following directive in both the http <VirtualHost *:80> and https <VirtualHost *:443> virtual host blocks:
ServerName your-app.com
ServerAlias www.your-app.com
Header always unset X-Frame-Options
Header set X-Frame-Options "SAMEORIGIN"
The reasoning behind this? Well by default if set, the server does not reset the X-Frame-Options header so we need to first always remove the default value, in my case it was DENY, and then with the next rule we set it to the desired value, in my case SAMEORIGIN. Of course you can use the Header set X-Frame-Options ALLOW-FROM ... rule as well.