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
I have checked that the bug I am reporting can be replicated, or that the feature I am suggesting isn't already present.
I have checked the pull requests tab for existing solutions/implementations to my issue/suggestion.
I realise that server-side connectors are provided by various contributors. The implementations are vary due to programming language features/limitations or other factors. Thus a particular connector may not implement, or partially implement, the API features.
I realise that any changes in configuration options and/or plugin parameters affect the plugin behavior. I specified all the differences from defaults in details.
I use the following server-side connector (check one):
PHP connector by servocoder
Java connector by fabriceci
Python3 Flask connector by jsooter
Python3 Flask connector by stevelittlefish
NodeJs connector by jlaustill and forestlake
ASP.NET Core connector by sinanbozkus
ASHX connector by richeflits
Other (specified below)
My familiarity with the project is as follows (check one):
I have never used the project.
I have used the project briefly.
I have used the project extensively, but have not contributed previously.
I am an active contributor to the project.
Hi!
I want to implement dynamically changeable behavior for client side configuration, (i.e. dynamically build filemanager.config.json). This will for example provide custom UI based on user role.
As far as i can see, paths for configuration files are hardcoded. I propose to add something like configUrl to available options,
vardefaults={baseUrl: '.',// relative path to the FM plugin folderconfigUrl: null,// Config url
and extend loadConfigFile with something like this
varloadConfigFile=function(type){varurl=null;type=(typeoftype==='undefined') ? 'user' : type;if(type==='user'){if(_url_.param('config')){url=fm.settings.baseUrl+'/config/'+_url_.param('config');}else{url=fm.settings.configUrl ? fm.settings.configUrl : fm.settings.baseUrl+'/config/filemanager.config.json';// if configUrl is defined}}else{url=fm.settings.baseUrl+'/config/filemanager.config.default.json';}return$.ajax({type: 'GET',url: url,dataType: 'json',cache: false,error: function(response){fm.error('Given config file ('+url+') does not exist!');}});};
The text was updated successfully, but these errors were encountered:
In raising this issue, I confirm the following (please check boxes):
I use the following server-side connector (check one):
My familiarity with the project is as follows (check one):
Hi!
I want to implement dynamically changeable behavior for client side configuration, (i.e. dynamically build
filemanager.config.json
). This will for example provide custom UI based on user role.As far as i can see, paths for configuration files are hardcoded. I propose to add something like configUrl to available options,
and extend
loadConfigFile
with something like thisThe text was updated successfully, but these errors were encountered: