Prerequisite: State Inspector Tool AngularJS Batarang
¶ General Info for CEF/DNN
- Changing any file in your skin folder will require the app pool for DNN to be restarted. This is because DNN can't detect file changes through the symlink.
- Clarity production boxes are more secure than the dev boxes. Your text editor will need to be in administrator mode as well as your terminal for building.
- New prod URL needs to be present in /c/windows/system32/drivers/etc/hosts
- virtual directories to both the placeholder image (in framework/content) and the images folder (../images) will need to be created in IIS
¶ AppSettings
- All of your development appSettings will need to be changed to reflect the new URL and such.
¶ Emailer
- EmailSettings Besides making sure your smtp server itself is running, there are a lot of AppSettings you will need to make sure are correct. Please refer to CEF Emails and {{Tokens}} Nuclino article
- There is no logging mechanism. You will need to attach at CEF\Providers\Clarity.Ecommerce.Providers.ScheduledTasks\Tasks\ProcessEmailBatchTask.cs:104 (in the SmtpClientSendCompleted function) and see the error message yourself, or add some logging using the emails SerializableAttributes.
¶ CEF Pages
- magiczoom and magicscrollplus js/css are NOT included by default, you will need to copy those over same as you did for development. (see productDetails.ascx)
Debugging Payment Integrations (FE)
More than likely the Backender that designed the integration will be helping
- Most of this should be handled in the backend, but occasionally our purchasing module will fail to send some piece of data that is not normally required, but is crucial for an external payment integration. For example the 'CardType', which is generated via an on-change event on the input for the cardNumber field -- if a user chooses to use a form filler, this never is sent. Et cetera.
Reaching out to third-party resources
- SSL / For non DNN CRM sites, like Wordpress for example, you do not have direct webserver access to install the SSL certificate. Wordpress has an online wizard to help install it, but I haven't ever gotten that to work. You may have to reach out to a wordpress rep over the phone, and FTP in to the Wordpress box to drop your SSL files ( .key / .crt / .pbt )
¶ Reading your Network Tab
- In the network tab of your browser's development tools you'll be able to see any network request that happens.
- If you need to verify your issue is data related instead of UI related, you can see exactly what the API sent you from any of these requests.
Example: CurrentAccount
Clicking that network call will allow you to view both the request (under Headers), and the response (under Preview or Response), like so. (Edited for brevity)
{
"IsTaxable": true,
"TaxExemptionNo": "22",
"TaxEntityUseCode": "22",
"IsOnHold": false,
"AccountContacts": [],
"AccountPricePoints": [],
"AccountCurrencies": [],
"AccountAssociations": [],
"AccountsAssociatedWith": [],
"TypeID": 2,
"Type": {},
"TypeKey": "CUSTOMER",
"TypeName": "Customer",
"TypeDisplayName": "Customer",
"StatusID": 1,
"Status": {},
"StatusKey": "NORMAL",
"StatusName": "Normal",
"StatusDisplayName": "Normal",
"Brands": [],
"Products": [],
"Stores": [],
"Vendors": [],
"Notes": [],
"Images": [],
"StoredFiles": [],
"Name": "Clarity Demo Account test",
"ID": 1,
"CustomKey": "walmart",
"Active": true,
"CreatedDate": "2019-01-22T19:06:12.7649340",
"UpdatedDate": "2020-10-14T23:55:14.9856684",
"JsonAttributes": "{}",
"SerializableAttributes": {}
}