Meta tags - Is there a release date?

Subscribing!

Nope. There is no planned release date for now. Right now it's just when we can fit in free time to work on this, and I'm pretty busy in the next month with DrupalCon and a wedding. After that I should be able to pick up steam on this.

Subscribing!

Please!

Subscribing

Like!

subscribe

subscribe

subscribe

subscribing

subscr :)

subscribe....

We are looking for a release of this great module.

...ibing. :)

Major bummer...

For those who can't wait:
http://www.devdaily.com/drupal/drupal-7-meta-tags-module-seo-google

subscribing

subscribe

subscribing

subscribing

subscribing

subscribing

Please remember every time you 'subscribe' to this issue I get an e-mail about it and I'm really close to locking comments on this issue. You can keep posted on the progress of this issue by checking back every so often. I'll be posting about important updates in Planet Drupal every so often.

Flowing progress.

Please don't ever change this issue away from fixed again.

Subscribing

Subscribing

Subscribing

@Dave, #22: I'm honestly, terribly sorry but since #34496: [meta] Add Flag module to allow users to subscribe/unsubscribe without posting a comment is not possible ATM, the only way for most of us to monitor this is by doing what you ask us not to (and only pray that there isn't one too many of us doing it, so we piss you off).

May I suggest that you create a "dummy" dev of the module (only .info file included for example). This way people can download it, place it in their setups *without enabling it* and check the option to check for updates for disabled modules as well. Once you have actually released something, they will be notified in their sites' status reports. What do you think?

PS: I was about to set this to 'postponed', but then I saw #25. ...I know ...'t ain't funny.

@I'm not asking people to not add subscribe comments - I can't avoid that. I don't want the status if this issue changed again and I have to be serious about it.

Subscribing

Subscribing (and of course, I wouldn't do that if there were other ways to put this on my tracker).

ok

subscribing

subscribing

Subscribing.

For any following drupaler. please use the rss-feed http://drupal.org/node/640498/release/feed . thx.

Ok, besides the fact that I want to subscribe. I also want to know if I in any way can contribute to making this module. I can't imagine it would be hard to provide with a basic version that does the job. Maybe not with all "wanted" features, but one people can start with and use for the time being.

Please let me know what has to be done and has been done yet.

subscribe

subscribe

Just an FYI: Sorry I am very busy this month. Had DrupalCon last week and I am getting married on the 19th, so please be patient or feel free to start patching. I should have more free time to resume working on contrib in April once I return from my honeymoon.

Subscribing

Keeping on eye on this one.

Subscribing (By the way, tired of subscribing ? http://3281d.com/2009/03/27/death-to-subscribe-comments)

subscribing

Subscribing.

Also, Congrats!

Congratulations, Dave!
I am one of (no doubt) many people waiting for that module. Dave, what were results of BoF?
I would be glad to join efforts on metatags module if you want. Probably it is possible to take some ideas and code from my http://drupal.org/project/metatags_quick module. It is far from nodewords functionality, but allows adding meta tags to nodes, taxonomy terms, users etc. via D7 Field API.
What do you think?

Subscribe

subscribing

+1

Subscribing. Thanks.

s 2 the ub.

Subscribing

+1

subscribe

subscribing!

Finally there was an upload but important files are missing in the archive!
http://ftp.drupal.org/files/projects/metatags-7.x-1.x-dev.tar.gz

@cybermcm: Good to see Dave has started work on the project, but I wouldn't try fiddling with it yet until he gives the all-clear.

Subscribing

Some results from the BOF at DrupalCon, although I can't find my specific notes, this is what I remember us discussing
1. Decided using custom storage/code over the trying to tackle the complexities of using the Field API for now. That could possibly be a 2.x version and eventually where we're headed, but to get code out as soon as I can, it needs to not be field-based.
2. Make configuration exportable and possibly ship with a default (either enabled or disabled) configuration that could easily be overridden
3. Minimize number of modules to enable and configuration steps
4. Everything will be token-based, with the ability to override individual meta tag values with different tokens or specific values

Based on this I'm starting to write code and get things worked out. I'll update this issue when I feel the code base is actually ready to be tested.

Thanks for the update.

Thanks Dave for all the hard work, and congrats on the wedding! :)

I'm waiting on a release so I can update the SEO Friend module to pull data from metatags for its reports.

If you need any help testing at any stage, please let me know.

Cheers,
Kristen

Sad to hear you decided not to base metatags on Fields API in 1.x (and I really regret I didn't attend Chicago BoF)
I have a feeling though that you overestimate complexity of this step. Do you completely reject my suggestion to join efforts with (Fields API-based) Meta tags quick?

@valthebald: The primary reasons decided against using Field API for now:
1. We can't make the entity/bundle configuration easily exportable with CTools.
2. Field API only works if you have entered data - for example, the user should be able to set the default meta tags for the story node type, and be able to have it work without having to actually edit any story nodes. Field API is not useful for this type of situation as the formatter would not get called if the node does not have any meta tag field data saved.

@Dave #63

I was looking at implemeneting this module for work but I came across your module so I was hoping I can help you or share my thoughts on what I came up with. I'm still fairly new at Drupal so perhaps some of my terminology may be incorrect.

My plan was to create a base entity for the metadata element. Each metadata element often have different sets of attributes, I can reuse the API to create different types of metadata elements. The attributes for these elements could be added/removed through the usage of the Field API. Since Field API allows a default value to be set, the Token system can be used to set a lot of default value such as, the title attribute will most likely have the node:title token. The dependent contrib modules will be limited to just Token API and Entity API.

I don't know if what I want to do is possible (it seems so from what I am reading), but I think this will give us a lot of flexibilities at creating different metadata elements based on each site's need.

@yeha: With a default value, you still don't 'get' that value with the field formatter until a user has actually saved the node. I'm also not keen on creating an entity for metatags.

I have a pretty good idea on how to get started and what I want to accomplish. That doesn't mean there can't be any competing ideas like metatags_quick, but just keep in mind I'm not working on any kind of migration/update script until the code has been finalized.

@Dave #66
1. Isn't this task classic for Features? (sincerely, I'm not big expert neither in Features not in CTools, but Features worked fine with CCK in D6, so I assume the same about Field API/D7. Probably I'm wrong)
2. Field API has built-in default values mechanism, and it just works. Module can bring one central place for setting default meta tag values for different entity types - for easier administration, but not added functionality. Also, while technically achievable, purpose of default meta tags values has very questionable value from the SEO perspective.

@valthebald: The concept of providing defaults is to cover for 80% of the potential audience who don't want to spend two months researching SEO techniques, and the other 20% can just change the defaults, no harm done. As I argue with someone during the Drupalcon BOF, Google isn't going to index your site in the fifteen minutes it would take to go from installing the module to customizing it to your needs, so you shouldn't have any problems.

@Dave #68

Do you mean during the create content form, the user won't be able to see the exact value of the meta terms until it's saved? Instead they will see just the actual token string?

@69
1. Features is for entire content types and their fields, not just adding specific fields to all content types.
2. Again, you do not get any value until the node itself has saved. So adding a default value in the field settings has no affect on any existing nodes that do not have have any value when we want to add the meta tags to the page output.

I feel that I need to make some disclaimer:)
If you ask me what is the biggest problem of the nodewords module, I will easily name upgrade path.
Every stable release, and often development snapshots had required db schema changes, resulting in more than 30 update functions. It may reflect progress in module development and additions in SEO industry, but it's a huge pain for site owners. I know companies which have stopped upgrading to new versions after 2 or 3 subsequent failed upgrades, and stuck to the last version where their data works correctly.
I think it's very important for the fresh start project like metatags to learn from the experience of its predecessor and be as stable in it's schema definition as possible.
So, I have 2 concerns of decision not to use Field API right now for some reason.
First concern is that right now. In other words, there is intent to use Field API in some future versions? Does that mean another non-upgradable version and need to migrate data?
Second concern is decision not to use built-in, standard drupal mechanism for extending site data. I am afraid that this could lead to changes in module schema (new types of meta tags, changes in existing). However, since Dave has more experience in drupal hacking than me, probably he has an idea how to avoid threat of constant schema changes. So the second concern worries me less.

I think I do a pretty good job personally as a maintainer handling upgrade paths. That's why I put so much time into planning and architecture. I want to get it at least close to right off the bat. Like the XML sitemap 2.x module - I handled updates through the entire rewrite process, and once I hit beta I supported the 1.x to 2.x upgrade.

If we ever switch to using FieldAPI then absolutely we'd support the upgrade ourselves. I commit to testing and making sure once you're on my code base that you will be ok.

#71 No, this is not the case.
Since default value is set, you will see it in the new node form

#74 Dave Reid
Please accept my apologies if I have offended you. I didn't want to blame neither nodewords nor its maintainers.
Opposite - I think its an excellent module with great maintainers, and I use every opportunity to stress that!
Which only strengthens my point - for a popular project, even great maintainers cannot plan and test all possible combinations of initial module versions, other installed modules, operating systems, PHP modules etc.
So, if there is an option to rely on core subsystem which is by definition tested and supported by larger number of people, it's worth doing so, even if it will postpone initial release.

@DamienMcKenna - and default values work with Fields out of the box :)

@valthebald #75

If the node is new and not saved, how can the Token system populate the fields properly?

I think I see the problem Dave pointed out, in the initial new content/node form, the user will see the default token strings of all the metadata elements. Once the user saves it, the token string is replaced by the values from the node/fields/etc and the metadata element would be save. The next time the user wants to edit the content/node form, the token string will no longer be there unless the user clears it so the default token string is used, thus more work on the user side.

I apologize if I'm asking too much questions but it's part of my learning process :)

#78
there was no word 'Token' in your question :)
If you want to use tokens - then yes, the problem definitely exists. But, also definitely, it is possible to think of solution :)

@yeha/78: No, the token string would be saved, not the result of the token string. Token replacement would happen when the meta tags are being processed (e.g. the node is being viewed).

@valthebald/75: I'm not referring to the node edit form, where default values work fine. I'm talking about the following process: you have an existing node, you then go and add a new field (let's call it field_test) to its content type with a default value of 'foobar'. Without re-saving that specific node, if you do a node_load() on it, then there is no value for $node->field_test. This is the data that is used when a node is viewed and when we would process the meta tags.

I agree! I'll continue coding tonight.

subscribing

Suppose we can use fieldAPI with default values if at least one field would be saved. So I think module just need implement int field:
[x] Use defaults (field to store)
other fields could be visible\hidden with formAPI #states

is this guy still on honeymoon?

can somebody tell me when this module will be ready? why it takes so much time?

It is a small module

/me sighs

@fender: these are some of the reasons I could figure out: reason 1, reason 2

If this is a small module, why didn't you write it by yourself?
Show some respect to others' work.

@fender,

Really? Really? If the module is so small and simple, why don't you whip it out and stop complaining here? I'm sure you can take care of it in a matter of minutes. I expect it will be better than dave's version here, and have a much more complete set of tools for doing this job. I also expect you can do this while maintaining, or helping to maintain 58 other projects on Drupal.org...

Oh what you can't do all that? Great, well maybe you can either be helpful, or see your way out of the issue queue. Module maintainers, don't need that sort of crap. I don't know what gave you the impressions that this sort of things was acceptable around here, but it's not. If you've done something similar to other module developers, I'd encourage you to go back to those posts and apologize. You should DEFINITELY apologize here.

Eclipse

'This guy' is awesome and builds awesome modules for our consumption.
Hush now.

So he maintains like the entire contrib world, has his fingers in everything good, offers support to anybody, fixes things as a webmaster, and still works a full-time job? And you can be impatient when he's on his honeymoon (and dying of some awful disease at the same time)?

@fender I got sick of waiting for Dave to work on this. It didn't take me long to get it all working. Please try my patch. Some people have said that it doesn't always apply cleanly, but I've found it works well for me, especially against the current git repo.

@davereid How dare you neglect the community! People's businesses rely on you producing code in a timely manner.

@skwashd omg, funny dude, I am still laughing, I think I can't stop, i have to visit doc or go to funeral to stop laughing. Dont be dissapointed, I hovered

seriously, why nobody said Drupal is not ready. WIthout metatags module it is kind of useless.

I mean Drupal 7 is out hwo many months now and still unusable in many ways.

Just my 50 cents. I wanted to provoke and speed up the system. Maybe Dave needs this, little bit of adrenaline shot. Is everybody sticking with D6?

@Fender,

Wow, just wow, 5 different people come here and tell you what an insensitive idiotic numbskull you are, and you just continue down the same road. Classy.

You realize that meta tags are amongst the last things that search engines even care about, and that with D7's out of the box rdf:a support you're providing way better stuff for the search engines to consume. D7's not useless with out this module.

If you want to provoke a speed improvement here, you can contribute code, money or useful resources of some sort. What you're doing currently is just trashing any sort of respect anyone in the community may have had for you.

Eclipse

@EclipseGc

Then give me a deadline, i can't give a site without meta tags to a costumer, you know how they are, they will say where are the tags.

Come on dude, G used description in results display. I guess you are not familiar with seo, for sure a site can do without them, but still they help get you rank better, at least meta description

@fender I'll keep you in mind for when my "costumer"s need typos in their meta tags.

@Fender,

You've been around here long enough, you should know that deadlines = invoices. Also, those descriptions are not exclusively cut from there, so again, my point stands.

ok then fuck the module right, who needs it. why are there so many subscribers you moron. You two are like babies

Can someone please remove that guy from d.o?

I firmly believe that non-spammer user blocking warrants very egregious and serious actions, which I do not think has happened.

@fender - at the very least please keep the language clean in here while you berate one of the community's best and most appreciated contributors (who does this work for *free* and was actually on his honeymoon then got a terrible flu, so as Tony would say, step off!). it's an all-ages open source project here, we don't need to bring it all down to that level.

(also, i will happily block any user who takes it too far. personal insults and i swearing are borderline. sometimes it's good to have a little time to think about your words and actions and then apologize before you can regain the privilege of participating here.)

ps. skwashd - nice tag.

I just want the module to be finished already. At least he can give some kind of deadline. And I am criticizing core drupal code too, because this module should be included by default.

And yes please check my videos about Drupal, I always have only positive comments. My videos have convinced many people to switch from Bugmla to Drupal. So I am contributing in that way.

It seems like I came across some oppressed individuals which can't take criticism. Well, this happens every day.

I always say directly what I think. That is just the way I am. And stop wasting this space for stupid comments. Better promote drupal like I am doing.

bye

@fender
I solemnly swear that you will never get any support or help on any modules I develop.
Feel free to exploit some other community.

Thats not criticism. Everyone here can take criticism very well. What you are doing here, however, is bashing... nothing else.

not to mention that maintainers of open source who do this as a volunteer have no obligation to give you a launch date for their projects. you want them to do it faster so that you can get paid for your project? why not HIRE THEM. or better yet, as mentioned above, finish the module yourself.

@fender,

Wow, just wow (you seem to inspire that response in me). Obviously arguing with you is a good way to get curses and insults thrown at me. Good to know for future reference.

Let's just disassemble your post since you don't seem to be following along well here:

I just want the module to be finished already. At least he can give some kind of deadline. And I am criticizing core drupal code too, because this module should be included by default.

Great, then you can contribute something other than insults and curses. Money, code and developers are almost always appreciated by any member of the community, and can help get your interests focussed on during that developer's "free time" that they are stealing from their family.

And yes please check my videos about Drupal, I always have only positive comments. My videos have convinced many people to switch from Bugmla to Drupal. So I am contributing in that way.

That's awesome, I hope you continue to do it, but that doesn't give you license to come in here and pull the crap you're pulling.

It seems like I came across some oppressed individuals which can't take criticism. Well, this happens every day.

Most of us take truly constructive criticism quite well. The problem with that is that it's fairly rare to get truly constructive criticism. You either get people who are completely uninformed about your project, or you get idiots who think they can demand deadlines from you...

I always say directly what I think. That is just the way I am. And stop wasting this space for stupid comments. Better promote drupal like I am doing.

Yeah, maybe you should think a little longer before you spit out whatever useless drivel you've decided is clever. You're the one with the stupid comments on this issue, and at the moment the only thing you're doing is promoting strife in the community.

@EclipseGc you happy guy, did you get the postcard from honeymoon? lol,

IMO, there is nothing more productive that can be had on this thread. I am therefore locking it. The maintainer is not, currently, able to provide a deadline because the scope of work is beyond his ability to determine when it will be done with any regularity. Giving a bad deadline is worse than no deadline.

That's the end.

Please:

1) stop trolling
2) stop feeding the troll.

I had to re-open this briefly just to clarify #91 - I'm not actually dying (except from discouragement). I got sick with a major fever/pneumonia while on my honeymoon which continued after we got back. So I didn't want anyone to get the wrong idea and I don't need to add anyone to my Drupal modules' last will and testament. :)