We are now using 1.2.4 release.
The sql statements are created as echos. and as plain file, if you select save as from the file menu, the resulted file will contain the internal calls in the code not only the sql statements.
In all cases the best way to do this is to do one of the following ways:
Way 1:
-- select all the text in the screen and copy, and paste them in any text file, and run this text file.
Way 2:
--right click on the screen, select view source, save the file and run it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We are now using 1.2.4 release.
The sql statements are created as echos. and as plain file, if you select save as from the file menu, the resulted file will contain the internal calls in the code not only the sql statements.
In all cases the best way to do this is to do one of the following ways:
Way 1:
-- select all the text in the screen and copy, and paste them in any text file, and run this text file.
Way 2:
--right click on the screen, select view source, save the file and run it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've read this comment before. It triggered my questions.
Are you saying that there is no bug? Then why do you post a workaround in the same message?
Let's try to look at the details of this long-standing bug.
> The sql statements are created as echos
Basically all PHP applications create their web output through echo. Where is the problem here?
> . and as plain file
Correct. A plain text file with SQL statements gets sent to the browser
> , if you select save as from the file menu, the resulted file will contain the internal
> calls in the code not only the sql statements.
Are you saying that using "Save as" in IE gives a different result than clicking on the link?
Is IE issuing a different request to the server in that case? If yes, what is the difference in the request?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
>Are you saying that using "Save as" in IE gives a different result than
>clicking on the link?
>Is IE issuing a different request to the server in that case? If yes, what
>is the difference in the request?
-clicking save as in IE will save the file the select file format with the created statements.
-There is no link created on the page?!.
-Selecting save page as in FireFox will create an out put file with the following error message
"-- WIS export file created 2007-07-01 11:28 by BMFO user 'bmfo'
<br />
<b>Warning</b>: ociexecute(): OCIStmtExecute: ORA-01858: a non-numeric character was found where a numeric was expected
in <b>C:\Program Files\bmfo\wis_export_file.php</b> on line <b>43</b><br />
<br />
<b>Warning</b>: Invalid argument supplied for foreach() in <b>C:\Program Files\bmfo\wis_export_file.php</b> on line <b>44</b><br />
-- End of WIS export file
"
even though the result is correct on the screen.?!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=30248
One of the problems is that I'm unable to reproduce the
problem. My IE 6.0 just works fine.
Logged In: YES
user_id=30248
Email to bmfo-info asking for help to reproduce the problem.
Logged In: YES
user_id=30248
Originator: YES
Hussein,
could you check this again with Internet Explorer 7.0?
Logged In: YES
user_id=30248
Originator: YES
Feedback from Hussein:
We installed Internet Explorer 7.0, but still have the same problem.
Logged In: YES
user_id=30248
Originator: YES
Ahmad,
could you try to to removed the following lines from
wis_export_file.php
and try this again with Hussein?
if(array_key_exists("action", $_REQUEST)) {
header("Content-type: text/plain");
}
Logged In: YES
user_id=30248
Originator: YES
I still need information about download managers, plug-ins, etc. installed on the machine.
Logged In: YES
user_id=695149
Originator: NO
We are now using 1.2.4 release.
The sql statements are created as echos. and as plain file, if you select save as from the file menu, the resulted file will contain the internal calls in the code not only the sql statements.
In all cases the best way to do this is to do one of the following ways:
Way 1:
-- select all the text in the screen and copy, and paste them in any text file, and run this text file.
Way 2:
--right click on the screen, select view source, save the file and run it.
Logged In: YES
user_id=30248
Originator: YES
> resulted file will contain the internal
> calls in the code not only the sql statements.
What calls are those? Could you post an example?
Logged In: YES
user_id=695149
Originator: NO
We are now using 1.2.4 release.
The sql statements are created as echos. and as plain file, if you select save as from the file menu, the resulted file will contain the internal calls in the code not only the sql statements.
In all cases the best way to do this is to do one of the following ways:
Way 1:
-- select all the text in the screen and copy, and paste them in any text file, and run this text file.
Way 2:
--right click on the screen, select view source, save the file and run it.
Logged In: YES
user_id=30248
Originator: YES
I've read this comment before. It triggered my questions.
Are you saying that there is no bug? Then why do you post a workaround in the same message?
Let's try to look at the details of this long-standing bug.
> The sql statements are created as echos
Basically all PHP applications create their web output through echo. Where is the problem here?
> . and as plain file
Correct. A plain text file with SQL statements gets sent to the browser
> , if you select save as from the file menu, the resulted file will contain the internal
> calls in the code not only the sql statements.
Are you saying that using "Save as" in IE gives a different result than clicking on the link?
Is IE issuing a different request to the server in that case? If yes, what is the difference in the request?
Logged In: YES
user_id=695149
Originator: NO
>Are you saying that using "Save as" in IE gives a different result than
>clicking on the link?
>Is IE issuing a different request to the server in that case? If yes, what
>is the difference in the request?
-clicking save as in IE will save the file the select file format with the created statements.
-There is no link created on the page?!.
-Selecting save page as in FireFox will create an out put file with the following error message
"-- WIS export file created 2007-07-01 11:28 by BMFO user 'bmfo'
<br />
<b>Warning</b>: ociexecute(): OCIStmtExecute: ORA-01858: a non-numeric character was found where a numeric was expected
in <b>C:\Program Files\bmfo\wis_export_file.php</b> on line <b>43</b><br />
<br />
<b>Warning</b>: Invalid argument supplied for foreach() in <b>C:\Program Files\bmfo\wis_export_file.php</b> on line <b>44</b><br />
-- End of WIS export file
"
even though the result is correct on the screen.?!