PHP Application Development: the error log is full and nobody

Php application development starts with a real fault on the site you have. The usual one is this: the error log is full and nobody has read the first line that matters.

What is usually wrong

• The error log is full and nobody has read the first line that matters
• A cron script that works in the browser and fails on the command line
• A form that reloads and never stores or emails the message
• A page is fine for a logged-in admin and broken for everyone else

What we look at

We have been in PHP since 2000. The useful job is reading the error and the file that throws it, then telling you what has to change before anyone rewrites the site.

• The exact PHP version and the disabled functions
• A copy of the page before we edit it
• The difference between what the host changed and what the code expects
• File permissions on the directory the script writes to

How the job starts

A new feature belongs next to the data you already keep. We map the field you have to the field the other system has, then we move a small set before we move everything.

Write down one example that is wrong today: one product, one vehicle, one order. That example is the specification.

Most of this work happens on the site you already have. You do not need to be in Toronto. The first step is still a look at the live page.

Call 905-426-1784. We look at the site and tell you what the work is before it starts. The service page for this is PHP help.