Repairer – Repair Shop Management System 2.3 Download

DOWNLOAD/LIVE PREVIEW

Repairer - Repair Shop Management System 2.3 Download

Repairer – Restore/Workshop Administration System is rigorously developed for simple administration of any sort of repairshop/workshop. It’s truly an revolutionary, easy and highly effective administration device, designed and developed for you. It’s simply your trusty worker. It’s an internet primarily based system the place you’ll be able to handle reparations, purchasers, stock, purchases and many others.

Demo

URL: demo.otsglobal.org/rms
Electronic mail: admin@admin.com
Password: password

Fast Set up Information

Obtain .zip package deal
Add it to your server
Extract the package deal
Run the uploaded url through browser (EXAMPLE.COM/RMS/INSTALL). Right here you need to present the settings for RMS:

  • Hostname : database host identify / IP
  • Database Title : create a mysql database for RMS in your host and write that identify right here
  • Database username : username of the created database (if relevant)
  • Database password : password of the created database

Backend – Admin:

  1. Dashboard (graphical report)
  2. Common settings (system customization)
  3. Consumer administration
  4. Reparation administration
  5. Stock Administration
  6. Purchases Managment
  7. Taxes, Fashions, Classes and many others.
  8. Graphical Experiences ( Inventory & Finance )

Frontend:

  • Reparation Standing
  • Login

Notification/ Alert System

Notify purchasers with their reparation standing through E-Mail or SMS

Documentation

Need to know extra about Repairer? Please learn our Documentation

How you can Replace

Change Log 3.Zero to three.5

  1. Obtain v3.5
  2. Take Database & Recordsdata Backup.
  3. Extract 3.5 information instead of 3.0
  4. Copy software/config/database.php from 3.Zero backup to three.5
  5. Copy software/config/config.php from 3.Zero backup to three.5
  6. Copy property/uploads from 3.Zero to three.5
  7. Run the Replace35.sql in PhpMyAdmin. Obtain right here: otsglobal.org/cc_updates/rms/Replace35.sql

Change Log 2.2 to three.0

- Add Picture in Stock Desk
- Repair Barcode Downside in Print Barcodes Stock
- Replace Restore Statuses (Accomplished checkbox factor)
- Repair any calculation concern for repairs with tax
- Settings -> order & reparation -> classes: can add class however disappears after saving
- Purchases -> download pdf : rounds up numbers, 2 decimals can be wanted
- modifying purchases: When it was arrange as ordered and I'm going again modifying to mark it as arrived or making an attempt to do any modifications to it its not doable
- POS Open/Shut Drawer completely different cash in settings
- Add SMSInfo.API android Gateway
- Add Authentic Nexmo API
- Add Sample/Pin Lock System
- Guarantee System
- Doc Signal
- Calendar Widget present repairs too
- Add Reparation ITEMS change amount and value
- Add Reparation Funds
- Add Gross sales Funds.
- Take away Advance Scene
- Add Paid System
- Import/Export Techniques Prospects
- Forgot password e-mail system
- Exercise Log
- Add Desk State Save primarily based on customers
- customized sms api perform. 
- Permission Lang
- And the tax is just not showing in POS bill. 
- Change standing immediately from desk
- And A lot Extra
  1. Obtain v3.0
  2. Take Database & Recordsdata Backup.
  3. Extract 3.Zero information instead of 2.2
  4. Copy software/config/database.php from 2.2 backup to three.0
  5. Copy software/config/config.php from 2.2 backup to three.0
  6. Copy property/uploads from 2.2 to three.0
  7. Create a folder named “indicators” in property/uploads
  8. Run the Replace30.sql in PhpMyAdmin. Obtain right here: otsglobal.org/cc_updates/rms/Replace30.sql

Change Log 2.2 to 2.3

- Fastened some bugs
  1. Obtain v2.3
  2. Take Database & Recordsdata Backup.
  3. Extract 2.Three information instead of 2.2
  4. Copy software/config/database.php from 2.2 backup to 2.3
  5. Copy software/config/config.php from 2.2 backup to 2.3
  6. Copy property/uploads from 2.2 to 2.3
  7. open software/config/config.php and change
    $config['composer_autoload'] = TRUE;

    with

    $config['composer_autoload'] = FCPATH.'vendor/autoload.php';

    on line 140

  8. Run the next SQL in PhpMyAdmin:


UPDATE `settings` SET `model` = '2.3' WHERE `settings`.`id` = 1;

Change Log 2.1 to 2.2

- Added composer
- Changed phpexcel with phpSpreadsheet
- Added Reparation in Consumer view modal
- Added Hyperlinks on Consumer Title And Reparation code. 
- Take away Tax Charge Required Attribute
- Add Assigned To discipline
- Added Producer discipline
- Added Three Experiences And Bill Templates
- Add Barcode Generator for reparations
- Added completely different views for accomplished & pending repairs
- Add autocompletion to defect & class
- Add anticipated shut date
- Add Imei to autofill restore particulars
- Add numeric codes for repairs
- And A lot Extra
  1. Obtain v2.2
  2. Take Database & Recordsdata Backup.
  3. Extract 2.2 information instead of 2.1
  4. Copy software/config/database.php from 2.1 backup to 2.2
  5. Copy software/config/config.php from 2.1 backup to 2.2
  6. Copy property/uploads from 2.1 to 2.2
  7. Create a folder named “backgrounds” in property/uploads
  8. Run the Replace.sql in PhpMyAdmin. Obtain right here: otsglobal.org/cc_updates/rms/Replace 2.2.sql

Change Log 2.Zero to 2.1

- Repair jQuery in templates
- Tax on Whole + Service Cost in Restore
- Add Theme Module
- And Bug Fixes
  1. Obtain v2.1
  2. Take Database & Recordsdata Backup.
  3. Extract 2.1 information instead of 2.0
  4. Copy software/config/database.php from 2.Zero backup to 2.1
  5. Copy software/config/config.php from 2.Zero backup to 2.1
  6. Copy property/uploads from 2.Zero to 2.1
  7. open index.php change $view_folder = ''; change it to $view_folder = 'themes';
  8. Run SQLs in PhpMyAdmin


ALTER TABLE `settings` ADD `theme` VARCHAR(100) NOT NULL AFTER `use_topbar`;
UPDATE `settings` SET `theme` = 'adminlte';
UPDATE `settings` SET `model` = ‘2.1’;

Change Log 1.71 to 2.0

- Add Darkish Theme
- Add Picture for shopper
- ADD Google GEOLOCATE
- Add Google RECAPTCHA
- MPDF PDF CREATION FIX for PHP 7
- Add Actions Button apart from easy buttons
- Reparation Log
- Add Calendar 
- Add Diagnostics Subject
- Add Excel, PDF Export And Column VISIBILITY
- Add Brand in Bill, Report
- CSS FIXES and Physique Font - Look Tab — like JR
- Add Search Reparation in Aspect Menu
- CHANGE SMS/EMAIL SEND BTN Location 
- Add Gallery for Restore - Like JR
- Add Assigned To discipline in repairer
- Add Date Adder for feedback
- ADD SETTINGS LINKS IN TOP NAVIGATION - Like JR
- ADD QUICK ADD ETC in prime nav
- Repair Barcode - print Label
  1. Obtain v2.0
  2. Take Database & Recordsdata Backup.
  3. Extract 2.Zero information instead of 1.71
  4. Copy software/config/database.php from 1.71 backup to 2.0
  5. Copy software/config/config.php from 1.71 backup to 2.0
  6. now open software/config/config.php and alter line 140 from
  7.  
      $config['composer_autoload'] = FALSE;
      

    TO

     
      $config['composer_autoload'] = TRUE;
      
  8. Copy property/uploads from 1.71 to 2.0
  9. Create folder named “pictures” in /property/uploads
  10. Run the Replace.sql in PhpMyAdmin. Obtain right here: otsglobal.org/cc_updates/rms/Replace 2.0.sql

Change Log 1.7 to 1.71

— Added Translations
  1. Obtain v1.71
  2. Exchange downloaded 1.71 software/languages folder in your server rms_folder (1.7)
  3. Exchange downloaded 1.71 software/views/_base/foot.php in your server rms_folder (1.7)

Change Log 1.6 to 1.71

— Added Stock Pictures
  1. Obtain v1.7
  2. Backup your present rms_application information (v1.6) and export present database as sql (as pre-caution).
  3. Delete v1.6 rms_application information and extract v1.7 as substitute
  4. Restore rms_application/property/uploads/logos & rms_application/property/uploads/members folder from v1.6
  5. Restore rms_application/software/config/config.php, rms_application/software/config/database.php information from v1.6
  6. Go to phpMyAdmin , choose your database and run the next SQL:


ALTER TABLE `stock` ADD `picture` TEXT NOT NULL AFTER `isDeleted`;
UPDATE `stock` SET `picture`="no_image.png" WHERE 1;
UPDATE `settings` SET `model` = '1.7' WHERE `settings`.`id` = 1;

Change Log 1.6

— Bugs Eliminated
— Fastened Translations
— House Web page Permissions
— Added Postal Code Subject for purchasers
— Added Parsley.JS Kind Validation
— Up to date Codeigniter and AdminLTE
  1. Obtain v1.6
  2. Backup your present rms_application information (v1.5) and export present database as sql (as pre-caution).
  3. Delete v1.5 rms_application information and extract v1.6 as substitute
  4. Restore rms_application/property/uploads/logos & rms_application/property/uploads/members folder from v1.5
  5. Restore rms_application/software/config/config.php, rms_application/software/config/database.php information from v1.5
  6. Go to phpMyAdmin , choose your database and run the next SQL:


ALTER TABLE `permissions` ADD `dashboard-qemail` BOOLEAN NOT NULL AFTER `categories-delete`, ADD `dashboard-qsms` BOOLEAN NOT NULL AFTER `dashboard-qemail`;
ALTER TABLE `purchasers` ADD `postal_code` VARCHAR(50) NOT NULL AFTER `metropolis`;
UPDATE `settings` SET `model` = '1.60' WHERE `settings`.`id` = 1;

Replace – v1.Three to v1.4

Change Log 1.40

— Added USER Permissions 
— Added e-mail notifications  - add for each standing;
— Added discipline - by from provider - Stock product
— Up to date SMS Library
— mounted dataTables search
— Added classes
And A lot Extra. 
  1. Obtain v1.4
  2. Backup your present rms_application information (v1.3) and export present database as sql (as pre-caution).
  3. Delete v1.Three rms_application information and extract v1.Four as substitute
  4. Restore rms_application/property/uploads/logos & rms_application/property/uploads/members folder from v1.3
  5. Restore rms_application/software/config/config.php, rms_application/software/config/database.php information from v1.3
  6. Go to phpMyAdmin , choose your database and run the next SQL:


CREATE TABLE `classes` (
`id` int(11) NOT NULL,
`code` varchar(55) NOT NULL,
`identify` varchar(55) NOT NULL,
`picture` varchar(55) DEFAULT NULL,
`parent_id` int(11) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

ALTER TABLE `stock` DROP `class`;
ALTER TABLE `stock` ADD `category_id` INT NOT NULL AFTER `model_name`, ADD `class` VARCHAR(250) NOT NULL AFTER `category_id`, ADD `subcategory_id` INT NULL AFTER `class`, ADD `subcategory` VARCHAR(250) NULL AFTER `subcategory_id`;
ALTER TABLE `stock` ADD `provider` VARCHAR(250) NOT NULL AFTER `subcategory`, ADD `supplier_id` INT NOT NULL AFTER `provider`;

CREATE TABLE `permissions` (
`id` int(11) NOT NULL,
`group_id` int(11) NOT NULL,
`repair-index` tinyint(1) NOT NULL,
`repair-add` tinyint(1) NOT NULL,
`repair-edit` tinyint(1) NOT NULL,
`repair-delete` tinyint(1) NOT NULL,
`repair-view_repair` tinyint(1) NOT NULL,
`customers-delete` tinyint(1) NOT NULL,
`customers-view_customer` tinyint(1) NOT NULL,
`customers-index` tinyint(1) NOT NULL,
`customers-add` tinyint(1) NOT NULL,
`customers-edit` tinyint(1) NOT NULL,
`inventory-index` tinyint(1) NOT NULL,
`inventory-add` tinyint(1) NOT NULL,
`inventory-edit` tinyint(1) NOT NULL,
`inventory-delete` tinyint(1) NOT NULL,
`inventory-print_barcodes` tinyint(1) NOT NULL,
`inventory-product_actions` tinyint(1) NOT NULL,
`inventory-suppliers` tinyint(1) NOT NULL,
`inventory-add_supplier` tinyint(1) NOT NULL,
`inventory-edit_supplier` tinyint(1) NOT NULL,
`inventory-delete_supplier` tinyint(1) NOT NULL,
`inventory-models` tinyint(1) NOT NULL,
`inventory-add_model` tinyint(1) NOT NULL,
`inventory-edit_model` tinyint(1) NOT NULL,
`inventory-delete_model` tinyint(1) NOT NULL,
`purchases-index` tinyint(1) NOT NULL,
`purchases-add` tinyint(1) NOT NULL,
`purchases-edit` tinyint(1) NOT NULL,
`purchases-delete` tinyint(1) NOT NULL,
`auth-index` tinyint(1) NOT NULL,
`auth-create_user` tinyint(1) NOT NULL,
`auth-edit_user` tinyint(1) NOT NULL,
`auth-delete_user` tinyint(1) NOT NULL,
`reports-stock` tinyint(1) NOT NULL,
`reports-finance` tinyint(1) NOT NULL,
`reports-quantity_alerts` tinyint(1) NOT NULL,
`auth-user_groups` tinyint(1) NOT NULL,
`auth-delete_group` tinyint(1) NOT NULL,
`auth-create_group` tinyint(1) NOT NULL,
`auth-edit_group` tinyint(1) NOT NULL,
`auth-permissions` tinyint(1) NOT NULL,
`utilities-index` tinyint(1) NOT NULL,
`utilities-backup_db` tinyint(1) NOT NULL,
`utilities-restore_db` tinyint(1) NOT NULL,
`utilities-remove_db` tinyint(1) NOT NULL,
`tax_rates-index` tinyint(1) NOT NULL,
`tax_rates-add` tinyint(1) NOT NULL,
`tax_rates-edit` tinyint(1) NOT NULL,
`tax_rates-delete` tinyint(1) NOT NULL,
`categories-index` tinyint(1) NOT NULL,
`categories-add` tinyint(1) NOT NULL,
`categories-edit` tinyint(1) NOT NULL,
`categories-delete` tinyint(1) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

INSERT INTO `permissions` (`id`, `group_id`, `repair-index`, `repair-add`, `repair-edit`, `repair-delete`, `repair-view_repair`, `customers-delete`, `customers-view_customer`, `customers-index`, `customers-add`, `customers-edit`, `inventory-index`, `inventory-add`, `inventory-edit`, `inventory-delete`, `inventory-print_barcodes`, `inventory-product_actions`, `inventory-suppliers`, `inventory-add_supplier`, `inventory-edit_supplier`, `inventory-delete_supplier`, `inventory-models`, `inventory-add_model`, `inventory-edit_model`, `inventory-delete_model`, `purchases-index`, `purchases-add`, `purchases-edit`, `purchases-delete`, `auth-index`, `auth-create_user`, `auth-edit_user`, `auth-delete_user`, `reports-stock`, `reports-finance`, `reports-quantity_alerts`, `auth-user_groups`, `auth-delete_group`, `auth-create_group`, `auth-edit_group`, `auth-permissions`, `utilities-index`, `utilities-backup_db`, `utilities-restore_db`, `utilities-remove_db`, `tax_rates-index`, `tax_rates-add`, `tax_rates-edit`, `tax_rates-delete`, `categories-index`, `categories-add`, `categories-edit`, `categories-delete`) VALUES
(2, 4, 1, 1, 1, 1, 1, 1, 1, 0, 0, 1, 1, 1, 1, 1, 1, 0, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 0, 0, 1, 1, 1, 0, 0, 1, 0, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1);

ALTER TABLE settings ADD `r_inprogress` longtext COLLATE utf8_unicode_ci NOT NULL;
ALTER TABLE settings ADD `r_approved` longtext COLLATE utf8_unicode_ci NOT NULL;
ALTER TABLE settings ADD `r_tobedeliver` longtext COLLATE utf8_unicode_ci NOT NULL;
ALTER TABLE settings ADD `r_delivered` longtext COLLATE utf8_unicode_ci NOT NULL;
ALTER TABLE settings ADD `r_cancelled` longtext COLLATE utf8_unicode_ci NOT NULL;
ALTER TABLE settings ADD `r_tobeapproved` longtext COLLATE utf8_unicode_ci NOT NULL;

ALTER TABLE `settings` ADD `rows_per_page` INT NOT NULL AFTER `model_based_search`;
UPDATE `settings` SET `rows_per_page` = '10' WHERE `settings`.`id` = 1;
ALTER TABLE `settings` ADD `iwidth` INT NOT NULL AFTER `rows_per_page`, ADD `iheight` INT NOT NULL AFTER `iwidth`, ADD `twidth` INT NOT NULL AFTER `iheight`, ADD `theight` INT NOT NULL AFTER `twidth`, ADD `watermark` BOOLEAN NOT NULL AFTER `theight`;
UPDATE `settings` SET `iwidth` = '800', `iheight` = '800', `twidth` = '150', `theight` = '150' WHERE `settings`.`id` = 1;

ALTER TABLE `classes`
ADD PRIMARY KEY (`id`),
ADD KEY `id` (`id`);
ALTER TABLE `permissions`
ADD PRIMARY KEY (`id`),
ADD KEY `id` (`id`);
ALTER TABLE `classes`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT;
ALTER TABLE `permissions`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT;

UPDATE `settings` SET `r_inprogress` = 'Hey %buyer%, your order/restore for %mannequin% was opened by %businessname%. Examine the state of restore anytime on %site_url%.' WHERE `settings`.`id` =1;
UPDATE `settings` SET `r_approved` = 'Hey %buyer%, your order/restore for %mannequin% was accredited. ' WHERE `settings`.`id` =1;
UPDATE `settings` SET `r_tobedeliver` = 'Hey %buyer%, your order/restore for %mannequin% was opened by %businessname%. Examine the state of restore anytime on %site_url%.' WHERE `settings`.`id` =1;
UPDATE `settings` SET `r_delivered` = 'Hey %buyer%, your order/restore for %mannequin% was delivered by %businessname%. ' WHERE `settings`.`id` =1;
UPDATE `settings` SET `r_cancelled` = 'Hey %buyer%, your order/restore for %mannequin% was cancelled. ' WHERE `settings`.`id` =1;
UPDATE `settings` SET `r_tobeapproved` = 'Hey %buyer%, your order/restore for %mannequin% must be accredited ' WHERE `settings`.`id` =1;

Replace – v1.Three to v1.4

Change Log 1.40

— Added Limitless Restore Statuses
  1. Obtain v1.41
  2. Backup your present rms_application information (v1.4) and export present database as sql (as pre-caution).
  3. Delete v1.Four rms_application information and extract v1.41 as substitute
  4. Restore rms_application/property/uploads/logos & rms_application/property/uploads/members folder from v1.4
  5. Restore rms_application/software/config/config.php, rms_application/software/config/database.php information from v1.4
  6. Go to phpMyAdmin , choose your database and run the next SQL:


UPDATE reparation SET standing = 10 WHERE standing = 3;
UPDATE reparation SET standing = 11 WHERE standing = 2;
UPDATE reparation SET standing = 12 WHERE standing = 0;
UPDATE reparation SET standing = 13 WHERE standing = 5;
UPDATE reparation SET standing = 2 WHERE standing = 10;
UPDATE reparation SET standing = Three WHERE standing = 11;
UPDATE reparation SET standing = Four WHERE standing = 12;
UPDATE reparation SET standing = Zero WHERE standing = 13;
CREATE TABLE IF NOT EXISTS `standing` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`label` varchar(150) NOT NULL,
`bg_color` varchar(50) NOT NULL,
`fg_color` varchar(50) NOT NULL,
`place` int(11) NOT NULL,
`send_sms` tinyint(1) NOT NULL,
`send_email` tinyint(1) NOT NULL,
`sms_text` textual content,
`email_text` textual content,
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=5 ;

INSERT INTO `standing` (`id`, `label`, `bg_color`, `fg_color`, `place`, `send_sms`, `send_email`, `sms_text`, `email_text`) VALUES
(1, 'In Progress', '#000000', '#ffffff', 1, 0, 1, NULL, 'Hey %buyer%, your order/restore for %mannequin% was opened by %businessname%. Examine the state of restore anytime on %site_url%.'),
(2, 'To Be Authorised', '#ff0000', '#ffffff', 2, 0, 1, NULL, 'Hey %buyer%, your order/restore for %mannequin% must be accredited '),
(3, 'Job carried out! able to ship', '#692121', '#ffffff', 3, 0, 1, NULL, 'Hey %buyer%, your order/restore for %mannequin% was opened by %businessname%. Examine the state of restore anytime on %site_url%.'),
(4, 'Delivered', '#1be323', '#000000', 4, 0, 1, NULL, 'Hey %buyer%, your order/restore for %mannequin% was delivered by %businessname%. ');

Replace – v1.2 to v1.3

  1. Obtain v1.3
  2. Backup your present rms_application information (v1.2) and export present database as sql (as pre-caution).
  3. Delete v1.2 rms_application information and extract v1.Three as substitute
  4. Restore rms_application/property/uploads folder from v1.2
    (Delete present rms_application/property/uploads folder and paste v1.2’s rms_application/property/uploads as substitute from backup.)
  5. Restore rms_application/software/config/config.php, rms_application/software/config/database.php information from v1.2
  6. Go to phpMyAdmin , choose your database and run the next SQL:

ALTER TABLE `reparation` ADD `imei` TEXT NOT NULL AFTER `date_closing`;
ALTER TABLE `settings` ADD `model_based_search` BOOLEAN NOT NULL AFTER `model`;
UPDATE `settings` SET `model` = '1.30' WHERE `settings`.`id` = 1;

Change Log 1.30

Amount Enhance Bug Fastened
delete affirmation added
added IMEI discipline
mounted Responsive Tables 
Entrance Web page Translation added
Russian Translation added
Menu Translation added
Import/Export Function added
Restore create with out including faulty objects 
Alert Amount added
And A lot Extra. 

Counter

Repairer - Repair Shop Management System 2.3 Download

DOWNLOAD/LIVE PREVIEW
Source

Be the first to comment

Leave a Reply

Your email address will not be published.


*


This site uses Akismet to reduce spam. Learn how your comment data is processed.