if you are using your own design CMS, or are familiar with the CMS login and release form properties, you can refer to the custom CMS API document design directly.
Before Design It is recommended to see if CMS is a supported CMS type for a template function by referring to the custom CMS API documentation.
CMS interface parameters of the times more, we take it as an example, how to find out the various parameters of the CMS template interface.
A test site is eXAMPLE,COM, the first part of the design template login.
eXAMPLE,COM, background landing address is: eXAMPLE,COM/admin/index.asp, the template background landing address fill index, php, background directory address fill admin (if This template is the need to inject more than one type of website, you can not fill in the specific website), the website language is Chinese. The login page looks like this:
After the login is successful, you can determine whether the login succeeds by using a clear success identification information on the page, as shown in the following figure:
Here you can select “My Account” as a successful login logo. Login section here basically designed well, if the test fails, you can check the remaining optional items. If you login with the verification code, it is recommended to cancel in the background, if you can not cancel, you can also fill in the corresponding parameters template, if you do not know the specific verification code name, you can right-click “View Page Source Code”, as shown below:
Find the corresponding CAPTCHA field name in the login form by searching for the keyword “Verify:” as shown in the following figure:
The verification code field name is “CODE” in name = “CODE” and the verification code address is “inc / sdcmscode.asp? T0 = 60 & t1 = 14” in src = “inc / sdcmscode.asp? T0 = 60 & t1 = 14” .
To start publishing part of the design template, first find the article editor address, as shown below:
Here’s the address for editing: sdcms_info.asp? Action = add, and then find the article’s management address, as shown below:
Here article management address: sdcms_info.asp? Set these two addresses can be tested released, if the test fails, you can check the rest of the optional items, such as the header field name and content field name here, you can In the publish edit page, “t0” and “t4” are found according to the keyword “information title” and “information content” in the form, as shown in the following figure: “View page source code”
If there are restrictions on the column requirements, you can limit the value of the column to achieve, such as column field name is “t13”, the selected value is “1”, as shown below:
If there are some special CMS types, after the success of publishing, the background may not display the article immediately, and you may fill in the information of the successful identification of the publication, for example, here is “Generate Success”.
Attached: Custom CMS API documentation
1 Unsupported Type Custom CMS Interface Unsupported Type:
1 The verification field with the verification code when it was released.
2 Publishing requires multiple submissions.
3 need to refresh the static page (support background publishing, but need to manually refresh the static).
4 publish edit page address can not get a fixed address, you need to get it dynamically.
5 Hidden fields or field values outside the form need to be encrypted in the process of login or publish. For example, the cookie needs special assignment during login , Login password need md5 encryption encoding.
2 login interface
2.1 Required parameters:
2.1.1 background landing address (adminloginPath)
Site background login address (such as containing the background directory address, landing address, do not include the background directory address).
2.1.2 website language (language)
Website design language, the default is Chinese.
2.1.3 login successful ID (loginSuccessMsg)
Successful identification information returned after the login is successful, such as the successful login information such as “login successful” and “welcome” in the webpage after the login is successful, or some returned link websites that appear only after successful login.
2.2 Optional parameters:
2.2.1 landing submitted address (loginaction)
Login form submission address, that is, the action address in the form, if the value assigned in the form’s action, the template can be automatically matched, otherwise you need to fill in.
2.2.2 username field
The name of the user name field in the login form. If the username field name contains the “name” character, the template can be matched automatically. Otherwise, it needs to be filled in.
2.2.3 password (passwordfield)
The name of the password field in the login form. If the password field name contains the “pass” character, the template can be matched automatically; otherwise, it needs to be filled in.
2.2.4 verification code name (loginVcodefield)
The name of the verification code field in the login form. If the login form contains the verification code, you need to fill in the specific verification code field name.
2.2.5 verification code address (loginVcodePath)
Url address, if the login form contains the verification code, you need to fill in the specific verification code image Url address.
2.2.6 Background directory address (adminPath)
Website background directory address.
2.2.7 login special field (loginSpecial)
Login special fields, including the name and assignment, the login form with or without, can be specified by adding, such as authentication code and other special landing authentication field, if there are multiple fields, separated by “|”, such as “nameA : valueA | nameB: valueB “.
If the form submission process in addition to the user name, password, verification code field (such as authentication code) have verification, you need to fill in.
3 release interface
3.1 required parameters
3.1.1 release edit address (postEditPage)
Url in the background when editing articles.
3.1.2 article management address (articleManagePath)
Display, delete, edit the URL of the article.
3.2 optional parameters
Publish the title of the article form field name, if the title field name contains the “title” character, the template can be automatically matched to, or need to fill out.
3.2.2 Content Name (contentfiled)
Publish the name of the content field in the article form. If the content field name contains the “content” character, the template can be matched automatically; otherwise, it needs to be filled in.
3.2.3 text type (contenttype)
Article encoding type, the default value is “html” encoding.
3.2.4 Post successfully identified postSuccessMsg
After the success of the success of identification information returned, such as the success of the release, such as the “success of the page”, “Congratulations” and other obvious success ID information, or return some only appear after the success of the link URL. If the publication is successful, the article background management page can not match the publication of the successful article title, you need to fill in.
3.2.5 column settings (catalog)
Article column or classification field, including the name and assignment, the middle with “:” separated, such as “catalogs: 10”. If you post an article, the column or category is required, the software can not automatically match the column value, you need to fill in.
3.2.6 release special name (postSpecial)
Publish special fields, including the name and assignment, blog group to build a mass, the landing form with or without, can be specified to add, such as the author and other special release field, if there are multiple fields, separated by “|” Such as “nameA: valueA | nameB: valueB”.
If the form submission process at the article title, content, field fields are limited, you need to fill in.
4 multi-user parameter settings:
If a template needs to be injected into multiple websites of the same type at the same time, do not include the website address in the process of filling in the template parameters. For example, the background login address is eXAMPLE,COM,, Background landing address parameters simply fill login.asp.
XEvil — easy, fast and flexible tool for automatic recognition of the most type of CAPTCHA’s (included so hard captchas like Google ReCaptcha v.1 and v.2, Solve Media, Facebook-captcha, etc.).
The application replaces such services as AntiGate (Anti-Captcha), RuCaptcha, DeCaptcher, etc., and at the same time it provides for higher recognition velocity (in 10 times) and is completely free of charge.
flexibility: the use of the scripted language Lua ensures the XEvil customization to the user’s tasks:
add support to emulation of any new recognition service
implement customization of interaction with any application
implement own module for logging and debugging of the results
PROPERTIES OF THE RECOGNIZED IMAGES
The recognized types: over 8400
Language: Roman type, Cyrillic, digits
Average precision of recognition – 60%-80%
Average recognition velocity – 1 s
for XRumer licenses owners
Average precision of recognition – 90%-100%
Average recognition velocity – 0.01…0.02 s
Google ReCaptcha v.1, v.2 and Solve Media recognition modules included
The recognition technology is backed by the most state of art neural networks. Xevil is using Delphi XE8, and Lua.
Anti-bot protection in the form of graphic captchas is going for good. It has been several years already, the captchas are recognized by various services and various application (free/non-free).
The captchas on the site can be customized continuously but this is dead end road. The captchas can push off the visitor of the site (who can be your potential customer). This type of anti-bot protection is outdated and will go for good in a 2-3 year with the introduction of more modern user authentication systems.
The state of art are provided with secure protection against Spam-bots with use of the following techniques:
Encrypted with JS-protection
It takes not more than 20-30 minutes (one day for the non-expert) to ensure site protection against robots without using such repulsive for users technologies as captchas.