Drush node-export type filter broken

I cannot accept this as a bug report. I understand you are experiencing a problem but without any more information to identify what the problem is I can't simply go on "I suppose it to be a node-export error".

Cheers

http://drupalcode.org/project/node_export.git/blob/refs/heads/7.x-3.x:/n...

Your options should be defined without the --. So 'type', not '--type'.

To use the code currently, you would have to do drush node-export-export ----type=foo for it to work.

Also, closing the issue like that is a little inappropriate.

Here's two patches.

One fixes the bug, the other also fixes all of the incorrect line endings in the file. Which you apply is up to you.

Was having issues with drush node-export using any flags as --flag (I had to use ----flag), also could not drush node-export-export to csv. This worked perfectly for me. Thanks!

patch work greats! thanks again. marking this RTBC.

Also, closing the issue like that is a little inappropriate.

Instead of applying the patch (which I would be able to very quickly and easily do) I will instead waste my time replying to your smarmy remark. I have to maintain this issue queue in a manageable way. If someone creates a bug report that is missing all the information I would need to pursue a fix, I have to make a judgement call whether it is worth spending my time on. I have learnt the hard way not to waste time on such issues as countless hours of my life have gone towards issues where there was no actual bug. I also make a determination of the level of trust I can have in the bug reporter and the phrase "I suppose it to be a node export error" was significantly dubious.

I acknowledged that the person was having a problem, and correctly marked the issue as me being unable to fix it.

Clearly this drush functionality has previously worked, for a very long time, so something has changed in the Drush module, but without knowing the facts there is nothing I could do. I know now there are multiple branches of Drush which work in different ways, but not even that information was provided.

Perhaps you would prefer I just never address the issue like many other maintainers? I am increasingly more reluctant to even check these issues queues in recent times because of these sorts of comments.

I don't need this patch since I don't use this module. I am both a responsible maintainer and a responsible member of the community, so I helped roll this patch.

I suggest you read the handbook on issue statuses, especially postponed (maintainer needs more info). That is the status you were looking for.

The patch is now RTBC, please commit it.

Quite the busy-body aren't you. How I organise my work load is up to me, your precious handbook reflects that.

See http://drupal.org/node/156119#closed

see #10, and see the doc on 'won't fix'. You have demonstrated you don't comprehend why the issue was closed, so your comments are meaningless, just annoying.

Wow, Daniel, it's module maintainers like you that are leading us towards needing a "Code of conduct" for the site. Do you talk to people like this in person in the way you do in your issue queue?

This issue should have originally been marked as postponed (maintainer needs more info), and if you want to not fix it, then should be moved to closed (won't fix) not closed (fixed)

It would appear to an observer that you are essentially allowing your module to stay broken just for the sake of ego. That's not helpful to anyone in the Drupal community.

In the end, it's your issue queue to maintain or not as you wish, but closing issues that have patches RTBC just for the sake of your ego reflects poorly on all of us.

Setting back to RTBC, as the attached patch does indeed fix the outstanding issue.

Daniel, I hope you'll see that this isn't a testament to anyone not thinking you are doing a lot of work. I appreciate the vast amount of modules you maintain, and also appreciate the fact that it's a lot of work. However, that doesn't mean we should just leave this broken.

The patch was committed: http://drupalcode.org/project/node_export.git/commit/7f6f5aa. Let's leave this issue to rest.

I had exactly the same problem, came here via a quick issues search, and found help immediately -- thanks to Tim's patch. So perhaps you might thank him for helping your users use your module. Those of us who are trying to use your code don't care who's correct about exactly what status this should have received or whatever. We need to use your code, and we need it to work. If not for Tim, this would have been another experience of the sort all too common with Drupal -- searching for a problem, finding a report of the problem, and finding no resolution to the problem, or worse yet, abuse of the person who posted the problem originally.

It's people like Tim who make the community work, and he certainly gets a vote of thanks from out here in the real world.