Posts by veedeoo which have been Voted Down

Hi,

The first thing you need to do is create a simple html page ( stand alone). This html page should have all the items you want on your modification. For example, if you are planning to have a form, place the form in this html page including the css. The next one, will be the form processor file, and finally test your script. For now, don't worry about the view.php. Modifying this will be easy later on, once you build a working prototype on what you want to make. The most important is to have a working stand alone script.

Once you are happy with the result, it is time we extend or modify the controller.php, view.php,add.php, edit.php and db.xml files. It should not be that hard, because it is written in OOP.

The main core of the comment block is the Controller.php. In the admin area, the settings are controlled by add.php and edit.php. The default setting options for the admin is delivered by the db.xml. Lastly, the view is where the form elements are located.

Hi,

I believe Windows is blocking the script from writing on C drive. Possible reason is that the location where the script is trying to write the file is outside of its working space, and the script do not have permission to do so.

Try changing the target location for logs_php.txt , it should be anywhere between htdocs and aaa directories. PHP script will not be able to write outside the htdocs directory. Outside this directory are write protected, and should be done by the root, but in windows there is no such definition unless you are physically writing the file . I mean DOS command can write in any space and any part of the physical drive, but not in php. PHP is more confined in the htdocs directory.

There a few exemption to this rule.. for example, if the php script is designed to execute a video encoder such as ffmpeg, mencoder, and metadata injectors such as flvtool2. Even though these applications are located in the root of the C drive, php exec function will still be able to execute these program without restriction. However, if we closely analyze what is really going on during the process, the output file is still saved and must be saved below the htdocs. All errors encountered by the ffmpeg during the process still have to be routed somewhere below the htdocs and not anywhere in the C drive.

Dude,

You need to learn how to relax, and take it easy... panicking will not make you a better coder. Just seat back, relax, look over the window, if you have a cup of starbucks coffee within your reach, take a sip or two, take a few deep breath, exhale , and then slowly.. look back at your monitor.

Once you have done that, look at your database query if it matches your database table columns..better yet, post your insert codes here.