Posted on: 06/03/04 05:43am
By: chief123
If I have the clean URL setting set to true then every access to a static page gets this error message "URL Class: number of names passed to setArgNames must be equal or greater than number of arguments found in URL".
If I take off the URL setting it goes back to normal.
Any ideas?
Thanks in advance.
PS I'm using 1.39 with no other plugins except static on Linux.
Static Pages conflict with URL rewrite
Posted on: 06/06/04 03:13pm
By: beewee
Please show a part of the code of your links, or your URL
Static Pages conflict with URL rewrite
Posted on: 06/09/04 10:29am
By: chief123
[QUOTE BY= beewee] Please show a part of the code of your links, or your URL[/QUOTE]
Well I moved the 2 GL sites that were on that host elsewhere so I have nothing to show right now.
The host was 1and1.com and it was simply a problem accessing static pages with the clean URL option turned on.
Static Pages conflict with URL rewrite
Posted on: 12/02/05 06:41am
By: roberto
Hi,
sorry for my bad english :-(
I have the same problem with geeklog 1.3.11sr1, fresh installation
if the url rewrite is ON, whichever attempt to modify/copy a staticpage answers with error "URL Class: number of names passed to setArgNames must be equal or greater than number of arguments found in URL"
if the url rewrite is OFF, modify/copy staticpage is OK
On the same server works regularly another site with geeklog 1.3.11sr1, updated regularly from 1.3.8, without these problems
any suggestion?
tnx!
rob
Static Pages conflict with URL rewrite
Posted on: 12/02/05 08:13am
By: Anonymous (Peachy)
I'm having the same issue... fresh install of 1.3.11sr1
I do not have this problem on sites running 1.3.11
Static Pages conflict with URL rewrite
Posted on: 12/04/05 09:18pm
By: Nygrah
I am having the same problem. I upgraded to the 1.3.11sr2 and now I can not edit my static pages. Any suggestions on how to fix this problem without doing a fresh load?
Static Pages conflict with URL rewrite
Posted on: 12/05/05 01:58am
By: Dirk
It's a known bug in 1.3.11sr2 (discussed at length
here[*1] - always try a search first ...).
A fix is forthcoming. Some patience, please.
bye, Dirk