NetTalk Central
NetTalk Web Server => Web Server - Ask For Help => Topic started by: Alberto on May 01, 2020, 08:34:26 AM
-
May be its me, may be is there another way to do it.
I have a custom.css, if I make changes to it I need to close the server and re run it to see the changes, besides the obvious Ctrl-F5 in the browser.
Is there any chance of make this CSS refresh of the server clicking in the actual "Restart Server" of the server settings tab?
Thanks
-
si tienes configurado el sistema en el webserver performance como web hay que cerrar y abrir ya que va todo comprimido, como debug no.
-
Hi,
I turn off "Enable File Cache" while i'm actively developing. This means I dont have to restart the server to clear the file cache.
You also either have to turn off "Combine Common Files" to remove the need to re-combine and compress resources (styles & scripts) each time you make a change OR you can add your own .CSS and .JS files into NT, just remember it is ok for us in development to have the press Ctrl-F5 but this is not satisfactory when in production (you can't tell hundreds or thousands of customers to do this). In this case a common technique is to place a version or random number as part of the css or js filename.
In my example move.js?v=2.29 as shown in the attachment.
As long as I change the version all clients browsers will reload the file.
Regards
Bill
-
yeah, the short answer,
a) on template settings, Performance tab - click the "Debug" button.
b) when editing in the browser just refresh the page normally between css changes. No need to restart the exe.
cheers
Bruce
-
Yes but... if I press the Debug button nothin works, the server compiles ok but nothing in the page works, I have to do it manually.
-
>> Yes but... if I press the Debug button nothing works, the server compiles ok but nothing in the page works, I have to do it manually.
Well that definitely needs to be sorted out before you continue.
So when you are in "debug" settings,
Ctrl-F5 in the browser - just to be sure the cache is cleared
and check the developer tools Console for errors.
There is no point in continuing until this is sorted out.
cheers
Bruce
-
Works ok now, dont know what happened.
Thanks