• | During installation of mySQL, the mySQL Server Configuration Wizard pops up, allowing you to define:
Server Machine, Multifunctional database
DB location: C:\<company name>\DB\mySQL
Concurrent Connections: 20-100
Enable TCP through port 3306
Standard character set (latin1) or Best support for Multilingualism (UTF8)
Install as a Windows service: yes
Change password for root account, and remember it!
In the Windows Firewall, define an Inbound rule port 3306 for the mySQL server. The other 2 rules you already defined in the Server Installation chapter. |
• | Create a database in HeidiSQL:
define a new session 3P and inside this session a database with the name pixpedia. Make sure the charset is utf8 as in this screenshot: |
• | Configure ODBC to link to mySQL in Microsoft Access.
You must use the 32-bit ODBC tool - There's a link in the SVN subfolder \4all\3p_install called odbcad32.exe. The full path on a Windows Server is: C:\windows\syswow64\odbcad32.exe
|
• | After you checked out from SVN (see Server Installation) and created the database in HeidiSQL, you can now install 3P OpenCart. In a browser, enter the URL:
http://demo1.domain.name/3p_installer/index.php
where domain.name is the shop domain you plan to host on your server. This will launch the 3P installation wizard, allowing you to define some mySQL database access information.
The password is the same as the one you defined during the mySQL installation above. |
Make sure the database pixpedia exists in the mySQL server, and the C:\inetpub\wwwroot\opencart folders have write access as decribed in the Server Installation chapter.
|
|
• | Create the following folders on your server, and assign the same write permissions as for the C:\inetpub\wwwroot\opencart folder (see Server Installation).
The meaning of these folders is described later in this topic:
C:\<company name>\3p_upload (UploadBaseFolder)
C:\<company name>\3p_print (DefaultQueueFolder)
C:\<company name>\3p_infos (InfoBaseFolder) |
• | In IIS, define a virtual directory 3p_print below the Default Web Site with the path to your DefaultQueueFolder (see below).
Edit the Site Binding and set the host name to admin.domain.name. Then start the Default Web Site.
|
• | In HeidiSQL or 3P BackOffice, edit the table oc_3p_option and check/change the values displayed in red. Make sure to replace domain.name and <company name>. |
Name
|
Value
|
Hint
|
UploadBaseFolder
|
C:\<company name>\3p_upload
|
The folder where the files are uploaded from the Publisher applications.
|
InfoBaseFolder
|
C:\<company name>\3p_infos
|
The folder where the print info files and invoices are stored.
|
DefaultQueueFolder
|
C:\<company name>\3p_print
|
The queue folders into which the printable PDF chunks (cover, content) are generated.
|
DefaultQueueURL
|
http://admin.domain.name/3p_print
|
The URL to your default print queue folder. Allows you to view the stitched PDFs from the 3P BackOffice.
|
PurgeIncompleteUploadDays
|
10
|
After how many days are unfinished upload files deleted?
The user is not warned.
|
PurgeOrderFilesDays
|
30
|
After how many days are finished order files deleted, i.e. how long can the user reorder?
The user is warned by email 10 and 5 days prior to the deletion.
|
DeleteFilesOnFailDetect
|
false
|
If the printer sets the order status values inside the job.xml files, the system detects these status changes and can automatically delete the corresponding PDF files (true).
Only status values 15 (processing), 3 (shipping) and 10 (failure) are checked in the job.xml. The printer can change the status from 2 to 15 (after he collected the files), or from 15 to 3 (after he printed the book). If an error occurs, he must set it to 10 and add an error message in the xml attribute OrderStatusMessage.
See order workflow for more info
|
DeleteFilesOnFailManual
|
true
|
If the printer or admin sets the order status values manually from the 3P BackOffice, the system will delete the corresponding PDF files (true).
|
CleanupOrphanFiles
|
true
|
A cron job automatically deletes PDF files that no longer have corresponding order records.
|
Print.MarginLeft
|
0.5
|
3P BackOffice PDF print options for database table or view data (queries).
|
Print.MarginRight
|
0.5
|
"
|
Print.ShowPageFooter
|
true
|
"
|
Print.Portrait
|
false
|
"
|
Print.ShowSqlInfo
|
true
|
Display the SQL command which the table or view is based on.
|
Url.IPSearch
|
http://www.utrace.de/ip-adresse/%s
|
Web service which displays geographic customer location.
|
Url.DefaultStore
|
http://demo1.domain.name
|
Needed by the 3P BackOffice to find:
• | the image folder, which is usually:
C:\inetpub\wwwroot\<company name>\opencart\image |
• | the 3P OpenCart Administration to edit a customer or an order |
|
Subshop.3pdemo-en
|
0
|
Default demo store (store_id = 0)
|
Subshop.3pshop-en
|
1
|
This test subshop will be filled with products as soon as you import a corresponding products.xml
|
• | In HeidiSQL or 3P BackOffice, edit the table oc_3p_queue and add print queue records for your product IDs. Use the current demo records as a guideline. In the example below, the Content chunk PDFs of all product IDs starting with dx013 and dx014 are placed into C:\<company name>\3p_print\vistaprint, while the Cover PDFs are placed into the default folder C:\<company name>\3p_print\Default\PDFs, because there is no other assigned folder for these products:
|
• | Run OpenCart Administration using the URL http://demo1.domain.name/admin and login with username admin and default password admin. First thing to do after login, is to change the admin password and email address. Don’t remove or change the admin user - we use this username by default. You can add another admin user, if you want to.
The default store settings can be found under the menu item System > Settings > 3p Demo Store > Edit. Here you should also change the global SMTP Mail configuration for all stores. Please check the installed hMailServer for your settings. You need to run a mail server, so Opencart can send the status notification and invoice mails to the customers.
Many of the settings in the default store apply to all stores, i.e. all of your subshops. We will not go into the details of the OpenCart store settings, as this simply requires some experimenting, and all settings are also covered by the OpenCart Online documentation.
|
In System > Settings > 3p Demo Store > Edit > Option, make sure the following status values are defined:
Name
|
Value
|
Hint
|
Order Status
|
Waiting for payment (1)
|
some payment gateways automatically skip this status
|
Complete Order Status
|
Shipping (3)
|
Order is paid (and shipping). Customer can now access purchased gift vouchers or reorder the book.
|
Out of Stock Status
|
Inactive
|
same as inside products.xml, see Product Migration
|
In HeidiSQL or the 3P BackOffice you can now open the table oc_setting and check the setting values, which were all created by the OpenCart Administration System > Settings page. The field store_id appears in many OpenCart mySQL tables, and it shows a unique ID for each of your subshops:
0 = demo1.domain.name
|
your 3P Demo Shop with subshopid 3pdemo-en. A demo products.xml is included and already imported by the installer.
|
1 = shop1.domain.name
|
your 3P Test Shop with subshopid 3pshop-en. You need to create your own products.xml and import it in the OpenCart Administration
|
2 = xy.domain.name
|
this will be your first live shop. You can copy the products.xml from your test shop and import it. You can later add any number of subshops with any language
|
|
|
demo1.domain.name
This shop has demo products installed
(see \opencart\admin\upload\3pdemo-en\products.xml)
|
shop1.domain.name
This shop does not yet have any products installed.
You can import and test your own products.xml here
|
• | Open the default customers group in Sales > Customers > Customers Group > Edit, and make sure the option Approve new customers is set to yes. This way, a new customer must register during upload and then activate his account by clicking on the link in the registration mail. Alternatively, the admin can also approve the new customer, if he has serious problems with his mail account or spam filter.
Forcing the customer to activate his account guarantees that his email is correct and you can send him order status mails and invoices. It also reduces double and fake registrations! |
• | The 3P Test Shop uses a commercial theme called AquaCart.
If you want to use this in a live shop, you need to purchase a license!
OpenCart provides two default modules - Banner and Carousel. AquaCart doesn't use these, but adds it's own custom modules AquaCart - Front Page Banners and AquaCart - Custom Slideshow. AquaCart also adds Store Settings and Template Styles modules, allowing you to adjust the theme. The following screenshots show you where you can switch the theme (i.e. to the free Palioxis theme) or edit the custom modules:
|
|
+ + + Important + + +
• | Any time you want to repeat the installation, you have to remove the files C:\inetpub\wwwroot\<company name>\opencart\config.php and opencart\admin\config.php |
• | When you are done with the installation, you should delete the folder opencart\3p_installer. Use SVN in the Windows Explorer context menu to do this, otherwise it will reappear next time you checkout. Removing this folder is essential - otherwise anyone can destroy your shop settings. |
• | Before installing and using 3P OpenCart & Backoffice, please make sure you read and understand the license agreements. |
• | The 3P Test Shop includes a theme called AquaCart. If you want to convert your test shop into a live shop, or if you want to use this theme in any new subshop, you must purchase a license for this theme at Theme Forest. If you want to use any other theme, please purchase this theme and send it to us, so we can test it with our code. The 3P Demo Shop includes a theme called Palioxis. This theme is free and can be found here. |
• | The 3P Test Shop includes a number of banners and graphics. You are NOT allowed to use these in a productive environment! You must remove them after installation of 3P OpenCart, so they cannot be accessed from the internet. |
• | Please send us any other payment, language and theme extension you plan to use, so we can test it and adapt the 3P OpenCart core code in case of a conflict. This service is not free, but we will inform you of the cost beforehand. |
• | Please check in any personal core code changes via SVN. Please note, that we are no longer responsible for shop malfunction in case you change the 3P OpenCart core code yourself. |
|
|