is this how the module is supposed to work? that you see 'missing' in robots fields for nodes that are set to default. it is a bit misleading.
i'm talking about the meta tags (node) report page.
is it possible to pull in the actual default setting to this report screen? or to simply state that the 'default' setting is in effect?
or perhaps the easiest solution is that i can just ignore that field and trust that 'missing' = 'default'.
---
also side question: i'm looking for a module that does for taxonomy terms what this module does for meta. meaning generating a list of nodes with associated taxonomy terms. does such a thing exist? if not, i might be interested to sponsor/contribute to get it developed.
---
btw, thanks for the module. i've only just installed it, but it seems quite helpful.
Comments
Comment #1
kristen polAgreed. I should change it to be smarter about the robots field. Thanks for the reminder!
As for taxonomy "reports", there are several modules were you can view nodes by term, e.g.
http://drupalmodules.com/module/taxonomy-browser
http://drupalmodules.com/module/taxonomy-vtn
but it sounds like you want it the other way around where there is a list of nodes, and then the terms associated with the nodes. If so, then you can easily do that with views. Create a "node" view and the fields would be:
Node: Nid
Node: Title
Taxonomy: All terms
Change the style to Table and add a page display with whatever URL you want to use. And voila...
I just created one and exported it below though not sure if it will show up properly or not:
$view = new view; $view->name = 'node_terms_report'; $view->description = ''; $view->tag = ''; $view->view_php = ''; $view->base_table = 'node'; $view->is_cacheable = FALSE; $view->api_version = 2; $view->disabled = FALSE; /* Edit this to true to make a default view disabled initially */ $handler = $view->new_display('default', 'Defaults', 'default'); $handler->override_option('fields', array( 'nid' => array( 'label' => 'Nid', 'alter' => array( 'alter_text' => 0, 'text' => '', 'make_link' => 0, 'path' => '', 'link_class' => '', 'alt' => '', 'prefix' => '', 'suffix' => '', 'help' => '', 'trim' => 0, 'max_length' => '', 'word_boundary' => 1, 'ellipsis' => 1, 'strip_tags' => 0, 'html' => 0, ), 'link_to_node' => 0, 'exclude' => 0, 'id' => 'nid', 'table' => 'node', 'field' => 'nid', 'relationship' => 'none', ), 'title' => array( 'label' => 'Title', 'alter' => array( 'alter_text' => 0, 'text' => '', 'make_link' => 0, 'path' => '', 'link_class' => '', 'alt' => '', 'prefix' => '', 'suffix' => '', 'help' => '', 'trim' => 0, 'max_length' => '', 'word_boundary' => 1, 'ellipsis' => 1, 'strip_tags' => 0, 'html' => 0, ), 'link_to_node' => 1, 'exclude' => 0, 'id' => 'title', 'table' => 'node', 'field' => 'title', 'relationship' => 'none', ), 'tid' => array( 'label' => 'All terms', 'alter' => array( 'alter_text' => 0, 'text' => '', 'make_link' => 0, 'path' => '', 'link_class' => '', 'alt' => '', 'prefix' => '', 'suffix' => '', 'help' => '', 'trim' => 0, 'max_length' => '', 'word_boundary' => 1, 'ellipsis' => 1, 'strip_tags' => 0, 'html' => 0, ), 'type' => 'separator', 'separator' => ', ', 'empty' => '', 'link_to_taxonomy' => 1, 'limit' => 0, 'vids' => array( '1' => 0, ), 'exclude' => 0, 'id' => 'tid', 'table' => 'term_node', 'field' => 'tid', 'relationship' => 'none', 'override' => array( 'button' => 'Override', ), ), 'edit_node' => array( 'label' => 'Edit link', 'alter' => array( 'alter_text' => 0, 'text' => '', 'make_link' => 0, 'path' => '', 'link_class' => '', 'alt' => '', 'prefix' => '', 'suffix' => '', 'help' => '', 'trim' => 0, 'max_length' => '', 'word_boundary' => 1, 'ellipsis' => 1, 'strip_tags' => 0, 'html' => 0, ), 'text' => '', 'exclude' => 0, 'id' => 'edit_node', 'table' => 'node', 'field' => 'edit_node', 'relationship' => 'none', ), )); $handler->override_option('sorts', array( 'nid' => array( 'order' => 'DESC', 'id' => 'nid', 'table' => 'node', 'field' => 'nid', 'relationship' => 'none', ), )); $handler->override_option('access', array( 'type' => 'none', )); $handler->override_option('cache', array( 'type' => 'none', )); $handler->override_option('items_per_page', 50); $handler->override_option('use_pager', '1'); $handler->override_option('style_plugin', 'table'); $handler->override_option('style_options', array( 'grouping' => '', 'override' => 1, 'sticky' => 0, 'order' => 'asc', 'columns' => array( 'nid' => 'nid', 'title' => 'title', 'tid' => 'tid', 'edit_node' => 'edit_node', ), 'info' => array( 'nid' => array( 'sortable' => 1, 'separator' => '', ), 'title' => array( 'sortable' => 1, 'separator' => '', ), 'tid' => array( 'separator' => '', ), 'edit_node' => array( 'separator' => '', ), ), 'default' => 'nid', )); $handler = $view->new_display('page', 'Page', 'page_1'); $handler->override_option('path', 'node-terms-report'); $handler->override_option('menu', array( 'type' => 'none', 'title' => '', 'description' => '', 'weight' => 0, 'name' => 'navigation', )); $handler->override_option('tab_options', array( 'type' => 'none', 'title' => '', 'description' => '', 'weight' => 0, ));Comment #2
kristen polIt looks like that exported okay... so import this into views, save it, and then go to:
[your-site]/node-terms-report
Good luck,
Kristen
Comment #3
john.kenney commentedwow, what service! thanks so much for your effort.
yes, the views approach was what i had in mind: create a list of nodes and show terms for each node.
i went ahead and tried using your code and a few tweaks later it's working perfectly. just what i was looking for. nice!
thanks.
Comment #4
kristen polGlad it was what you were looking for.
I'll keep this open so I remember to deal with the robots txt behavior.
Kristen
Comment #5
kristen polComment #6
kristen polI have updated the code to handle the robots default option as well as showing the robots choices better. Once the drupal cron has created a new dev version, please download that and test.
Thanks!
Kristen
Comment #7
john.kenney commentedok, i will give it a try.
thank you.
Comment #8
john.kenney commentedsorry for the delay in testing this out. thanks for keeping an eye on the issue.
unfortunately, not a good result. the page admin/reports/seo/nodewords, the meta tags (node) report page, doesn't work in this .dev version.
it worked before and i just went back to beta6 again to confirm it was / is working. but in .dev, the table has no entries and there is a msg saying "Unable to determine column name for page_title table"
it may be because i am still way back on v6.x-1.0 of nodewords? i simply haven't been able to get any version since then to work on my system. i'm waiting for my technical consultant to look into that. but again, beta6 worked ok with the older nodewords.
if i look at the SEO Info tab on a specific node or two (which i don't generally do), it has the data in the right fields - except it says "page_title is not installed". which it isn't and hasn't been. so it says this same thing in either version.
is that clear?
Comment #9
kristen polThanks for testing. I believe I have fixed this issue. I've tested with page_title turned off and can see the report with the fix without any error.
Please test when you get a chance (once the cron rolls a new dev version).
Thanks!
Kristen
Comment #10
john.kenney commentedhi kisten:
i downloaded and installed the new .dev version with today's date (06 May).
it now displays the meta tags (node) table, so that earlier error is gone. but the robots field still shows 'MISSING' for all pages where it is not set to something other than default. i assume you're seeing something else.
i tried clearing cache, running cron, and updating db to see if that might help, but no effect.
anything else i should try?
on an unrelated point, i tweaked the CSS for the table, so it's easier to read. a little padding on the td's helps a lot. :)
the '!important' part is necessary in my theme because of other things that would override it, but may or may not be advisable generally.
as well, if you get inspired, it would be nice to get a class added to the 'SEO Info' tab tables. presently there is nothing there to style against. same class as above is probably fine there, too.
john
Comment #11
kristen polThanks for testing.
I guess the discrepancy must be because you are using an older nodewords. I'll need to try it with the old version. Will try to do that next week.
Kristen
Comment #12
john.kenney commentedok, don't worry about it too much if it is just me. i'll get around to upgrading nodewords at some point.
thanks for your efforts.
Comment #13
kristen polI'm pretty sure I got it working. Tested with older nodewords and newer nodewords.
Please test dev once it gets created by the cron.
Btw, I also updated the CSS per your comment (added this issue: http://drupal.org/node/797240).
Thanks!
Kristen
Comment #14
john.kenney commentedgreat. i will test asap.
glad the CSS suggestions were helpful. :)
thank you, kristen.
Comment #15
john.kenney commentedworks!! yay.
all pages now show node-specific info. 'DEFAULT (index,follow)" where it should say that and page specific settings where those apply.
looks great. well cone.
thank you very much!
Comment #16
kristen polAwesome. Thanks for reporting & testing.
I think I'll roll a new version today as there are a lot of fixes in dev.
Cheers,
Kristen
Comment #17
kristen polunassigning old issues