hi
I tried the last Beta on a Dev Site.
I can not add Specfic Meta Tags and Meta for custom pages.

On the URL's is no form present.

admin/content/nodewords/custom/add
admin/content/nodewords/meta-tags/errorpage_404

No other errors or something in the watchdog.

Comments

sonlinemedia’s picture

same issue here... no form to add information on.

sslam’s picture

Version: 6.x-1.12-beta9 » 6.x-1.x-dev
Component: Code » Third-party modules integration
StatusFileSize
new24.89 KB
new35.48 KB

I 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: Я пытаюсь добавить Описание для страницы Галереи, но вместо нужных мне тегов видны теги по умолчанию.

Anonymous’s picture

Component: Third-party modules integration » Code
shaneonabike’s picture

Yeah 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

Anonymous’s picture

Status: Active » Postponed (maintainer needs more info)

May anybody report if the issue is still present in the latest developed code? I cannot reproduce this issue.

bennos’s picture

ok. will try the latest dev.

Strykerraven’s picture

I 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!

danny englander’s picture

I 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.

danny englander’s picture

I 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.

danny englander’s picture

I 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.

Anonymous’s picture

@highrockmedia: see what reported in #807554: Some admin links are not functioning.

danny englander’s picture

Ok 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.

volocuga’s picture

I can confirm it does not work for me too. Latest dev :(

snorkers’s picture

Using 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....

danny englander’s picture

Wondering 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.

tomboone’s picture

@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.

snorkers’s picture

Run latest DEV and custom pages have no effect at all. Defaults work fine on the whole

igorik’s picture

Status: Postponed (maintainer needs more info) » Active

I 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.

danny englander’s picture

I 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?

terry22’s picture

No update on this issue? this function is very important for lot of people I guess.

pxlar8’s picture

So 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.

danny englander’s picture

Just 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)

Anonymous’s picture

Same problem. No custom pages and cannot delete on June 16 DEV

Hardrocker’s picture

Guys 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®

danny englander’s picture

@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.

Anonymous’s picture

Actually, 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. Meta tags enabled in administrative settings 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.

danny englander’s picture

@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).

Anonymous’s picture

Yep, #24 does not necessarily work for custom pages.

Anonymous’s picture

Yep, #24 does not necessarily work for custom pages.

It 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.

danny englander’s picture

@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?

Anonymous’s picture

@#30: Yes, I have tried it; it works, for me.

Brian294’s picture

Danny, 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

danny englander’s picture

@Brian294 - Did you try the patch at http://drupal.org/node/835158#comment-3145076 -- did it work, just curious.

Brian294’s picture

@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).

Anonymous’s picture

I 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.

danny englander’s picture

Status: Active » Fixed

This 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.

Anonymous’s picture

@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. :-)

Anonymous’s picture

Title: Specific Meta tags and Custom Pages does not work » Custom pages meta tags do not work
Anonymous’s picture

I have marked #835158: Metatags do not appear on custom pages as duplicate of this report.

igorik’s picture

I can confirm that with latest dev custom pages work nice.
Thank you!

zabej’s picture

StatusFileSize
new27.93 KB

did "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

danny englander’s picture

What 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.

Anonymous’s picture

@zabej: The error message is not related with Nodewords, but with your Drupal installation that has many modules that need to be updated.

gbernier’s picture

Version: 6.x-1.x-dev » 6.x-1.11
StatusFileSize
new3.84 KB

Hey 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

Anonymous’s picture

Version: 6.x-1.11 » 6.x-1.x-dev

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

ari-meetai’s picture

#24 saved my day. Thanks.

divesh.kumar’s picture

Hi,

I am not able to see this in the settings anywhere. Can you please provide some screenshot or help on this.

danny englander’s picture

StatusFileSize
new131.31 KB

divu18in -- 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.

danny englander’s picture

Status: Closed (fixed) » Active
ergophobe’s picture

Solution 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.

ccshannon’s picture

Does 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.

kentr’s picture

subscribe

ergophobe’s picture

If 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

bmodesign’s picture

I 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.

ccshannon’s picture

Thanks @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!

Brian294’s picture

I'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

ccshannon’s picture

Thanks, Brian. Will do.

ergophobe’s picture

I 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.

damienmckenna’s picture

Priority: Normal » Critical
Issue tags: +v6.x-1.12 blocker

Bumping the priority of this and adding to the v6.x-1.12 blockers list.

nirvanajyothi’s picture

Hi,

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

damienmckenna’s picture

@nirvanajyothi: please check the nodewords General Settings page and ensure you have items selected in the "Meta Tags Enabled On Administrative Settings Pages" block.

damienmckenna’s picture

Status: Active » Fixed

I 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.

nirvanajyothi’s picture

@DamienMcKenna

please check the nodewords General Settings page and ensure you have items selected in the "Meta Tags Enabled On Administrative Settings Pages" block

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. :)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

damienmckenna’s picture

Status: Closed (fixed) » Needs work

This may need some work, or at least some review, given we've reverted everything back to the last changes on December 31st, 2009.

damienmckenna’s picture

Version: 6.x-1.x-dev » 6.x-2.x-dev
Status: Needs work » Closed (fixed)
Issue tags: -v6.x-1.12 blocker

Removing this from the 6.x-1.12-blocker list as it is no longer relevant to 6.x-1.x.