Further to this thread, here’s a feature request to make LG Better Meta MSM-aware…
Hey Leevi,
MySQL ERROR:
Error Number: 1171
Description: All parts of a PRIMARY KEY must be NOT NULL; If you need NULL in a key, use UNIQUE instead
exp_lg_better_meta
( id
INT( 8 ) NOT NULL AUTO_INCREMENT , site_id
INT( 8 ) NOT NULL DEFAULT ‘1’, entry_id
INT( 8 ) NULL , weblog_id
INT( 8 ) NULL , url_title
VARCHAR( 255 ) NULL , title
VARCHAR( 255 ) NULL , keywords
VARCHAR( 255 ) NULL , description
VARCHAR( 255 ) NULL , publisher
VARCHAR( 255 ) NULL , rights
VARCHAR( 255 ) NULL , author
VARCHAR( 255 ) NULL , index
TINYINT( 1 ) NULL , follow
TINYINT( 1 ) NULL , archive
TINYINT( 1 ) NULL , PRIMARY KEY ( entry_id
) , UNIQUE (id
) )The other extensions I have enabled are:
LG Add Sitename
LG TinyMCE Custom Field
Fresh Variables
REEOrder
The other plugins I’ve got are:
Magpie RSS Parser (v.1.3.4)
Find and Replace (v.1.3)
Word Limiter (v.1.0)
Widon’t (v.1.0)
List Maker (v.1.0)
LG Better Meta (v.1.4.2)
XML Encode (v.1.2)
Nice date (v.1.0)
TruncHTML (v.1.2.1)
EE Typography (v.1.1)
Character Limiter (v.1.0)
Pages – Crumbs (v.1.1.3)
Pages – Nested Menu (v.1.1.8)
Randomizer (v.1.0)
Extract URL Plus (v.2.0.1)
Form_Helper (v.1.9)
Any help?
Further to this thread, here’s a feature request to make LG Better Meta MSM-aware…
Its my goal to make all of my extensions MSM aware in the near future… Now I just have to find the time 😊
Hey Leevi, I’ve got the latest version and am running 1.6.1. After I upload the files and click ‘Enable’ in the extensions manager I get this error screen: — MySQL ERROR: Error Number: 1171 Description: All parts of a PRIMARY KEY must be NOT NULL; If you need NULL in a key, use UNIQUE instead Query: CREATE TABLE IF NOT EXISTS `exp_lg_better_meta` ( `id` INT( 8 ) NOT NULL AUTO_INCREMENT , `site_id` INT( 8 ) NOT NULL DEFAULT ‘1’, `entry_id` INT( 8 ) NULL , `weblog_id` INT( 8 ) NULL , `url_title` VARCHAR( 255 ) NULL , `title` VARCHAR( 255 ) NULL , `keywords` VARCHAR( 255 ) NULL , `description` VARCHAR( 255 ) NULL , `publisher` VARCHAR( 255 ) NULL , `rights` VARCHAR( 255 ) NULL , `author` VARCHAR( 255 ) NULL , `index` TINYINT( 1 ) NULL , `follow` TINYINT( 1 ) NULL , `archive` TINYINT( 1 ) NULL , PRIMARY KEY ( `entry_id` ) , UNIQUE (`id`) ) — The other extensions I have enabled are: LG Add Sitename LG TinyMCE Custom Field Fresh Variables REEOrder The other plugins I’ve got are: Magpie RSS Parser (v.1.3.4) Find and Replace (v.1.3) Word Limiter (v.1.0) Widon’t (v.1.0) List Maker (v.1.0) LG Better Meta (v.1.4.2) XML Encode (v.1.2) Nice date (v.1.0) TruncHTML (v.1.2.1) EE Typography (v.1.1) Character Limiter (v.1.0) Pages – Crumbs (v.1.1.3) Pages – Nested Menu (v.1.1.8) Randomizer (v.1.0) Extract URL Plus (v.2.0.1) Form_Helper (v.1.9) Any help?
Hey TCFleck,
Try replace the sql on line 255 of the ext file with:
$sql[] ="CREATE TABLE IF NOT EXISTS `exp_lg_better_meta` (
`id` INT( 8 ) NOT NULL AUTO_INCREMENT ,
`site_id` INT( 8 ) NOT NULL DEFAULT '1',
`entry_id` INT( 8 ) NULL ,
`weblog_id` INT( 8 ) NULL ,
`url_title` VARCHAR( 255 ) NULL ,
`title` VARCHAR( 255 ) NULL ,
`keywords` VARCHAR( 255 ) NULL ,
`description` VARCHAR( 255 ) NULL ,
`publisher` VARCHAR( 255 ) NULL ,
`rights` VARCHAR( 255 ) NULL ,
`author` VARCHAR( 255 ) NULL ,
`index` TINYINT( 1 ) NULL ,
`follow` TINYINT( 1 ) NULL ,
`archive` TINYINT( 1 ) NULL ,
PRIMARY KEY ( `id` ) ,
UNIQUE (`entry_id`)
)";
And see how you go… Its just a hot fix for now. I’ll try and get a new release out sometime after the easter break
Hi Leevi,
Thanks for a very useful extension. There’s one minor bug that I came across today; selecting either of the “non-standard” separators (the right angled quote or the right arrow) results in the character code being displayed in the title bar.
An example may help to clarify what I mean. If the page title should read “Current Page » Site Name”, the extension displays:
Current Page » Site Name
A quick look at the source reveals that it’s encoding the ampersand. I’ve tested this in Safari 3 and Firefox 2 on Mac OS 10.5.2.
Cheers, Stephen
EDIT - Poop! Sorry for this post Leevi, just noticed that on your site it states that it has been tested with 1.6.1! Do you know when you think it might be working with the latest version at all?
Hi Leevi,
Just got around to trying out your 1.4.2 version alongside EE 1.6.3 but when I enable the extension and then go to publish a new entry or edit an existing one then the control panel goes completely blank and there is absolutely no source code available in the browser.
Does this yet work with 1.6.3 or am I doing something (knowing me) that is obviously wrong?
Thanks for any help on this.
Best wishes,
Mark
Mark, I just tested with my local 1.6.3 install, and I’m not getting an error. However, I didn’t do much more than fill in a few fields and re-save the entry.
There are no database changes in 1.6.2 and 1.6.3.
How much memory is allocated for PHP? Also try disabling the auto check for updates, or increase the time to check for updates.
Hi Sue,
Hmm not too sure what I have going on then. I have this currently installed on a localhost so not sure if that is doing it? I installed the extension and then when I go to Publish a new entry the admin panel goes completely blank with no source code or anything.
I did have this problem with some other extension before this which was making the pages go blank too but I could never narrow it down to which one and so had to turn off around 4 in the end.
I will try completely disabling extensions which will hopefully empty the database of any info for them and try again. Will let you know what happens.
Thanks for the info though.
Best wishes,
Mark
Quick update. Just disabled all extensions and had to manually flush out all the entries to the exp_extensions table as they didn’t go and then re-enabled extensions. LG Better Meta seems to be working now! I knew Leevi’s work wasn’t to blame!! 😊
I will try and find out now which extension is giving me all the grief and grind the pesky blighter into the ground! 😊
Thanks again Sue and thanks Leevi for a fantastic extension!
Best wishes,
Mark
Hi Leevi, Thanks for a very useful extension. There’s one minor bug that I came across today; selecting either of the “non-standard” separators (the right angled quote or the right arrow) results in the character code being displayed in the title bar. An example may help to clarify what I mean. If the page title should read “Current Page » Site Name”, the extension displays:A quick look at the source reveals that it’s encoding the ampersand. I’ve tested this in Safari 3 and Firefox 2 on Mac OS 10.5.2. Cheers, StephenCurrent Page » Site Name
I’m having the same problem, are there any workarounds?
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.