element, so that this information will be displayed correctly in the admin area under :point\_right: "[Find Plugins](https://userguide.e107.org/administration/manage/plugin-manager#find-plugins)".
| Attribute | Description |
| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Price | Purchasing price of the plugin (in xx.xx format).
Example: 25.00
|
| Currency | Currency codes (ISO 4217)
Example: EUR
|
| URL | Direct path to the website page where the plugin can be purchased. When the user clicks to download your plugin, the URL will be displayed.
❗Note: do not add the URL to the generic homepage of your website, but only the URL to the specific page for that specific plugin.
|
#### Example
```markup
```
## *plugin*\_menu.php
....
## *plugin*\_setup.php
{% hint style="info" %}
Do not forget to use your plugin name in the filename, e.g. "*myplugin\_setup.php*"
{% endhint %}
{% hint style="info" %}
TODO: Add this section, provide example.
{% endhint %}
## *plugin\_shortcodes.php*
Please refer to the [Plugin shortcodes](#plugin_shortcodes.php) page
{% content-ref url="/pages/-MUU-xAktEgx\_STyxzDR" %}
[Plugin shortcodes](/plugin-development/plugin-shortcodes.md)
{% endcontent-ref %}
## *plugin*\_sql.php
{% hint style="info" %}
Do not forget to use your plugin name in the filename, e.g. "*myplugin\_sql.php*"
{% endhint %}
This file contains the SQL database structure of the plugin. It will be analyzed on plugin install and missing tables will be installed automatically.
Any differences between the defined structure here and the table structure on the server will be detected and the user will be informed in the Admin Area.
{% hint style="success" %}
:thumbsup:**TIP:** To check if the table structure is still valid, run :point\_right:"Admin Area > Tools > Database > [Check for Updates](https://userguide.e107.org/administration/tools/database#check-for-updates)"
{% endhint %}
### Supported operations
For the moment, the following operations are supported:
* Create table
* Change field type, field size, field null or not, field default value
* Add index
### Unsupported operations
Operations that are currently NOT supported are:
* **Rename table:** by renaming the tablename, e.g. "blank" > "blank2"). The renamed table will be considered as new!
* **Drop a table:** e.g. if you remove the "blank" table definition from this file, the table will NOT be deleted from the database!)
* **Rename or drop a field:** a renamed field will be considered new, a missing field definition will NOT be recognized at all!
* **Change an index/key:** the change is recognized, but leads to an error message and the change is not applied.
* **Rename or drop an index/key:** rename is recognized as a new index and the missing index is not recognized at all!)
* A field definition containing "NULL DEFAULT NULL". The "Check for updates" method will always detect a change.
* but fails silently when trying to update. In that case remove the first "NULL" and run the the "Check for updates" again.
{% hint style="success" %}
:thumbsup:**TIP:** Check the *blank\_setup.php* file or the forum\_setup.php file for examples on renaming/dropping/modifying tables, fields and indexes.
{% endhint %}
### Example
```sql
CREATE TABLE blank (
`blank_id` int(10) NOT NULL AUTO_INCREMENT,
`blank_icon` varchar(255) NOT NULL,
`blank_type` varchar(10) NOT NULL,
`blank_name` varchar(50) NOT NULL,
`blank_folder` varchar(50) DEFAULT NULL,
`blank_version` varchar(5) NOT NULL,
`blank_author` varchar(50) NOT NULL,
`blank_authorURL` varchar(255) NOT NULL,
`blank_date` int(10) NOT NULL,
`blank_compatibility` varchar(5) NOT NULL,
`blank_url` varchar(255) NOT NULL,
`blank_media` json DEFAULT NULL,
`blank_class` int(10) NOT NULL,
PRIMARY KEY (`blank_id`)
) ENGINE=MyISAM;
```
## admin\_config.php
Please refer to the[ Admin-UI (User Interface) page. ](/plugin-development/admin-ui.md)
{% content-ref url="/pages/-M8AVDQ4CL\_ofKpUF9gG" %}
[Admin-UI (User Interface)](/plugin-development/admin-ui.md)
{% endcontent-ref %}
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://devguide.e107.org/plugin-development/installation-and-configuration.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.