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
but if i’m looking at frontpage source, it’s still uses a default metadescription.
Er yeah, cause it isn’t article. Automatic metadescription is only aplied in individual article context as stated in the doc :) The plugin can not magically know what content to use, you know ;)
i can’t find rah_section_form from rahforum.biz :(
Here you go: rah_output_section_form I use that plugin to output “section/category/tag” etc listing page descriptions.
Last edited by Gocom (2008-10-27 13:31:42)
Offline
#17 2008-10-27 14:29:58
- Gallex
- Member
- Registered: 2006-10-08
- Posts: 1,331
Re: rah_metas // new 1.x-versions of SEO/redirecting/automatic meta-tools
Gocom wrote:
Er yeah, cause it isn’t article. Automatic metadescription is only aplied in individual article context as stated in the doc :)
i don’t understand one thing: if it’s not an article then what is it?
Here you go: rah_output_section_form I use that plugin to output “section/category/tag” etc listing page descriptions.
you wrote rah_section_form instead of rah_output_section_form in previous post, that’s why i didn’t find it :)
Offline
Re: rah_metas // new 1.x-versions of SEO/redirecting/automatic meta-tools
Gallex wrote:
i don’t understand one thing: if it’s not an article then what is it?
It’s a list context page, a section page, as frontpage always is. Not an individual article page, just a page where you just output the article, and as we know, rah_metas can not know that.
Article context is place where permlink leads, where if_individual_article conditional returns true.
Last edited by Gocom (2008-10-27 15:09:18)
Offline
Re: rah_metas // new 1.x-versions of SEO/redirecting/automatic meta-tools
New version, 1.0.4, of rah_metas released. Changelog:
- Added attribute:
relnext. - Added attribute:
relprev. - Minified amount of used globals by one.
Offline
Re: rah_metas // new 1.x-versions of SEO/redirecting/automatic meta-tools
Hi Jukka,
I know you fixed a bug related to last words being truncated wrongly, but both in v1.0.3 and v1.0.4 I’m getting this output if rah_metas truncates the sentence on an html entity:
“word……” (correct version: “word……”
or
“‘last words&…” (correct version: “‘last words’&hellip”).
BTW, as a Christmas gift (for you to us!) it may be cool to cut the … if it is the latest character on the truncated text, so to avoid a double ellipsis. Ok, ok, Santa Claus must be already on his way, maybe for next X-mas…
Offline
Re: rah_metas // new 1.x-versions of SEO/redirecting/automatic meta-tools
maniqui wrote:
I know you fixed a bug related to last words being truncated wrongly, but both in v1.0.3 and v1.0.4 I’m getting this output if rah_metas truncates the sentence on an html entity
You have just reached the limit of characters. All chars are counted as chars, also that are in entities.
Will fix this by using textile body and textile excerpt, instead of body_html and moving Textiling and html removing after the count. That way it will avoid these situations. Will make page load slower but well. I already have somehow useless textile parsing in the code.
maniqui wrote:
BTW, as a Christmas gift (for you to us!) it may be cool to cut the
…if it is the latest character on the truncated text, so to avoid a double ellipsis. Ok, ok, Santa Claus must be already on his way, maybe for next X-mas…
Will be that by removing dots and commas end of the description after count is done, before content is Textiled.
Edit. Forget about that, going to build a brand new word/char counting method that doesn’t use really slow preg functions :)
Last edited by Gocom (2008-12-24 23:45:47)
Offline
Re: rah_metas // new 1.x-versions of SEO/redirecting/automatic meta-tools
Released a new version of rah_metas, 1.0.5. Changelog:
- Added attribute: escape.
- Rebuild description’s word and chars counting: now always counts correctly: doesn’t ever cut words.
- Optimized parsing and speed: plugin is around 20% faster than before.
- Removes
…from the end of the description if trails are used and description is cut from context and shortened. - Updated docs and now PHP minimum requirement is 4.4.0+.
Edit. All that downloaded plugin before 3:50 AM GMT+2, it was not version 1.0.5, even if the page stated so. There was some issues with syncing, that why 10 minutes “offset”. Now the plugin download is version 1.0.5 and not 1.0.4.
Last edited by Gocom (2008-12-25 01:56:51)
Offline
#23 2009-04-14 08:53:23
- mrjysta
- Member
- Registered: 2008-09-22
- Posts: 89
Re: rah_metas // new 1.x-versions of SEO/redirecting/automatic meta-tools
Hey guys, any way this plug-in will work for section stickies and the default home page? ATM I don’t get any description or keywords on these pages.
Offline
Re: rah_metas // new 1.x-versions of SEO/redirecting/automatic meta-tools
mrjysta wrote:
Hey guys, any way this plug-in will work for section stickies and the default home page? ATM I don’t get any description or keywords on these pages.
Because those aren’t articles, but article_list context pages, so the plugin can not know what to show in the meta data, because there is none to show of. Some quotes from the previous page:
Er yeah, cause it isn’t article. Automatic metadescription is only aplied in individual article context as stated in the doc :) The plugin can not magically know what content to use, you know ;)…
It’s a list context page, a section page, as frontpage always is. Not an individual article page, just a page where you just output the article, and as we know, rah_metas can not know that.
Article context is place where permlink leads, where if_individual_article conditional returns true.
Solutions: pull them manually, if_section compinations, description and keywords default values, rah_output_form or so on.
Last edited by Gocom (2009-04-14 09:12:08)
Offline
Re: rah_metas // new 1.x-versions of SEO/redirecting/automatic meta-tools
Gocom, been using this plugin for ages now: a real time saver, thanks.
Just noticed a curious behaviour that I think (not 100% confirmd yet) may be related to the relnext attribute. What I’m seeing is that when I visit Page A, the TXP logs dutifully show that I visited Page A but also show that I visited Page B. Similarly, if I visit Page J, the logs show Page J and, immediately after that, Page K.
In short, it seems to be logging two hits per page visit; one for the current article and one for the next article. Switching rah_metas off appears to make the logs record one hit per page.
Could there be something in your use of link_to_next() or newer() that’s causing this? It’s just messing up smd_lately which uses the log files to show what a visitor has viewed recently. Confused me for ages because it was showing articles I hadn’t actually viewed and I thought smd_lately was broken!
Any ideas?
EDIT: I’m running a stock 4.0.8 with rah_metas 1.0.5
Last edited by Bloke (2009-08-04 13:31:11)
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Hire Txp Builders – finely-crafted code, design and Txp
Offline
Re: rah_metas // new 1.x-versions of SEO/redirecting/automatic meta-tools
Bloke wrote:
Gocom, been using this plugin for ages now: a real time saver, thanks.
You’re welcome.
Bloke wrote:
Could there be something in your use of
link_to_next()ornewer()that’s causing this?
I don’t think it’s in the server side code, Mr. Bloke :)
If there is log hit made with your referrer, I would suspect the method your browser uses to handle relative links. Is the hit also noted by the server not just by TXP?
If it is, then most likely the browser is pre-fetching/checking the previous and next pages. For example, browsers, like Firefox even if there isn’t favicon, try to load favicon.ico from the root of domain. Similiar case. Some media browsers check the rss feeds for instance.
You can avoid that by turning relative links off from the plugin.
Last edited by Gocom (2009-08-04 15:54:17)
Offline
Re: rah_metas // new 1.x-versions of SEO/redirecting/automatic meta-tools
Gocom wrote:
I don’t think it’s in the server side code, Mr. Bloke :)
Hehehe, that’s what confused me: I couldn’t find anything in the core that ran log_hit in any of the functions you used!
So I guess it’s browser-related. Stupid Firefox trying to be clever and doing what I don’t want it to. I’ll check the server logs to find out. Guess I have to live without relnext then :-(
Thanks for putting me on the right track, man.
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Hire Txp Builders – finely-crafted code, design and Txp
Offline
Re: rah_metas // new 1.x-versions of SEO/redirecting/automatic meta-tools
That prefetching thing seems evil… it’s unwanted optimization, slowing down the tubes, wasting resources, compromising privacy (I don’t want you, Firefox, fetching unwanted pages just to trick people that your browser is faster than others).
Offline
Re: rah_metas // new 1.x-versions of SEO/redirecting/automatic meta-tools
maniqui wrote:
That prefetching thing seems evil… it’s unwanted optimization, slowing down the tubes, wasting resources, compromising privacy (I don’t want you, Firefox, fetching unwanted pages just to trick people that your browser is faster than others).
It is (if it’s true that is). Even that favicon thing is bad IMHO. Eats both, users and server’s bandwidth. Plus what I’ve have tested, Firefox is slower than all the other major browsers, when looking at the hardware load stats and memory eating.
Hopefully, you can disable all (read: some) the nasty features by config in firefox. Also the memory optimizing feature that just eats CPU. Only thing that you can’t change by config is the new JavaScript engine, which IMO is really bad and unstable.
Note: my post is entirely IMO. You can take it as fiction.
Last edited by Gocom (2009-08-04 17:14:28)
Offline
Re: rah_metas // new 1.x-versions of SEO/redirecting/automatic meta-tools
Hi,
I have always been led to believe that description meta should always appear before keywords meta for fully optimised SEO (as most search engines ignore keywords nowdays anyway). rah_metas seems to default to keywords first then description, or can this be manually changed?
Thanks,
Phil
Offline