Deletions:
HomePage

---

Additions:
When you start working on a new action, announce this at PluginsInDevelopment, someone else may be willing to help. The community mailing list and IRC channel are also a good place to find help and support from other Wikka users and contributors.
Deletions:
When you start working on a new action, announce this at PluginsInDevelopment, someone else may be willing to help. The community mailing list and IRC channel are also a good place to find help and support from other Wikka users and contributors.

---

Additions:
As you know from this tutorial, to use an action in a page you simply put the name of an action (and parameters if necessary) between double braces ({{action_name [parameter1="A"][ parameter2="B"]}}). The Wikka formatter then sends the text between the two brackets to the Action() core method . Everything after the first word is treated as a parameter of the action. If the corresponding action-file is found in the action directory, parameters are passed to it in the form of an array.
Deletions:
As you know from this tutorial, to use an action in a page you simply put the name of an action (and parameters if necessary) between double braces ({{action_name [parameter1="A"][ parameter2="B"]}}). The Wikka formatter then sends the text between the two brackets to the Action() core method . Everything after the first word is treated as a parameter of the action. If the corresponding action-file is found in the action directory, parameters are passed to it in the form of an array.

---

[943] Edited on 2008-03-09 18:29:25 by DarTar [quickly edited, needs more work]

Additions:
See also
Technically, actions are nothing else then normal php-files, which are included through the wikka-engine:
As you know from Using actions in Wikka pages, you simply put the name of an action (and parameters if necessary) between {{ and }}. The wikka-formatter then sends the text between the two brackets to the function Action($action, $forceLinkTracking = 0) in the wikka.php . If you take a closer look at it, you will see that everything after the first word is treated as a parameter of the action. If the action-file is found, the parameters are given to it in form of an array.
You can easily extend wikka's functionality by writing your own actions and saving them under a name in the actions directory. This page intends to give you some help with it.
At first, you should think about what you want to do and if an action is the best choice for it.
Mostly you will have to choose between action and handler. You can easily seperate them with the following question:
Do you add something to a page, or do you want to do something with the page?

1. for an addition to a page (the google-form, a weather-forecast, a table), an action should be your choice.
2. for doing something to a page (like cloning, deleting, editing...), use a handler

Let others do your work... ;-)

Since there are many people working with php, it is highly possible that someone has already written the code you need. You surely have looked at the (offical) WikkaFeatures and the Development-Category, but have you also seen the (unoffical) CodeContributions and the UserContributions-category?
It may take you some time to search all this places, but it is better than doing the same work twice.

... or at least help you

When you have started working on your action, announce this at PluginsInDevelopment, perhaps someone else wants to help you working on it.
You should always keep in mind that every user, who has write-access to your pages, can use an action by default. That means if you want your action being limited to administrators or registered users, you have to take care of it in the action itself, because Wikka won't!
As said above, parameters are given as an array to the action. A special name, $vars, is reserved for this array. You can use the following code to get their values:
A string representation of all the parameters given is also available through the special variable, $vars['wikka_vars']. It is supported for backward compatibility, and is documented here to help you understand at a glance some actions like {{rss}}, but it's not recommended to use it in your action scripts.
On the example above, you've seen the syntax $this. It refers to the main Wakka class, just as if your action were a method of this class. Thus, you have every methods and members defined for this class available for you.

define and function inside an action

Because an action can be called more than once, all the code that is inside it can be executed twice or more. The general rule you must take care of is:

• if you use a define statement, make it conditional using the syntax if (!defined(...))
• if you define a function, make it conditional using the syntax if (!function_exists(...))

---

Additions:

How actions work and how to write your own

Deletions:

How actions work and why it is easy to write your own

---

Additions:

2. Security

You should always keep in mind that every user, who has write-access to your pages, can use an action by default. That means if you want your action being limited to administrators or registered users, you have to take care of it in the action itself, because Wikka won't!

# Put this as the very first line of code inside your action
# The action won't work for non-administrator users.
if (!$this->IsAdmin())
{
    return;
}

As said above, parameters are given as an array to the action. A special name, $vars, is reserved for this array. You can use the following code to get their values:

# action called as {{example parameter="thevalue"}} will create a variable $vars
# defined like this: $vars = array('parameter' => 'thevalue');
if (is_array($vars))
{
    foreach ($vars as $parm => $value)
    {
        // your code here.
    }
}

A string representation of all the parameters given is also available through the special variable, $vars['wikka_vars']. It is supported for backward compatibility, and is documented here to help you understand at a glance some actions like {{rss}}, but it's not recommended to use it in your action scripts.

Global methods and members

On the example above, you've seen the syntax $this. It refers to the main Wakka class, just as if your action were a method of this class. Thus, you have every methods and members defined for this class available for you.

define and function inside an action

Because an action can be called more than once, all the code that is inside it can be executed twice or more. The general rule you must take care of is:

• if you use a define statement, make it conditional using the syntax if (!defined(...))
• if you define a function, make it conditional using the syntax if (!function_exists(...))

if (!defined('D_ACTION_MYACTION_LOGSIZE')) define ('D_ACTION_MYACTION_LOGSIZE', 60);
if (!function_exists('f_action_myfunction_get_default_logsize'))
{
    function f_action_myfunction_get_default_logsize()
    {
        return D_ACTION_MYACTION_LOGSIZE;
    }
}

to be continued
Deletions:

2.Security

You should always keep in mind that every user, who has write-access to your pages, can use an action by default. That means if you want your action beeing limited to admins or registered users, you have to take care of it in the action itself, because wikka won't!
code for restricting access
As said above, paramters are given as an array to the action. You can use the following code to get their values:
code for getting params
will be continued

---

Additions:
HomePage
Deletions:
Wikka Documentation

---

Additions:
As you know from Using actions in Wikka pages, you simply put the name of an action (and parameters if necessary) between {{ and }}. The wikka-formatter then sends the text between the two brackets to the function Action($action, $forceLinkTracking = 0) in the wikka.php . If you take a closer look at it, you will see that everything after the first word is treated as a parameter of the action. If the action-file is found, the parameters are given to it in form of an array.
You can easily extend wikka's functionality by writing your own actions and saving them under a name in the actions directory. This page intends to give you some help with it.

1. for an addition to a page (the google-form, a weather-forecast, a table), an action should be your choice.
2. for doing something to a page (like cloning, deleting, editing...), use a handler

Since there are many people working with php, it is highly possible that someone has already written the code you need. You surely have looked at the (offical) WikkaFeatures and the Development-Category, but have you also seen the (unoffical) CodeContributions and the UserContributions-category?
When you have started working on your action, announce this at PluginsInDevelopment, perhaps someone else wants to help you working on it.
CategoryEN - CategoryReview
Deletions:
This Page is also avaible in German
As you know from Using actions in Wikka pages, you simply put the name of an action (and parameters if necessary) between {{ and }}. The wikka-formatter then sends the text between the two brackets to the function Action($action, $forceLinkTracking = 0) in the wikka.php . If you take a closer look at it, you will see that everything after the first word is treated as a parameter of the action. If the action-file is found, the parameters are given to it in form of an array.
You can easily extend wikkas functionality by writing your own actions and saving them under a name in the actions directory. This page intends to give you some help with it.

1. for an addition to a page (the google-form, a weather-forecast, a table), an action should be your choise
2. for doing something to a page (like cloning, deleting, editing...), use a handler

Since there are many people working with php, it is highly possible that someone has already written the code you need. You surely have looked at the (offical) WikkaFeatures and the Development-Category, but have you also seen the (unoffical) CodeContributions and the UserContributions-category?
When you have started working on your action, announce this at PluginsInDevelopment, perhaps someone else wants to help you working on it.
CategoryDocumentation

---

Wikka Documentation

---

How actions work and why it is easy to write your own

Technically, actions are nothing else then normal php-files, which are included through the wikka-engine:

As you know from Using actions in Wikka pages, you simply put the name of an action (and parameters if necessary) between {{ and }}. The wikka-formatter then sends the text between the two brackets to the function Action($action, $forceLinkTracking = 0) in the wikka.php . If you take a closer look at it, you will see that everything after the first word is treated as a parameter of the action. If the action-file is found, the parameters are given to it in form of an array.

You can easily extend wikkas functionality by writing your own actions and saving them under a name in the actions directory. This page intends to give you some help with it.

1. Planning

At first, you should think about what you want to do and if an action is the best choice for it.

Action vs. Handler

Mostly you will have to choose between action and handler. You can easily seperate them with the following question:
Do you add something to a page, or do you want to do something with the page?

1. for an addition to a page (the google-form, a weather-forecast, a table), an action should be your choise
2. for doing something to a page (like cloning, deleting, editing...), use a handler

Let others do your work... ;-)

Since there are many people working with php, it is highly possible that someone has already written the code you need. You surely have looked at the (offical) WikkaFeatures and the Development-Category, but have you also seen the (unoffical) CodeContributions and the UserContributions-category?

It may take you some time to search all this places, but it is better than doing the same work twice.

... or at least help you

When you have started working on your action, announce this at PluginsInDevelopment, perhaps someone else wants to help you working on it.

2.Security

You should always keep in mind that every user, who has write-access to your pages, can use an action by default. That means if you want your action beeing limited to admins or registered users, you have to take care of it in the action itself, because wikka won't!

code for restricting access

Parameters

As said above, paramters are given as an array to the action. You can use the following code to get their values:

code for getting params

will be continued

---

CategoryDocumentation