Some plugins can be entirely compatible with different elgg versions - they should able to be marked as such for people searching for plugins. Otherwise it may be misleading, and people may assume that if a plugin is tagged as 1.8 that it won't work in 1.9.

Currently you can edit the general plugin info but not the release-specific info. It would be helpful to be able to edit also the info of a specific release. For example, you might only notice later you made a spelling error in the release notes, you might have selected the wrong Elgg version as compatible version or you forgot to set the release as recommended.

With the new option to select multiple Elgg versions it would be especially useful to be able to edit release info afterwards. Let's say you tested a plugin that you originally have written for Elgg 1.8 now on Elgg 1.9 and it turns out that the plugin works without changes. Then it would be nice to update the compatibility info without the need to upload a new release.

Right now only the number of downloads and recommendations of the plugin project that is kept will remain while the number of downloads and recommendations of the project that is merged get lost. It would be nice, if the total number of downloads and recommendations would be preserved after the merge.

Sometimes nice to get even more than screenshots -- links to live demos are cool, especially for themes

Want themes to be more pretty. More picture-centric in general

https://community.elgg.org/plugins/1939498

Perhaps a button on the plugin page.

Clicking it would:

• Create the relation ElggUser -> ownership_request -> ElggPlugin
• Send a notification to admins

A page in the admin panel would list all pending requests.

also, layout breaks at the size 820 +.

Current:

With margin:

Community Site:Bug: can't delete others comments from own plugins

User can show on profile a widget with "i use this" widgets listing

When using plugins search, the title on results page is displayed different from the title when using site search.

The title is not wrapped in elgg-head and is therefore shown without padding just below the navbar.

Plugin search:

<div class="elgg-main elgg-body">
    <h2>Found 113 plugins, displaying 1 to 10</h2>

Site search:

<div class="elgg-main elgg-body">   
    <div class="elgg-head clearfix">
        <h2 class="elgg-heading-main">
            Results for "
            <strong class="search-highlight search-highlight-color1">plugins</strong>

I can click on the ilnk to the old release, but it shows the current release

for example on https://community.elgg.org/plugins/1894193 there is an old release v1.0 https://community.elgg.org/plugins/1894193/releases/1.0. But it shows the download link the current release and the changelog for the current release

probably related to #61
this doesn't work: http://community.elgg.org/plugins/384520/2.1/analytics-plugin
but this does: https://community.elgg.org/plugins/384520

and http://community.elgg.org/plugins/384520/2.1 redirects incorrectly to https://community.elgg.org/plugins//releases/2.1

you can see it in above picture!

offenders:

• project_sidebar
• plugins/forms/*
• object/plugin_project
• navigation/sort
• add_contributors

As plugins grow older, the list of previous releases will be long. Would be nice with a dropdown instead.

Encourage Elgg-y coding this way

Use something like: Elgg/Elgg#6731

When commenting inline on river item about new plugin, comments get attached to the plugin project, not the particular version. W don't have display specific to plugin project to display comments on, so they may be considered "lost" by the users.

We should:

• remove commenting of plugin project in favor of versions only
• add place to display plugin project comments (confusing IMO)

hi, I'm trying to install it on 1.7.10...after installation, there are only white pages clicking on plugins' links. Some advice to set up this plugin?
thanks in advance

Browse most recent plugins or using category search goes to the "No plugins found" page.

Now the version is required in the link http://community.elgg.org/plugins/736695/2.7.1/event-manager

a link like this
http://community.elgg.org/plugins/736695/event-manager
should point to the latest release

It seems that Recommend has started showing up on owned plugins. I don't remember seeing it before.

The list of my plugins is getting longer... it would help in managing them if i had a page with river activity / comments on my plugins

All the plugin project administration features (edit, delete, upload new release, etc) are found only form the page displaying a single release. If user removes all releases they cannot administer the project anymore.

Not sure whether its due to any caching. But the plugin titles in river is not changing when we change the plugin name.

For eg:
User X released a new version of the plugin title_name

Every time I need a list of my plugins I get lost and end up using search or going to my profile, clicking on one of my plugins and then going to the list from there. Perhaps an icon in the topbar next to messages would do us good.

If I go to http://community.elgg.org/plugins and click at Newest, Most downloads or Most recommended, any of the 3 link will show the newest plugins list. I think it is right just for the first link ;)

I just realized that the compatibility info displayed for a plugin - more precisely its releases - might not be sufficient for all situations. Right now it seems only the plugin title shows the version a plugin is compatible to. I I've not yet tried what would show up if you select multiple version of Elgg as compatible. Maybe it shows even all compatible versions. But still this seems not sufficient.

If you want to keep all releases of your plugin for all Elgg versions together in one single entry you (and the people who want to download it) come across some problems at some point:

• you don't see directly which release of a plugin is compatible to which Elgg version.
• if you need to release separate versions of a plugin for separate Elgg versions you have a problem if you don't want to support only the latest version of Elgg only. The problem is that there is only ONE recommended release. What am I supposed to select as recommended. Example: Tidypics. I want to continue to release versions for Elgg 1.8 while I started today to release a version working on Elgg 1.9. If I would have added both versions within a single entry in the plugin repository I'm pretty sure it would have resulted in a lot of confusion.

Suggestion: include links to all releases of a plugin in the sidebar sorted by Elgg releases they are compatible with. For each Elgg major release all compatible versions should be listed (as indicated by the plugin uploader). Therefore, the same version might show up more than once, i.e. under each Elgg version the release is working with. There might also be no longer the necessity to define a "recommended" release then. Maybe it's best to assume that the latest release displayed under each Elgg release is the recommended version.

It could look like this:

for Elgg 1.9

- 1.9.1 (release 10 days ago)

- 1.9.0 (released 100 days ago)

for Elgg 1.8

- 1.8.13 (released today)

...

or in another case:

for Elgg 1.9

- 1.3 (released yesterday)

- 1.2 (released 8 days ago)

- 1.1 (released 10 days ago)

for Elgg 1.8

- 1.1 (released 10 days ago)

- 1.0 (released 11 days ago)

This relates to #56, it is also valuable information to know which plugins are outdated and may not be maintained.

Let a warning appear automatically when a plugin reach a certain age without being updated.

We could add an option for the plugin author to add a box that says, "This plugin is no longer maintained." I know you can edit the text and add it, but better if you just need to tick the a check box.

Removing all releases from a plugin leaves it in lists, but provides no way of adding a new release or editing it. URL is set to the site URL.

Currently when you search on Google you end up getting all of a plugin's releases listed as separate results. This is not a great experience. Instead, you probably just want the canonical page for that plugin, which would then tell you the recommended release or allow you to browse further releases.

Recommend changing URL structure to:

• /plugins/:plugin_guid -- Plugin profile page (allows direct download of recommended release)
• /plugins/:plugin_guid/releases -- List of all releases with direct download links

Each release should not even have it's own profile URL, methinks, though we may still need it so people can get to the comments.

If projects decide to use Transifex (or some other online service), plugins should be able to direct people to that page.

Problem: Recursive delete process is slow, and when errors occur, the user is left to continue posting.

I'm thinking: ban with reason "being deleted", place GUID in cron job to delete content in time-limited chunks. When no content left, delete user. Possibly perform deletion outside of API with fast queries.

I wonder if there's a way we could automatically add Travis support to plugins submitted to the Elgg repo. We could at least give plugins a place to specify the build-status badge location (thought that's not necessarily Travis-specific).

Currently, you have to open each preview image separately to view them. You can't browse to the next/previous image available anymore in the lightbox.

Problem: Need a way for community to police itself.

Let's say that established community members (e.g. accounts over 6 months old) can vote newbies (accounts under 1 month old) as likely spammers (stored as a relationship). When N votes are received, the newbie is banned and placed in a moderation queue for admins to handle.

Admins see vote count beside name.

Later: Allow voting to disable content, too.

Lets add a cron handler to notify plugin author if the plugin is outdated.

We could check e.g. whether:

• The plugin hasn't received a release n months
• The recommended version is n minor versions behind the latest stable Elgg release
• Has the Elgg compatibility setting been updated (this might actually be enough for this feature!)

This cannot be added straight to Transifex yet, right?

Background:
There is no way to ask for support for a particular plugin other than in release comments, but that doesn't lend itself to identifying and resolving separate issues very much. Early on a few plugins made groups for themselves to be able to have discussions handle this need.

We should just build this right into the plugin project page itself so that pages don't just get long strings of comments, but discussions can be separated into different issues and people can easily look through the list of known issues.

Features:

• Discussions should be contained by the project, not the release, otherwise they'll disappear every time a new release is shipped, which is probably not actually what you want.
• URL for this: /plugins/:guid/discussion
• Option to turn it off?
• Way to move all those groups' content to the appropriate plugins.
• Way to move individual discussions from a group to the specific plugin, (similar to moving to another group)

I've always thought search should be a more primary action. Can we:

• Get rid of that wall of text (people ignore blah-blah text anyways)
• Visually promote searching. It's shoved off to the side too much. We also need to support text based search, not just category and Elgg version, which is far too limiting.
• Visually demote uploading (important, but secondary)

Old releases aren't downloadable as the files in the old user data directory are not copied/moved to the new owner

See my previous PR: #8

Git tags in a valid php version format or vX.Y.Z format would automatically become releases.

Requested here: http://community.elgg.org/discussion/view/1664217/elgg-community-page-view-recently-updated-plugins

This might be handy to see which projects are active.

These would be far more helpful than user avatars, for example. @PerJensen is working on something.

That would cover:

• giving preview of package contents (files tree, zip packages handling example here: https://github.com/Srokap/srokap_plugin_installer)
• extracting manifests (could display it's data and even compare with declared license/compatibility)
  • automatic extraction of screenshots
• code quality analysis
  • coding standards
  • detect deprecated functions usage - https://github.com/Srokap/code_review
  • existence of comments?
  • some nice tool for potential problems finder?

See #34

All of it would serve only informative purposes. I wouldn't want to automatically block plugins, trigger an alert at most.

Some existing tools ideas:

• http://www.sonarsource.com/
• http://sourceforge.net/projects/rips-scanner/
• https://www.owasp.org/index.php/Source_Code_Analysis_Tools