Renoise Wiki

And here it is!

Looking for extended documentation of all the tips and tricks and uses of Renoise, and all related production issues? Check it out!

Want to make your contribution? Easy. It’s wiki, so learn about how to edit and share some wisdom. The more of us contributing the better.

Moderators: can we have this pinned?

Thanks. We’ll try and keep some attention on this throughout the year.

dear diary,

I did a small contribution to the renoise wiki today.

MLKjr day was supposed to be a day of community service. So, I added stuff to the wiki and gave away an FM synth to someone who will use it more than I do.

Thank you for raising awareness on this day.

Spam appeared on February 14th in the Talk:Main Page‎…

Lock-down imminent.

Hmm, I’ve let my contributions slip to this due to focus being elsewhere. Maybe a user system is needed?

Alas that is inevitable. On the long run I think it’s for the better.

That was what i already foresaw coming as soon as the system was put up.
A simple “edit” password (and emphasized explanation about it) and spambots are out of your system.

Yep sounds great. I’ve already got back into things to editing stuff and deleted any nonsense I’ve come across. I don’t know how to implement these sorts of things though…

Well you can start by altering the table of default rights for the “all” users group:

GroupRights (all)

  • Create discussion pages (createtalk)
  • Create new user accounts (createaccount)
  • Create pages (which are not discussion pages) (createpage)
  • Edit pages (edit)
  • Read pages (read)
  • Use of the write API (writeapi)

a href="."/w/edit/Renoise_Knowledge_Base:Users?redlink=1" class=“new” title=“Renoise Knowledge Base:Users (not yet written)”>Users

  • Create discussion pages (createtalk)
  • Create pages (which are not discussion pages) (createpage)
  • Edit pages (edit)
  • Mark edits as minor (minoredit)
  • Move pages (move)
  • Move pages with their subpages (move-subpages)
  • Override files on the shared media repository locally (reupload-shared)
  • Overwrite an existing file (reupload)
  • Purge the site cache for a page without confirmation (purge)
  • Read pages (read)
  • Upload files (upload)
  • Use of the write API (writeapi)

You can find this stuff somewhere DefaultSettings.php

 * Permission keys given to users in each group.  
 * All users are implicitly in the '*' group including anonymous visitors;  
 * logged-in users are all implicitly in the 'user' group. These will be  
 * combined with the permissions of all groups that a given user is listed  
 * in in the user_groups table.  
 * Note: Don't set $wgGroupPermissions = array(); unless you know what you're  
 * doing! This will wipe all permissions, and may mean that your users are  
 * unable to perform certain essential tasks or access new functionality  
 * when new permissions are introduced and default grants established.  
 * Functionality to make pages inaccessible has not been extensively tested  
 * for security. Use at your own risk!  
 * This replaces wgWhitelistAccount and wgWhitelistEdit  
$wgGroupPermissions = array();  
// Implicit group for all visitors  
$wgGroupPermissions['*']['createaccount'] = true;  
$wgGroupPermissions['*']['read'] = true;  
$wgGroupPermissions['*']['edit'] = true; //Set this one to false  
$wgGroupPermissions['*']['createpage'] = true; //set this one to false  
$wgGroupPermissions['*']['createtalk'] = true; //set this one to false  
$wgGroupPermissions['*']['writeapi'] = true; //set this one to false  
// Implicit group for all logged-in accounts  
$wgGroupPermissions['user']['move'] = true;  
$wgGroupPermissions['user']['move-subpages'] = true;  
$wgGroupPermissions['user']['read'] = true;  
$wgGroupPermissions['user']['edit'] = true;  
$wgGroupPermissions['user']['createpage'] = true;  
$wgGroupPermissions['user']['createtalk'] = true;  
$wgGroupPermissions['user']['writeapi'] = true;  
$wgGroupPermissions['user']['upload'] = true;  
$wgGroupPermissions['user']['reupload'] = true;  
$wgGroupPermissions['user']['reupload-shared'] = true;  
$wgGroupPermissions['user']['minoredit'] = true;  
$wgGroupPermissions['user']['purge'] = true; // can use ?action=purge without clicking "ok"  
// Implicit group for accounts that pass $wgAutoConfirmAge  
$wgGroupPermissions['autoconfirmed']['autoconfirmed'] = true;  
// Users with bot privilege can have their edits hidden  
// from various log pages by default  
$wgGroupPermissions['bot']['bot'] = true;  
$wgGroupPermissions['bot']['autoconfirmed'] = true;  
$wgGroupPermissions['bot']['nominornewtalk'] = true;  
$wgGroupPermissions['bot']['autopatrol'] = true;  
$wgGroupPermissions['bot']['suppressredirect'] = true;  
$wgGroupPermissions['bot']['apihighlimits'] = true;  
$wgGroupPermissions['bot']['writeapi'] = true;  
#$wgGroupPermissions['bot']['editprotected'] = true; // can edit all protected pages without cascade protection enabled  
// Most extra permission abilities go to this group  
$wgGroupPermissions['sysop']['block'] = true;  
$wgGroupPermissions['sysop']['createaccount'] = true;  
$wgGroupPermissions['sysop']['delete'] = true;  
$wgGroupPermissions['sysop']['bigdelete'] = true; // can be separately configured for pages with > $wgDeleteRevisionsLimit revs  
$wgGroupPermissions['sysop']['deletedhistory'] = true; // can view deleted history entries, but not see or restore the text  
$wgGroupPermissions['sysop']['undelete'] = true;  
$wgGroupPermissions['sysop']['editinterface'] = true;  
$wgGroupPermissions['sysop']['editusercssjs'] = true;  
$wgGroupPermissions['sysop']['import'] = true;  
$wgGroupPermissions['sysop']['importupload'] = true;  
$wgGroupPermissions['sysop']['move'] = true;  
$wgGroupPermissions['sysop']['move-subpages'] = true;  
$wgGroupPermissions['sysop']['patrol'] = true;  
$wgGroupPermissions['sysop']['autopatrol'] = true;  
$wgGroupPermissions['sysop']['protect'] = true;  
$wgGroupPermissions['sysop']['proxyunbannable'] = true;  
$wgGroupPermissions['sysop']['rollback'] = true;  
$wgGroupPermissions['sysop']['trackback'] = true;  
$wgGroupPermissions['sysop']['upload'] = true;  
$wgGroupPermissions['sysop']['reupload'] = true;  
$wgGroupPermissions['sysop']['reupload-shared'] = true;  
$wgGroupPermissions['sysop']['unwatchedpages'] = true;  
$wgGroupPermissions['sysop']['autoconfirmed'] = true;  
$wgGroupPermissions['sysop']['upload_by_url'] = true;  
$wgGroupPermissions['sysop']['ipblock-exempt'] = true;  
$wgGroupPermissions['sysop']['blockemail'] = true;  
$wgGroupPermissions['sysop']['markbotedits'] = true;  
$wgGroupPermissions['sysop']['suppressredirect'] = true;  
$wgGroupPermissions['sysop']['apihighlimits'] = true;  
$wgGroupPermissions['sysop']['browsearchive'] = true;  
$wgGroupPermissions['sysop']['noratelimit'] = true;  
#$wgGroupPermissions['sysop']['mergehistory'] = true;  
// Permission to change users' group assignments  
$wgGroupPermissions['bureaucrat']['userrights'] = true;  
$wgGroupPermissions['bureaucrat']['noratelimit'] = true;  
// Permission to change users' groups assignments across wikis  
#$wgGroupPermissions['bureaucrat']['userrights-interwiki'] = true;  
#$wgGroupPermissions['sysop']['deleterevision'] = true;  
// To hide usernames from users and Sysops  
#$wgGroupPermissions['suppress']['hideuser'] = true;  
// To hide revisions/log items from users and Sysops  
#$wgGroupPermissions['suppress']['suppressrevision'] = true;  
// For private suppression log access  
#$wgGroupPermissions['suppress']['suppressionlog'] = true;  
 * The developer group is deprecated, but can be activated if need be  
 * to use the 'lockdb' and 'unlockdb' special pages. Those require  
 * that a lock file be defined and creatable/removable by the web  
 * server.  
# $wgGroupPermissions['developer']['siteadmin'] = true;  

I rejected MediaWiki because it did not contain a simple password protection system.
You have to disclose editing for all public but users.
Since bots still have the ability to automatically create an account, you also need to have some kind of protection from auto creation of accounts. That kind of stuff is usually not worth the trouble for most users to create an account and simply add a remark to one page.
Or you have to validate users yourself.

PmWiki is much simpler, you can just define a basic edit-password for all pages without a user requiring to create an account.
By simply publically announcing what the password is, someone can just quickly add a comment without all that fuzz you need to submit with MediaWiki, yet is as much effective against bots.

If we’re talking wiki, I personally know a bunch of TikiWiki developers and can get my questions answered over beers.

I’ve been solicited to be a contributor; but as I have no TikiWiki based projects, it’s hard for me to transition into the group.

I know TikiWiki not the most popular, but if we can work TikiWiki into Renoise, it would open up some doors for anyone who’s motivated. (not just me)

Version 3.0 is due in march.

Thanks for the interesting info! I don’t know how to access that php file, and I probably shouldn’t have access not being an admin or anything like that.

A new one:

I’ll slowly do all the FX like this.

I can access the file alright, i just can’t save back a modified version. (restricted rights which is imho okay as well)

Is there a way to remove my user profile that got linked to the ordinary user group?
I used the same board credentials to create an account on the wiki before you applied the above changes.


EDIT: Well that was weird!!! I logged into the wiki with my forum user and I couldn’t post on the board HERE! I had to log out from the wiki to post THIS message. Hmmm…

Great …This is a very great idea

Probably because the same cookie is being used (and altered).
Perhaps a separate cookie has to be generated

Shouldn’t it be more than 100+ posts? I got a 100 posts in about two months. And I don’t feel like I know enough to have any true power over pages.

It should be higher, no? Maybe a 1000.

You’re a dedicated Renoise user. I believe that’s all it takes to be able to submit to the wiki.