Unpublishing projects/modules

subscribe

Subscribe!!

Subscribe

subscribe
and a question: would it be possible to link or redirect from the project page(s) to here, instead of just displaying something like "you are not allowed to access this page" and leaving the user to their own devices to find out why?
Thanks in any case.

As rondp says on #5, i think something should be written on the project module pages, for the future, instead of just:

Access denied
You are not authorized to access this page.

What do you think?

I see.
You are right ;-)

Thanks for responding.

subscribing

Do we know if this is something that is likely to be resolved soon? How will this effect the implementation of these modules? I have been using both of these modules recently and am wondering about this status.

The fact that the issue queue is no longer accessible from this node makes it hard for most people to figure out what is going on here. Maybe the drupal.org redesign team / project module team should think about the best way to solve this problem ;-) If the problem is a licensing issue then it sounds like the best way to handle something like this would be to disable the download of the code, and disable the project from appearing in the module repository update. But keep the node published so you can still see the project description and keep the link to the issue queue open so that people can see what is happening and why it is revoked.

Current practice is bad for usability, and very scary when you see module revoked from the update status page and there is nothing to click on. The page shows access denied when you try and go to the node if you do find the old link, also scary especially if you are not a search ninja

Just my 2 cents.

@westwesterson: about usability, the only thing users will do is NEVER trust these kinds of modules, considering them as non-professionals!!
And this is what i might say — and a lot of people with me— ByeBye module, till i see if i remember you again or not.

Of course this is very serious, especially if you worked with for long time. But this is life, easy come… easy… GO… Modules free, and someday = ashes.

I also think that project owners, instead of unpublishing the node (like #7 AjK kindly explained before) they should consider disabling the download links and keep UP-To-Date all information of why, when, how, … on their corresponding nodes.

Anyway, i of course disabled the module and will not use it again till i see what's going on.

Maybe you should know that drewish (Andrew) said this on http://drupal.org/node/302730#comment-991269 which is considerable, respectable but non-understandable ;-)

Finally, about the search ninjaz, it's very easy to go drupal.org and search for translation_overview and you get this http://drupal.org/search/node/translation_overview where you could very easily dl what you want. They should consider not to let ppl dl' em, shouldn't they? indeed i think!!

FUN.

I agree with the people above who have mentioned that there should be some additional info when a module is revoked, I was disoriented when I saw this on my module updates page...

Subscribing and waiting patiently....

Apologies to everyone affected by this. Hopefully it'll be resolved quickly but I need to take them down until I can clarify that I'm allowed to post the code. I didn't realize the update status module would make such a big deal of this.

aja

subscribe

subscribe

watching

subscribe

AND:

AjK said:
"This issue is about the two unpublished modules. If you have a problem about the way/method/handling of situations like these by the drupal.org site please create another issue and discuss it there. Thanks."

First, this is not an issue about anything.... the module was just revoked, and NO explanation was given to people who uses it.
This is far from being a 'issue'

Second, the first thing that comes on mind about unpublished modules is what happened? If you have given some explanation, we won't be looking all about to discover what happened ( and by the way, I still don't know what happened). Is this some kind of 'Stalin-like thing? "oh, yeh... that module... never heard about it... never existed.. so you never used, and if you are using, stop using and go on never using, ok? "

you do not even have to search for the answer, it is right before you: #302704-14: Unpublishing projects/modules

so it looks like active_translation is okay to be republished but i might need to make some changes to translation_overview before that can happen. could someone flip AT back on for me?

AT flipped back on.

Setting back to postponed, pending TO.

Is this a Joke or something?!

How come?! you activate/flip back AT when it still says:

Active Translation 6.x-1.0 Project revoked: This project has been revoked, and is no longer available for download. Disabling everything included by this project is strongly recommended!
Includes: Active Translation

Should we or should we not use this module, this is indeed not a trust in any way!!

Now i tried to install (went to http://drupal.org/project/active_translation and dl) the module —just to try to understand what exactly is it trying to do— and first thing to say is (under …/admin/build/modules):

The active translation module is incompatible with the Internationalization module's query rewriting. Change the Content selection setting to All content in the Multilingual system settings page. (Currently using Active Translation Incompatible with i18n query rewriting)

So i went to select All content as it says under …/admin/settings/i18n and back to enable the module again —at least trying to do so—

Now i go visit my home page and i have no content at all, is this a joke?

I have 4 installed working languages with all content translated.

Of course this was not my up-working site, i tried it —as always do— on my dev backup site.

Anyone got what i have?

Still saying that modules should be professional and not making any "—in such ways—" confusions for end users "—us—".

Thanq.

N.B.: Forgot to say, uninstalled the module and everything went as before again —thank God—.

Setting the priority back.

@errement: If you are having an issue with the module, please use its issue queue. This issue is about the unpublishing due to possible licensing issues.

Michelle

Subscribing

thanks for your patience everyone, i finally got this straightened out. could someone republish translation overview?

Republished.

Michelle