Awards/Badges for Vanilla Forums (RC1) is available!

/in , ,

You can buy it from Awards Plugin page.

It took longer than I thought, but the Badges/Awards Plugin for Vanilla Forums 2.0 is now in RC1 stage. This means that Beta testing phase was completed for the existing features, and the plugin is now ready. Latest version includes many bug fixes, an improved User Interface and the ability of exporting and importing Awards and related data with just a few clicks. Also, plugin comes with a set of pre-configured Awards and Classes, to help you getting started with your Community. To view a full list of plugin’s current and upcoming features, please visit the Awards Plugin page in the shop.

More good news: Release Discount!

To celebrate this important release, you can avail of 10% discount on the regular price by using the coupon code awds-10-0513. The code is valid for the first ten orders of the plugin, and it expires on the 15/05/2013, so make sure you get your licence quickly!

Some screenshots

As they say, pictures are worth a thousand words, so here are some screenshots from latest version, showing some of plugin’s great features. The target was to make something that looked great and worked great, and I think we got it!

Post Scheduler and Hot Threads Plugins have been updated

/in , ,

As indicated in the title, the following Plugins for Vanilla Forums have been updated. Please download the latest version to make sure you get all the new features and bug fixes.

Post Scheduler

  • Fixed bug in filtering of Scheduled Discussions. The bug allowed unauthorised Users to see Scheduled Discussions when clicking on a Category.

Hot Threads

  • Added weighing of Discussions’ age to prevent stale Discussions with a high “hot” score from appearing in the Hot Discussions list forever.

To get the latest versions, simply click on the download link(s) that you received when you purchased the plugins. New purchases will automatically receive the latest version.

Apology – Content removed due to poor quality

/in ,

This post is an apology to all the readers for having published a post, now removed, which was not constructive and contained poor quality content and that upset one of our readers.

The purpose of this blog is sharing experiences related to Software Development, in the hope that they might be useful to fellow Developers. The removed post did little to achieve such objective, and contained excessive remarks that should have been avoided.

As the person responsible for the content of the blog, I would like to apologies to the reader who reported the post, and to anyone else who could have found it upsetting.

I will make sure that such type of content won’t be published again.

Regards,

Diego

Post Scheduler and Hot Threads Plugins for Vanilla 2.0/2.1 are now available

/in ,

It was a busy week, and I’m happy to announce that two new plugins for Vanilla Forums are now available. Post Scheduler allows you to publish a Post (Discussion) at a later time, thus freeing you from the burden of getting up at ungodly hours to send a message to your community, while Hot Threads displays a list of the Discussions which have received the highest amount of Comments and/or visits.

Also, to celebrate my anniversary in Vanilla Community, you can get 10% discount by using the coupon code VanYear-13 (valid until 15/03/2013).

Enjoy!

Why you should always add Licensing Terms to any software you distribute

/in ,

I recently got involved in a debate on the topic of Software Licensing, and I found it sad that there is so little understanding, amongst Developers, of such an important topic. Together with writing complete and accurate documentation, knowing how to license your Software is one of the skills that any Developer worth his salt must have. At the same time, Users must learn how to read licences, and get the habit of doing it, unless they like risking to violate them without even knowing. Read more

How NOT to interact with non-technical Users

/in ,

The content of this post has been removed following a complaint received by a reader.

The objective of this blog is to share experience with fellow developers in a constructive way. We acknowledge that the original post didn’t meet such objective, due to some non-constructive remarks that should have been avoided.

We would like to extend an official apology to anyone who was offended by the post, and reassure all our readers that we won’t be publishing such type of content again.