Page 2 of 2

Posted: Tue Jun 10, 2008 7:13 pm
by judebert
I'm willing to believe it's a configuration issue with Serendipity. I've even gone over the code to try and find it, but I'm just not getting it. Everywhere I look, we always return the appropriate header; in fact, when you specifically eliminated all the 404s from the code, we still got a 404. How can we possibly be getting a header we're not actually coding?

I'm reduced to guessing. But I don't have many guesses left. Do you have an actual posts/ directory? Do those invalid URL characters in your .htaccess play a part?

The worst part is that I can't duplicate on my server, so I can't do any of the debugging on my own. Any luck creating a simple example problem that does the same thing, like the stuff I provided before?

Posted: Thu Jun 12, 2008 10:34 pm
by psiege
Hi Judebert,

I do not have an actual /posts/ directory. You mention invalid URL characters in my .htaccess, which characters are you referencing.

I could not duplicate with your sample you provided before. This problem ONLY occurs in the /posts/ directory. There are other directories using rewrite rules that do not have the same problem.

Out of curiosity, I looked in the error logs and noticed this:

PHP Warning: uniqid() expects at least 1 parameter, 0 given in /hermes/bosweb/web015/b157/ipw.pcdoctor/public_html/blog/plugins/serendipity_event_karma/serendipity_event_karma.php on line 158

I have no idea if it's related, or what problems that might be causing. I'm grabbing at straws here.

Posted: Thu Jun 12, 2008 10:55 pm
by psiege
Ah ha! I've stumbled across something interesting. I was playing with the permalinks in the config for Serendipity.

Here is my current Permalink Entry URL structure:

Code: Select all

posts/%year%/%month%/%day%/%title%/
After changing to this:

Code: Select all

posts/%id%/%year%/%month%/%day%/%title%/
The problem was corrected! All I did was add the id to the permalink. Surely, there must be a fix to prevent me from having to use the id. I'm trying to ensure that my permalinks match my old blog (Wordpress) so that all of our existing links work.

Any ideas now?

Posted: Fri Jun 13, 2008 10:09 am
by garvinhicking
Hi!

I believe I've had a similar report earlier on. Can you try to change the "archives directory" (NOT the archive permalink) and change that from you surely currently have "posts" to something like "postarchive"?

The reason is that if you only have numbers in your first two parts of the URL, serendipity might jump to the archive view instead of the permalink view.

Regards,
Garvin

Posted: Mon Jun 16, 2008 6:29 pm
by psiege
Hi Garvin!

My current "Path to archives" and "Path to archive" are "archives" and "archive". I changed to this long ago. That should be fine, correct? As long as it's not "posts", as you said.

Any other ideas?

Thanks!

Posted: Tue Jun 17, 2008 10:22 am
by garvinhicking
Hi!

Hm, maybe in your case the problem is the other way round? Have you tried setting "archives" to "posts" instead?

Regards,
Garvin

Posted: Tue Jun 17, 2008 5:32 pm
by psiege
I don't believe it, it worked!!!

Thanks Garvin. Now my posts can finally be submitted to Digg!