Hello,
I am using the following setup:
Xampp local host server
Drupal 5.7
Drigg 1.31
Views 1.6
Voting API 1.6
User Karma 1.8
Tagadelic 1.0
CCK 1.7
Everything works well except for when I try to browse one of my tags.
I set up everything according to the instructions so that I have a scoop with the following fields:
Node Title
link
time of post
Category: business (for example)
Tags: business, sales (for example)
Now, if I click on the category item I get sent to the page:
http://localhost/drupal-5.7/tag/business
And if I clink on one of the tags I get sent to:
http://localhost/drupal-5.7/tag/business
http://localhost/drupal-5.7/tag/sales
All these pages return the following error:
Access forbidden!
You don't have permission to access the requested object. It is either read-protected or not readable by the server.
If you think this is a server error, please contact the webmaster.
Error 403
localhost
05/11/08 13:44:51
Apache/2.2.8 (Win32) DAV/2 mod_ssl/2.2.8 OpenSSL/0.9.8g mod_autoindex_color PHP/5.2.5
The thing is if I browse to the category using the url:
http://localhost/drupal-5.7/business (note: without the "tag" dir)
I get to the "published scoops" page and see all the relevant scoops in the category.
So I assume the problem is with the "tag" url rewrite module.
I tried applying different settings to my xampp settings as suggested here:
http://drupal.org/node/75537 but I still continue to get the errors.
Any idea how to solve this one?
Thanks in advance,
Nimi.
Comments
Comment #1
mercmobily commentedHi,
This is really odd.
Can you please include:
* Your custom_url_rewrite function
* The actual server's error log
...?
Do you by any chance have a directory called "tag" in your servers' root directory? (you shouldn't)
Bye,
Merc.
Comment #2
nimi commentedHi,
Thanks for your quick reply.
I checked for a "tag" directory on root - there isn't one.
custom_url_rewrite_function.php:
Server's error log:
Thanks,
Nimi.
Comment #3
mercmobily commentedHi,
I don't understand the logs. Are you actually clicking on http://localhost/drupal-5.7/tag/business ? Or Just on /tag?
Please send me *only* th error log lines which pop out *precisely* when you click on a tag, and please double-triple check that you're actually clicking on a link with the tag name following it.
This problem is due to a server configuration, and you seem to be using Apache under Windows. I can try and direct you towards the right direction, but I don't really support anything but Apache on Linux. With this sort of problem, you are better off asking the Drupal forums (there are more Windows users there)
Bye,
Merc.
Comment #4
nimi commentedOk thanks Merc I'll try first uploading my site to a Linux server to see if it will solve the problem.
Comment #5
mercmobily commentedHi,
OK thanks :-D
I will close the issue for now, because I am basically 99.99999% sure it was a server misconfiguration...
Merc.
Comment #6
mercmobily commentedComment #7
chrisdfeld commentedApologies for resurrecting an old issue, but I encountered the same problem today and wanted to report the solution. I'm running Drupal 6.14, also under Apache on Windows. Please note that I'm not using the Drigg module. This issue isn't specific to any particular module.
The symptom, as described above, is getting an HTTP 403 error ("Access Forbidden") when visiting a URL like /tag/mytag. The "access forbidden" page you see is a plain vanilla Apache error page, not a Drupal error page. The cause of the error is this code at the top of Drupal's .htaccess file:
That code is intended to prevent requests for certain files that might be dangerous to serve in some circumstances. Notice that Tag (with a capital "T") is one of the phrases listed above. Because Windows uses a case-insensitive filesystem, that phrase also unintentionally matches the all-lowercase URL /tag/mytag. This isn't a problem on Unix servers because the filesystem in case-sensitive.
A fix for this is to delete the Tag| bit from the FilesMatch directive in Drupal's .htaccess. You can then use Drupal URLs in the format /tag/mytag. You'll need to remember to re-apply the same change whenever you upgrade Drupal.