Closed (fixed)
Project:
Nodewords: D6 Meta Tags
Version:
6.x-2.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
19 Apr 2010 at 01:08 UTC
Updated:
26 Jun 2011 at 15:09 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
sonlinemedia commentedsame issue here... no form to add information on.
Comment #2
sslam commentedI have a same problem.
Custom Pages meta tags does not works.
I try to add tags for views:image_gallery by adding tag description on the Custom pages meta tags but tag didn't add to page. Only default tags are displayed. Sorry for my English.
In Russian: Я пытаюсь добавить Описание для страницы Галереи, но вместо нужных мне тегов видны теги по умолчанию.
Comment #3
Anonymous (not verified) commentedComment #4
shaneonabike commentedYeah I am having the same issue actually. I can create custom pages but no data is being setup for the meta attributes that are being set.
Any ideas or solution would be great!
Thanks
Comment #5
Anonymous (not verified) commentedMay anybody report if the issue is still present in the latest developed code? I cannot reproduce this issue.
Comment #6
bennos commentedok. will try the latest dev.
Comment #7
Strykerraven commentedI had same issue as well, Turned out I had both versions stacked on each other and it appears they were fighting for control. I simply disabled the modules, deleted the nodewords folder, and re-uploaded. Hope this helps!
Comment #8
danny englanderI am having the same issue. (newest dev from 2010-May-17)
I tried the above mentioned deactivating module, deleting folder and reinstalling but still no joy.
Comment #9
danny englanderI am fairly sure I just got to the crux of this issue, the nodewords_custom table is not being created with a new install in MYSQL or updated properly if you are coming from an older version of this module.
Update: I have now completely uninstalled and made sure there were no references whatsoever of nodewords left in Drupal, and then tried a clean install of the module and sure enough the _custom table does not get created.
Comment #10
danny englanderI tried the newest dev version from May 27 and there were two syntax errors:
http://drupal.org/node/810880
http://drupal.org/node/810078
but moreover as related to this issue, now when I go to "Custom pages meta tags" at /admin/content/nodewords/custom and click "add", nothing appears to happen, i do not get form fields or anything.
Comment #11
Anonymous (not verified) commented@highrockmedia: see what reported in #807554: Some admin links are not functioning.
Comment #12
danny englanderOk that fixed being able to add a custom tag but now I am back to the older issue of the custom tag not showing up on the page I have specified in custom path.
Comment #13
volocuga commentedI can confirm it does not work for me too. Latest dev :(
Comment #14
snorkers commentedUsing 31 May DEV and I cannot get custom pages to work at all - took a while to uninstall nodewords_custom_pages, then re-install it so that the MySQL table nodewords_custom created, but that didn't seem to fix things.
The entries in MySQL [in nodewords and nodewords_custom] all seem to look right, but the tags aren't being rendered in HEAD on the targeted page.
Mmmm....
Comment #15
danny englanderWondering if anyone has tried 6.x-1.x-dev / 2010-Jun-03 version yet to see if that has fixed this issue with custom tags.
BTW, I also noticed that this ticket is marked as "postponed (maintainer needs more info)", I am wondering what more info is needed, the last three posts show that three different people are having this same issue.
Comment #16
tomboone commented@highrockmedia: I'm running 6.x-1.x-dev / 2010-Jun-03 version and having the same problems. Previously set custom pages are there, but editing or deleting them doesn't take effect, and the stored description tag isn't displaying on the pages in question.
Comment #17
snorkers commentedRun latest DEV and custom pages have no effect at all. Defaults work fine on the whole
Comment #18
igorik commentedI can confirm that custom pages on latest dev version from June 7, 2010 doesn't work at all.
basic and default meta tags on nodes works well.
Comment #19
danny englanderI noticed there is another new dev from today (2010-Jun-11) . Wondering if the issue of custom tags / paths working has been addressed in this release?
Comment #20
terry22 commentedNo update on this issue? this function is very important for lot of people I guess.
Comment #21
pxlar8 commentedSo far as I can tell, I'm having a similar issue. I get the form for the custom page "Edit page meta tags" and the Name and Path fields update but any changes to the other fields like Abstract, Description, etc, are lost when I hit save, so it has no effect.
UDPATE: updating to 6.x-1.x-dev fixed the saving issue but it still has no effect on the page source output.
Comment #22
danny englanderJust tested the new dev version from 2010-Jun-16 amd still no joy, custom path meta tag does not show up on the given page. To add insult to injury deleting a custom tag does not delete it (which didn't work anyway so it's kind of a moot point)
Comment #23
Anonymous (not verified) commentedSame problem. No custom pages and cannot delete on June 16 DEV
Comment #24
Hardrocker commentedGuys the solution is very simple. Go to the general settings tab and in "META TAGS ENABLED ON ADMINISTRATIVE SETTINGS PAGES" select the check boxes you wish to be displayed to be shown in the edit form. Use the default value "when meta tag is empty" and save. Then go to the custom pages meta tab now and select the add tab from the top and your fields will be visible now. Good luck and cheers!
Hardrocker
Guyanese Businesses Online®
Comment #25
danny englander@Hardrocker Custom Pages are for a virtual path, in other words perhaps a view that does not have an actual node where you can edit the tags. That makes your statement above not applicable, sorry. In addition there are several other issues (if you have a read above) that have not been fixed or addressed.
Comment #26
Anonymous (not verified) commentedActually, what reported in comment #24 is applicable.
If you don't enable the meta tags for administrative pages, you are probably not going to see the meta tags in custom pages. refers to the meta tags that are shown in the administrative settings page like the custom pages settings page, the taxonomies settings pages; in other words, they are all the settings pages to which users can access if they have an administrative permission. The other settings pages the module is referring are the node edit pages, and the user profile pages.
Comment #27
danny englander@kiam regardless, as I said it's a moot point, I have those settings enabled and custom pages is still completely broken (and as reported by several others above).
Comment #28
Anonymous (not verified) commentedYep, #24 does not necessarily work for custom pages.
Comment #29
Anonymous (not verified) commentedIt is true the opposite; if you don't select any meta tags that must appear in the administrative settings pages (which include also the custom pages settings), you will not see any meta tag fields on that page.
Before #24, nobody reported that any meta tags were enabled to appear in the administrative settings pages, which leads me to think that nobody noticed those options.
Comment #30
danny englander@kiam - If you create a view (lets say a display of type page with a set url), can you create a new custom meta tag (description and keywords for example) to work for that view display / URL? Have you tested this?
Comment #31
Anonymous (not verified) commented@#30: Yes, I have tried it; it works, for me.
Comment #32
Brian294 commentedDanny, I think you're right. There is probably a relationship with #835158. I make an observation about the following file is missing from nodewords_custom_pages (In http://drupal.org/node/835158#comment-3142624):
nodewords_custom_pages\includes\nodewords_custom_pages.nodewords.hooks.inc
which is probably why the hook: nodewords_custom_pages_nodewords_type_id isn't firing. This results is a "0" PAGE TYPE (instead of 10) and a "0" ID (Instead of whatever argument was detected in the beta9 version).
Peace,
Brian
Comment #33
danny englander@Brian294 - Did you try the patch at http://drupal.org/node/835158#comment-3145076 -- did it work, just curious.
Comment #34
Brian294 commented@highrockmedia - I never considered trying that patch as I am not using 1.11 and the _nodewords_detect_type_and_ids function was depreciated in the 1.14 API (-dev version).
Comment #35
Anonymous (not verified) commentedI fixed a problem with an include file that for some reason was removed from CVS, but it was still present in the Mac I use to develop Nodewords.
Comment #36
danny englanderThis makes me feel better that I (and the multitudes of others subscribed to this issue after several weeks of reporting this feature has not worked) were not imagining there was a problem.
This is now working as expected I can add and delete custom pages tags and they show up in a custom page path such as a view. It also proves that #24 was not the solution to this issue as I have stated a few times. This is one gigantic sigh of relief and no more headaches trying to figure out why this was not working.
Comment #37
Anonymous (not verified) commented@highrockmedia: Clearly, #24 was not the solution to the problem; still, to point out that there are settings that were not present in the previous versions was in someway necessary, as some users could not have noticed them, and wondered why they were not able to see the meta tags as before.
I still have to understand how it has been possible that a file has been removed from CVS, without that the local copy of that file has been deleted or renamed.
I am glad the issue has been resolved, and finally I was able to understand what somebody was trying to communicate. :-)
Comment #38
Anonymous (not verified) commentedComment #39
Anonymous (not verified) commentedI have marked #835158: Metatags do not appear on custom pages as duplicate of this report.
Comment #40
igorik commentedI can confirm that with latest dev custom pages work nice.
Thank you!
Comment #41
zabej commenteddid "update to 6.x-1.x-dev 2010-Jul-02" version but custom page meta tags didn't appear.
Do you have any vision about this?
It is view of situation in attachment
Thanks
Comment #42
danny englanderWhat happens when you click "add"? Can you add a new custom tag and associate it with a path to a view? Looks like you have lots of security & module updates too, not saying that's the issue but you should take care of those.
Comment #43
Anonymous (not verified) commented@zabej: The error message is not related with Nodewords, but with your Drupal installation that has many modules that need to be updated.
Comment #44
gbernier commentedHey All,
I've created a patch against 6.x.1.11 which fixed the issues we were having regarding custom page meta data not showing up. I don't trust the dev version to put it onto our production site so decided to patch this one. Main issues were strings were passed as arguments when functions were expecting integer id's
I've also responded to the issue http://drupal.org/node/844270#comment-3166920 with the same page
Comment #45
Anonymous (not verified) commentedComment #47
ari-meetai commented#24 saved my day. Thanks.
Comment #48
divesh.kumar commentedHi,
I am not able to see this in the settings anywhere. Can you please provide some screenshot or help on this.
Comment #49
danny englanderdivu18in -- see my screen shot attached (the path is: /admin/content/nodewords/custom)
-- also check your modules to see if you have "Meta tags for custom pages" enabled.
Comment #50
danny englanderComment #51
ergophobe commentedSolution in #24 works, though I am using the nodewords_pagetitle module which adds the Page Title meta tag. If you use *only* that tag, you don't get a Custom Pages form. If you check at least one other, you do.
Comment #52
ccshannon commentedDoes not work for me and I'm using newest nodewords-6.x-1.x-dev, dated Oct. 6, 2010
I use an editions paradigm for my homepage. Homepage is a node type with a date field in it, that a View uses to produce the homepage. So, when you look at the Homepage of the site, you are looking at a one-node View.
The View path is 'homepage_current', which is set as the default front page in Site Information. So, when you view the homepage, you are viewing the same node that is available at homepage_current. This allows editors to have multiple versions of their homepage in development, so they can arrange their stories around and have it set to be active at a specific time.
I followed all the steps above, set the admin settings for description and keywords in case meta are empty. I created a 'custom pages meta tags' for my homepage. I put both <front> and homepage_current as paths to use the custom description and keywords.
View source on homepage ... no meta tags. Go to /homepage_current. Still no tags.
So, I go to the Homepage node itself, just to see if the values stored with the node will show up instead ... it has meta tag form for description and keywords. It has the default tokens. I wipe those out and put in my custom description. Save node. Go back into edit form. Tokens are still there!!!???
So, the custom pages meta tags don't work (for Views at least), and I couldn't override the default meta tags in my nodes, even if I wanted to. It always uses the Defaults. Why expose the meta tags form in nodes if I can't change the values in it for that node?
Automated default token tags do work, though, even if I can't override them ... and after reading some of the issues for this module, I guess I should be thankful.
Comment #53
kentr commentedsubscribe
Comment #54
ergophobe commentedIf you want to affect the title of a page display of a View, you need the nodewords_pagetitle module
http://drupal.org/project/nodewords_pagetitle
Comment #55
bmodesign commentedI was facing the same issue. I couldn't get my custom meta tags to show up on a page dynamically generated by Views.
I had FCKeditor installed on the site that was giving me trouble, so I had a rich text editor showing up for PATH and the DESCRIPTION text boxes.
It made me think that it was automatically adding a tag to all of my meta description and the paths I wanted the custom meta data to show up on.
So I told the FCKeditor not to show up for those fields, or for that admin page (there should be a link under your rich text editor telling you how to do that).
I went back into my 'Other Pages' custom meta data that I setup earlier that wasn't working....
And then edited the paths and the description text to NOT have any HTML embedded in them. I deleted any < p > and < / p > html code.
I hit save, went to look at my pages source code and it WORKED!
Let us know if anyone else has the same scenario.
Comment #56
ccshannon commentedThanks @ergophobe for the tip. Obviously, that name 'nodewords_pagetitle' is a bit misleading. I'll check it out.
I worry though, from the module page for nodewords_pagetitle:
=================
Steps to install:
1. Enable nodewords / nodewords_custom_pages (1.12-beta9 required. Follow their upgrade instructions or you might be sorry!)
=================
1.12-beta9 was pulled off nodewords module page. That version went back to the drawing board. I'll see if it will work with 1.1.x-dev.
Thanks, again!
Comment #57
Brian294 commentedI'm the module developer for nodewords_pagetitle. It *should* work with the latest dev version. I confirmed that my latest dev was working with their latest dev back in May 2010. Back in May, beta9 was the preferred 1.12 release, so that's why my instructions call for it. The steps of getting upgraded to 1.12-beta9 were kind of hairy at the time, so that's why I cautioned people to follow to the instructions (or they might be sorry!)
My module is incompatible with 1.11 because custom pages radically changed in 1.12.
As always, do your nodewords 1.1x-dev testing on a non-production site! Please let me know the results.
Peace,
Brian
Comment #58
ccshannon commentedThanks, Brian. Will do.
Comment #59
ergophobe commentedI ran into the beta problem and just installed the dev version of nodewords and it's all good. If you're in this thread, you're all set I think. The issue with nodewords 6.x-1.11 is that it doesn't even have a custom pages module.
You can download beta 9 here
http://drupal.org/node/774564
but I'm dong fine with the dev version.
My only stumbling block was that since I install using drush, I didn't see that beta 9 was the min requirement and got confused by the dependencies. Works great now though.
Comment #60
damienmckennaBumping the priority of this and adding to the v6.x-1.12 blockers list.
Comment #61
nirvanajyothi commentedHi,
Am sorry, I could not get the Oct 6, 6.x-1.x-dev to solve the custom pages issue. The metatags I added to custom pages before updating to 6.x-1.x-dev from 6.x-1.1 version is still working when i check out html-page source. But I cant edit those or add a new page.
The edit link takes me to a page with no editing fields. Wonder why this is still happening.
-Thank you
Comment #62
damienmckenna@nirvanajyothi: please check the nodewords General Settings page and ensure you have items selected in the "Meta Tags Enabled On Administrative Settings Pages" block.
Comment #63
damienmckennaI tested the latest v6.x-1.x-dev release on a fresh new site and it was all working correctly for me. If you are not seeing any fields show up when you go to edit a custom path definition please ensure that you have fields selected in the "Meta Tags Enabled On Administrative Settings Pages" block on the General Settings page.
Comment #64
nirvanajyothi commented@DamienMcKenna
makes it work again for me.
I must have unticked the options accidentally while configuring, i guess.
Could not figure it out for long. Thanks very much. You made my day. :)
Comment #66
damienmckennaThis may need some work, or at least some review, given we've reverted everything back to the last changes on December 31st, 2009.
Comment #67
damienmckennaRemoving this from the 6.x-1.12-blocker list as it is no longer relevant to 6.x-1.x.