vanillaforums / community Goto Github PK

Dumps you back to addon's main page, which then has no valid data & pulls every discussion. It also then cannot be deleted the rest of the way from the UI.

There is no way for the community as a whole to leave feedback in an easily digestible manner.

I am thinking something along the lines of WordPress version voting widget that says "90% of people with Vanilla version 2.1.6 report this addon as working".

Anything that doesn't require manually intervention on Vanilla Inc.'s employees would be a step in the right direction, imo.

Uploading a normal addon such as an application with an addon.json file and no about.php fails with an empty red error box, similar to issue #128.

Upon debugging to find the error in Vanilla 2.5: an exception gets thrown in handleAddonUpload() when UpdateModel::analyzeAddon() is called.

UpdateModel::analyzeAddon() handles looking for and parsing an addon.json file in the if (file_exists("$path/addon.json")) { ... } block, but the problem is that $path is a path to a zip file, so it falls to the else block wherein $entries = self::getInfoZip($path, $infoPaths, false, $throwError); does not return any entries due to not having addon.json in $infoPaths.

The zip file should be processed before parsing addon.json.

No error is given. An empty red error box appears.

Perhaps implemented like the delete screenshot button as an 'x' in the corner. Should probably confirm too.

It's just the polite thing to do.

The addon list CSS relies on clearing floats. This appears to conflict with the side panel.

The picture shows that the first addon item extends all the way down past the side panel.

From http://vanillaforums.org/, "Documentation" goes to http://vanillaforums.org/docs.

From http://vanillaforums.org/discussions, "Documentation" goes to http://docs.vanillaforums.com/.

Asks "Are you sure you want to delete this version of the addon?"

Todd is now passing 'PercentComplete' along from Transifex, which would be useful meta data to include on the web page.

Don't make me type in the box when I already wrote a nice one in the plugin description. :(

The user must currently start a discussion via the "ask a question" link on the addon page for the discussion to be associated with the addon.

Some tools to allow moderators to link to a specific plugin would be awesome.

http://vanillaforums.org/discussion/comment/226144/#Comment_226144

I have an account already. When I try to sign in with Google, I get this

Is this asking for my GitHub login? If so, that seems pretty insecure.

Or is this just a mislabelled field?

Would like a bot to post on new PRs, cross-referencing the GitHub user with whether they have signed the Contributors' Agreement on .org, and state whether they have signed it or not, and if not, link them to it.

• Add percent complete and Name (en) to the search results page. I want to be able to change the locale names to be just in their target locale and I know from experience that this becomes a pain to maintain if I can't easily see the English name.
• The language code in Name (en) should be lowercase. Language codes are lowercase as a standard convention.

I see some sort of commit.

but either commit does not address the problem, or I don't follow it.

You end up with a local /uploads path when the file has in fact checked out to the CDN. Missing a file upload hook in there.

http://vanillaforums.org/discussions

"Fork me on GitHub" is on top (z-wise) of the top-right sign-in links, depending on screen width. Should have a lower z-index so I can actually click those things.

The call to UpdateModel::analyzeAddon() on the check() page doesn't account for cloud files and tries to access the files locally. They'd need to be pulled back down from cloud files locally to analyze them again and not have PATH_UPLOADS prepended to their path blindly.

Please fix the issue of mobile theme add-on tag un-readability .

Here is the code which does not exist in the theme but needs to be added to fix this. You can use other colors just make the contrast better because blue on grey is not readable on the mobile.

.Tag.Tag-Addon a{
color: #FCFF00;
text-shadow: 0 1px 0 #000;
}
.Tag.Tag-Addon {
background: #666;
}

Thanks

From vstatscontroller, mostly so we don't lose them in a code purge:

    $VanillaDownloads += 311528; // There were 311,528 Vanilla downloads before moving to this new database

    // There were 1,171,794 plugin downloads when we started recording plugin downloads in LUM_Download

    $AddonDownloads += 1232885; // This was the count when we migrated to garden

Suggestion: If an addon is submitted without a description, try getting it from an included README.md

This would help streamline the upload/update process

There's no way to navigate to the directory from the forum on the mobile theme.

Ideally, the addons repository would support public git repositories as a source instead of requiring a zip upload.

The addon author could release a new version by submitting the commit hash or through a more intuitive method.

So extra fun github only stuff could be implemented too.

The resulting popup after clicking on the option is empty.

• Duplicate controller names is no longer allowed.
• Every open source dashboard in the world uses endpoints on that controller. Tread carefully.

It's time to get some help on this repo. I cannot find any issues with it being so.

Add messaging to addon directory explaining cloud.

• Why certain plugins aren't available.
• Theming concerns.
• Differences in versioning.
• Cloud benefits.

When starting a discussion that is linked to an addon, the discussion message has a prepended notice:

This discussion is related to the Example addon.

This does not show up on any pages of the discussion beyond the first one.

Uploading a new version and then deleting it still bumps it to the top of the Recent pile, which is kinda dumb.

This is going to block the 2.5 release. The directory uploader is a rat's nest of deprecated code that needs to be ripped out and done correctly.

Or, we need a new strategy immediately.

Site:

• Rework top-level site nativation. "Docs" and "Cloud" options go to other sites and should not be parallel to "Community" and "Addons". "Blog" can be removed now.
• Add navigation to Addon directory to mobile theme.

Directory Functionality:

• Remove "Everything" option. Force selection to Addons, Themes, or Locales.
• Remove "Core" option. Show Vanilla & Porter in their own areas outside the directory lists.
• Add "Alphabetical" sort order.

Directory Styling:

• Rework sidebar info to right-side. Rewrite explainer texts & emphasize open source differences.
• Implement "Addons" page D3 style for addon directory list.
• Apply D3 style to addon upload, edit, search, and pagination features.
• Review and test functionality on mobile.

Single View:

• Redesign the single addon/theme/locale view using Dashboard v3 style guide.
• Implement redesigned single view.

https://open.vanillaforums.com/download

I'll fix it on cl300 afterward.

In the vforg app's homeController_getFeed_create() we get the product blog's announcements. This source needs to be changed from https://blog.vanillaforums.com/category/dashboardnews/feed to https://blog.vanillaforums.com/topic/news/rss.xml on Nov 1. A PR should be ready to go for then.

Possibly related to Google end-of-lifing its older version of OpenID, I can't log in with Google any more on http://vanillaforums.org/discussions.

There is an issue with the way files are listed on the /addon/check page. Example here. I'm hoping it's just a matter of passing stuff through Gdn_Upload::url().

There is no link to the GitHub repository. How about adding a star button like it can be created here: https://buttons.github.io

That button could go under that Faccebook, Twitter, LinkedIn and Google+ links. Or on top of them...

https://open.vanillaforums.com/addon/add

All addons must declare an appropriate GPL2-compatible license. These include: GNU GPL2, MIT, BSD, GNU LGPL, or Mozilla Public License (MPL) v2. Addons uploaded without explicit license information will be declared as GNU GPL2. By uploading your new or revised addon, you agree to these terms.

I uploaded an addon with no license info. It was rejected with "License is required." instead of being assumed GNU GPL2.

I added the GNU GPL2 as a LICENSE file in home directory. It was also rejected with "License is required".

So I'm not sure what to do next.

Based on keyword or maybe user behavior, there should be a list of similar addons.

This should be hidden to reduce confusion.

mtschirs said:

It seems that addon downloads (http://vanillaforums.org/addons) no longer start automatically. I found a lot of JS/jQuery errors via Web console on that site, might be related.

http://vanillaforums.org/discussion/30569/addon-downloads-broken