I am working on a new version of my website. Had problems with the designer / programmer and he delivered the source code developed so far in a zip file.
I came a long way to have it running on Apache 2.0.59 PHP 5.2.0
Still a nasty problem is left. According to the designer ( he does not want to help any further) it has to do with the activation of Multiview.
Here is the root:
Here is part of the PHP code:
<?
echo "<p><a href=\"add_destination/\">Add destination</a></p>";
echo "<br />";
$res_itinerarydestinations = $tripbuilder->GetItineraryDestinations($_SESSION['trip_id']);
if(!empty($res_itinerarydestinations))
{
//print_r($_SESSION['destinations']);
$day_count = 1;
$destination_count = 1;
The problem is that <a href=\"add_destination/\">Add destination</a> ends up into a 404 error.
Here is part of the httpd.conf file:
# First, we configure the "default" to be a very restrictive set of
# features.
#
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
and:
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "C:/htdocs"
#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
#
# First, we configure the "default" to be a very restrictive set of
# features.
#
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#
#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory "C:/htdocs">
#
# Possible values for the Options directive are "None", "All",
# or any combination of:
# Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
#
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
#
# The Options directive is both complicated and important. Please see
# # for more information.
#
Options Indexes FollowSymLinks MultiViews
#
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be "All", "None", or any combination of the keywords:
# Options FileInfo AuthConfig Limit
#
AllowOverride None
#
# Controls who can get stuff from this server.
#
Order allow,deny
Allow from all
</Directory>
Other functions on the side, using Multiviews are working fine.
When the site was running on the server of the designer, the link that was build was:
<a href=" destination</a>
(derived from de source code view in the browser)
So that means that Apache / multiviews has to build the link
The root contains the file tripbuilder.php and according to the designer, this file is used to build the link.
Hope I made it clear.
I welcome any suggestion.
Thanks
I came a long way to have it running on Apache 2.0.59 PHP 5.2.0
Still a nasty problem is left. According to the designer ( he does not want to help any further) it has to do with the activation of Multiview.
Here is the root:
Here is part of the PHP code:
<?
echo "<p><a href=\"add_destination/\">Add destination</a></p>";
echo "<br />";
$res_itinerarydestinations = $tripbuilder->GetItineraryDestinations($_SESSION['trip_id']);
if(!empty($res_itinerarydestinations))
{
//print_r($_SESSION['destinations']);
$day_count = 1;
$destination_count = 1;
The problem is that <a href=\"add_destination/\">Add destination</a> ends up into a 404 error.
Here is part of the httpd.conf file:
# First, we configure the "default" to be a very restrictive set of
# features.
#
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
and:
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "C:/htdocs"
#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
#
# First, we configure the "default" to be a very restrictive set of
# features.
#
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#
#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory "C:/htdocs">
#
# Possible values for the Options directive are "None", "All",
# or any combination of:
# Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
#
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
#
# The Options directive is both complicated and important. Please see
# # for more information.
#
Options Indexes FollowSymLinks MultiViews
#
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be "All", "None", or any combination of the keywords:
# Options FileInfo AuthConfig Limit
#
AllowOverride None
#
# Controls who can get stuff from this server.
#
Order allow,deny
Allow from all
</Directory>
Other functions on the side, using Multiviews are working fine.
When the site was running on the server of the designer, the link that was build was:
<a href=" destination</a>
(derived from de source code view in the browser)
So that means that Apache / multiviews has to build the link
The root contains the file tripbuilder.php and according to the designer, this file is used to build the link.
Hope I made it clear.
I welcome any suggestion.
Thanks