Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
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
Re: Txp 1.0 RC3 Available
About Textile – I’ve never understood why Textile is not just replaced with f.e. htmlArea? (or some other wysiwyg editor) …
Haven’t we been over that one already? Granted, I’ve replaced Textile with Markdown on my personal site, but really WYSIWYG is just horrific overkill for this application, not to mention bad UI in some cases.
You cooin’ with my bird?
Offline
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) …
After using Textile for two years now, I prefer it to the wywiwyg editors. I find it much easier to use textile tags than clicking around another interface.
Last edited by michaelkpate (2005-02-22 16:10:35)
Offline
#99 2005-02-22 14:46:22
- Niloc
- Member
- Registered: 2004-05-15
- Posts: 38
Re: Txp 1.0 RC3 Available
> michaelkpate wrote:
> > raveoli wrote:
> About Textile – I’ve never understood why Textile is not just replaced with f.e. htmlArea? (or some other wysiwyg editor) …
After using Textile for two years now, I prefer to the wywiwyg editors. I find it much easier to use textile tags than clicking around another interface.
I fully agree.
Offline
#100 2005-02-22 14:50:50
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) …
First was Textile, then Textpattern.
Do you remember that this is Textpattern forum, the web publishing tool by Dean Allen, the original Textile author?
That’s the reason. Textile is brilliant. Pure genious.
Pedro Palazón
http://kusor.net http://kusor.com
Offline
#101 2005-02-22 15:21:25
Re: Txp 1.0 RC3 Available
Jeremie: I suspect this is a workaround (hmm) for the bug where unescaped i18n characters confuse textile. This has to do with the way TExtile recognizes text boundaries.
VC3 :: weblog :: my wishlist
Offline
#102 2005-02-22 16:58:57
Re: Txp 1.0 RC3 Available
Etz, I was hoping one of the three Djinn answer that, since we got them here :)
Offline
#103 2005-02-22 18:40:57
- Remillard
- Plugin Author
- From: Lenexa, KS
- Registered: 2004-05-16
- Posts: 169
Re: Txp 1.0 RC3 Available
Well Musings of an Engineer has been bumped to 1.0RC3 with nary a problem. In fact fewer problems than RC2! (which never really saw the light of day on MOAE). Looks great.
EDIT: Alright there was ONE problem, but it was so minor as to not be a problem. I had a list where I’d specified UL as a wraptag, and LI as a break tag, and had to take that part out, because the link listing actually worked right the first time :). So technically I was unfixing a workaround not fixing a problem.
Last edited by Remillard (2005-02-22 18:43:50)
Offline
#104 2005-02-22 18:56:10
Re: Txp 1.0 RC3 Available
I wouldn’t want to publish anything without Textile. Period.
Offline
#105 2005-02-22 23:15:23
Re: Txp 1.0 RC3 Available
Textile produces far better markup in most cases than htmlarea. Smaller and more standards-compliant. Better typography too (e.g., correct open/closed double quotes, em- and en-dashes).
Offline