Integrated Metatags

By rogerwebb on 11 May 2008 at 10:40 UTC

I have a multi-topic site so need to control the metatags on the various sub-home pages so i downloaded Integrated metatags and Integrated Metatags - CCK.

However when i try to activate the Integrated Metatags - CCK module i get the following warning

Adds Integrated Metatag functionality to CCK types and fields.
Depends on: Int_meta,content (missing)

But i can't find Int_meta,content

Can anyone help?

Roger

Comments

"int_meta" is one of the

WorldFallz commented 11 May 2008 at 14:04

"int_meta" is one of the modules in the integrated metatags package, it seems you have that one installed. "content" is the content construction kit module that brings field capabilities to content types-- this module requires it. I'm not exactly sure why you would need this module if you dont have it already, but in any case, you need to download and install it in order for this module to enable properly.
===
"Give a man a fish and you feed him for a day.
Teach a man to fish and you feed him for a lifetime." -- Lao Tzu
"God helps those who help themselves." -- Benjamin Franklin
"Search is your best friend." -- Worldfallz

Int_meta

rogerwebb commented 12 May 2008 at 13:15

I reloaded CCk but it made no difference

Any further thoughts?

Roger

Does it still say "content

WorldFallz commented 13 May 2008 at 01:22

Does it still say "content (missing)"? If so, the problem is with CCK which must be enabled before the other module will be allowed to be enabled.

===
"Give a man a fish and you feed him for a day.
Teach a man to fish and you feed him for a lifetime." -- Lao Tzu
"God helps those who help themselves." -- Benjamin Franklin
"Search is your best friend." -- Worldfallz

metatags CCK

rogerwebb commented 13 May 2008 at 06:35

CCK has been loaded - and reloaded - and all its submodules are enabled

Roger

Yes, but does it still

WorldFallz commented 13 May 2008 at 13:01

Yes, but does it still say

Depends on: Int_meta,content (missing)

as mentioned in your original post? "content (missing)" = cck not available.

If you have content module enabled and still receive this message, this helps me diagnose where the problem is. Telling me you enabled & reenabled cck without answering my question doesnt help me figure out where the problem is.

Does the fieldgroup module (or any other modules that are part of the CCK distribution) also say content (missing)?

If the "content" module is enabled and the other CCK modules don't show "content(missiing)", then there's a bigger problem somewhere. Drupal handles detection of the dependencies for modules, not the modules themselves. All the module has to do is put "dependencies = content" in the .info file.

Re Integrated metatags

rogerwebb commented 13 May 2008 at 13:22

In the CCK modules:
content
content copy
fieldgroup
node reference
number
options widgets
text
user reference are all enabled successfully

Integrated Metatags says: Provides functionality for modules to dynamically add Metatags.
Depends on: AHAH Forms (enabled)

Integrated Metatags - CCK says: Adds Integrated Metatag functionality to CCK types and fields.
Depends on: Int_meta,content (missing)

Hope the problem isn't too great

Roger

nevermind, i installed it

WorldFallz commented 13 May 2008 at 13:16

nevermind, i installed it myself and took a look-- open the int_meta_cck.info and change "int_meta,content" to "int_meta, content" then visit the modules page.

You should also file a bug report on the issues queue for the module.

Int_meta

rogerwebb commented 13 May 2008 at 15:03

Great

Cleared one fault - brilliant - but up came another

Integrated Metatags - CCK Adds Integrated Metatag functionality to CCK types and fields.
`````````````````````````Depends on: Int_meta, (missing), Content (enabled)

int meta

rogerwebb commented 13 May 2008 at 15:06

You have to move the comma too

dependencies = int_meta content

Thanks for everything - i would never have found it myself

You're welcome--- sometimes

WorldFallz commented 13 May 2008 at 18:14

You're welcome--- sometimes it just requires another pair of eyes.

Sorry; but clearing one

rogerwebb commented 13 May 2008 at 15:11

Sorry; but clearing one fault reveals another

Int_meta now enables OK but the following warnings come up when you attach metatags to a node type

warning: array_keys() [function.array-keys]: The first argument should be an array in /homepages/36/d186685211/htdocs/drupal/modules/int_meta/int_meta_cck.module on line 42.
warning: Invalid argument supplied for foreach() in /homepages/36/d186685211/htdocs/drupal/modules/int_meta/int_meta_cck.module on line 42.
warning: array_keys() [function.array-keys]: The first argument should be an array in /homepages/36/d186685211/htdocs/drupal/modules/int_meta/int_meta_cck.module on line 42.
warning: Invalid argument supplied for foreach() in /homepages/36/d186685211/htdocs/drupal/modules/int_meta/int_meta_cck.module on line 42.

Yeah, I'm getting the same

WorldFallz commented 13 May 2008 at 18:13

Yeah, I'm getting the same thing and there's issue #234505: The first argument should be a array error with no response yet. I took at look at the offending line and managed to get rid of the error, but I have no idea if it otherwise breaks the module.

If you like, try it and see:

in int_meta_cck.module change line 42 to:

foreach (array_keys($info) as $col) {

And test it out. I use nodewords, so I'm not sure I can provide any more info--- hopefully the maintainer will see that bug report (you might want to post to it as well).

rogerwebb commented 14 May 2008 at 11:12

That worked. Thanks

Do you happen to know the settings that will allow me to copy a list I made in a field called 'keywords' (a CCK text field I made), so that it becomes the keyword metatag??

I will understand if you're thoroughly fed up with this!

Roger

AFAIK, your fields should

WorldFallz commented 15 May 2008 at 02:46

AFAIK, your fields should show up in the "Field" drop down on the "Metatags" tab for each content type when you edit the content type. You should be able to select it from the list and click add (for each field you want to be in the metadata) then save the content type.

and no worries... i'm not "fed up", lol.

A long and winding road

rogerwebb commented 16 May 2008 at 14:30

You would think so but i set up a CCK field called keyword to store keywords for my various bookpages instead of using the Manual Metatag entry.

When I try to set this up in Content types i am offered the following list

field.keyword allowed_values
field.keyword allowed-values.php
field.keyword db-storage
field.keyword field_name
field.keyword max_length
field.keyword multiple
field.keyword required
field.keyword text_processing
field.keyword_type
field.keyword-widget

When all i want to do is to put the values into the !<............> fileld in place of the maual site-wide values

Can i ask for your help again

By the way the system works. Using the manual values which only represent the site as a whole my hit rate has doubled since i set up the manual values a week ago

Roger

Ok, lets see if I can

WorldFallz commented 16 May 2008 at 14:34

Ok, lets see if I can replicate the problem on my dev box....

You would think so but i set up a CCK field called keyword to store keywords for my various bookpages instead of using the Manual Metatag entry.

So, you added a cck field named "keyword" to your book page content type? What type of field? tell me all the settings so i can duplicate it precisely, then we'll go from there.

Field metatags

rogerwebb commented 16 May 2008 at 14:58

Type textfield
Label keyword
Rows 1
Default Value retired and active, retired but active, online community, over 50, baby boomers
PHP Value blank
Display in group metatags
Help Text The keys on which an internet search might be mounted
data Settings
required
multiple both un enabled
max length 150
allowed values list blank
php code blank

hope this helps

Ok, i've narrowed it down to

WorldFallz commented 16 May 2008 at 16:06

Ok, i've narrowed it down to the d5 port of the d6 module and that line 42 we changed above.

The module works as expected for d6-- with line 42 unchanged. In d6, th choices in the dropdown list are things like field_keywords.value, field_tags.value, field_name.value, etc.-- which is what we want in the d5 version.

Simply removing 'columns' may fix the error message, but that's somehow related to making the cck fields available in the drop-down box. This is probably because cck has also changed between d5 and d6. And being that a simple error like the comma in the .info file was present, I suspect the maintainer hasn't tested the d5 port (it was written for d6 then backported).

We're beyond my skills here I think. I took at look at the code, but I'm afraid I've no clue how to fix it for d5.

Integrated Metatags - CCK

Comments

"int_meta" is one of the

Int_meta

Does it still say "content

metatags CCK

Yes, but does it still

Re Integrated metatags

nevermind, i installed it

Int_meta

int meta

You're welcome--- sometimes

Sorry; but clearing one

Yeah, I'm getting the same