Files
friendica/src/Module
Hypolite Petovan cf5beafec0 Move self key to $profile tamplate variable in hovercard.tpl template
- Simplify network and mention menu items by checking for group in Model\Contact::photoMenu
2023-10-02 21:34:49 -04:00
..
2023-03-26 16:13:07 -04:00
2023-09-10 08:16:06 +00:00
2023-01-01 09:36:24 -05:00
2023-01-01 09:36:24 -05:00
2023-01-11 09:01:24 -05:00
2023-03-26 16:14:16 -04:00
2023-01-01 09:36:24 -05:00
2023-01-01 09:36:24 -05:00
2023-01-01 09:36:24 -05:00
2023-01-01 09:36:24 -05:00
2023-01-01 09:36:24 -05:00
2023-02-19 11:12:48 +01:00
2023-02-19 11:12:48 +01:00
2023-04-15 14:17:30 +00:00
2023-01-01 09:36:24 -05:00
2023-02-26 22:43:45 +00:00
2023-01-01 09:36:24 -05:00
2019-05-01 20:17:15 +02:00
2023-01-01 09:36:24 -05:00

Friendica\Module

The Module namespace contains the different modules of Friendica. Each module is loaded through the App.

There are mainly two types of modules:

  • frontend modules to interact with users
  • backend modules to interact with machine requests

Frontend modules

This type of modules mainly needs a template, which are generally located at view/templates/.

A frontend module should extend the BaseModule, especially the content() method.

Backend modules

This type of modules mainly responds either with encoded XML or with JSON output. It isn't intended to respond with human readable text.

A frontend module should extend the BaseModule, especially the rawContent() method.

Routing

Every module needs to be accessed within a route. The routes are defined inside Router->collectRoutes().

Use the given routes as a pattern for further routes.

The routing library and further documentation can be found here.