Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - Norodo
Documentation / Hooks
« on February 5th, 2014, 01:48 AM »
This topic might be a little barebones for now. Taken from file wedge/core/ManagePlugins.php on 5feb2014

Language hooks

Found in: core/app/ManageServer.php && core/app/Help.php
Called when: Loading the admin help language file and template || Loading the help items, plus any from plugins for (?) icons.

Found in: core/app/Who.php
Called when: Viewing the "Who's Online page"?

Found in: core/app/Modlog.php
Called when: Displaying the moderation and administration logs

Foundation stone items

Found in: core/app/Load.php
Called when: Load.php is used for a lot of database interaction. It is loaded on nearly every page. When loading from database.

Found in: core/app/QueryString.php
Called when: Handling URLs?


Threads and posts display

// Admin

// User related

// User permissions

// Content creation

// Likes

// Thoughts

// Process flow and execution

// Verification/CAPTCHA points

// Who's Online

// Miscellaneous

// Notifications

// Infractions
Documentation / SSI.php
« on June 29th, 2012, 02:32 PM »
SSI.php is a common way of weaving forum data into a non-forum webpage. For instance, you can list recent topics in the sidebar of your homepage.

How to use SSI.php

So far, SSI.php is pretty much the same in Wedge as in SMF, so you can usually refer to the SMF documentation
Documentation / Configuration [To be created]
« on June 28th, 2012, 07:47 PM »
[To be created]
Documentation / Using Wedge [WIP]
« on June 28th, 2012, 07:46 PM »
This section is marked as “for users” but as you and I know, users will never read a manual like this unless they are in some way odd. Therefore, this section will contain information that might be an idea to include in a “FAQ” post at your forum or something like that.


Note: This section is very likely to change rapidly while Wedge is still in its infancy.

What is BBCode?

BBCode is a way to mark up your text in a forum in order to make it bold, italic or even make it a link.

It seems Wedge will use BBCode for text formatting, but the exact tags that will be supported is a matter to change (we don't even know if Wedge will use BBCode yet.) For now you can read up a bit on BBCodes over at SMF.

Wedge specific BBCodes

These are some codes that are not in SMF core but exist in Wedge:
nbInserts a footnote[nb]footnote[/nb]
spoilerInserts text that is not readable before a button is clicked[spoiler]Darth Vader: No. I am your father.[/spoiler]
Documentation / WeCSS [WIP] [Definitely needs Naos steady hand]
« on June 28th, 2012, 07:45 PM »
Note: WeCSS is the CSS parser in Wedge. This page will, when completed, contain information on how WeCSS works. For now it will contain what I know.
WeCSS basics

Something about no semicolons and variables [tbc]

How WeCSS looks

Code: [Select]
    overflow: hidden
    border-radius: 5px
    padding: 5px 10px 5px

Using "regular" CSS

You can use regular CSS on a filewide basis, which means you can not mix WeCSS-style CSS and regular CSS, and you may not use regular CSS in the main files. If you want to use both kinds of CSS, put them in different files. [probably need to answer why.]
Determining the scope of your project

Needs and goals when modifying messageboards can vary a lot. Some of us simply want to edit the background color of posts, while some of us want to redesign our pages from the bottom up to give them that “unique” feel. Wedge fortunately makes it relatively simple to do either.

If you want to change how the whole site feels and behaves, you want to create a theme. If you want to make a quick change to Wedge, like changing the colour of post content, you want to create a skin. A skin slides over its theme to change only a few properties of it.


To make a theme, make a subfolder […tbc…]

  • To make a skin, make a subfolder in the skins folder. The skins folder will by default be in /var/www/wedge/Themes/, but this can vary depending on your service provider. It will at least be in the Themes subfolder of your Wedge installation. [1][2]
  • The next step is to fill in the information for your skin so Wedge can know the basics of what it's dealing with. An easy way to do this is to copy the skin.xml file from the Wuthering skin folder to your skin folder and editing the contents of it. A deeper description of the skin.xml file can be found in the ~Warm/skin.xml file
  • CSS [tbc]
 1. The folder can have any name you want, but I would recommend you name it either the same as your skin, or the shortened name of your skin. For example: For a skin called The Undertaker, you can name the folder Undertaker.
 2. Protip: You can also create subskins by creating new skin folders inside the already existing skin folders. For example, you can edit the Warm skin by creating a folder inside the Warm folder
Documentation / Backups
« on June 28th, 2012, 07:42 PM »

As you already know, taking backups of your content is important. [1]

Backing up forum data

In order to back up your userbase, threads and posts, you are going to have to copy your database. There are several ways to do this, but the easiest way is by using phpmyadmin[2]

Using phpmyadmin to take a database backup
  • Log on to your phpmyadmin page. It is usually found at or in an admin panel at your host.
  • Click your way into “databases” and find the one you instructed Wedge to install to. Click it.
  • Press export
  • Make sure all the tables are selected. You can do this by pressing “select all”. Ensure that you've got SQL marked as the desired output.
  • At the bottom, turn on bzip compression. This will severely shrink (75-80%~) the size of the backup, which can get fairly huge with larger forums.
  • Click “Go”
  • Make a nice cup of tea and wait for your file to be downloaded.
Alternatives to phpmyadmin

Using SSH / the command line

Making backups using the command line or SSH is of course also possible. This is generally done with the mysqldump command like this:
Code: [Select]
mysqldump -u user -ppassword database_name > dumpfilename.sql
Where user is the Wedge database user or root. Password is this users password (note that there is no space between -p and the password), database_name is the database name you used for Wedge and dumpfilename.sql is the name and location of the backup file (ie: /home/bob/backup.sql). Your backup file is now available in that location. To conserve bandwidth you might want to compress the file. For simplicity and compatibility we recommend you use bzip or gzip compression, as these can be imported via phpmyadmin easily as long as they're under 8MB or your PHP max limit.

Backing up settings and themes

In order to back up most of your settings, themes and add-ons, you simply have to backup your forum files using FTP or another remote file administration program.

See also

Restoring backups
Automated backups
 1. And if you don't know now, you will know when your data gets lost or corrupted someday.
 2. If you don't know if you have phpmyadmin, ask your provider. phpmyadmin can sometimes be accessed from an admin panel on your webhost, or on
Documentation / Installing Wedge
« on June 28th, 2012, 07:41 PM »

  • Before you start the installation, make sure your server fulfills the requirements
  • Get the latest Wedge package and unpack it on your server in a web accessible folder. [1]
  • Create a database and a “semi-privileged” user. [2]


  • Point your web browser to and follow the instructions.  The first hinder you'll meet is likely to be setting up file permissions.[3]
  • Next up you will have to enter some information about the database you set up in step 3 of the initial setup. [4]
  • After this, simply follow the instructions and you should end up with a functioning forum.

After install
  • At this point you may want to remove anything superfluous like the Wedge installation files.
  • At last you should start configuring Wedge to function like you want.
 1. There are several ways to do this. For more help, see Uploading.
 2. See database for more information on this.
 3. See permissions for more information on this.
 4. See database continued for more information on this.
Documentation / Style guidelines [Very WIP]
« on June 28th, 2012, 07:13 PM »

Don't add a top level header


Header (Defined in "subject")
Subheader - 14pt bold
[Body text]
[Sub-subheader - bold]
[Body text]
Documentation / Requirements
« on June 28th, 2012, 07:12 PM »
Server side

A HTTP server
Apache or an "Apache compliant" server like lighttpd is recommended. Wedge will also run on ISS.

PHP 5.2
PHP 5.2 or higher.

MySQL 5.1
MySQL 5.1 or higher.

GD2 for PHP.
GD is a graphics library used to output graphics from PHP, and will be a requirement in Wedge.

Client side

A modern browser
Opera 9.0 or higher, 11.x or higher recommended.
Microsoft Internet Explorer 6.0 or higher, 9.0 or higher recommended.
Mozilla Firefox 2.0 or higher, 3.5 or higher recommended.
Apple Safari 3.0 or higher, 5.0 or higher recommended.
Google Chrome 1.0 or higher, 5.0 or higher recommended.</code>
Flash (mostly for playing videos)
Javascript (Wedge can be run without JS, but it will be less smooth)
Off-topic / Baidu bloody loves me.
« on September 8th, 2011, 04:22 AM »
What is this... It does this all the time. Are you toying with my head, or is Baidu very Norodo-happy?

Features / "User" usability
« on June 23rd, 2011, 01:00 PM »
Back with more.

First, back to what I said last time: (About the drop-down menus)

Conclusion first:
The web is (for most of us) a visual medium. Menus that the user might be interested in should be in plain view when the user is in the "right place" (profile settings is the right place to start when you want to change your theme.)
And the actual write-up:

(click to show/hide)
Quote from Norodo on June 22nd, 2011, 06:43 PM
1. Drop down menus. The problem is not so much that there are drop down menus, it's more that thee content in them can be ambiguous. For example, the first time you register, and you want to change your theme, where do you go? In the beginning you'll probably be looking for something called "settings" or "control panel", maybe you'll scroll down to the bottom of the page to check if there's a dropdown menu for it, as it is on many boards. When you don't find it there you'll look further. Could your settings be under "Profile", maybe? Yes. Yes they could. So you click account settings and what do you see?

Just an example.

You're getting confused. Where can I change my theme? If you are an inquiring mind you might just hover over modify profile long enough to find look and layout.

Thank God. You're there. The same problem develops if you want to change the default setting of " Return to topics after posting by default." or "Messages to display per page:"

This problem is to a big extent fixed when you use the "sidebar menus" instead of dropdown menus whenever possible, but there might be better solutions...
The dropdown menu system examplifies, at least to me, a system that did not have the user in mind much at all. I think I can understand the reasoning for it,[1] but it just won't do.

Let's look at what MyBB does:

(click to show/hide)
You click user CP

Edit options...

And you're there.

Now this is better but it's still not great. There's some "sensory overload" in some of these screens, where again, there is too much information being presented at the same time. Especially when you are in the user CP.

So what is the fix? I'm not quite sure. What can help tremendously is to make the first settings page you see have more of the most usually used settings, and make the other settings pages easy to reach, if you should want to do so.

In the last topic, Nao replied:
Quote from Nao/Gilles on June 22nd, 2011, 07:56 PM
But as you see... It's something we're aware of.
Which I think is super. I also think it is nice to discuss usability in general, so I hope you don't mind. :)

2. Icons.

Icons, eh, a source of many debates. With that said, I do think a lot of people do appreciate them. We've all come to understand a set of wrenches or tools to mean "preferences", maybe this could be taken further with an "eye" for the "looks and layout" part of the settings, eg.
 1. Creating dropdown menus lets you give the user more information in a smaller space. SMF is very powerful, and as such has a lot of information you want to present the user with. Dropdown menus seems like a good idea, but isn't.
Features / Groups / Permission system.
« on June 23rd, 2011, 12:15 AM »
I always thought the SMF permission system was a little funky: Like if you inherit one class from another then change the parents "available boards", the child will not reflect this (I'm not sure if it ever reflects it actually). Also, the postcount based groups / "regular group" divide seems kind of odd.

Are you planning any changes to this?
Off-topic / Is there an IRC / Chat?
« on June 13th, 2011, 05:25 PM »
I want to know, to idle, to breathe Wedge.  8-) I did try to search but, I was unable to find it. Sorry if this has been answered.

Oh and this happened when I was trying to post, might want to look into that:

Good thing I can speak faux-French (I blame Transformice) or my post would have been for my friends only. (No offense of course.)