Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Txp 1.0 RC3 Available
About clean URLs. Is the state of things RC3 the final state ? I’m thinking about the XML feeds or the categories for example that don’t use clean URLs.
And, will there be some kind of clean URL scheme generator (or some way to edit it) as it was in zem_rewrite plugins, or the four RC3 schemes are final ?
Just curious.
Offline
#86 2005-02-21 16:35:13
- Mary
- Sock Enthusiast
- Registered: 2004-06-27
- Posts: 6,236
Re: Txp 1.0 RC3 Available
Jeremie: “I’m thinking about the XML feeds”
Dean: “Added some dapper new url-parsing options: you can now call up site.com/category/{categoryname}, site.com/author/{authorname}, site.com/atom/, and site.com/rss. These are hooked into the language files, so site.fr/auteur/baudelaire and site.es/categoria/escandalo should work fine. More are on the way.”
Last edited by Mary (2005-02-21 16:35:23)
Offline
Re: Txp 1.0 RC3 Available
Independent of the state of urls on RC3, there are more possibilities for urls. In fact, you are able to use your own customized url_scheme function. Give a look at line 951 of taghandlers.php.
Final state will be on 1.0. And be patient until Alex rewrites the code of his plugin ;-)
Pedro Palazón
http://kusor.net http://kusor.com
Offline
Re: Txp 1.0 RC3 Available
> kusor wrote:
> Independent of the state of urls on RC3, there are more possibilities for urls. In fact, you are able to use your own customized url_scheme function. Give a look at line 951 of taghandlers.php.
Thanks I will take a curious look.
> Final state will be on 1.0. And be patient until Alex rewrites the code of his plugin ;-)
I am :) I was just curious to know if this was the final 1.0 stage or not, to know how to build the arborescence of future websites. Good to know, thanks a lot.
And thanks Mary, that was why I was not sure.
Offline
#89 2005-02-21 17:26:17
- Ray
- Member
- Registered: 2004-03-02
- Posts: 154
Re: Txp 1.0 RC3 Available
> kusor wrote:
> … there are more possibilities for urls. In fact, you are able to use your own customized url_scheme function.
Final state will be on 1.0. And be patient until Alex rewrites the code of his plugin ;-)
Thanks Kusor. Would I be correct to say that your above reply pretty much answers the questions in<a href=“http://forum.textpattern.com/viewtopic.php?id=6473”>this</a> thread?
Offline
Re: Txp 1.0 RC3 Available
Another question : is it planed to be able to localize the TXP help (especially the Textile Help) in the 1.0 ?
Right now, there are no easy way to do this, apart from installing a localized XMLRPC server somewhere and hack the code to link to it.
If the textpattern.com XMLRPC help server can handle several version (aka localized files), I can provide them for my language if needed (and if I know the format of the datas).
Last edited by Jeremie (2005-02-21 19:37:28)
Offline
Re: Txp 1.0 RC3 Available
Perhaps an option could be added, in the event mod_rewrite is unavailable, for prepending ‘index.php/’ to URLs in the link itself. Then you’d be able to keep the clean URL and still use $_SERVER[‘PATH_INFO’].
I had a plugin in the works to add this functionality to TxP but RC3 killed it :)
- sgb
Offline
Re: Txp 1.0 RC3 Available
> kusor wrote:
> Independent of the state of urls on RC3, there are more possibilities for urls. In fact, you are able to use your own customized url_scheme function. Give a look at line 951 of taghandlers.php.
Be careful, though. I badly damaged my test install trying to get year/month/title to work.
It is good to knew more flexibility is coming because I made some really odd choices on a couple of weblogs a couple of years ago that I would like to preserve when I switch them over.
Offline
Re: Txp 1.0 RC3 Available
Sorry if this has been discussed before. I think it would be a good idea if “classic” TxP URLs (section/id/title) always work, regardless of which URL scheme is selected. That way authors are free to switch schemes on their sites without fear that they may break existing links.
Looking at publish.php this might be easily accomplished by moving:
case ‘section_id_title’:
$out[‘s’] = (ckEx(‘section’,$u1)) ? $u1 : ‘default’;
$out[‘id’] = (is_numeric($u2) && ckExID($u2)) ? $u2 : ‘’;
// although you’d know $u2 is a number so you could do away with the extra logic at this point and say
// $out[‘id’] = (ckExID($u2)) ? $u2 : ‘’;
break;
to the outter switch block and changing the case to:
case is_numeric($u2):
These are just my thoughts. I’m sure there are some caveats with this method but I think it might be worth while to investigate a means to preserve “classic” compatibility.
Update: I’ve tried this on my local server (Linux PPC, Apache 2, PHP 4.3.10, TxP 1.0RC3) and it seems to be working perfectly. I have the URL mode set to “/title” but the site correctly responds to “/section/id/title” URLs.
Update: I realize this isn’t the best place so I started a <a href=“http://forum.textpattern.com/viewtopic.php?pid=41809#41809”>new topic here</a>
- sgb
Last edited by sungodbiff (2005-02-22 04:10:20)
Offline
Re: Txp 1.0 RC3 Available
I have another (yes, I know :p) question, about Textile this time. Why Textile use entities for every non-ascii characters, instead of the raw UTF8 character ?
In pre-RC3 versions, editing the encodeEntities function of the Textile lib from htmlentities to htmlspecialchars worked fine; it seems it doesn’t anymore.
I’m sure there is a good reason for the systematic use of entities, but I can’t think of one…
Offline
Re: Txp 1.0 RC3 Available
Great to hear Textpattern rears its pretty face once again, and in a much more active fashion than ever before.
Nice!
About Textile – I’ve never understood why Textile is not just replaced with f.e. htmlArea? (or some other wysiwyg editor) …
?
Last edited by raveoli (2005-02-22 10:44:03)
Offline
#96 2005-02-22 11:12:02
- tim
- New Member
- From: England
- Registered: 2004-03-26
- Posts: 3
Re: Txp 1.0 RC3 Available
> raveoli wrote:
> About Textile – I’ve never understood why Textile is not just replaced with f.e. htmlArea? (or some other wysiwyg editor) …
Plaintext > WYSIWYG
Offline