.thumb.png.bb00626fe8ec8fe51758dbdc1421e958.png)
Що можна обрати замість
Роблять те саме — можна поставити замість.
Admin Log позволяет записывать все действия всех пользователей в административной части вашего интернет магазина. Благодаря присутствующим опциям вы можете настроить лог под свои нужды.
Модуль можно использовать не только для интернет магазинов с несколькими администраторами/редакторами, а и например, для контроля разработчиком за пользователем, для предотвращения “настроек” по не знанию, для отслеживания попыток взлома авторизации или попыток доступа в запрещенный раздел.
Опции модуля предельно обширны и позволяют максимально точно настроить запись (логирование) действий в админке вашего интернет магазина на Opencart. Вы можете:
включить или выключить запись вообще;
включить или выключить запись авторизаций (входов);
включить или выключить запись деавторизаций (выходов);
включить или выключить запись неверных авторизаций, позволяя таким образом отследить попытку взлома вашей администраторской панели с помощью подбора паролей (брут форса);
включить или выключить запись просмотров разделов (просто доступ);
включить или выключить запись редактирования разделов (обновление);
настроить запись всех действий, только разрешенных действий, или только попытки запрещенных действий.
Для редактирования самого лога предусмотрено удаление как отдельных записей, так и полная очистка лога. При выполнении этих действий в лог будут сделаны соответствующие записи, что позволит предотвратить безнаказанную очистку лога.
Установку можно произвести либо с заменой файла (system/library/user.php), либо с установленным vQmod. В файлах архива присутствует описание модуля, инструкция по установке, скриншоты работы, файлы для установки с vQmod и без.
С подробной информацией и остальными модулями вы можете ознакомиться на официальном сайте: http://nikita-sp.com.ua
Страница модуля: http://nikita-sp.com.ua/2015/01/module-admin-log-for-opencart.html..
Updated
Администраторский лог
Free
150
Не замінюють, але додають можливостей до цієї задачі або працюють у парі.
Інші рішення в тій самій області магазину.
Store Analytics Dashboard — GA4, Search Console and Google Ads in the OpenCart admin panel
Store Analytics Dashboard is a module for OpenCart and ocStore that brings store analytics, organic search metrics and advertising statistics together in a single widget on the main administrator dashboard.
View traffic, transactions, revenue, search queries, ad spend and conversions without constantly switching between Google services. CRON-based monitoring also delivers advertising status reports directly to Telegram.
Main features
A single widget for Google Analytics 4, Google Search Console and Google Ads Use GA4 on its own, combine it with Search Console, or connect Google Ads only GA4 traffic, transactions, revenue and key event metrics Statistics for channels, traffic sources and top revenue-generating products Search Console clicks, impressions, CTR, positions, queries and pages Ad spend, clicks, conversions, CPA, ROAS and campaign statuses CRON-based advertising monitoring with Telegram notifications Support for multiple Telegram recipients Interactive charts displaying several metric lines at once Tooltips for metrics, tables and chart points Preset reporting periods and custom date ranges Previous-period comparisons for key GA4 and Search Console metrics Report caching using native OpenCart functionality Detailed built-in service setup instructions No Composer installation or additional Google SDKs required Google Analytics 4: traffic and store performance
The widget displays key GA4 metrics for the selected period:
Users — active users reported by GA4 Sessions — site visits recorded by analytics Orders — transactions recorded in GA4 Revenue — total revenue reported by the GA4 totalRevenue metric Conversion — the transaction-to-session ratio calculated by the module Key events — events marked as important to the business in GA4 Key events per 100 sessions — a measure of how frequently target actions occur Average order value — GA4 revenue divided by the number of transactions These metrics show the current value, the previous-period value and the percentage change. For example, a selected 7-day period is compared with the preceding 7 days.
Important: the module uses GA4 data, not the OpenCart order database. Transaction counts and revenue can differ from internal store reports due to tracking behaviour, refunds, user consent and analytics blockers.
Channels, traffic sources and products
Top channels — sessions, transactions, key events and revenue by GA4 channel groups, including Organic Search, Paid Search, Direct and Referral Traffic sources — results by session source and medium, such as google / organic or google / cpc Top products — the five item names with the highest GA4 item revenue, showing units purchased and item revenue These sections help you compare traffic sources, identify channels that deliver results and see which products generate revenue.
Ecommerce events
A dedicated section displays counts of the main ecommerce events:
view_item — product view add_to_cart — add to cart begin_checkout — checkout started purchase — purchase Each event count is accompanied by a percentage relative to the first non-zero step. This compares independent event counts; it is not a sequential funnel tracking the same users through each step.
Google Search Console: store visibility in search
Connecting Search Console adds a Google organic search section to the widget:
Clicks — clicks to the site from search results Impressions — appearances of links to the site in search CTR — the ratio of clicks to impressions Average position — the average position of the site's highest result across impressions A trend chart and previous-period comparisons are available for the main metrics. Search query and page tables help assess demand, identify pages receiving organic traffic and find opportunities to improve content, titles and descriptions.
Search Console data covers ordinary Google search results and does not replace Google Ads advertising statistics.
Google Ads: ad spend and performance
Advertising statistics appear in the same widget alongside store analytics. No separate module or additional widget needs to be installed.
Cost — total advertising spend for the selected period Impressions — the number of times ads were shown Clicks — the number of clicks on ads CTR — clicks as a percentage of impressions CPC — average cost per click Conversions — target actions credited to advertising according to Google Ads settings CPA — average cost per conversion Conversion value — the total conversion values supplied to or configured in Google Ads ROAS — conversion value divided by advertising spend A campaign table displays statistics, statuses and reasons for limitations. A chart shows impressions, clicks and spend. Monetary values use the advertising account's currency, while reporting periods and check timestamps respect its timezone.
Conversions do not necessarily mean purchases only: they can include enquiries, phone calls and other configured goals. ROAS expresses the relationship between conversion value and spend; it is not net profit.
Advertising monitoring and Telegram notifications
The module can check advertising through CRON and send a report to Telegram. This helps you notice account issues, campaign configuration problems or missing expected activity.
Checks advertising account and campaign status Respects statuses, start and end dates, and ad schedules Detects missing impressions and spend within a configured window of expected activity Separate settings for the analysis window and reporting delay A report after every completed check, including when no problems are detected Brief impressions, clicks and spend statistics in the message Notifications about data retrieval errors and previously detected issues that are no longer observed Delivery to multiple recipients using comma-separated numeric chat IDs A test message button and the latest check result displayed in the widget Protection against simultaneous duplicate checks Set the CRON schedule on your hosting, for example every 2 hours. The module imposes no minimum launch interval. A ready-to-use HTTP command is provided, so PHP CLI is not required.
Important: this monitors advertising status and activity, not the account balance. Google Ads API does not expose an exact prepaid balance. An “OK” status means that none of the issues checked by the module were detected in the analysed period; it does not confirm that funds remain in the account.
Interactive charts
Charts can display several metrics at once. Use checkboxes to enable or disable individual lines:
GA4: sessions, transactions, key events and revenue Search Console: clicks, impressions, CTR and position Google Ads: impressions, clicks and spend Hovering over or clicking a point displays the metric name, date and value. Advertising spend includes the currency. When Ads spend and count metrics are displayed together, spend uses a separate right-hand axis.
Reporting periods and metric explanations
Available periods include today, yesterday, 7 days, 30 days, this month, last month and a custom date range. The period selector and refresh button are shared across the widget sections.
All 21 main metrics include explanatory tooltips describing what each metric means, how it is calculated and what to consider when assessing results. Tooltips are also available for table headings and supporting sections.
Detailed setup help
The module settings include a Help tab with step-by-step instructions:
Creating a Google Cloud service account and JSON key Connecting GA4 and finding the correct Property ID Connecting Search Console and specifying siteUrl Configuring Google Ads access and understanding the difference between Customer ID and MCC Creating a Telegram bot and obtaining chat IDs Setting up CRON, the activity window and reporting delay Troubleshooting common access, authorisation and message delivery errors Caching and widget settings
Reports use native OpenCart caching with a configurable lifetime in minutes. This reduces the number of Google API requests. The force-refresh button requests fresh report data, while CRON checks do not use the report cache.
Configure the widget width, display order, initial reporting period, default GA4 and Search Console chart lines, service connection settings and Telegram monitoring.
Connection and system requirements
OpenCart 3.x or ocStore 3.x Module code tested on PHP 7.1–8.5; compatibility with a particular PHP version also depends on the store core and other extensions PHP OpenSSL Outbound HTTPS requests through cURL or enabled HTTPS URL streams A Google Cloud project with the required service APIs enabled A service account JSON key with access to the relevant Google resources For Google Ads: approved API access for the Cloud project to production advertising accounts; Test access is insufficient For Telegram: a bot token and numeric recipient IDs For automatic monitoring: a CRON scheduler on the hosting server Authorisation runs on the server through a service account and does not require an interactive Google sign-in through a browser. One JSON key is used for the connected services, provided the appropriate access permissions have been granted.
Important considerations
The module reads previously collected data; it does not install a GA4 tag or ecommerce tracking on the site Purchase, revenue and product metrics require correctly configured ecommerce event tracking The module does not modify advertising campaigns, their budgets or the store's SEO settings Google service statistics may be delayed and revised after processing Monitoring analyses completed hours with the configured delay, not real-time activity For low-traffic campaigns, missing impressions over a short period do not necessarily indicate a payment problem Search Console requires the exact property URL or a value in the format sc-domain:example.com Installation
Upload the archive through Extensions → Installer. Open Extensions → Extensions and select the Dashboard extension type. Install Store Analytics Dashboard and open its settings. Add the service account JSON and configure the required services: GA4, Search Console and/or Google Ads. Grant the service account access within the relevant Google services. Configure the widget, enable the module and save the changes. If required, connect Telegram, check the test message and add the generated CRON command to your hosting scheduler.
Store Analytics Dashboard is a module for OpenCart and ocStore that brings store analytics, organic search metrics and advertising statistics together in a single widget on the main administrator dashboard.
View traffic, transactions, revenue, search queries, ad spend and conversions without constantly switching between Google services. CRON-based monitoring also delivers advertising status reports directly to Telegram.
Main features
A single widget for Google Analytics 4, Google Search Console and Google Ads Use GA4 on its own, combine it with Search Console, or connect Google Ads only GA4 traffic, transactions, revenue and key event metrics Statistics for channels, traffic sources and top revenue-generating products Search Console clicks, impressions, CTR, positions, queries and pages Ad spend, clicks, conversions, CPA, ROAS and campaign statuses CRON-based advertising monitoring with Telegram notifications Support for multiple Telegram recipients Interactive charts displaying several metric lines at once Tooltips for metrics, tables and chart points Preset reporting periods and custom date ranges Previous-period comparisons for key GA4 and Search Console metrics Report caching using native OpenCart functionality Detailed built-in service setup instructions No Composer installation or additional Google SDKs required Google Analytics 4: traffic and store performance
The widget displays key GA4 metrics for the selected period:
Users — active users reported by GA4 Sessions — site visits recorded by analytics Orders — transactions recorded in GA4 Revenue — total revenue reported by the GA4 totalRevenue metric Conversion — the transaction-to-session ratio calculated by the module Key events — events marked as important to the business in GA4 Key events per 100 sessions — a measure of how frequently target actions occur Average order value — GA4 revenue divided by the number of transactions These metrics show the current value, the previous-period value and the percentage change. For example, a selected 7-day period is compared with the preceding 7 days.
Important: the module uses GA4 data, not the OpenCart order database. Transaction counts and revenue can differ from internal store reports due to tracking behaviour, refunds, user consent and analytics blockers.
Channels, traffic sources and products
Top channels — sessions, transactions, key events and revenue by GA4 channel groups, including Organic Search, Paid Search, Direct and Referral Traffic sources — results by session source and medium, such as google / organic or google / cpc Top products — the five item names with the highest GA4 item revenue, showing units purchased and item revenue These sections help you compare traffic sources, identify channels that deliver results and see which products generate revenue.
Ecommerce events
A dedicated section displays counts of the main ecommerce events:
view_item — product view add_to_cart — add to cart begin_checkout — checkout started purchase — purchase Each event count is accompanied by a percentage relative to the first non-zero step. This compares independent event counts; it is not a sequential funnel tracking the same users through each step.
Google Search Console: store visibility in search
Connecting Search Console adds a Google organic search section to the widget:
Clicks — clicks to the site from search results Impressions — appearances of links to the site in search CTR — the ratio of clicks to impressions Average position — the average position of the site's highest result across impressions A trend chart and previous-period comparisons are available for the main metrics. Search query and page tables help assess demand, identify pages receiving organic traffic and find opportunities to improve content, titles and descriptions.
Search Console data covers ordinary Google search results and does not replace Google Ads advertising statistics.
Google Ads: ad spend and performance
Advertising statistics appear in the same widget alongside store analytics. No separate module or additional widget needs to be installed.
Cost — total advertising spend for the selected period Impressions — the number of times ads were shown Clicks — the number of clicks on ads CTR — clicks as a percentage of impressions CPC — average cost per click Conversions — target actions credited to advertising according to Google Ads settings CPA — average cost per conversion Conversion value — the total conversion values supplied to or configured in Google Ads ROAS — conversion value divided by advertising spend A campaign table displays statistics, statuses and reasons for limitations. A chart shows impressions, clicks and spend. Monetary values use the advertising account's currency, while reporting periods and check timestamps respect its timezone.
Conversions do not necessarily mean purchases only: they can include enquiries, phone calls and other configured goals. ROAS expresses the relationship between conversion value and spend; it is not net profit.
Advertising monitoring and Telegram notifications
The module can check advertising through CRON and send a report to Telegram. This helps you notice account issues, campaign configuration problems or missing expected activity.
Checks advertising account and campaign status Respects statuses, start and end dates, and ad schedules Detects missing impressions and spend within a configured window of expected activity Separate settings for the analysis window and reporting delay A report after every completed check, including when no problems are detected Brief impressions, clicks and spend statistics in the message Notifications about data retrieval errors and previously detected issues that are no longer observed Delivery to multiple recipients using comma-separated numeric chat IDs A test message button and the latest check result displayed in the widget Protection against simultaneous duplicate checks Set the CRON schedule on your hosting, for example every 2 hours. The module imposes no minimum launch interval. A ready-to-use HTTP command is provided, so PHP CLI is not required.
Important: this monitors advertising status and activity, not the account balance. Google Ads API does not expose an exact prepaid balance. An “OK” status means that none of the issues checked by the module were detected in the analysed period; it does not confirm that funds remain in the account.
Interactive charts
Charts can display several metrics at once. Use checkboxes to enable or disable individual lines:
GA4: sessions, transactions, key events and revenue Search Console: clicks, impressions, CTR and position Google Ads: impressions, clicks and spend Hovering over or clicking a point displays the metric name, date and value. Advertising spend includes the currency. When Ads spend and count metrics are displayed together, spend uses a separate right-hand axis.
Reporting periods and metric explanations
Available periods include today, yesterday, 7 days, 30 days, this month, last month and a custom date range. The period selector and refresh button are shared across the widget sections.
All 21 main metrics include explanatory tooltips describing what each metric means, how it is calculated and what to consider when assessing results. Tooltips are also available for table headings and supporting sections.
Detailed setup help
The module settings include a Help tab with step-by-step instructions:
Creating a Google Cloud service account and JSON key Connecting GA4 and finding the correct Property ID Connecting Search Console and specifying siteUrl Configuring Google Ads access and understanding the difference between Customer ID and MCC Creating a Telegram bot and obtaining chat IDs Setting up CRON, the activity window and reporting delay Troubleshooting common access, authorisation and message delivery errors Caching and widget settings
Reports use native OpenCart caching with a configurable lifetime in minutes. This reduces the number of Google API requests. The force-refresh button requests fresh report data, while CRON checks do not use the report cache.
Configure the widget width, display order, initial reporting period, default GA4 and Search Console chart lines, service connection settings and Telegram monitoring.
Connection and system requirements
OpenCart 3.x or ocStore 3.x Module code tested on PHP 7.1–8.5; compatibility with a particular PHP version also depends on the store core and other extensions PHP OpenSSL Outbound HTTPS requests through cURL or enabled HTTPS URL streams A Google Cloud project with the required service APIs enabled A service account JSON key with access to the relevant Google resources For Google Ads: approved API access for the Cloud project to production advertising accounts; Test access is insufficient For Telegram: a bot token and numeric recipient IDs For automatic monitoring: a CRON scheduler on the hosting server Authorisation runs on the server through a service account and does not require an interactive Google sign-in through a browser. One JSON key is used for the connected services, provided the appropriate access permissions have been granted.
Important considerations
The module reads previously collected data; it does not install a GA4 tag or ecommerce tracking on the site Purchase, revenue and product metrics require correctly configured ecommerce event tracking The module does not modify advertising campaigns, their budgets or the store's SEO settings Google service statistics may be delayed and revised after processing Monitoring analyses completed hours with the configured delay, not real-time activity For low-traffic campaigns, missing impressions over a short period do not necessarily indicate a payment problem Search Console requires the exact property URL or a value in the format sc-domain:example.com Installation
Upload the archive through Extensions → Installer. Open Extensions → Extensions and select the Dashboard extension type. Install Store Analytics Dashboard and open its settings. Add the service account JSON and configure the required services: GA4, Search Console and/or Google Ads. Grant the service account access within the relevant Google services. Configure the widget, enable the module and save the changes. If required, connect Telegram, check the test message and add the generated CRON command to your hosting scheduler.
Updated
Store Analytics Dashboard: GA4 + Search Console + ADs
Free
68
Оскільки у власників магазинів часто виникають проблеми з розумінням того, що відбувається на їх сайті, розміром кешу та іншими нюансами, я вирішив створити корисний віджет для головної сторінки адмін-панелі, який допоможе очищати, визначати розмір і відстежувати розташування в папках журналів, системного кешу та кешу зображень.
Updated
Домовий - Віджет для моніторингу стану магазину
Free
726
Дебаг панель для мониторинга времени выполнения методов контроллера и запросов к базе данных(с указанием метода модели и пути к файлу)
Перечень функционала
Вывод времени выполнения контроллеров
Вывод времени выполнения запросов в базу данных
Вывод суперглобальных переменных(get, post, server, cookie)
DEMO YOUTUBE..
Updated
Debug Panel
Free
257
У вас большой файл ошибок, и вы не можете его посмотреть?
Этот мод позволяет просматривать 100 последних строк ошибок (Больше и не надо) и фиксит вывод html кода в лог (ситуации разные бывают)
Мод также задевает и просмотр лога модификаторов - при большом логе - не всегда можно зайти в модификаторы..
Submitted
Tail error.log
Free
170
AskMyStore is an AI chat right inside the OpenCart admin panel. Ask about your store in plain words: "Which products sold best this month?", "Which products have no photo?", "Are there any errors in the log today?". The assistant finds the data in the store database and files on its own and answers briefly and to the point, with tables and links to products and orders.
Updated
AskMyStore - AI assistant for admin
Free
0
Компонент JOOMIDO ANTIHACKER входит в пакет инструментов JOOMIDO TOOLKIT, и предназначен для отслеживания и блокировки хакерских атак.
Сама идея взята от джумловского компонента OSE ANTIHACKER, который больше не поддерживается разработчиком. Ранее проверку работы компонента защиты проверял на OPENCART, правда с использованием джумловских библиотек, но позже занялся разработкой системы с использованим стандартных методов opencart, а также реализацией админки с jQuery.
О функционале
1) защита админки путем использования секретной ссылки типа domen/admin?_key=_var
При включенном режиме попытки входа по стандартной ссылке блокируются и происходит редирект на главную.
2) блокировка I уровня, когда потенциально опасный код вставлен в ссылку, типа domen? chr= (сигнатуры таких кодов хранятся в БД).
3) блокировка II уровня, когда запрос передается методом get или post. Для проверки потенциальной опасности используется последняя версия библиотеки HTMLPurifier
Все атаки заносятся в лог, а также отпавляется сообщение на почту (рекомендуется использовать SMTP, потому как многие сервера болше не будут поддерживать метод MAIL). В будушем планирую добавить отправку в Telegram.
В последующих релизах буду учитывать пожелания пользователей, а также добавлю функционал, типа сканирование загружаеміх файлов антивирусом (сейчас занимаюсь разработкой системы ANTIVIRUS). Еще планирую добавить проверку и блокировку заходов с токсичных доменов, а также улучшить проверку на основе результатов тестовых атак IronWasp и других инструментов.
Пока только для версии 2.3. В ближайшее время выложу доработки длч 2 и 3 версий.
Установка Демо-версии
1) Загружаем языковой файл меню language_menu.ocmod.zip
2) Инсталлируем модификатор меню toolkit_menu_23.ocmod.xml
В админ-панели появится новая вкладка. Так как еще не загужены модули ToolKit, эта вкладка не открывает подпункты.
3) Загружаем архив библиотек system.ocmod.zip
4) Загружаем архив manual.ocmod.zip
5) Загружаем архив системы администрирования admin.ocmod.zip
6) На вкладке Joomido ToolKit появится подпункт Antihacker. Настройте разрешения админа, и проведите установку.
Тестовые данные (в файле example.sql) можно загузить при помощи инструмента восстановления бэкап.
В демо режиме имеется возможность настройки секретной ссылки для входа в админку. Для того инсталлируем модификатор toolkit_admin_antiacker_23.ocmod.xml
В полной версии доступно тестирование / иммитация атак из админки.
Установка Полной версии
1) Загружаем языковой файл меню language_menu.ocmod.zip
2) Инсталлируем модификатор меню toolkit_menu_23.ocmod.xml
В админ-панели появится новая вкладка. Так как еще не загужены модули ToolKit, эта вкладка не открывает подпункты.
3) Загружаем архив библиотек system.ocmod.zip
4) Загружаем архив manual.ocmod.zip
5) Загружаем архив системы администрирования admin.ocmod.zip
6) На вкладке Joomido ToolKit появится подпункт Antihacker. Настройте разрешения админа, и проведите установку.
7) Загружаем архив catalog.ocmod.zip
8) Инсталлируем модификатор toolkit_admin_antiacker_23.ocmod.xml
9) Инсталлируем модификатор toolkit_catalog_antiacker_23.ocmod.xml
Примечание. Подключить модуль также можно без инсталляции модификаторов toolkit_admin_antiacker_23.ocmod.xml и toolkit_catalog_antiacker_23.ocmod.xml
Для этого необходимо:
- открыть на сервере файл system/framework.php
- найти строки
// Front Controller
$controller = new Front($registry);
- добавить перед ними код
$loader->controller('tool/antihacker');
Важно! В демо-режиме такой вариант подключения (через framework.php) не подходит, поэтому для его применения необходимо создать файл catalog/controller/tool/antihacker.php с нижеприведенным кодом
class ControllerToolAntihacker extends Controller {
public function index()
{}
}..
Submitted
Компонент Joomido Antihacker
Free
10
Работает на всех версиях opencart.
Сделан с целью отражения примитивных брутфорс атак
Для версий 2.х использовать ocmod
Для версих 1.5.х использовать vqmod файл
Изменяет url страницы авторизации в админку по дефолту на domain.com/admin/?secretkey=mysecretkey
Параметр secretkey можно легко заменить на свой в этом учаcтке кода. Выделяю жирным, что стоит менять.
$mysecretkey='mysecretkey';..
Updated
Изменяет url админки
Free
755
Простой Profiler для отладки магазинов.
Добавляет после футера лог с полезной информацией.
Отображает время загрузки страницы и общее количество запросов.
А также подробную статистику, время выполнения и контроллер по каждому sql - запросу.
Очень полезно для выявления узких мест.
Для Opencart 1.5.6.x - отдельная версия.
ДАННОЕ ПРОГРАММНОЕ ОБЕСПЕЧЕНИЕ ПРЕДОСТАВЛЯЕТСЯ «КАК ЕСТЬ», БЕЗ КАКИХ-ЛИБО ГАРАНТИЙ, ЯВНО ВЫРАЖЕННЫХ ИЛИ ПОДРАЗУМЕВАЕМЫХ, ВКЛЮЧАЯ, НО НЕ ОГРАНИЧИВАЯСЬ ГАРАНТИЯМИ ТОВАРНОЙ ПРИГОДНОСТИ, СООТВЕТСТВИЯ ПО ЕГО КОНКРЕТНОМУ НАЗНАЧЕНИЮ И ОТСУТСТВИЯ НАРУШЕНИЙ ПРАВ. НИ В КАКОМ СЛУЧАЕ АВТОР НЕ НЕСЕТ ОТВЕТСТВЕННОСТИ ПО ПРЕТЕНЗИЯМ О ВОЗМЕЩЕНИИ УЩЕРБА, УБЫТКОВ ИЛИ ДРУГИХ ТРЕБОВАНИЙ ПО ДЕЙСТВУЮЩИМ КОНТРАКТАМ, ИЛИ ИНОМУ, ВОЗНИКШИМ ИЗ, ИМЕЮЩИМ ПРИЧИНОЙ ИЛИ СВЯЗАННЫМ С ПРОГРАММНЫМ ОБЕСПЕЧЕНИЕМ ИЛИ ИСПОЛЬЗОВАНИЕМ ПРОГРАММНОГО ОБЕСПЕЧЕНИЯ ИЛИ ИНЫМИ ДЕЙСТВИЯМИ С ЭТИМ ДОПОЛНЕНИЕМ...
Updated
Opencart Profiler Vqmod
Free
1401
«Список всех действий в админ панели» знято з продажу
Ми підібрали схожі модулі інших розробників — їх можна придбати вже зараз.
Інші варіанти
1.0.0
Ioncube Loader: Ні
Withdrawn from sale
The marketplace administration has withdrawn this file from sale
OpenCart3.0
ocStore3.0
License type На один домен
Activation method Без активации
Ioncube LoaderНі
Get request to server of developerНі
Downloads5
Submitted01/26/2022
Updated04/23/2022
File Size21.67 kB
-
Recently Browsing 0 members
- No registered users viewing this page.