Search Engine Friendly

(8:20:37 AM) marclaport1: Redhatter: how do you get forums.html instead of tiki-forums?
(8:21:05 AM) Redhatter: Two things: mod_rewrite, and a modification to the templates.
(8:21:57 AM) Redhatter: The mod_rewrite thing is distributed with Tikiwiki for what it's worth... I just modified the template so that the hyperlinks utilise it.
(8:24:29 AM) Sug4r` left the room (quit: Read error: 113 (No route to host)).
(8:25:15 AM) luciash left the room (quit: Read error: 113 (No route to host)).
(8:25:20 AM) Redhatter: I'm thinking we should actually write a smarty plugin that generates these URLs, hooked up to a class that's used internally.
(8:26:34 AM) Redhatter: e.g. {thread(forum=>3, comment=>1234, offset=>123)}link to some thread{thread} ... links to a thread.
(8:27:19 AM) marclaport1: I see. Why do you do it?
(8:30:04 AM) marclaport1: Redhatter: weird char on this page: http://www.asperger.asn.au/Contact_Us.html
(8:30:43 AM) Redhatter: Well, they look cleaner, and they are more friendly to search engines.
(8:31:01 AM) Redhatter: Think about bookmarking, or manually entering a URL that may exist on a printed page.
(8:31:20 AM) Redhatter: The default Tiki URLs are a PITA in that regard due to their shear length.
(8:31:31 AM) marclaport1: http://www.asperger.asn.au/Contact_Us would be nice too, no?
(8:32:19 AM) Redhatter: It would... I throw the .html on the end so that tools like `wget` will put a sane extension on when fetching a page.
(8:32:35 AM) marclaport1: interesting
(8:32:35 AM) Redhatter: The URL you just mentioned though, does work. :-)
(8:33:13 AM) marclaport1: I would like to see RW rules as a tiki builit-in feature
(8:33:29 AM) marclaport1: optional off of course because it would likely only work on Apache
(8:33:56 AM) Yoni left the room (quit: Read error: 110 (Connection timed out)).
(8:34:05 AM) marclaport1: There have been some hacks but nothing that everyone is converging around
(8:34:10 AM) Redhatter: Apache, and apache-compatible servers (perhaps lighttpd)
(8:34:29 AM) Redhatter: I've started working towards something, but I'm not completely sure how to achieve it.
(8:34:51 AM) marclaport1: On most of my sites, I rename _htaccess to .htaccess and it helps but the problem is internal links
(8:35:18 AM) Redhatter: Yeah. I had to hack the code to get those to work.
(8:35:27 AM) marclaport1: I remember Sylvie mentioning a solution but it's not built-in
(8:35:43 AM) Redhatter: I'm thinking a PHP class that contains functions which spit out the raw URL, given the script parameters.
(8:35:48 AM) marclaport1: did you see coofercat's work on that?
(8:36:01 AM) Redhatter: No I haven't.
(8:36:56 AM) marclaport1: http://www.coofercat.com/wiki/TikiURLt
(8:37:51 AM) marclaport1: Coofercat writes below on the page "I submitted the odd patch here and there, and got as good as no response from them (not even to say "sorry, but no thanks"). I suspect other people have has the same experience, which means that version after version, the same problems persist."
(8:38:43 AM) marclaport1: I am 99% sure I wrote to coofercat and 80% sure I commented the previous page to ask him to share his work.
(8:38:51 AM) marclaport1: Maybe he didn't get my email
(8:39:18 AM) Redhatter: Perhaps... Email is a best-effort delivery mechanism.
(8:40:18 AM) marclaport1: Anyway, I don't like these offsite, alone-in-a-corner hacks for many reasons
(8:40:49 AM) marclaport1: Much better to do in main source code base, in collaboration with other people of the community
(8:40:52 AM) Redhatter: Indeed, this is why I submitted some of the more critical patches for our site.
(8:41:00 AM) marclaport1: :-)
(8:41:12 AM) Redhatter: The URL rewriting is a nice-to-have (the site works without the hacks)
(8:41:20 AM) jcyrisse: morning all...quick question. when downloading the 1.10 branch from cvs, do i use BRANCH-1-10?
(8:41:21 AM) marclaport1: And if people have varying needs, it's simpler to make some options
(8:41:27 AM) marclaport1: jcyrisse: yes
(8:41:37 AM) jcyrisse: ty
(8:42:01 AM) Yoni n=Yoni@DSL212-143-221-71.bb.netvision.net.il entered the room.
(8:42:11 AM) sylvieg: nobody around ready to give me a hand on the javascript to have the suckerfish menu working on IE?
(8:43:41 AM) marclaport1: Redhatter: in your question to make good SEFURLs for Tikiwiki, and hopefully add as an option to Tiki 1.10 code, coofercat's work is the most important, and #2 would be to consult with sylvieg who has implemented this in many places
(8:43:45 AM) Yoni: testing i can Sylvie
(8:44:33 AM) Redhatter: marclaport1, Sounds sane :-)
(8:45:19 AM) Yoni left the room (quit: Client Quit).
(8:46:02 AM) marclaport1: Redhatter: http://dev.tikiwiki.org/Search+Engine+Friendly
(8:46:56 AM) Yoni n=Yoni@DSL212-143-221-71.bb.netvision.net.il entered the room.
(8:48:55 AM) jcyrisse: anyone had any success posting to tw blogs with ScribeFire?
(8:49:07 AM) marclaport1: jcyrisse: never tried
(8:49:30 AM) Redhatter: Just a silly question though... the forum thread links... Out-of-the-box tikiwiki generates a URL of the form:
(8:49:30 AM) Redhatter: tiki-view_forum_thread.php?comments_parentId=XXXX&topics_threshold=XXX&topics_offset=XXXX&topic
(8:49:30 AM) Redhatter: s_sort_mode=lastPost_desc&topics_find=&forumId=XXXX
(8:49:46 AM) Redhatter: What exactly are the meanings of these fields?
(8:50:02 AM) jcyrisse: marclaport1: thanks
(8:50:28 AM) Redhatter: I've figured out the only real ones I need to view a thread, are the forumId, comments_parent
(8:50:55 AM) Redhatter: *comments_parentId and topics_offset... but can't quite figure out where these parameters come from.
(8:51:21 AM) marclaport1: sylvieg: the new group subscribe plugin: do you think it'll work with InterTiki?
(8:51:39 AM) marclaport1: Redhatter: forum URLs are too long
(8:51:48 AM) marclaport1: bad to post in an email...
(8:52:04 AM) Redhatter: Yeah... hence the following line in .htaccess:
(8:52:13 AM) Redhatter: RewriteRule ^thread-(0-9+).(0-9+).(0-9+).html tiki-view_forum_thread.php?comments_parentId=$2&topics_threshold=0&topics_offset=$3&topic
(8:52:13 AM) Redhatter: s_sort_mode=lastPost_desc&topics_find=&forumId=$1 QSA,L
(8:55:47 AM) ***Redhatter starts pulling his svn working copy of the ASA site
(8:57:55 AM) sylvieg: marclaport1: if the group are on the main - no
(8:58:16 AM) marclaport1: hmmm
(8:58:37 AM) marclaport1: I would like to dogfood to make project groups on dev.tikiwiki.org
(8:59:13 AM) marclaport1: If people sub to the slave, their groups will be overwritten at their next login (I think)
(8:59:32 AM) luciash n=luci@rtvrtv.pol.bezdrat.net entered the room.
(8:59:39 AM) ricks99_ i=945701ab@gateway/web/cgi-irc/linux-quebec.org/x-91cb3db8b65c12ee entered the room.
(9:00:06 AM) ricks99_: hi all
(9:01:01 AM) marclaport1: polom ricks99_
(9:01:31 AM) Sug4r n=Sug4r@rtvrtv.pol.bezdrat.net entered the room.
(9:01:52 AM) marclaport1: ideally, users could self-subscribe to groups on the master and join the appropriate group on the slave, at their next login
(9:06:17 AM) marclaport1: Redhatter: another thing that would be nice is configuring URLS from tiki admin panel. Ex.: a blog post could have an alternate and more descriptive URL (like many blog engines)
(9:07:11 AM) Redhatter: marclaport1, Indeed. I feel it's definitely a feature worth developing.
(9:07:21 AM) luciash: polom polom
(9:07:55 AM) Redhatter: I'll see what I can come up with ... even if it's a hard-coded class for now.