SEF-Plugin produces 404-Error SEF-Plugin produces 404-Error
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

SEF-Plugin produces 404-Error

Started by Satyr, November 30, 2005, 10:20:33 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Satyr

Aber activating the plugin for sef-urls i receive the errormessage "404, site not found".    ???
Have i forgot something?  ???
Kein Support über PN. Bitte im Forum posten, dann ist anderen auch geholfen.

http://www.gothicmodels.net/gothicmodels/gallery/

Testuser: Test23 PW: 123456

donnoman

If you are not using apache or are not allowed to use .htaccess files do NOT enable the sef plugin.  If you have enabled it in err, you will need to use phpmyadmin and turn it off by modifying its entry in the plugins table.

Satyr

#2
Edit: omg how this can happen to me. I forgot to set chmod on htaccess and it wasn's written so by the script.   :D
Kein Support über PN. Bitte im Forum posten, dann ist anderen auch geholfen.

http://www.gothicmodels.net/gothicmodels/gallery/

Testuser: Test23 PW: 123456

Satyr

But i have the problem that displaying the recent comments/uploads for a single album.
In this case the comments/uploads are displayed from the whole gallery.
Is it possible to deactivate the rewriting only for the links "newest comments" and "newest uploads"?
Kein Support über PN. Bitte im Forum posten, dann ist anderen auch geholfen.

http://www.gothicmodels.net/gothicmodels/gallery/

Testuser: Test23 PW: 123456

senorsam

I've updated all of the files in the sef_urls folder to the ones listed on sourceforge,

-configuration.php 
Coppermine version: 1.4.5
$Source: /cvsroot/coppermine/stable/plugins/sef_urls/configuration.php,v $

-codebase.php
  $Source: /cvsroot/coppermine/stable/plugins/sef_urls/codebase.php,v $
  $Revision: 1.8 $

-ht.txt
##  $Source: /cvsroot/coppermine/stable/plugins/sef_urls/ht.txt,v $
##  $Revision: 1.6 $

Upon installing the plugin, the message about updating .htaccess came up. The file was modified (I checked this by downloading it via FTP). However, I am still getting 404 errors. I'm going to uninstall the plugin for now since nothing will work.

What am I doing wrong? url: http://www.tastywearphotos.com

Nibbler

Are you using apache, have checked that you can use .htaccess files and have mod_rewrite available on your server ?

senorsam

I am using 1AND1 as a host. Info is posted here about what is available to us: http://faq.1and1.com/dedicated_servers/managed_server/3.html

We can use .htaccess files. mod_rewrite is available on the server.

Is there another step where I need to manually actuate mod_rewrite?

tfischer

I know this is an old thread, but maybe it will help someone else.  I just had to figure this out today (I'm also on 1&1 hosting).

SEF URL's doesn't work "out of the box" with 1&1 hosting.  You have to tweak the .htaccess file manually, then it will work.  Specifically:

- Comment out the line that begins "Options FollowSymLinks".   Evidently 1&1 has this on by default, and having this line can cause problems.

- Uncomment the line beginning RewriteBase.  If coppermine is installed at the root of your domain/subdomain, you want it to read "RewriteBase /".  If it's in a subdirectory off of the domain, subdirectory, use the subdirectory.  For example if it's at yourdomain.com/foobar, you want the line to read "RewriteBase /foobar"

Anyway hope this helps someone else, perhaps doing a search, in the future.  I know I would have liked seeing this before I thrashed through it all...   :P

-Tim

afg89

Hey

When i install the plugin i get the following error:
<--------------------------->
Internal 500 server Error

Please Contact your adminstrator.....

<--------------------------->

what should i do please help me.

Joachim Müller

You should do as the error message suggests and contact your server admin. If you can't/won't, then turn the plugin off and disable the .htaccess file it created.