It is always necessary to have a Help section in our software application. When users do not find a way out from a specific problem in our application, it is the help section they turn to. Hence it is important that the help feature is well maintained and without any errors. In this article by Tim Lavers and Lindsay Peters, we will see the errors that can occur in our help section and how to test the help section.Read Testing a HELP System in a Java Application in full
The installation of Joomla! is a matter of five minutes. If you have installed it before, you can do it in two minutes. In order to be able to even start the installation, your development environment must include a web server that supports PHP and a database that is supported by Joomla!. Joomla! is one piece of the puzzle in this so-called Client-Server System. This topic is very complex, since there is an unmanageable number of providers and an even more unmanageable combination of installed Apache, PHP, and MySQL versions and Webspace administration tools such as Visas and Plesk.
In this article by Hagen Graf, we focus on the following points:
- A PHP safe mode, possibly activated in the php.ini
- Prohibited conversion of URLs with Apache because of the non-activation of the so called rewrite engine
- Directory rights in Linux that are set differently than in Windows
JBoss jBPM is a free, open-source, business process management solution. It enables users to create business processes that coordinate people, applications, and services. JBoss jBPM is an Integrated Development Environment (IDE) , which is based on another open-source tool, Eclipse, which is widely used for Java development. The JBoss jBPM IDE gives us not only our graphical process modeler, but can also generate the workflow user interface for us. In this article by Matt Cumberlidge, we will explain the concepts or the key terms in JBoss jBPM. We will also look at jBPM Process Definition Language (jPDL).Read JBoss jBPM Concepts and jBPM Process Definition Language (jPDL) in full
Most web applications have rather simple error handling strategy. When an error occurs, the script terminates and an error page is presented. The error should be logged in the error log, and the developers or maintainers should check the logs periodically. In this article by Dennis Popel, we will look through the most common sources of errors in database-driven web applications.
- Server software failure or overload such as the famous "too many connections" error
- Inappropriate configuration of the application, which may happen when we use an incorrect connection string, a rather common mistake when an application is moved from one host to another.
All web applications and web servers have security vulnerabilities and there is every chance that our website will be compromised. Most web hosts have their own backup procedures in place, but it is not uncommon for a web host to become victim to an attack, and have problems with a small percentage of its customer backups. Because of this it is very important that we keep backups of our website. In this article by Michael Peacock, we will see how to backup our website and restore it back gain from our backup.Read Backing Up and Restoring TYPO3 Websites in full