LG Better Meta v1.4.0 - Bug fixes and source code comments

Finally got around to re-installing this and it seems to be working fine. I feel like a dunce though as far as the output. My meta tags are in a different include than my title tag. How do I return just the title on the one template and the “block” of tags (which I edited for this specific site) on the meta tag include?

Also, noting that on line 209 of the plugin I see:

if($row['meta_robots_index']){
  $robots['archive'] = $row['meta_robots_archive'];
}

Should that first line be:

if($row['meta_robots_archive']){

Also, just to note, that clicking “Quick Save” loses all the meta info on my install.

What’s the easiest way to increase the amount of characters I can place in the default keyword field in the settings? The client gave me a list of keywords and they’re getting lopped off in the box. I caould change the DB field for keywords to “text” but is there some limit on that fields in the CP?

It’s weird because keywords and description look the same in the db (varchar(255)) but I can put a lot more text in the desc field than keywords.

Well it looks like it’s doing this under the hood of the page in the control panel:

Where in the world is that maxlength coming from? I don’t see it in the extension file. Is this being placed there by EE? Can I just change this field to textarea so I can get my extra words in there?

Anyone? This thread has crickets chirping!

Hey Ryan,

I’n not sure where the limitation is coming from!

I don’t think it is an EE thing although it could be doing some things crazy.

I have uploaded the lastest version I have running in my local environment. It fixes the one bug robots you mentioned and adds a recommended description character counter.

Grab it from the top of the thread

I changed the keywords to a textarea and that seems to have worked. I would grab your new files but I have already thoroughly modified this extension from the defaults for this particular install!

I have a feeling EE is “inserting” that code by default into textareas in the CP. I don’t know how else the maxlength could have been put in there - it certainly isn’t in your code!

If you have any improvements to the code send them through and I’ll add them to the extension 😊 Or even any suggestions and feedback!

Just a quick note to everyone using this extension…

There is new documentation and download available on my Expression Engine customisation resource!

All future updates / downloads will be made available at the link above. Feel free to still ask questions in this forum

Leevi -

You’re becoming a valuable resource, thanks for your work. I have two suggestions for you:

1. A detailed changelog for every new version of extension, plugin, etc. I would love to know exactly what changed between the last release and this one.

2. Some form of license for commercial usage with attribution removal. I would like to remove the attribution (only the HTML comment) for Better Meta on an install I did, and I’m sure some amount of money is worth that 😊 . If the client gets in there and sees it, and wants it removed (which isn’t a problem so far…), I’ll have to tell them something! And I’d rather not have to uninstall it just because of an HTML comment.

Again, thank you for your work. Keep it up! I look forward to trying to break whatever else you come up with!

Looks like a great plugin (just what I was looking for infact) but I saw the license comment in the screenshot and decided not to install it.

Anyway it’s your plug-in and you can do what you like 😊 Let me know if you change your mind though.

If your after a commercial license just drop me an email or pm and I will organise something with you.

There will be a commercial version released after I finish my next extension. It will also include a new settings form.

Cheers

Excellent excellent extension. Very polished! I agree about paying to remove the attribution - I’d pay a small fee to do that as well. Once again thanks and well done!

Looks like a great extension, but I’m still struggling to pass the values from an individual post into an embedded template that contains all the <head> content.

I’m just getting the default values even when they are set differently for that post. Could you provide a brief example of what the embed tag needs to look like, and anything that needs to be picked up at the other end by the lg_better_meta tag?

Many thanks

Same problem here, no values from individual post. Any help ?

Looks like a great extension, but I’m still struggling to pass the values from an individual post into an embedded template that contains all the <head> content. I’m just getting the default values even when they are set differently for that post. Could you provide a brief example of what the embed tag needs to look like, and anything that needs to be picked up at the other end by the lg_better_meta tag? Many thanks

Hey guys,

Your embedded head template should look like this:

<head>
  ...
  {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}"
  }
  ...
</head>

and the template calling the head template should look something like:

{embed="_includes/.head" entry_id="3"}

or

{embed="_includes/.head" url_title="{segment_2}"}

In the first example I am setting the entry_id and in the second the url_title. One or the other is required.

In the head template you can see there are a lot of extra {embed: tags. These will be ignored if a value is not set.

you could pass any other variables through as parameters as well:

{embed="_includes/.head" entry_id="3" title="This is a hardcoded title"}

Hope that clears things up a little