Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: rah_metas // new 1.x-versions of SEO/redirecting/automatic meta-tools
maniqui wrote:
1. Option (attribute) to “disable” limits (ie. words/maxchars) if the preferred field (ie. description_from) is being used.
User won’t need the plugin for that. If user doesn’t want limit or whatnot, the one can use custom_field. But if the user wants, the user can use if_custom_field to raise the articele word limit to huge amount.
[...]words='<txp:if_custom_field name="description">9999<txp:else />25</txp:[...]Possibilities are limitless.
“id” attribute, to generate/grab meta from a very specific article.
Sure. Thanks. When I’m going to release the next version, it will include the id support.
Currently, custom article content can fetched by using article_custom and feeding it to the attributes. Tho, that is useless for list of articles, because if you are making metas for that particular need, you don’t obviously need rah_metas for that.
Last edited by Gocom (2009-11-30 23:43:47)
Offline
Re: rah_metas // new 1.x-versions of SEO/redirecting/automatic meta-tools
Oh, I missed your reply, Gocom.
Gocom wrote:
(…) But if the user wants, the user can use if_custom_field to raise the article word limit to huge amount. (…)
Thanks for the trick.
Sure. Thanks. When I’m going to release the next version, it will include the id support.
Great! Much welcomed :)
Is the next version just around the corner? ;)
Offline
Re: rah_metas // new 1.x-versions of SEO/redirecting/automatic meta-tools
a wonderful plugin, Gocom, thank you. After tweaking around for a while, i have still one small issue i cannot fix.
The facts: i use txp 4.2.0 + rah_metas 1.1; keywords=’<txp:article><txp:keywords /></txp:article>’ keywords_limit=“30”
In my blog-startsite there are several single postings, each with its keywords (titled in german as “abgelegt unter”).
The issue: the keywords are comma-separated but the last keyword of each posting has no ending comma. That leads to: it is meltet with the first keyword of its following posting. To be seen in html view.
Example: <meta name=“keywords” content=“cms, txpB2B-Marketer, sales-pipeline, ..
“txp” was the last keyword of the youngest post and “B2B-Marketer“was the first of the elder post. Where do I have to screw?
Last edited by geroldbraun (2010-01-21 19:14:38)
Smile, Breath, Go slowly – Thich Nhat Hanh
Offline
Offline
Re: rah_metas // new 1.x-versions of SEO/redirecting/automatic meta-tools
thank you for a perfect quick fix and really quick answer, Gocom. Everything is fine now.
Smile, Breath, Go slowly – Thich Nhat Hanh
Offline
Re: rah_metas // new 1.x-versions of SEO/redirecting/automatic meta-tools
Hey Gecom, nice plugin!
One problem:
Although the messy_to_clean_redirect redirects to the clean url nicely, it doesn’t seem to create a genuine 301 header. Instead, I get the “usual” 304/Not modified header.
I have observed this with the Live HTTP Headers add-on for Firefox.
I see nothing strange in you code though…
Could this be a malfunction?
Kensington TXP powered rock
Offline
Re: rah_metas // new 1.x-versions of SEO/redirecting/automatic meta-tools
jan wrote:
Could this be a malfunction?
Hi Jan,
Could be that Textpattern’s header block owns the flat of the tiny teddy bear; TXP’s core is defined first. To get over double headers-sent and content-before-headers boguses, one can use new output buffer.
Likely this includes that the header code is sent before TXP starts own markup output. To do this we could take redirection code off and put it inside a shiny new function:
rah_metas_totallyunofficial_redirect();
function rah_metas_totallyunofficial_redirect() {
if(!is_numeric(gps('id')) and !gps('s'))
return;
ob_start();
ob_end_clean();
if(gps('s'))
header('Location: '.pagelinkurl(array('s' => gps('s'))),TRUE,301);
if(is_numeric(gps('id')))
header('Location: '.permlink(array('id' => gps('id'))),TRUE,301);
exit();
}Something along those line. I would put my hopes on in tho.
Offline
Re: rah_metas // new 1.x-versions of SEO/redirecting/automatic meta-tools
Makes sense :) Will try that, and post results!
Kensington TXP powered rock
Offline
Re: rah_metas // new 1.x-versions of SEO/redirecting/automatic meta-tools
as far as i can see, description_from=“metadescription” and keywords_from=“custom2”, will not work with sections (will work fine with articles); If i want static pages (sections like .. www.mysite.com/contact/) with keywords and description, i have to “hardwire” it in the page header, right? Or did i miss something?
Smile, Breath, Go slowly – Thich Nhat Hanh
Offline
Offline
Re: rah_metas // new 1.x-versions of SEO/redirecting/automatic meta-tools
Thanx Gocom, again a quick and clear answer . I will workaround with <txp:if_section > in the call of your plugin.
Smile, Breath, Go slowly – Thich Nhat Hanh
Offline
Re: rah_metas // new 1.x-versions of SEO/redirecting/automatic meta-tools
Hi
I don’t understand how it works. I’m reading all pages and the help but may be i’m a idiot, can´t figure out hehe
How can i do to make the automatics keywords?
not sure but i copied this code
<txp:rah_metas keywords='<txp:article><txp:keywords /><txp:if_last_article><txp:else />,</txp:if_last_article></txp:article>' />
when i go to see the source code between the description and copyright there is a empty space without “keywords”
I tried to explain my best
Sonríe | Smile . <txp:lover />
Offline