LG Better Meta 1.4.0 - NEW RELEASE!

Hi Leevi,

Was just wondering if you had any ideas on the Site Title situation at all yet?

Thanks.

Best wishes,

Mark

Hi Leevi, Was just wondering if you had any ideas on the Site Title situation at all yet? Thanks. Best wishes, Mark

Hey Mark,

Sorry I didn’t get back to you on this… for some reason I wasn’t being notified… Anyway I’m building a new site now with LG Better Meta and I am trying to squash as many bugs as I go. Hopefully a new release won’t be too long that fixes all of the bugs.

Cheers

Hiya,

Not a problem. Thought you might be busy or something 😉 You’re always up to something you are 😉

Not a real problem but just caught me out the one day as you know how it is, when you know the system really well you tend not to look at the names of things but then when something changes you think you are going mad or something. The site still works fine so I can wait patiently 😊

Thanks again for the fantastic support on all your work. Hope you are keeping well.

Best wishes,

Mark

I’m having some problems with this extension. According to what others have specified on the boards and what Leevi has told me specifically, when I embed my header template, I need to pass on a url_title as a parameter.

This is what I did:

{embed="includes/header" url_title="{segment_2}"}

The following does not result in anything additional being displayed in the browser titles. I have the header stock, with all the original embed tags as follows:

{exp:lg_better_meta
    entry_id="{embed:entry_id}"
    weblog_id="{embed:weblog_id}"
    url_title="{embed:url_title}"
    title="{embed:title}"
    description="{embed:description}"
    keywords="{embed:keywords}"
    author="{embed:author}"
    publisher="{embed:publisher}"
    rights="{embed:rights}"
    date_created="{embed:date_created}"
    date_modified="{embed:date_modified}"
    date_valid="{embed:date_valid}"
    identifier="{embed:identifier}"
    robots_index="{embed:robots_index}"
    robots_follow="{embed:robots_follow}"
    robots_archive="{embed:robots_archive}"
}

UPDATE Not too sure about “url_title”, but I’m able to get the “title” parameter to work. Right now, I’m testing it on a template used to catch member information with Solspace’s User module.

So rather, this is what I am doing:

{embed="includes/header" title="{segment_3}"}

This seems to append the information just fine. However, if I’m doing anything wrong, if anybody could enlighten me on this, I’d greatly appreciate it. Does the url_title parameter only apply to pages with a weblog:entries tag?

Which version of LG Better Meta are you using?

Leevi,

Thanks for the lightning quick response. I’ve just posted an update to the original post I made above.

Leevi, Thanks for the lightning quick response. I’ve just posted an update to the original post I made above.

The url_title only applies to weblog entries tags. As there is no meta for members you will need to pass different values through.

If you want some nice meta I suggest passing through the following params

title=”{screen_name} | Member Profiles” description=”{bio}”

or something similar

Leevi,

Thanks for the tips. I think I was missing a fundamental understanding of how it works, as I’m probably one of the less technically inclined active members around here. =) I think I understand how everything works now.

This plugin has exceeded my expectations! =)

Good to hear… so which version are you using… the latest Commercial version is MSM aware and fixes quite a few bugs I haven’t fixed in the free version.

Leevi,

I actually purchased this module off you, so I’m using the commercial one (1.5). =)

One last question.. I don’t know if this should be treated as a Better Meta question, or just EE in general, but I’ve noticed that things such as apostrophes and any other special characters automatically get parsed into the HTML tag equivalent.

Is this recommended? Does it really matter? And finally, have you solved this? If so, should I run them all through a plugin like No Formatting?

HTML formatting is something I am in the middle of testing with the next release. At the moment you can pass the values though as unencoded and the module should encode them for you.

HTML formatting is something I am in the middle of testing with the next release. At the moment you can pass the values though as unencoded and the module should encode them for you.

For descriptions, it was noted on your site that it should be limited to 150 characters or less. Would it be recommended than, to post a description or summary directly pulled from my weblog entry details? The posts are not great in length, so they more or less can squeeze in there, or at least some of them.

Was wondering would this be a practical usage of the “description” field? Could you highlight what one might put in there, if not for something such as the body of an arrticle? I understand that I can override these by specifying a description as per post, but if I don’t, would this be the next logical thing to insert in there pretty much?

Hey guys,

Version 1.6.1 is now available.

• Integrated LG Addon Updater (fixes blank cp issues)
• Fixed update script from version 1.4.2 up

As always LG Better Meta 1.6.1 is available on the ExpressionEngine section of my site.