RapidPHP2007 Version 8.1(8.1.0.78)
This may be covered earlier but I have browsed thru and cannot find any reference to it.
If a preview or page fails I have to open manually the php.log file, run to the end and see what it was I failed to do to allow my pages to work.
It normaly is something as daft as a semi colon or one " or } too many or too short.
The syntax check just beeps and says Ng filename.php in a little popup or says no problemo.
when it says Ng it resets to the top of the script and leaves me guessing where.
To me this is a major problem as it really slows me down.
Is the php and or other scripting types not pre-processed before we get to the preview stage, nothing seems to appear in the messages view or Inspector view so I am at a loss.
Obv something simple and I am too simple to see it.
Regards
Gary
Syntax Error and PHP formatting errors
Moderator: kfury77
Forum rules
Please try to follow these guidelines. This will help to receive faster and more accurate response.
Please try to follow these guidelines. This will help to receive faster and more accurate response.
- Check the Support section of the corresponding product first. Chances are you will find your answer there;
- Do not create new topics for already reported problems. Add your comments to the existing topics instead;
- Create separate topic for each problem request. Do NOT post a number of non-related problem reports in a single topic;
- Give your topic a meaningful title. Titles such as "A question," "Bug report" and "Help!" provide others no clue what your message is about;
- Include the version number of the software you are using;
- This is not an official customer support helpdesk. If you need a prompt and official response, please contact our support team directly instead. It may take a while until you receive a reply in the forum;
Hmm ok I seem to have managed to find a solution by switching error reporting on in the php.ini file.
Personally this isn't what I was hoping for.
Is it not possible for the PHP Editor to capture the log and display results that way rather than leaving your site in a position where information that could be detrimental to your security has to be enabled.
ie the following from the ini file.
; Print out errors (as a part of the output). For production web sites,
; you're strongly encouraged to turn this feature off, and use error logging
; instead (see below). Keeping display_errors enabled on a production web site
; may reveal security information to end users, such as file paths on your Web
; server, your database schema or other information.
display_errors = On
Personally this isn't what I was hoping for.
Is it not possible for the PHP Editor to capture the log and display results that way rather than leaving your site in a position where information that could be detrimental to your security has to be enabled.
ie the following from the ini file.
; Print out errors (as a part of the output). For production web sites,
; you're strongly encouraged to turn this feature off, and use error logging
; instead (see below). Keeping display_errors enabled on a production web site
; may reveal security information to end users, such as file paths on your Web
; server, your database schema or other information.
display_errors = On
