প্ল্যাটফর্ম অনুরোধ

Platform Requests gives your site a public page where visitors and members ask for a site to be supported. Everybody sees the requests and can like them, so the most wanted platform stands at the top and you know which module to add next. The plugin is free and works with every licence.

Switching it on

A new installation switches it on once; after that you decide with Admin → Plugins → Platform Requests → Enable or Disable. It keeps its data in two tables, platform_requests and platform_request_votes. Its screens are in the admin menu under Plugins: Platform requests and Requests settings.

The public page

/en/requests (and the same in every language of the site) is called Request a platform. The introduction ends with how many sites are supported already. A link to it stands in the footer.

The list has three tabs:

• Most liked (the default): open and planned requests, the most liked first, with their number on the tab;
• Newest: the same requests, the newest first;
• Added: what was added from the list, the most recently added first.

Each request shows a heart with its number of likes, the name, the site's address, a badge Planned or Added, the asker's note, your note under it, and a line such as "12 likes · Rahim · 3 Oct 2026". Requests that wait for your approval and declined requests are never shown.

Asking for a site

The box Ask for a site has Name of the site, A link from it ("Best: the address of a video you would like to download."), Why this site? (optional) and, for guests, Your name (optional); a member's request carries the account name. Under Send request it says "Your request is shown on this page for everybody."

What the site does with a request:

1. A link without https:// gets it; one that is not a site address is refused. Without a name, the name is made from the address (example.com gives "Example"); one of the two is needed.
2. A site one of your platforms handles already is not listed: "Good news: TikTok is supported already. Paste its link on the home page."
3. A site that was asked for before (the same address, or the same name when there is no link) gets no second entry: the visitor's like goes to the earlier request ("... was asked for before. Your like was added to that request."). A declined request does not count here, so a declined site can be asked for again.
4. Otherwise the request is saved with the asker's own like on it, and the bell tells you: "A platform was asked for: ...".

One internet address may send Requests per address per day; then "You have sent 3 requests today. Please come back tomorrow." Requests you send while signed in to the admin panel skip that limit and the approval.

Likes

A click on the heart likes a request; another click takes the like back. The number changes at once. A member has one like per request; a guest is known by a cookie (aiod_voter, kept for a year). So that fresh cookies cannot pile up likes, one internet address gives a request at most five guest likes, and one address may click 40 times in ten minutes. An added request cannot be liked any more. When likes are for members only, a guest's click leads to the sign-in page.

The guard against bots

The form asks no puzzle. It carries a field only bots fill in, a task signed by your installation that works once within two hours, and a small calculation the browser does in a blink. A form sent in under three seconds is refused, and one address may send six an hour. A visitor who fails reads "The form could not be checked. Please try again."; the log gets "platform request refused" with the reason. The form needs JavaScript.

Statuses

A request starts as open, or as pending when A new request waits for my approval is on.

The Platform requests screen

On top: All and a button per status with its number (red for waiting requests, a number the menu entry shows too), a Search box for name, address and note, and The page. Up to 300 requests are listed, the waiting ones first, then the most liked.

Each request shows its likes, name, link, status, note, the asker (with the member number for a member), the internet address and the time. Below it:

• Name shown and Your note under the request (optional), for example "Planned for the next update", then Save. Your note stands under the request on the page.
• A button for every other status: Approve (for a waiting request), Open, Planned, Added, Declined.
• The bin deletes the request and its likes, after you confirm.

Added by itself

When a new platform module arrives, one you upload or one that comes with an update, and its platform gets the New badge (see Platforms and modules), every waiting, open or planned request whose address is one of its domains, or a sub-domain of one, turns to Added. A request without a link cannot be matched; mark it yourself.

Requests settings

Who may take part:

Without member accounts (Settings → Users), "Members only" counts as "Everyone".

The page: Title (empty: "Request a platform" in the visitor's language), Introduction (empty: the translated default), Link in the footer (on) and Link in the main menu (off).

Tips

• Most liked is your to-do list. A short note and a Planned badge on the top requests show visitors that somebody reads it.
• Switch approval on if the list attracts spam or sites you will never support.
• Declined hides a request, but the same site can be asked for again and starts from zero likes. Answer with a note and keep it Open if you want people to see why it cannot be done yet.
• After uploading a module, check the Added tab: requests with a link moved there by themselves.