SCRIPTCASE does not update LOG file entry

Scriptcase 8 Bugs
#1

I used one log file (sc_sec) then later replaced this file with another one (xtr_log). Despite new file is selected when using LOGIN App the app still looks for the old file. Another words whatever I select in the log dropdown list is ignorred.

When the Security wizard is user SC creates a library with functions where the log_file_name is HARDCODED and callot be changed at a later time (despite the LOG module allows to do it). Changing the log file should be in this case either disabled OR the LIB file should be modified to keep lof file as STRING. Also when the LOG filename is removed SC does not clean up a code causing buildup of many unused entries in sc_logged.php file.

On top of that many entries in that lib file are idiotic or irrelevant. For example

 $str_sql = "INSERT INTO asc_log(username, inserted_date, `action`, ip_user) VALUES ('blocked', '". microtime(true) ."', '_SC_BLOCKED_SC_', '". $ip ."')";
 76|             sc_exec_sql($str_sql);

The “inserted_date” has nothing to do with CHANGED or DELETED so it shows wrong/confusing information. If any changes are made to the LOG in MODULES section of SC the sc_logged.php becomes total mess. SC needs to clean up this code. In my opinion the whole concept and the way this is done is bad. Hard coding anything like that makes terrible mess in the source code.

[ATTACH=CONFIG]n71767[/ATTACH]

[ATTACH=CONFIG]n71768[/ATTACH]

log_error01.png

log_error02.png

#2

I think you must create the table XTR_LOG. May some old forms was created for prior table ASC_LOG.

#3

I created that table manually and got this managed but in place of this I got another issue (error) -> see this post
http://www.scriptcase.net/forum/forum/scriptcase-8/discussion-aa/71777-the-log-files-mess

#4

I Think, When a form, Control, Grid are Created, It build in The current table Log. And If the table Log was changed, Then the forms, controls, etc are not updated. Then you must regenarate all forms again.

#5

Yes you are right and that is a big flaw. they should either prevent from changing the log file name (once it is created) or fix the issue and update the generated code when the log file is changed. The problem is that this code resided in LIBRARY,