Hi guys,

Just upgraded to LG Better Meta version 1.8.0 from 1.4 to get MSM support. Installed and configured fine and the default Site Title and Metas are displaying on the site no problem. However, when I go to add Meta data for an entry on the Publish screen, I get the following MySQL error;

Anyone else having this problem?

It looks like it’s just an INT column, so if this is the case does anyone know if it’ll be OK just to go and manually add an append_default_keywords column to the database?

Running EE version v 1.6.3.

Thanks.

Hmmm looks like something may have been out of kilter with your upgrade. Run the following SQL and you should have no issues:

ALTER TABLE exp_lg_better_meta
ADD `canonical_url` VARCHAR( 255 ) NOT NULL,
ADD `region` VARCHAR( 255 ) NOT NULL ,
ADD `placename` VARCHAR( 255 ) NOT NULL ,
ADD `latitude` VARCHAR( 25 ) NOT NULL ,
ADD `longitude` VARCHAR( 25 ) NOT NULL ,
ADD `append_default_keywords` TINYINT( 1 ) NOT NULL

Hi Leevi and thanks for your reply.

I’ve run the code and the table has been updated and the error now no longer shows. However I’ve encountered what appears to be another couple of bugs:

1) When I enter some data for the Meta Title, Description etc. and click on Update to save the entry, it updates successfully. However, if I do the same and click Quick Save, the data isn’t saved and the fields come out blank.

2) When I successfully save the Meta data using Update, it doesn’t show on the website. All I get is the Better Meta defaults that I set on the extension Settings page (page title,  description etc.). I’m using:

in my template.

Any ideas this time..?

Thanks!

I’m also using 1.8 and also only see the default meta information. I posted in another thread about it.

However, I think the code you’re using may need the entry_id= or url_title= parameter per the instructions on Leevi’s site:

“7.2. Add entry specific meta data

Lucky for us it is a requirement of the ExpressionEngine templating system that either an entry_id or the url_title in the url for specific entry pages. Knowing this allows us to use segment variables inside the {exp:lg_better_meta_pl:template} tag.”

In my case, Leevi recommended that I use the code:

with the segment number changing depending on your URL structure (EE documentation about segements.)  Regardless I still only see the default meta information like you so I’m not sure what’s going on with mine yet. I attached some screen shots, etc. on the post referenced above asking for help. Anyway, if the “entry_id=” or “url_title=” parameter works please for you let me know. Otherwise, I’ll know it’s not something I’ve done wrong.

Good luck,

Jerry

Thanks for the reply. In terms of problem 2) above, yes, looks like I hadn’t read the instructions properly and adding the entry_id parameter works.

However problem 1) still occurs:

When I enter some data for the Meta Title, Description etc. and click on Update to save the entry, it updates successfully. However, if I do the same and click Quick Save, the data isn’t saved and the fields come out blank.

ska_mna - 22 June 2009 01:35 PM

Thanks for the reply. In terms of problem 2) above, yes, looks like I hadn’t read the instructions properly and adding the entry_id parameter works.

However problem 1) still occurs:

When I enter some data for the Meta Title, Description etc. and click on Update to save the entry, it updates successfully. However, if I do the same and click Quick Save, the data isn’t saved and the fields come out blank.

What other extensions / tabs do you have installed? A lot of 3rd party addons do not support quicksave and throw various errors.

Hello

I am getting the same problem it seems.

FOr some reason on the site i was working on I had updated all the folders for the LG meta meta, such as the lg_better_meta folder in the extensions. I noticed I hadnt upload it and put it up there.

Now I get errors; I noticed that the extension setting’s look changed too.

I get this error now when I try to Upate a entry:

Also when I view the actual page in the site I see this error at top of page:

I am not sure how to fix it?

Hi Kevin,

Run the following sql:

Then save your extension settings again. This should fix your issues.

Do I run this with PHPmyAdmin? i see a delimitor option there

I see this at bottom of SQL window in phpmyadmin

Delimiter ]  Show this query here again

is that right setting?

Hmm I’m not sure what that message means!

Has the exp_lg_better_meta table been updated? Can you save the extension settings?

Hey leevi

im just trying trying to make sure I run the SQL right; I do this in phpmyadmin?

Thanks!

Hey Leevi, I ran the sql and it got rid of the error in the edit window when you update but still getting the error on the actual page. I will pm you the link.

at top of page it says

One more thing, after I ran the SQL, it seems to have taken the page URI away from the Pages module…none of the 1000 pages we added are there.

Why would that SQL do that? The entries are still there but the link went away in the Pages tab back to the default link.

Anyway to get them back?
Thanks!

More on this, I noticed in Plugins folder I have to plugin files there for the LG better meta: pi.lg_better_meta_pi.php and pi.lg_better_meta_pl.php

I think pi.lg_better_meta_pl.php is for 1.8 and the other one is 1.7. So i think this is why Im getting that sitemap_defaults problem?

How do I fix that problem?

thanks!

It seems I didnt follow the upgrade instructions at .(JavaScript must be enabled to view this email address) when uploading the 1.8 files.

SO that’s why I am getting the error for sitemap_defailts at top?

Ok I changed the references in my template to exp:lg_better_meta_pl:template and the error at top of page went away. So I think my issue is fixed other than the problem of the Pages disappearing. Lesson learned! read the update instructions!

One other small issue it seems.

I tried Disabling all the extensions to try to see if there was a conflict with one of the extensions, to try to get the Page URIs back (that didn’t work); now I see in Better Meta preferences setting this error at the top of the pages:

UPDATE: nevermind it seems to have went away after I resubmitted the prefs.