#2286 Restrict tools per neighborhood [19919]

Cory Johns
Chris Tsai


At my home project page https://sourceforge.net/u/z80maniac/ I added a tool called "Summary". Then I placed this tool at a first position in my tools list. Now I can't even reach my home project page. It keeps redirecting me forever in a loop.
I know, that I can enter a project as an admin and delete this tool, but that's still a bug.

BTW, what is this tool supposed to do after all?

I'm wondering about the last question as well. Is the fact that this is a user project a problem here?


Tickets: #4642


  • Mark Ramm

    Mark Ramm - 2011-06-13
    • milestone: limbo --> jun-17
  • Dave Brondsema

    Dave Brondsema - 2011-06-14
    • size: --> 4
  • Dave Brondsema

    Dave Brondsema - 2011-06-14

    Chris: The tool produces a link back to the SF summary page, e.g. /projects/foobar/ This does not work for SF Beta user-projects and should not be used. At some point we'll make it so you can't even install the tool on a user-project.

    • milestone: jun-17 --> backlog
  • Dave Brondsema

    Dave Brondsema - 2011-06-14

    We should implement a mechanism so that neighborhood admins can control which tools may be installed.

  • Dave Brondsema

    Dave Brondsema - 2012-04-16
    • summary: "Summary" Tool Bug [19919] --> Restrict tools per neighborhood [19919]
  • Anonymous - 2012-05-12

    Originally by: earnie

    For others who find themselves in the too many redirect loop; replace the URL with /u/USER/SUB-PROJECT/admin/tools and then delete it.

    It would be nice if this could be used for the sub-project. Currently the Summary is giving a URL of /projects/SUBPROJECT.USER.u which redirects to /u/USER/SUBPROJECT which then tries to redirect to /u/USER/SUBPROJECT and for whatever reason doesn't check the URL before redirecting again. Can't the code be fixed to check for multiple redirection and not redirect? And the URL be redirected to /u/USER/SUBPROJECT/summary?

  • Anonymous - 2012-07-31

    Originally by: akozar

    This is rather confusing! (I've been banging my head against the Summary tool and reading docs for a couple of days now and I was about to file a ticket when I found this. I was trying to get http://sourceforge.net/u/akozar to display a project summary instead of redirecting to http://sourceforge.net/u/akozar/profile/ :)

    Why does a user project have metadata like name, short summary, and full description if they are not intended to be displayed somewhere like the summary page? It seems to me like the summary page would be useful for a SF user to clarify what they are using the user project for.

    What is the intended purpose of the user project anyways? I can't seem to find any info on it but I was thinking of using mine for sharing all of those miscellaneous coding artifacts littering my HD (plus putting them under revision control :) I have been assuming that user projects like http://sourceforge.net/u/akozar are supposed to behave like normal SF projects and that they are different than the user profile pages (http://sourceforge.net/users/akozar). But perhaps the former is intended to replace the latter in SF 2.0? (But then why are there trove categories for them?).

    Anyways, I understand that this is a beta implementation and if the answer is "those features are unfinished", that is fine. I'm just wondering what the vision for the end result is?

    Thanks to anyone who can clarify or point me towards an explanation!

  • Dave Brondsema

    Dave Brondsema - 2012-08-01

    Hi Anthony,

    We do have some cleanup & improvements we should do for user projects. I think you understand it pretty clearly though - it is intended for miscellaneous code and other stuff. The metadata probably should be removed. I'll make a ticket for that :)

    I would recommend installing a Wiki tool into your /u/akozar user project and use that to describe what you have in your project. Another nice option is to put a README file in your code repository and it will automatically be displayed on your code page (markdown, plaintext, restructured text formats supported)

  • Anonymous - 2012-08-03

    Originally by: akozar

    Thank you very much, Dave, for your kind clarification and tips!!

    Using the wiki tool sounds like a good alternative and I did not know about the auto-display feature on the README. Helpful! :)

    I am excited about the new options and flexibility that the Beta site offers and I deeply appreciate all of the hard work and patient responses from the SF developers and staff. You are all fantastic!! ^_^

    Thanks again.

  • Dave Brondsema

    Dave Brondsema - 2012-08-27

    We should also consider preventing subprojects on user-projects. A real project should be created for projects of that significance.

  • Anonymous - 2012-08-27

    Originally by: earnie

    I sure hope you aren't serious. I have made use of that nicety and would be truly offended at the removal of the service.

  • Chris Tsai - 2012-08-28

    Hello Earnie,

    Could you clarify your use-case? It would be good to have some concrete examples of how folks use that feature, and why either a full project, or tools installed directly to the user project (without the intermediate subproject) wouldn't be sufficient.


  • Anonymous - 2012-08-28

    Originally by: earnie

    Currently besides sub-projects I use Wiki, Downloads and Extenal Web link. I added Downloads to overcome an issue with adding files and directories under sub-project/Downloads. I have thought about adding a code repository for tracking various mixes of personal files that I feel are not right for a full blown sub-project.

  • Chris Tsai - 2012-09-26
    • labels: support --> support, p3
  • Dave Brondsema

    Dave Brondsema - 2014-02-21

    This should be a simple list of prohibited tools per neighborhood. Add it to the form at /u/_admin/overview All existing tools will be unchanged, this should just prevent a tool from being installed (should work well to add logic to the App.installable property I think)

  • Dave Brondsema

    Dave Brondsema - 2014-02-21
    • Labels: support, p3 --> p3, support, 42cc
    • Status: open --> in-progress
  • Igor Bondarenko

    Igor Bondarenko - 2014-02-28
    • status: in-progress --> code-review
  • Igor Bondarenko

    Igor Bondarenko - 2014-02-28

    Closed #550. je/42cc_2286

  • Cory Johns

    Cory Johns - 2014-03-04
    • QA: Cory Johns
  • Cory Johns

    Cory Johns - 2014-03-04
    • status: code-review --> closed
    • Milestone: forge-backlog --> forge-mar-7
  • Cory Johns

    Cory Johns - 2014-03-04
    • status: closed --> validation
  • Dave Brondsema

    Dave Brondsema - 2014-03-07
    • status: validation --> closed
  • Dave Brondsema

    Dave Brondsema - 2015-01-05
    • Milestone: unreleased --> asf_release_1.2.0

Log in to post a comment.