Closed (fixed)
Project:
Nodewords: D6 Meta Tags
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
26 Apr 2009 at 16:40 UTC
Updated:
20 Dec 2011 at 23:03 UTC
When edit meta tags is enabled the user also sees edit meta tags on the account pages where they edit their username, password etc.. With normal content then admin can turn off editing of meta tags in the content type but there seems no way to turn it off for user account pages. Meta tags on these pages does not make a lot of sense anyway since only the user sees those pages not searches engines. I think meta tags should be restricted just to nodes (and views).
Comments
Comment #1
briansea commentedWhile this isn't the most elegant way, creating a module with this in it will fix your problem:
Hope this helps.
Comment #2
avpadernoSearch engines can see also the user profiles pages, if the anonymous user has the access user profiles permission.
This is more a feature request. I will value it.
Comment #3
avpadernoThe code has been changed for version 6.x-1.x-dev, and committed in CVS.
Comment #4
avpadernoThe meta tags fieldset is still visible in the user profile pages to the users with administer users permission; those users can still set the user meta tags, but their value will not be used when the user meta tags are not enabled.
Comment #6
vmenelas commentedThis is not working for me.
I added the above code in my css, any ideas?
Comment #7
avpadernoThere is nothing reported here that should be added to a CSS file; what you see is PHP code.
Comment #8
vmenelas commentedOh I see, where do I add this php code?
Comment #9
avpadernoAs the code has been already added in the development snapshot, there is no code to add (click on "View all the releases" to see the link to version 6.x-1.x-dev).
Comment #10
avpadernoI am adding a tag to track the differences between version 6.x-1.0 and version 6.x-1.1-beta1.
Comment #11
kthullI made a custom module as recommended in #1 and it did the job. Thanks and +1!
Comment #12
danyaeldemonic commentedHow do you create a module with that code?
Comment #13
kthullNot as scary as it seems. In my case, I named my module profile_meta, so I created a folder named profile_meta in my sites/all/modules/custom folder (doesn't need to be inside a folder named custom, but that lets anyone maintaining the site know it's not a contrib module).
Next, create a file named profile_meta.info and in it:
Then, create a file named profile_meta.module and in it:
Last step, turn on the module and you are all done. Naturally, if you want to name your module something different, you can, just replace "profile_form" with whatever you wish, but in all cases.
Comment #14
tyler-durden commentedkthull,
Thanks for the simple explanation, works beautifully and saved me hours of work testing and updating the module which is working just fine other than this change I needed.