Placing ready-made solutions in the Bitrix Marketplace: how to save time. Placing ready-made solutions in the Bitrix Marketplace: how to save time Bitrix play market

The 1C-Bitrix marketplace is already over 3 years old, and 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 tutorials. Perhaps, for experienced developers, the API documentation is enough, but for several years now, thinking about how to make my decision, 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 allowed).
• In places where it is supposed to replace the content with the values ​​​​entered into the fields of the wizard by the user, there are MACROS.
• successively. EXAMPLE:

Site packing principle:

Stage 3 - Module

Structure:

Peculiarities:

Packing principle

1. We make a master.

Stage 4 - Archive for Market

Packing principle:

Structure:

Identical to the archive for the market with a few exceptions*

• ** - /VERSION_NUMBER/..

Peculiarities:

Packing principle:

1. We take the archive with the latest stable module (full), all changes will be in the site installation wizard.
2. Delete unmodified files
3. We issue "accompanying files" (updater, module version, description)
4. We archive the folder with all the contents in VERSION_NUMBER.zip

Hooray, 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 over 3 years old, and 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 tutorials. Perhaps, for experienced developers, the API documentation is enough, but for several years now, thinking about how to make my decision, 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 repository on GitHub, I published 5 commits corresponding to 5 stages of turning a simple site into a full-fledged module for the Market (and its subsequent update):

• Stage 1 - Website
• Stage 2 - Site Creation Wizard
• Stage 3 - Module (containing the master)
• Stage 4 - archive for sending to the 1C-Bitrix Marketplace
• Stage 5 - Archive with UPDATE for 1C-Bitrix Marketplace

So, let's briefly analyze what each of the stages contains and what transformations occur with it:

Stage 1 - Website

Here

Structure:

• Public files - / (from the root of the site)
• Site template files – /bitrix/templates/TEMPLATE_ID/

Peculiarities:

• Files of included areas are stored 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 (it seems inconvenient to me, because 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 the solution to be moderated and the calls were moved from the template to the page in the version 0.2.1)

Stage 2 - Site Creation Wizard

Here

Structure:

• The module itself is /bitrix/wizards/NAME_SPACE/MASTER_NAME/..
• .description.php* - ../.description.php
• 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 (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 by user
• In the appropriate steps, fill in the fields, create sites, copy files from the file folders (section "WHAT WE PUT"). No specific action.
• The use of Cyrillic is not allowed!!! All Cyrillic characters are inserted as language phrases!
• **** - Contains a copy of the Template files. Important:
• Cyrillic is NOT allowed. Either use language files or macros.
• In places where it is supposed to replace the content with the values ​​​​entered into the fields of the wizard by the user, there are MACROS.
• ****** - Array of services connecting successively. EXAMPLE:

• ******* - Folders with group/type names contain service files. Services carry out SPECIFIC edits. For example, they replace macros in public/template files with values ​​from the installation wizard (in the example) or import infoblocks (not in the example).

Site packing principle:

1. Upload public files to /bitrix/wizards/NAMESPACE/MASTER_NAME/site/public/LANGUAGE_ID/
2. Upload the template to /bitrix/wizards/NAMESPACE/MASTER_NAME/site/templates/template_ID/
3. We replace the necessary pieces with macros
4. We write a wizard and a description step by step with variables that are important for the public / template
5. We write services that work with macros
6. We make out (we write language phrases, etc.)

Stage 3 - Module

Here

Structure:

• * - /bitrix/modules/PARTNER_CODE.MODULE_CODE/..
• Required 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 demo protection, it may be empty.
• *** - Critical value for the market!
• **** - Contains the code of the module with a partner.
• ***** - A copy of the contents of the corresponding folder of the previous stage. When installing the solution, it is copied to the /bitrix/wizards/ folder, taking you to Stage 2.
• ****** - Not shown in the example. It is simply copied to the appropriate folder when installing the module.

Packing principle

1. We make a master.
2. We decorate any tinsel according to the preparation.

Stage 4 - Archive for Market

Here

Packing principle:

1. We take the contents of the /bitrix/modules/PARTNER_CODE.MODULE_CODE/ folder and add it to the /.last_version/ folder
2. Archive the /.last_version/ folder to the archive.last_version.zip

Stage 5 - Market Update

Here

Structure:

Identical to the archive for the market with a few exceptions*

• ** - /VERSION_NUMBER/..
• Text description of the update*** - ../description.ru
• Update Installer**** - updater.php

Peculiarities:

• * - Only CHANGED files are applied to 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 format 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:

1. We take the archive with the latest stable module (full), all changes will be in the site installation wizard.
2. Delete unmodified files
3. We issue "accompanying files" (updater, module version, description)
4. We archive the folder with all the contents in VERSION_NUMBER.zip

Hooray, the module/update is ready to be sent to the Market!

How to install a free solution?

How to buy a paid solution

To purchase, click the "Buy" button in the solution card, place an order, choosing a convenient payment method. After payment, a letter with a coupon and instructions for its activation will be sent to the e-mail specified by you when ordering.

Attention! Activate coupononlyon the project for which the solution is being purchased. Do not activate it on NFR and DEMO keys.Coupon cannot be reactivated

1. Log in to your site's control panel with administrator rights.
2. Go to the Marketplace section > Update Solutions - "Coupon Activation" tab and enter the coupon in a special field.
3. After entering the coupon, the purchased solution will appear in the list of installation solutions. Click "Install" and follow the 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 site. website.

Updates and support for paid solutions in "1C-Bitrix: Marketplace" are valid for1 year old.After the end of the support period, 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 that time, your solution will work as before, the lack of updates does not affect performance.

The purchase of a new version is carried out from the control panel of your site: Marketplace - Installed solutions. It also indicates the timing of the updates.

Marketplace is a service from 1C-Bitrix that allows developers to share their solutions with a wide audience consisting of clients and other developers. What are solutions? This can be a ready-made module or component for a project on 1C-Bitrix products, such as Site Management or Corporate Portal, or a ready-made website also on 1C-Bitrix platforms. The first category of solutions involves mainly an audience of other developers, and the second is more customer-oriented. Solutions can be both paid and free.

The advantages of using this tool for developers are the opportunity to make a profit, new customers, as well as additional points to increase their rating in the 1C-Bitrix partner system. A nice bonus: for the first placed solution, Bitrix accrues the so-called welcome points - three times the amount due.

To place solutions in the Marketplace, you need to complete several steps:

You need to become a partner of 1C-Bitrix.

Sign a license agreement.
To host paid solutions, a license agreement is required. The contract is completed in the partner's personal account.

Prepare a solution in accordance with the requirements of the company.
Rules, regulations and requirements can be found in your account in the "Marketplace" section, as well as requirements for solutions can be found at the link.

Prepare graphic materials for creating the solution installation wizard and for placing the solution on the Marketplace.

Create an installation wizard and build the distribution of the solution.
Documentation for creating ready-made solutions Marketplace Bitrix Framework.

Conduct self-testing of the solution.
The test plan can be found in the course of Bitrix Framework developers.

Prepare solution description texts, installation and technical support data.
This is also an important stage, because the description should help the client to understand what your solution is like, whether it suits him and whether it is worth buying.

Select the name of the solution and the category to be placed in the catalog of ready-made solutions.
It should be taken into account that clients often search for solutions by searching by name, and changing the name requires sending new versions of applications to the contract, so it is important to immediately choose the right capacious and understandable name for the solution.

Prepare a demo site.
To make it easier for buyers to understand that your solution is exactly what they were looking for and decide on a purchase, you need to prepare an online demonstration of the finished solution.

Download the distribution kit in the partner's personal account.
You can read more about downloading on the Marketplace website. General placement questions can be found in your account in the "Marketplace" section.

Wait for your decision to be moderated.
Please note that the process can take quite a long time. If inconsistencies with the requirements are found, the solution will be returned for revision, and after the defects are eliminated, the moderation process is repeated anew. In this case, the decision is returned after the first discrepancy found, so moderation can not go through 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 phase of your product.

Think about ways to attract buyers to the solution.
Because it’s not enough to create a good product, you need to help the target audience find it!

Development of ready-made solutions will allow you to reach a higher level of development. You will be able to develop the product as you see it, taking into account the needs of customers and get the opportunity to increase the number of customers whose satisfaction depends on the quality of your solution, its maintenance and technical support. And for customers, this is a quick and fairly budget start. Therefore, we advise you to take a closer look at such a useful tool from 1C-Bitrix.

Marina Sennikova

CTO, whatAsoft