You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
This issue is related to #642. This is mostly related to the upload part. After removing the purge key manually from app_settings.json and uploading it to the server. It doesn't get updated in the settings in the database.
To Reproduce
Steps to reproduce the behavior:
Create a purge.js file and add your purge logic
Run the command cht compile-app-settings upload-app-settings
Purging should be enabled
Manually remove the purge key from the app_settings.json file
Run the command cht upload-app-settings
Check if purging is disabled
Expected behavior
Purging should be disabled if the purge key is removed from the app_settings.json file and uploaded to the server.
Logs
If applicable, include the cht-conf output, server logs, and/or browser logs.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment
Instance: Local
Client platform: Linux
cht-conf version: 4.1.1
cht-core version: 4.13
Additional context
A workaround as described in #642 is to make the purging.js file blank and then, compile and upload the settings works but it creates a key in the settings in the database with an empty object which is probably not ideal.
The text was updated successfully, but these errors were encountered:
Describe the bug
This issue is related to #642. This is mostly related to the upload part. After removing the
purge
key manually fromapp_settings.json
and uploading it to the server. It doesn't get updated in the settings in the database.To Reproduce
Steps to reproduce the behavior:
cht compile-app-settings upload-app-settings
purge
key from theapp_settings.json
filecht upload-app-settings
Expected behavior
Purging should be disabled if the
purge
key is removed from theapp_settings.json
file and uploaded to the server.Logs
If applicable, include the cht-conf output, server logs, and/or browser logs.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment
Additional context
A workaround as described in #642 is to make the
purging.js
file blank and then, compile and upload the settings works but it creates a key in the settings in the database with an empty object which is probably not ideal.The text was updated successfully, but these errors were encountered: