Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Pages: 1
older and newer tags broken
OK, I’m doing my second textpattern site and something that worked before no longer works properly. I am trying to page through articles, using the txp:older and txp:newer tags from the following page:
http://x.y.com/pagenameThe URL that is created for older is:
http://x.y.com/pagename/?pg=2But this gives me a scrambled version of the page. It has the correct content but no styles. However the following URL gives me the correct page:
http://x.y.com/pagename?pg=2I have tracked this down to the function pagelinkurl which definitely appends slashes in code like the following:
$url = hu.urlencode($keys['s']).'/';Is this a bug? If so, why does my other site work? Is there something wrong with my current site? Everything else seems to work ok. Any help would be appreciated.
robin
Offline
Re: older and newer tags broken
What does your link to the stylesheet look like? As the problem is probably there, as there is nothing wrong with pagelinkurl.
So also your topic title “older and newer tags broken” is quite wrong as it has something to do the styles loading/linking, and nothing with the older and newer tags, as anyone could see, as the links are exatly same as with your other site – or with any Textpattern site ;)
Cheers!
Last edited by Gocom (2008-01-07 03:17:52)
Offline
Re: older and newer tags broken
Gocom wrote:
What does your link to the stylesheet look like? As the problem is probably there, as there is nothing wrong with
pagelinkurl.
Changing the CSS links from relative to absolute fixed the problem. Thanks!
So also your topic title “older and newer tags broken” is quite wrong as it has something to do the styles loading/linking, and nothing with the older and newer tags, as anyone could see, as the links are exatly same as with your other site – or with any Textpattern site ;)
That seems a little harsh. I did specify I’d only worked with one other site, and perhaps that had no issues because there were different features, a different domain name structure etc. etc. Guessing that it was stylesheets and not something in the .htaccess or configuration or elsewhere would have been quite a leap of logic on my part, especially as I had already had clean URL problems.
Besides, look at these three lines:
http://x.y.com/pagename
http://x.y.com/pagename?pg=2
http://x.y.com/pagename/?pg=2The first two seem semantically correct, the last one not so. I now know that lines 1 and 3 are correct but don’t agree it should be this way.
robin
Offline
Offline
Pages: 1