ABCD
1
#BugDetails/ReasonFix
2
1EasyBashWEB needs "step by step" work flow.CGI technology is a costant "ping-pong à trois" between browser, server and CGI script.No way.
3
2Temp files still remain in "dir_tmp" directory FOR EVER if you don't...EasyBashWEB needs a session temp file to follow logical flow (and for security reasons), but this file is intended to be removed with "web_final_message()" usageUse "web_final_message", at the end of your script, or alternatively use "clean_temp()" before your last script function
4
3Http-server user doesn't execute "source easybashweb"Http-server user (e.g.: "apache") usually doesn't have PATH and HOME variables setPlease set 'hem before sourcing EasyBashWEB (see examples)
5
4After web_question() usage, command "answer=$?" will give always "0"If you execute "answer=$?" after an "if-then-fi", you will intercept ITS exit code, and not web_question() exit code. 3 fixes -choose one of them- 1) use "exit_code" var: "answer=$exit_code" ; 2) put "answer=$?" directly after "source easybashweb" command ; 3) use "case-esac" instead of "if-then-fi"
6
5I sometimes find "step=[integer]" in "${dir_tmp}/${file_tmp}"When you execute "next_step [integer]", next_step() will write the string "step=[number]" in session temp fileExecute FIRST "choice=$(cat "${dir_tmp}/${file_tmp}" )" THEN "next_step [foo]"
7
6"web_fselect()" is missingOld WeBash "input_cgi()" was in beta state, so far I decided to not insert it officially in EasyBashWEB(Fixed since version 2.0.0 )
8
7Images related to "web_ok_message" and "web_alert_message" are not displayedImages problem still need to be fixed...User couldn't do anything about. ...Please wait...
9
8"web_input" doesn't have any page title/descriptionActually is not yet implemented(Fixed since version 2.0.0 )
10
9set_costant() failsVery rarely, it seems "blank" spaces are the cause. Need to investigate.Avoid spaces in variables transformed in "costants"