Meta tags "Revisit after" and "Robots" are not output

I would need more information, to understand what the problem is.

I will re-verify the code after I am done with the changes I am actually implementing.

- Subscribing. Ask if you need any information from me.

It seems the issue is only for those meta tags that use a form field that is not a textfield, or a textarea.
I still have to understand what is different in that case.

The code has been changed, and committed.

Thanks for your report.

Issue still exists with latest DEV. I have selected "noarchive" in admin/content/nodewords/global and expect that noarchive is now enabled for all pages. This is broken. Selecting other checkboxes also doesn't help anything and will also not show other values.

I fixed the code, and committed it in CVS.

Thanks for your report.

We have still the problem with missing robots and locale tags on our sites, using nodewords 6.x-1.2.
Will there be an 1.3 Version to fix the issue?

This issue has been fixed after 1.2

Where can I find the higher version 1.2?

Is it the dev version?

If it is so. What gives?

The dev statement:
ATTENTION: Although some issues are fixed in the development snapshot, do not install it in a production site.

Why did I post here?

I use the version 1.2 and can not define the standard robots. The options to configure the standard robots is not displayed in the administer interface.

Dear maintainer. I have a tip for you. Before you contribute a module, you should test this module.

LOL, you are *not* alone. Nodewords (and all sites using the module versions 1.1+) seems to go the same way like xmlsitemap 1.x. Ruined by the co-maintainer for the reason of untested and broken, but committed code.

Do not install latest DEV if you don't like to run into ***more*** troubles. Restore a backup of previous nodewords tables if you can, keep staying at 1.0 and never install any release of the current co-maintainer on a production system without deep testing - if you are not totally crazy and like to loose at least - parts or all of your data. This is my personal suggestion - for all releases in any project of the current co-maintainer. Expect that releases are only pre-alpha or alpha code quality - nothing more! Sorry.

PS: Complain to the real maintainer for granting him CVS access :-)

never install any release of the current co-maintainer

Of course, you could not install any releases of Nodewords made from hass (for the simple fact he has not even tried to become co-maintainer of the module), who is good to talk of what other people do, but he doesn't talk of the code he develops.
Let's rollback to the as it was before I committed new code, and see what hass can do with that.

Or let's talk of him not understanding why the attribute colspan of a row Operations in a table with two operations is set to 2.

I would like that Mr. hass would keep his personal opinions about persons for himself. I could guess that he does that because he cannot speak of the most important thing because maybe he doesn't know much of coding.

As hass, with his comment, involved another person who is not here to reply, let's see what he said in http://drupal.org/node/104231#comment-1671334 (in reply to hass who was wondering why Robrecht gave me access to the project CVS):

Kiam was given CSV access because he promised (and did!) to look into the code of nodewords to make it more extensible and performant. He really is cleaning up the project and implements a more sane module. We all should be grateful!

Of course, you could not install any releases of Nodewords made from hass (for the simple fact he has not even tried to become co-maintainer of the module), who is good to talk of what other people do, but he doesn't talk of the code he develops.

Only for your info - Nodewords 1.0 is my code... I have upgraded 5.x to 6.x.

He really is cleaning up the project and implements a more sane module. We all should be grateful!

LOL, this was said weeks/months before the 1.1 release... now the module is only buggy and broken and break other sites, delete manually added user data, does not upgrade correctly and so on.

You will never find such a buggy and untested module made by my hands... I would never ever get committed and I would only release re-developed versions as 2.x - if code is stable.

Kim,

I am amazed.

You're the first person who commented on all the new modules with the "need review" status. In this work, you are very accurate but also extremely despotic. You show the module developers fault, but at the same time you also give comments which injury a module developer. I do not want to talk about the thing with the injury and your despotism.

What surprises me is that you find many errors in the modules of other developers, but at the same time You contribute your own modules with errors.

My public incitement to the module nodewords version 1.2: Unpulish this release and publish the last working release!

You're the first person who commented on all the new modules with the "need review" status.

I am also one of the people who approve the CVS applications, but that doesn't matter with the topic here (as it is not relevant your comment about my despotism, which is to prove).

I do not want to talk about the thing with the injury and your despotism.

It seems that we are expressing personal opinions about a person without even know the person.
Could we stop expressing such personal opinions? It seems that is easy enough, here, to pass from your code doesn't work as it should, or your code doesn't work in all the cases to you are despotic, or you don't know what you are doing (which has turned to be true for somebody else that was talking about me).

As I said, who doesn't have arguments invents them, or adds arguments that are not related with the current topic.

Excuse me for my other stuff, I talked a little with my heart.

But, when will nodewords version 1.2 unpublished?

which has turned to be true for somebody else that was talking about me

Are you talking about your bug with the colspan you have missed in the table? Take a look to your bug at http://drupal.org/files/issues/nodewords_table_column.png. I know very well what I'm doing and there may be one place in core where two columns are used for two operation links - mostly it's one column in core and I have never committed such buggy module code, but shame on my head - I comment sometimes codewise without trying it. But this doesn't change the bad quality of the 1.1+ releases up to latest DEV that make all sites broken and loosing data.

Today I wasted again 4 hours in testing this buggy module and reviewing install/upgrade processes after an 11 hour working day what resulted in another 7 critical bug issues and one reopen. Most of the cases are still followup's of previous untested buggy commits. I'm pretty worried that a stable module I've upgraded 3-4 months before D6 release - is now cluttered for the reason that I'm using it in production and I cannot trust one of this pre-alpha releases to be a save update. Data loss is *unacceptable* in all cases and if someone asks me - better nobody is working on a module than someone how crashes my site, delete my data with a new version. This hardly suxxxxx.

I'm pretty sure and think I speak for all nodewords users that - we only like to update the module without loosing any data and without having any other issue on updates.

I'm pretty sure and think I speak for all nodewords users

Please, not again with this; I have already replied on that. You have not been elected to speak for other people.

I see you keep to make personal attacks to my person, and I have all times to show you are wrong about your suppositions.

From now on, I will keep a different behavior in respect of you.