Maintainer is clearly ignoring issues and is certainly not "Actively Maintaining" this module. There are several major bugs that have been reported and even issues that were re-opened because they clearly still exist, were immediately changed back to "Closed" and when questioned why it was closed, no response.

Comments

crystaldawn’s picture

Category: Task » Support request
Priority: Normal » Minor
Status: Active » Closed (works as designed)

The "unable to reproduce" option exists for a reason. Just because you have an issue, does not mean everyone does. Thanks for not understanding how software development works. And if the maintainer closes an item, that also means that it's actually quite actively maintained. Your configuration issues clearly have you angered and baffled at the same time. Do not attempt to take them out on others in a public forum, it could end badly for you.

crystaldawn’s picture

Title: Change Maintenance Status to Abandoned » What is the status of the module?

Update subject to something more appropriate. The project is still "clearly" maintained. Current status of closed is correct.

marty.true’s picture

"it could end badly for you"... Wow! Did you really just threaten me on Drupal.org?
How about actually responding to issues reporting rather than just closing them leaving users out to dry?!

crystaldawn’s picture

For one, users do not pay me to fix their issues (that would include you, you've never paid me a dime). Thus, users who leave demands and ridiculous threads usually end up worse off than when they arrived because their issues never get resolved due to no one wanting to put forth the effort to offer help to combative people. So yes, your issues are likely to end badly for you. And to answer the point, I have stated many times that issues such as those you have experienced are SERVER related. Not all servers are created equal. Especially when it comes the the $_SERVERS variables. When that is stated, you dont re-open a thread and make the claims you have made without re-producible proof AND/OR a patch to prove your point. Then at that point it's up to the maintainer to determine if the patch will effect any other users negatively before it is implemented. You sir, have provided neither other than to annoy a maintainer by opening purposefully closed threads, leaving accusatory remarks in the issue queue, and obviously combative actions by acknowledging that a maintainer is somehow inactive after stating that they close threads which directly contradicts your own claims of inactivity. So your situation is very likely going to end badly in that your issues will never get resolved if this is how you go about trying to fix things. So, it's not a threat. It's just a fact of life based on the way you handle your development issues. I would hate to be your client, I can imagine not very many things get completed in a timely manor if you're unable to get help when you need it simply because of the way you go about asking for it.

marty.true’s picture

Sorry but closing a thread, unanswered, is not considered "maintaining" anything other than a poor attitude towards people that may not have ready some other thread where you said something about that particular issue. And as far as being "combative", I have contributed to many issues on many different modules and have never had an experience with a maintainer like I have with you. For you to start out by saying "users don't pay me to fix issues" speaks volumes to why this whole "argument" even exists... you don't want to have to address issues of the module that you created because you're not getting paid? Hey, just a little secret... Drupal is open-source and is based on community so try being a little more supportive to "the community" when support is sought on a module you created.

But whatever, I'm done with this. We've obviously both been "rubbed wrong" by each other and this is going nowhere and will have no positive outcome so.... enjoy your day!

crystaldawn’s picture

Open Source also != demands are acceptable. It also means, you can see the source, so fix it yourself. So if this were paid, then demands would be warranted. That is the point I make. The queue is filled with plenty of re-producible issues that I have fixed. And those that I cant reproduce, I will not even attempt to fix as it's a waste of my time that I could be using elsewhere.

Also, if you look at the "Closed" settings of a thread, you may just happen to notice that there are MULTIPLE "Closed" options. Take a guess as to why. That's right, each one of them has an "Answer" after it that is common enough to include as a default option. Maybe you didnt read the closed method that was used "Cannot reproduce". So dont attempt to insinuate that I did not answer anything. It's insulting and just a flat out farce because in order to close anything at all, it forces you to give a reason as to why its being closed which contradicts your statements. So yea, you rub people the wrong way when making accusatory remarks like this. There are 1000's of examples in D.O that have issues closed with nothing more in them other than the default Closed reason. The most common..... "Works as designed" and "Unable to reproduce". Many of which have no explanations other than that. When that happens, it usually means the OP did not read something such as the thread history or the manual.