The best free and open-source ecommerce platform

Versioning

The version is broken down into 4 points e.g 1.2.3.4 We use MAJOR.MINOR.FEATURE.PATCH to describe the version numbers.

A MAJOR is very rare, it would only be considered if the source was effectively re-written or a clean break was desired for other reasons. This increment would likely break most 3rd party modules.

A MINOR is when there are significant changes that affect core structures. This increment would likely break some 3rd party modules.

A FEATURE version is when new extensions or features are added (such as a payment gateway, shipping module etc). Updating a feature version is at a low risk of breaking 3rd party modules.

A PATCH version is when a fix is added, it should be considered safe to update patch versions e.g 1.2.3.4 to 1.2.3.5

Описание работы и настроек

Первое что следует сделать, это на сайте 4dealer.ru в настройках API в профиле, сгенерировать ключ API и вставить его у себя в установленном модуле в разделе «Общие настройки»

Далее синхронизировать Ваш каталог с каталогом дистрибьютора. Это весьма простое действие: на странице «Сопоставление категорий» с одной стороны кликните на категорию своего каталога, а с другой стороны — на категорию каталога дистрибьютора. Затем нажмите кнопку «Установить». Всё! Теперь товары будут загружаться в нужные Вам категории.

Если у Вас нет своего каталога, то довольно легко сформировать точную копию каталога дистрибьютора, при этом все привязки будут выполнены автоматически.

В разделе «Наценки/Настройки» параметров дилера, Вы можете самостоятельно устанавливать необходимые наценки на товары в процентах. Эти наценки можно делать как на все товары, так и на их определенные категории.

Далее вам необходимо настроить задание по расписание в планировщике cron или его аналоге.

Releases

OpenCart will announce to developers 1 week prior to public release of FEATURE versions, this is to allow for testing of their own modules for compatibility. For bigger releases (ones that contain many core changes, features and fixes) an extended period will be considered following an announced release candidate (RC). Patch versions (which are considered safe to update with) may have a significantly reduced developer release period.

The master branch will always contain an «_rc» postfix of the next intended version. The next «_rc» version may change at any time.

Developer release source code will not change once tagged.

If a bug is found in an announced developer release that is significant (such as a major feature is broken) then the release will be pulled. A patch version will be issued to replace it, depending on the severity of the patch an extended testing period may be announced. If the developer release version was never made public then the preceding patch version tag will be removed.

History

05.02.2019

Added: Fastor for OpenCart 3.x udpated with TWIG files
Added: New default skin for OC 3.x

04.08.2018
2.2

Fixed: MegaFilter Pro styling

20.06.2018
2.1

Fixed: Link in Fastor Theme Options
Added: Checkboxes for all forms and newsletter fields

26.01.2018
2.0

Fixed: Twitter widget ID
Fixed: Cookie box "don't show again" checkbox removed
Fixed: Additional Pop-up in newsletter removed
Fixed: Affiliate tracking on affiliate page
Fixed: Brand redirection in QuicView
Fixed: Error 3rd level of categories on category page
Fixed: Structured data SEO for product page
Fixed: Collapse vertical megamenu on mobile devices
Fixed: Text_message error in contact form
Fixed: Facebook language
Fixed: Load fastor modules in advanced grid
Fixed: Autocomplete search in Search bar in MegaMenu
Fixed: Problem with empty column on category page
Fixed: Required fields on advanced grid
Fixed: Image uploader for blog post
Fixed: Increase NEW BADGE limit
Fixed: Increase autocomplete megamenu results in admin panel
Fixed: Product tabs - remove content problem
Fixed: Multilanguage links in MegaMenu and Advanced Grid modules
Fixed: Undefined variable error in header in firefox browser on OpenCart 3.0
Fixed: Default opencart menu in OpenCart 3.0
Added: QuickCheckout for OpenCart 3.0.2
Fixed: Breadcrumb title bug fo OpenCart 3
Fixed: Header error for OpenCart 3
Added: Compability with OpenCart 3.0.2.0 (quickcheckout will be update in next few days)
Added: Quick One-page Checkout
Added: Vertical MegaMenu for product page
Added: Collapse MegaMenu on mobile
Fixed: Fashion 7 demo on lower screens
Fixed: Category issue in OpenCart 2.2
Fixed: Product_tabs issue in OpenCart 2.3
Fixed: Small bugs and improvements
Fixed: Bug on category page in OC 2.1
Fixed: PHP Parse error: syntax error, unexpected ...header.tpl on line 250 in OC 2.1
Fixed: Errors on Account page in OpenCart 2.1
Added: 7 new skins!
Added: Fixed menu
Added: Logout button for all headers
Added: More levels of subactegory in default category module
Added: Default category module collapse on mobile
Added: Countdown translation in admin panel
Added: Information in admin panel which demo content is replaced
Improved: Google Rich Snippets
Improved: Awesome Icons update
Improved: Autocomplete list increased to 10 in admin panel
Improved: Whitespaces on mobile
Fixed: Pagination on history page
Fixed: Problem with cookie bar
Fixed: Google captcha
Fixed: Affiliate tracking on affiliate page
Fixed: Contact form is closed after message sent
Fixed: z-index issue in MegaMenu module
Fixed: Button name in MegaMenu module
Fixed: Bug with summernote editor
Fixed: Product tabs bug in OC 2.3
Fixed: MegaFilter Pro bug in OC 2.3
Fixed: Multistore permission but in OC 2.3
Fixed: Multilanguage Revolution Slider bug for OpenCart 2.3
Fixed: Issue with blog post removing for OpenCart 2.3
Fixed: Small bug with MegaMenu for OpenCart 2.3
Added: Compability with OpenCart 2.3 
Fixed: Registry error in OpenCart 2.2
Fixed: Log out bug with Live Editor in OpenCart 2.2
Fixed: "Registry" bug in Advanced Grid and Filter product
Fixed: Small bug in compability with OpenCart 2.2.0.0
Added: Compability with OpenCart 2.2.0.0>
Improved: Data-Vocabulary replaced with new modern Schema
Fixed: Camera Slider bug after rtl update
Added: 3 new skins
Added: RTL Lanugages compability
Fixed: Validation errors on category page
Fixed: Small issue with product block module
Fixed: Title on FAQ page
Fixed: Custom_class error in MegaaMenu
Fixed: Revolution slider Update
Fixed: T_VARIABLES error in fastor.php file

Theme released

19.11.2015

API

For using OpenCart API you should enable it previously, via admin part of you’re site.
Go to System->Users->API and you’ll see a predefined user named «Default».
Edit it — and the are no API-key so generate it, by pressing the button and set «Status» to enable.
Next, add you’r IP to list of permitted for API access on another tab.

API is avaliable via URL like

where route is using choose appropriate controller.

NOTES:

  • API users always have customer_id as ‘0’. And have the own api_id.
  • I’ll us python-requests library for this examples, but the main idea is describing parameters so console curl will be fine enough.
  • And in descriptions I’ll assume what we have «oc_» prefix on DB tables.

Firstly, you can and definitly should get token for you session — you’ll get cookie file and OpenCart server will identify activity by this way.

If everything was done right, you’ll get json-response with api_token for you’r session.
Check site admin API page, edit API user and open «Sessions» tab — you can see established session.

Now, what you can do with OpenCart API?

Login

api/login

Establishing session for API user by key
PARAMS:
DATA:
username:username from oc_api
key:key from oc_api
EXAMPLE:

Currency

DESCRIPTION:change session currency
PARAMS:
api_token
DATA:
currency:code from table oc_currency
EXAMPLE:

Cart

api/cart/add

DESCRIPTION:adding product to cart
PARAMS:
api_token
DATA:
product_id:product_id from table oc_cart
quantity:quantity from table oc_cart
option:option array from table oc_cart
EXAMPLE:

api/cart/edit

DESCRIPTION:edit product quantity in cart
PARAMS:
api_token
DATA:
key:cart_id from table oc_cart
quantity:quantity from table oc_cart
EXAMPLE:

DESCRIPTION:cart content
PARAMS:
api_token
DATA:
EXAMPLE:

DESCRIPTION:apply existing coupon
PARAMS:
api_token
DATA:
coupon:code from oc_coupon;
EXAMPLE:

api/shipping/address —

DESCRIPTIONIPTION:set shipping address for current session
PARAMS:
api_token
DATA:
firstname
lastname
address_1
city
country_id
zone_id
EXAMPLE:

DESCRIPTION:set shipping method for current session
PARAMS:
api_token
DATA:
shipping_method
EXAMPLE:

Reward

Order

api/order/add

DESCRIPTION:new order by cart content and payment/delivery information has beeen set by current session
PARAMS:
api_token
DATA:
EXAMPLE:

Payment

api/payment/address

DESCRIPTION:set payment address for this session
PARAMS:
api_token
DATA:
firstname
lastname
address_1
city
country_id
zone_id
EXAMPLE:

api/payment/method

DESCRIPTION:setting payment method of avaliable in api/payment/methods
PARAMS:
api_token
DATA:
payment_method
EXAMPLE:

Важно, если не выполнить корректно путь 7 импорт работать не будет!!!

После того, как выполнены привязки, установлены наценки и настроена задача по расписанию в планировщике CRON, зайдите на страницу задач, установите «Полное обновление» и нажмите кнопку «Обновить».

После этого начнется синхронизация. Если Вы желаете просто обновить ранее выгруженные товары, то установите «Быстрое обновление». Модуль 4Dealer предоставляет возможность выставить время синхронизации, для этого дополнительно добавьте запуск в планировщике задач.

Модуль 4Dealer для OpenCart позволит синхронизировать Ваш магазин с любым дистрибьютором из нашей системы, такими, например, как: 220 Вольт, EASA, ELKO, IN|LINE , Marvel (Марвел), MERLION (Мерлион), Mics (Микс), NETLAB (Нетлаб), OCS Distribution (ОСиЭс), Staten (Стэйтен), Treolan (Треолан), USN Computers (ЮСН), А1 ТИС (A1 Tis), Комус-ОПТ (Komus), НИКС (NIX), ОнЛайн Трейд (OnLineTrade), Ресурс Медиа (Resurs Media), Самсон (Samson) и многими другими.

Команда 4Dealer всегда готова проконсультировать Вас по всем вопросам, связанным с использованием наших программных решений и желает успеха и процветания Вашему бизнесу.

Reporting a bug

Read the instructions below before you create a bug report.

  1. Check all open and closed issues on the GitHub bug tracker.
  2. If your bug is related to the OpenCart core code then please create a bug report on GitHub.
  3. READ the changelog for the master branch
  4. Make sure that your bug/issue is not related to your hosting environment.

Important!

  • If your bug report is not related to the core code (such as a 3rd party module or your server configuration) then the issue will be closed without a reason. You must contact the extension developer, use the forum or find a commercial partner to resolve a 3rd party code issue.
  • If you would like to report a serious security bug please PM an OpenCart moderator/administrator on the forum. Please do not report concept/ideas/unproven security flaws — all security reports are taken seriously but you must include the EXACT details steps to reproduce it. Please DO NOT post security flaws in a public location.
Ссылка на основную публикацию