The 1C-Bitrix marketplace is already more than 3 years old, but full-fledged educational materials In my opinion, there are still no examples of development. This problem was not solved even with the release of the official 1C-Bitrix training course with video lessons. Perhaps the API documentation is enough for experienced developers, but for several years now, thinking about how to make my own solution, I didn’t even know where to start.
Especially to solve this problem, I released my own simplest solution with minimal functionality (in version 0.2) - “SimpleAdaptive Landing”.
Structure:
Peculiarities:
Structure:
- WHAT WE PUT - ../site/
- “Services” - ../services/
Peculiarities:
- *** - Contains a copy of public files (Cyrillic is acceptable).
- In places where content is supposed to be replaced with values entered into the fields of the wizard by the user, there are MACROES.
- sequentially. EXAMPLE:
Website packaging principle:
Stage 3 – Module
Structure:
Peculiarities:
Packing principle
- Let's make a master.
Stage 4 – Archive for the Market
Packing principle:
Structure:
Identical to the market archive with a few exceptions*
- ** - /VERSION_NUMBER/..
Peculiarities:
Packing principle:
- We take the archive with the latest stable module (full), all changes will be in the site installation wizard.
- Deleting unmodified files
- We prepare “accompanying files” (update, module version, description)
- Archive the folder with all the contents in VERSION_NUMBER.zip
Hurray, the module/update is ready to be sent to the Market!
An example of a simple ready-made solution for the 1C-Bitrix Marketplace
The 1C-Bitrix marketplace is already more than 3 years old, but in my opinion there are still no full-fledged training materials with development examples. This problem was not solved even with the release of the official 1C-Bitrix training course with video lessons. Perhaps the API documentation is enough for experienced developers, but for several years now, thinking about how to make my own solution, I didn’t even know where to start.
Especially to solve this problem, I released my own simplest solution with minimal functionality (in version 0.2) - “SimpleAdaptive Landing”.
In the GitHub repository, I published 5 commits corresponding to the 5 stages of turning a simple site into a full-fledged module for the Market (and its subsequent update):
- Stage 1 – Website
- Stage 2 – Website Creation Wizard
- Stage 3 – Module (containing a wizard)
- Stage 4 – archive for sending to Marketplace 1C-Bitrix
- Stage 5 - Archive with UPDATE for 1C-Bitrix Marketplace
So, let's briefly look at what each stage contains and what transformations occur with it:
Stage 1 – Website
Here
Structure:
- Public files – / (from the site root)
- Site template files – /bitrix/templates/TEMPLATE_ID/
Peculiarities:
- We store files for included areas in the site structure (so that you can easily add new landing pages in different sections of the site and inherit the necessary “slides” of included areas)
- The call to include areas is located on the index.php page (this seems inconvenient to me, since it introduces the risk of damaging the code for calling components by content editors, but does not add any benefit. However, this was a mandatory requirement for passing the moderation of the decision and the calls were moved from the template to the page in the version 0.2.1)
Stage 2 – Website Creation Wizard
Here
Structure:
- The module itself is /bitrix/wizards/NAME_SPACE/MASTER_NAME/..
- .description.php* - ../.description.php
- Wizard wizard.php** - ../wizard.php
- Wizard language files (wizard and description!) - ../lang/language_ID/
- Pictures (used in the installation wizard to DESIGN the installation process) - ../images/
- WHAT WE PUT - ../site/
- Public files*** - ../public/LANGUAGE_ID/
- Template files**** - ../templates/TEMPLATE_ID/
- “Services” - ../services/
- List of services****** - ../.services.php
- “Types”/“Groups” of services, for example MAIN******* - ../main/
Peculiarities:
- * - contains the wizard version (not critical) and an array of wizard steps (it is important to add new steps to the array!)
- ** - Contains the wizard steps themselves, as well as “default values”. Important in this file:
- Pass the “default” values from the primary array to the appropriate step and process them there, even if you do not plan to change them custom
- In the appropriate steps, fill in the fields, create sites, copy files from file folders (section “WHAT DO WE PUT”). No specific actions.
- It is unacceptable to use the Cyrillic alphabet!!! We insert all Cyrillic characters into language phrases!
- **** - Contains a copy of the Template files. Important:
- Cyrillic is NOT allowed. Either use language files or macros.
- In places where content is supposed to be replaced with values entered into the fields of the wizard by the user, there are MACROES.
- ****** - Array of services connecting sequentially. EXAMPLE:
|
"TYPE_NAME/GROUP" => Array( "NAME" => GetMessage("SERVICE_MAIN_SETTINGS"), "STAGES" => Array( "service_file_1.php", "service_file_2.php", "service_file_3.php", |
- ******* - In the folders with the names of groups/types there are service files. Services make SPECIFIC edits. For example, they replace macros in public files/templates with values from the installation wizard (in the example) or import information blocks (not in the example).
Website packaging principle:
- Upload the public files to /bitrix/wizards/NAME_SPACE/MASTER_NAME/site/public/LANGUAGE_ID/
- Upload the template to /bitrix/wizards/NAME_SPACE/MASTER_NAME/site/templates/template_ID/
- Replace the necessary pieces with macros
- We write the wizard and description step by step with variables that are important for the public/template
- We write services that work with macros
- We design (we write language phrases, etc.)
Stage 3 – Module
Here
Structure:
- * - /bitrix/modules/PARTNER_CODE.MODULE_CODE/..
- Mandatory include** - ../include.php
- Module language files - ../lang/LANGUAGE_ID/
- module installer - ../install/
- Module version*** - ../version.php
- Installer**** - ../index.php
- Installation Wizard***** - ../wizards/
- Components****** - ../components/
Peculiarities:
- * - partner code in small letters. The module code is also in small Latin letters without underscores (unlike the template/master)
- ** - If you do not implement protection for the demo version, then it may be empty.
- *** - Critical for the market!
- **** - Contains the code for the module with the partner.
- ***** - A copy of the contents of the corresponding folder of the previous stage. When installed, the solution is copied to the /bitrix/wizards/ folder, moving you to Stage 2.
- ****** - Not shown in the example. It is simply copied to the appropriate folder when installing the module.
Packing principle
- Let's make a master.
- We arrange all sorts of tinsel according to the blank.
Stage 4 – Archive for the Market
Here
Packing principle:
- Take the contents of the /bitrix/modules/PARTNER_CODE.MODULE_CODE/ folder and put it in the /.last_version/ folder
- Archive the /.last_version/ folder into archive.last_version.zip
Stage 5 - Market Update
Here
Structure:
Identical to the market archive with a few exceptions*
- ** - /VERSION_NUMBER/..
- Text description of the update*** - ../description.ru
- Update installer**** - updater.php
Peculiarities:
- * - Only CHANGED files are included in the update
- ** - Instead of /.last_version/, the module version number is used in the folder name (must match the module version number in /VERSION_NUMBER/install/version.php)
- *** - Text file, used to display information about the update in the 1C-Bitrix Marketplace
- **** - In the simplest case, a sample from the repository can be used; no specific actions have been included in it yet.
Packing principle:
- We take the archive with the latest stable module (full), all changes will be in the site installation wizard.
- Deleting unmodified files
- We prepare “accompanying files” (update, module version, description)
- Archive the folder with all the contents in VERSION_NUMBER.zip
Hurray, the module/update is ready to be sent to the Market!
Marketplace is a service from 1C-Bitrix that allows developers to share their solutions with a wide audience of clients and other developers. What are the solutions? This can be a ready-made module or component for a project on products from 1C-Bitrix, such as “Site Management” or “Corporate Portal”, or a ready-made site also on 1C-Bitrix platforms. The first category of solutions involves mainly an audience of other developers, while the second is more focused on clients. Solutions can be either paid or free.
The advantages of using this tool for developers are the opportunity to receive profit, new clients, and additional points to increase their rating in the 1C-Bitrix partner system. A nice bonus: for the first solution posted, Bitrix awards so-called welcome points - in triple the size from those who rely.
To place solutions on the Marketplace, you need to complete several steps:
You need to become a 1C-Bitrix partner.
Conclude a license agreement.
To place paid solutions, a license agreement is required. The agreement is completed in personal account partner.
Prepare a solution in accordance with the company's requirements.
Rules, regulations and requirements can be found in your personal account in the “Marketplace” section, and requirements for solutions can be found at the link.
Prepare graphic materials for creating a solution installation wizard and for posting the solution on the Marketplace.
Create an installation wizard and assemble a distribution package of the solution.
Creation Documentation ready-made solutions Marketplace Bitrix Framework.
Conduct independent testing of the solution.
The test plan can be found in the Bitrix Framework developers course.
Prepare text descriptions of the solution, installation and technical support data.
This is also an important stage, because from the description the client must understand what your solution is, whether it is suitable for them and whether it is worth buying.
Select the name of the solution and category for placement in the catalog of ready-made solutions.
It should be taken into account that clients often look for solutions by searching by name, and changing the name requires sending new versions of annexes to the contract, so it is important to immediately choose the right name for the solution.
Prepare a demo site.
To make it easier for customers to understand that your solution is exactly what they were looking for and to decide on a purchase, you need to prepare an online demonstration of the finished solution.
Download the distribution package in your partner’s personal account.
You can read more about downloading on the Marketplace website. General questions about placement can be found in your personal account in the “Marketplace” section.
Wait for moderation of your decision.
Please note that the process may take quite some time. long time. If inconsistencies with the requirements are found, the decision will be returned for revision and, after eliminating the shortcomings, the moderation process will be repeated again. In this case, the decision is returned after the first discrepancy found, so you may not go through moderation several times in a row and lose a lot of time. Therefore, we recommend that you immediately familiarize yourself with the requirements and do not skip the testing stage of your product.
Think about ways to attract solution buyers.
Because it's not enough to create good product, we need to help the target audience find it!
Developing ready-made solutions will allow you to achieve more high level development. You will be able to develop a product the way you see it, taking into account the needs of clients and will have the opportunity to increase the number of clients, whose satisfaction depends on the quality of your solution, its maintenance and technical support. And for clients this is a quick and fairly inexpensive start. Therefore, we advise you to take a closer look at this useful tool from 1C-Bitrix.
Marina Sennikova
CTO, whatAsoft
Bitrix24 has an open API which allows our clients and partners to enhance their cloud intranets solution through adjusting workflows and business logic inside their cloud-based portals. Bitrix24 also represents a great SaaS platform for creating custom businesses applications.
How to create your app for Bitrix24?
If you are an IT-specialist and considering creating a web app for Bitrix24, please follow these simple instructions:
- If you’d like your application to be available to all Bitrix24 accounts, become our partner by filling out . If you want to create a private app for your account only, registration is not necessary.
- Learn all about and how you can create your web apps.
- Select ‘Add application’ in the Applications menu inside your Bitrix24 account (on the left) to upload your private app or in your Partner Profile if you want your app to be listed publicly!
Web app authorization and security
The process of adding a new app to your Bitrix24 Cloud account is easy, and we also tried to make it as transparent and secure as possible. Each web app provides you with a list of data it may use (and change) in your Bitrix24 account, and asks your permission to do so. The new app will be installed only if you give your permission.
The oAuth security mechanism makes sure that this web app gets access only to the data you have specified (e.g. a web app may ask your permission to access tasks, CRM leads, etc.).
Got ideas for web apps?
If you are not an IT-professional but you have special needs that you believe can be solved through a custom app in your Bitrix24 portal, feel free to share your ideas with us! We"ll do our best to make your intranet solution a perfect fit for your business! Shoot us an email to
How to install the free solution?
1. Install 1C-Bitrix: Site Management or Corporate portal .You can download them here link.
2. On the page of the selected solution, click the green "Install" button.
In the pop-up window, enter the address of your website or portal (see point 1), click "Install"
3. The installation will open in a new tab, then follow the steps of the wizard.
4. Each solution has its own specifics and may require different steps to complete installation and configuration.
Detailed information and documentation are provided in the solution card in the "Installation" block. We recommend that you review this information before beginning installation.
How to buy a paid solution
To purchase, click the “Buy” button in the solution card, place your order, choosing a payment method convenient for you. After payment, a letter with a coupon and instructions for activating it will be sent to the e-mail you specified when ordering.
Attention! Activate the coupononlyon the project for which the solution is purchased. Do not activate it on NFR and DEMO keys.Coupon cannot be reactivated
To install the solution you need:
- Log in to the control panel of your site with administrator rights.
- Go to the Marketplace section > Update solutions - “Coupon Activation” tab and enter the coupon in the special field.
- After entering the coupon, the purchased solution will appear in the list of solutions to install. Click "Install" and follow further instructions.
Technical support and updates
1C-Bitrix is not responsible for the decisions of partners in the Marketplace. Technical support for solutions in the Marketplace is provided by their developers. Contact details and regulations are indicated in the solution card in the "Support" tab
All solutions from the Marketplace catalog are installed only on 1C-Bitrix products withactive license.
You can check the status in the control panel of your site, in the “Updates” section or on our website.
Updates and support for paid solutions in 1C-Bitrix: Marketplace are valid for1 year.After the support period expires, you can buy a new version at any time at a price of 50% of the cost of the solution (provided that the developer has released a new version and its number is higher than the one you have installed). Until this time, your solution will work as before; the lack of updates does not affect performance.
Purchasing a new version is carried out from the control panel of your site: Marketplace - Installed solutions. The deadlines for receiving updates are also indicated there.