Best Of

Sim, você pode. Existe uma versão de código aberto (Open Source) e uma versão paga.

The module solution proposed in that thread is probably the best. But you could also load in the categories using JavaScript similar to a solution I have proposed for the leaderboard recently.

You should be able to use the included pockets plugin to display a pocket after the discussion list. You can then include this script:

<script>
jQuery.get('/categories?DeliveryType=VIEW').done(function (html) {
   jQuery('main')
       .append(jQuery(html).find('.CategoryList'))
})
</script>

Hi everybody,

As promised in another thread I am currently working on a new library of YAGA reaction icons. After the amazing code contributions to YAGA by @Bleistivt with help from @R_J and @pioc34 as well as others... it is now about time to give the look of reactions a fresher appearance.

This is the old icon table that - especially on retina displays - appears to be blurry and uncrisp.

I started working on new SVG icon set to integrate into YAGA. They will be able to scale to any dimension as they are SVGs. So far I cover some basics and before I come to more special icons I would like to ask the community what could be smart and relevant reactions making sense to many forums.

So first of all, what do you think of it and more importantly which reactions should I create that could be utilized by many communities? 🤔

Please provide one or two sentences of little explanation so I can understand the reaction you propose.

➡️ Current YAGA version can always be found here: https://vanillaskins.com/plugins.html#yaga

Thanx to everyone,

phreak

Large images uploaded by forum users were clogging up my server. Rather than make changes to core vanilla code, I decided a simple solution would be to run a cron script that checks for "large" jpeg's, and compresses one image every 30 minutes.

This is the script I came up with.

I added these files to my public_html, and then added a run line to cron this command every 30 minutes:

/usr/local/bin/php /home/mywebsitedomain/public_html/compressimages.php

I'm not an experienced php developer, so critical eyes and feedback are welcome, as there's the possibility I'm making big mistakes. This seemed like a simple solution to this issue for my server at least, and it freed up a lot of space, and the settings I've chosen have negligible compromise on image quality.

Hopefully this helps someone, or at least draws dev attention for a need for an integrated feature like this.

Thanks all.

I understand these kind of announcements have been kind of ad-hoc in the past, but I'd like to do them more frequently in the future. My intention is to outline in broad strokes what features and parts of the framework we'll be working on in the next few months.

Warning: These notes are not a guarantee of any particular version number or release date. It just represents some of our development goals. In particular any of these numbered releases may be broken up or shifted if we make an extra release.

Primary Goals

• Add some small new features.
• Clear our Low/Medium security backlog.
• Wrap up various on-going technical projects.

Vanilla 3.2

• New Content Embed System & Documentation. See OSS preview + announcement thread.
• User homepage selector plugin.
• Enhanced automated testing on pull requests with CircleCI.
• Various Rich Editor & Forum bug fixes.
• Low/Medium severity security fixes from the backlog.

ETA End of July

Vanilla 3.3

This one likely won't be clarified until after a few more product team meetings.

Rich Editor

• Alt-text for images.
• Better handling of embeds on mobile devices.

Routing

The team has been doing a lot of work over the last few months on a new base controller, and static routing system. A lot of the interface and classes used here are already development but may change between now and the release where they are publicly documented.

Builtin Docker Images

Vanilla currently has a project, vanilla-docker that is used for all of our team's development environment. These images are planned to be moved into the core repo, and have all dependencies placed inside. This will also include a production configured image & setup script for hosts that support Docker (looking at an installer for digital ocean).

Using this system the only dependency will Docker. All other tooling (php, composer, node, yarn, etc) will run inside of the containers.

Formatting Pipeline

Work has begun on a major refactoring of the text rendering pipeline. The goals being:

• Consistent interface for different formatters.
• Unified configuration options between Rich Editor & other formats.
• Configuration options for embeds.
• Break up Gdn_Format
• Increased automated test coverage.

JS module system

We've begun breaking up our core typescript codebase into individual packages and publishing them to NPM. These will be published under the org. The intention is to consolidate various packages & build processes floating around.

ETA End of August