LG Better Meta 1.7.x - Now with sitemap meta and generator! - Official Support Thread

Hey Leevi - Great extension - enjoying using it very much. Just looking for confirmation of some testing - the extension will parse global template variables as content for items such as keywords (I store these as a global template variable), but does not (as far as I can see) parse path.php variables. [I’m able to enter {keywords} in the Site keywords box, and it is parsed - a global template variable - but {site-tite} - which is a path.php variable, is not parsed.] Is that right? Not a biggie, just want to check. Thanks again.

Hey Les,

The extension settings template should not parse any path or global variables. I just realised there is no official list in the docs for the variables that can be used in the template. A list does appear in the extension settings so I’ll add that here for now:

“The following variables will be replaced with their meta values generated from either the entry information or tag parameters: {robots}, {title}, {description}, {keywords}, {author}, {publisher}, {date_created}, {date_modified}, {date_valid}, {rights} and {identifier}.”

A second question, Leevi (I reckon with the time difference you’ll be able to pick them both off together 😊 ) Although from the 1.5 release you say the extension is ‘MSM compatible’, am I right in saying that this refers only to the ability to have different settings for each MSM site, and does not mean that there is a ‘site=”somesite” parament for the plugin tag? In other words, if Site A is displaying an article from Site B, I cannot do something like:

{exp:lg_better_meta_pi:template site="site_b" weblog="some_weblog" entry_id="{segment_3}"}

Am I right?

Yes you’re right but it’s a very good point. The extension will add the site defaults for the site the visitor is using but you should be able to choose.

I’ll add this feature in the next release. Thanks for the feature request.

I have quotes in some of my titles, and LG Better Meta seems to be doing this:

<title>“Title” -  My Site</title>

That’s supposed to read like a quoted word:

<title>"Title" -  My Site</title>

I seem to recall there was a fix for that in a previous version - correct? Using 1.7.0, and EE 1.6.6. Thanks!

Are you trying to add standard quotes or curly quotes to your page title?

Thanks, Leevi - I look forward to the addition of the ‘site’ parameter - I’m using an ugly sql query at present :(

Just to say LG Better Meta rocks - thanks, Leevi!

As an EE newbie I was setting about creating all sorts of custom fields to do the kinds of things that your extension takes in its stride and does more elegantly. Worth every bit of the $40.

Sorry if this has been covered, but I can’t find the answer anywhere… Sorry if it’s a silly question.

I can see how Better Meta is great for single entry pages. Does it have any functionality for templates displaying multiple entries from the same weblog (e.g. a latest news listing page showing summaries of latest 10 entries)? Obviously in this case there’s no one entry to grab meta data from. In this example, the meta description would most appropriately be something generic like “Latest news stories from the XYZ Corp.” rather than anything pulled from a single News entry.

Currently, my solution is always to have a weblog called ‘Index Page Meta’, which contains the meta info for each of my top-level sections, which I then ‘hardcode’ the entry id’s for these into the templates for any ‘multiple entry’ templates. It makes the meta descriptions client-editable. Does LG Better Meta cover this (sort of) hack?

Thanks 😊

lithiumdave– that’s exactly how I handle metas on my landing pages using LG Better Meta. I have a “landing pages” weblog that I’ve enabled LG Better Meta on. Then I hardcode LG Better Meta on those pages with the entry_id.

Hey slapshotw - so do you mean you enable LG Better Meta on the landing page weblog, but don’t have any other custom fields in the publish page?

In my case, I actually do because my landing pages have other content on them that I like to easily control–but essentially it’s the same premise.

Ah yes of course - even a simple listing of recent entries will usually have an introductory paragraph or so. Great suggestion, and certainly cemented my decision to use LG Better Meta. Thanks slapshotw 😊

I bought LG Better Meta 1.7 but have a bit of a problem. I’ve enabled the extension for just one weblog for now - going into Edit and clicking any entry in that weblog results in a completely blank screen. I’ve narrowed it down to the LG TinyMCE extension (v.1.3.2) I think. Or at least, disabling that extension solves the problem, re-enabling it brings the problem back. I’ve tried disabling other extensions but it’s definitely LG TinyMCE that appears to be the culprit.

Has anyone else had a similar problem? If I can’t run this extension alongside LG TinyMCE it’s no good to me :(

Thanks.

Ok… I have tried everything and can’t figure this out… How do you get a custom field to display in the sitemap? I have a weblog that contains pdf files. I want them to be included in the sitemap. I have tried all kinds of different combinations, including the ones below. Neither work, I just get a blank where {file} should be.

{exp:lg_better_meta_pi:entries
        weblog="downloads"
        disable="categories|category_fields|customer_fields|member_data|pagination|trackbacks"
        dynamic="off"
        rdf="off"
        status="open"
    }
    <url>
        <loc>http://www.domain.com{exp:weblog:entries weblog="downloads" entry_id="{entry_id}"}{file}{/exp:weblog:entries}</loc>
        <lastmod>{edit_date format="%Y-%m-%d"}</lastmod>
        <changefreq>{change_frequency}</changefreq>
        {priority}</priority>
    </url>
    {/exp:lg_better_meta_pi:entries}

{exp:lg_better_meta_pi:entries
        weblog="downloads"
        disable="categories|category_fields|customer_fields|member_data|pagination|trackbacks"
        dynamic="off"
        rdf="off"
        status="open"
    }
    <url>
        <loc>http://www.domain.com{file}</loc>
        <lastmod>{edit_date format="%Y-%m-%d"}</lastmod>
        <changefreq>{change_frequency}</changefreq>
        {priority}</priority>
    </url>
    {/exp:lg_better_meta_pi:entries}

You should check out the syntax error first on the disable– it says “customer_fields,” which I don’t think is an option.

Actually, I see that’s actually on Leevi’s docs– I’m going to email him about it. Seems like a typo (unless I’m confused about how LG Better Meta works).

I’m a bit confused. I’m needing to create a sitemap index file that points to several other sitemap files. From what I can tell, these files, including the index, all need to be named xxx.xml. Is this correct, do we need to have the .xml extension? If so, how do we do this within EE? I’ve already created all of my files individually, but of course get a 404 when trying to access them in the document root, which is why I’m trying to run them now as EE templates.

FYI - I used LG Better Meta to create templates to produce the XML output, then saved that output as individual XML files and uploaded to the root.