tru_tags: A tagging plugin for textpattern

merz1 · 2010-03-21 12:23:19

No idea :(
Diagnosis? Missing files?
Change the TXP status from ‘live’ to ‘debug’ and check the output.

BTW: Parameter 404redirect="0" is new to me and Textbook search shows no hits. Is a documentation available/missing?

truist · 2010-03-21 13:53:09

It seems likely that the articles in question are draft, are future-dated, or are in a section that is marked not searchable. Does one of those explain it?

Markus, 404redirect is a tru_tags attribute.

merz1 · 2010-03-21 14:25:00

Thanks Nathan, found the 404redirect explanation :)

If a tru_tags_handler is called for a tag that is no longer valid, it will redirect the user to the site’s default 404 page. You can override this behavior with the noarticles attribute, which accepts a URL that it will redirect to, instead. You can turn off this behavior by setting the 404redirect attribute to 0.

Could you elaborate the this behavior part of the explanation. To me it sounds like a double override.

default 404 page
404: ‘noarticles attribute’ sends visitor to user defined URL
‘404redirect attribute to 0’ switches off what? What will show up?

What’s the logic?

kevinpotts · 2010-03-21 17:05:54

@truist — The problem was indeed the future dating of the articles. A single time attribute fixed everything. Thanks for the speedy response, as always. (And fantastic plugin … it’s been a key piece of my arsenal for years.)

truist · 2010-03-22 17:34:44

Markus, I believe that setting it back to ‘0’ will revert the plugin back to the behavior before I implement the 404 feature – namely that the user will just get an empty page, with no articles.

merz1 · 2010-03-22 18:06:05

Nathan, thanks for the answer. Well, I am not using it anyway, but…

If you find time you might add a funny (4 line?) matrix table into the tru_tags documentation which will precisely show what to expect :-)

truist · 2010-05-21 19:54:36

Survey / Poll:

tru_tags currently has a problem where keywords with “hyphens-and spaces” don’t work. (Keywords with just hyphens or just spaces do work.) I have a user who has offered to implement a fix and submit a patch, but it will be cumbersome to fix it in a backwards-compatible way.

The way tru_tags currently handles spaces is by converting them to hyphens in URLs, and then converting hyphens back to spaces when querying the Textpattern database. The ideal fix would be to either use a less-likely character (like “+” or “—”), or to URLencode the keywords before putting them in URLs (so “with spaces” will become “with%20spaces” in URLs). The problem is that this would break bookmarks and any external links into your sites, which I have very carefully avoided doing in the past.

So, a two-part poll:

1) Which solution would you prefer: (a) a clean-looking but still non-standard character like “+” or “—” or (b) URLencoded keywords in URLs?

2) How important is it to you that we provide a “do it the old way” setting, so your old URLs still work the same way?

I can’t make a real poll here, so please just reply by making comments. Thanks!

alanfluff · 2010-05-21 20:34:03

Hi Nathan,

1) If you’re going to bother to do this, then I assume someone might want a “+” or “—” as part of a tag name(!), so for those (edge case) people, URLencoded would be best. URLencoded seems the most complete solution if I understand this right.

2) I would say it was very important to provide a “do it the old way” facility for sites that are up and that spidered by the SE’s.

Cheers, -Alan

Last edited by alanfluff (2010-05-21 20:35:00)

alanfluff · 2010-05-21 20:37:34

PS: It seems a chunk of work for you for no big gain. Presumably people are keep to loose the visual look of dashes in a tag cloud? jQuery etc could re-write those on the fly, as it’s arguably a presentational request.

Again, if I’ve understood this right ;)

merz1 · 2010-05-22 10:25:35

1) I don’t care

2) ~~Very~~ Not so important (because I have plenty of articles where I use tag links inside the article body. But on the other hand) I have no idea how many ‘n word’ tags I have used in the past inside article bodies but not too many.

2a) Give me a database filter and I clean up the mess :)
2b) SEO wise it’s the same. ‘N word tags’ are seldom and search engines will adopt in a matter of days.

3) But I like the ‘hyphen way’ tru_tags is working now. Does that count as an argument?
3a) Building external URLs with tru_tags (eg Amazon widgets) is safe with hyphens. I am not sure about other characters.
3a1) For Amazon search links I already use striphyphens="1" urlencode="1".
3a2) Because of bad performance all Amazon widgets are already deleted.

Go ahead as you like :)

pfctdayelise · 2010-06-03 13:56:38

Hi,

I’ve been using tru_tags on a few Textpattern sites for as long as I knew about it.
I recently redid my friend’s site and noticed the snippets on tag pages were displaying “special characters” poorly. Mainly I think characters are escaped that shouldn’t be.
I saw that in tru_tags 3.5 there is a comment that “Fixed problems with multi-byte (utf-8, unicode, international) characters.” so I upgraded. But I still have bad output:
compare
http://www.clntranslations.org/tag/social-security/
to
http://www.clntranslations.org/search-results/?q=social+security

I have unticked the box “Convert tags to lowercase by default” under Extensions. I’m running tru_tags 3.6 on Textpattern 4.2.0.

On my tag page I have

<txp:tru_tags_handler form="search_results"/>

this form is also called by my search page, although slightly differently:

<txp:article limit="100" searchform="search_results" />

I tried changing the tru_tags_handler attribute to searchform, but it didn’t fix the smart quotes problem.

Any ideas?

thanks,
Brianna

truist · 2010-06-03 14:54:39

pfctdayelise – the problem is probably with a tag in your search_results form. I’ll bet you’re using something like the TXP tag search_term which won’t work with tru_tags (because it specifically looks for the ‘q’ parameter. Can you paste the contents of your search_results form?

Textpattern CMS

Textpattern CMS support forum

#673 2010-03-21 12:23:19

Re: tru_tags: A tagging plugin for textpattern

#674 2010-03-21 13:53:09

Re: tru_tags: A tagging plugin for textpattern

#675 2010-03-21 14:25:00

Re: tru_tags: A tagging plugin for textpattern

#676 2010-03-21 17:05:54

Re: tru_tags: A tagging plugin for textpattern

#677 2010-03-22 17:34:44

Re: tru_tags: A tagging plugin for textpattern

#678 2010-03-22 18:06:05

Re: tru_tags: A tagging plugin for textpattern

#679 2010-05-21 19:54:36

Re: tru_tags: A tagging plugin for textpattern

#680 2010-05-21 20:34:03

Re: tru_tags: A tagging plugin for textpattern

#681 2010-05-21 20:37:34

Re: tru_tags: A tagging plugin for textpattern

#682 2010-05-22 10:25:35

Re: tru_tags: A tagging plugin for textpattern

#683 2010-06-03 13:56:38

Re: tru_tags: A tagging plugin for textpattern

#684 2010-06-03 14:54:39

Re: tru_tags: A tagging plugin for textpattern

Board footer