Question Fatal error in module - exclude from webpage routing

Right now exist situation when added module/addon to webtrees without turn on in panel effecting on system for users, eg. when some problems with module/addon user seeing errors



Soo.. admin can try install module, upload to dir `webtrees\modules_v4\` but files are sitll copying then some files and class are not available, soo module/addon is not ready, but system taking this into production as ready and turned on. This is bad case in whole when in fact addon/module is developed with bugs.

Admin should have option to test addon/module outside official views, as "mode-test" or "mode-preview" url, then not to much errors on production can offer more option for test, experiments and fix as way to resolve problems and grow solutions as addon/module and build community to develop more nice solutions.

Added dir with addon/module can be in default as turned on in panel, coz if problems with this is impossible to turn off and eg. edit something.
Admin should have option to test addon/module in other card in browser and have other card with panel where he can turn of and save, other way errors around whole system and panel due no isolation.
 

webtreesFUN wrote:

Admin should have option to test addon/module outside official views, as "mode-test" or "mode-preview" url, then not to much errors on production can offer more option for test, experiments and fix as way to resolve problems and grow solutions as addon/module and build community to develop more nice solutions.

 

Most developers will test modules outside the production area, e.g on localhost using Xampp or Wamp. Only when a module is ready for production they will upload it to their public server.
But in cases like this, when something goes really wrong and you can't reach the control panel anymore you can always disable the module on the server by going into the modules_v4 folder and renaming the module folder. Put .disable (dot disable) after the folder name to turn it off.

JustCarmen wrote:

Most developers will test modules outside the production area, e.g on localhost using Xampp or Wamp. Only when a module is ready for production they will upload it to their public server.
But in cases like this, when something goes really wrong and you can't reach the control panel anymore you can always disable the module on the server by going into the modules_v4 folder and renaming the module folder. Put .disable (dot disable) after the folder name to turn it off.
 

For my cases something working on local, not working on remote : )
Or user can do some case that not have exeption way.. then this should be logged and eg after 3 repated logs addon turn off for admin checking.

Did not know about option moduleName.disable  - thx.