This project is NOT MEANT FOR PRODUCTION. You should only use this as a reference or proof of concept to show how product images may be imported at any time programmatically. It's based upon the image import section in the documentation below.
Related Documentation: https://hotcakescommerce.zendesk.com/hc/en-us/articles/205426535-Product-Import
Hotcakes Commerce is an e-commerce solution that empowers developers and designers alike to be able to actually fulfill client requirements when building an online store. We believe that e-commerce should be easier, for EVERYONE on your team.
Prerequisite: You must already have a CMS ready to use this with, and a superuser account on the site.
- Download the latest release and save it somewhere on your computer.
- Login using your superuser account.
- Use the control panel to navigate to Host > Extensions.
- Click the "Install Extension" button, and a popup installation wizard will appear.
- Follow the steps in the installation wizard.
- After installation, add the module to a page and use it (preferrably a security-protected page).
- You should create a website folder where your project will be. This can be anywhere on your system. For example
C:\Websites\MyProjectName\ - Clone the repository into that folder
- Create a new folder in the root: Website (Example:
C:\Websites\MyProjectName\Website\) - Update IIS and your local HOSTS file to point to your local development URL, such as http://ProcessImagesModule.loc
- Install the CMS into the website folder (see version info below).
- Install Hotcakes Commerce into the CMS.
- Run the Hotcakes Commerce "Getting Started" wizard.
- Add sample products, or add some of your own.
- Build this project in Debug mode.
- "Install" the ProcessImages module using the Create New Module > Create from Manifest. (You can also install the package you created when building in Release mode.)
- If it's not on a page already, add this module to a new or existing page.
- Play with the module.
This solution is currently being built against DNN 09.02.02.
Be sure that you get the file permissions properly assigned to the folders when you install DNN.
The following Visual Studio 2019 extensions are currently installed and being used in my environment, but are not necessary to work on the project. There are more, but these are the only ones that are relevant to this project.
- Guidinserter2
- Microsoft ASP.NET and Web Tools
- NuGet Package Manager
- ReSharper (not free, except to active open source developers)
- UIMap Toolbox
- Web Essentials
Here's the steps to help update this.
- Create an issue.
- Collaborate.
- Fork the project.
- Create a branch.
- Write your code.
- Test your code.
- Create a pull request.
- Hotcakes staff will review the pull request and take any necessary actions.
While there continues to be only a single module here, you can safely build from the Solution or Project level.
When you first begin using this project, you should first build using DEBUG mode, discussed below.
Building in DEBUG mode will compile the project/solution as you'd expect, but an MS Build script will also move the module files into the appropriate Website\DesktopModules\ folder as well.
Building in RELEASE mode will not move the project files, but it will package the module in an Install and Source package that can be used to install on another Hotcakes site for testing or deployment.
~\Website\Install\Module\
This is VERY important to know. This module has a Module.Build file that properly maps it's files that need to be moved into the Website folder.
https://github.com/upendoventures/generator-upendodnn
Debugging should be done using the "Attach to Process" method found in Visual Studio.
You'll find a website and database backup in the Assets folder. This should be used as your starting point, as defined in the Getting Started section above.
This solution folder contains the common configuration files for the entire solution, such as the web.config.
This contains the various module projects that will be placed onto pages.
The website project is only used for reference. Any core code changes to the CMS itself are forbidden.