INTERNAL Class catalog setup

Created by Ezra Weinstein, Modified on Fri, 21 Oct 2022 at 03:53 PM by Hannah Harris

THIS ARTICLE IS OUT OF DATE.  The Fragment for classes should now be defined by default in the management client on each server.  It should not be necessary to create it in the client site.


This is internal documentation to complete the steps that are not available to clients in this article: Set up Events and Training Classes in coreFORCE


After the event, product and variant taxonomy has been set up and at least some classes are created, the next step is to create a fragment for displaying event products in a user-friendly way.  


  1. In Orders > coreFORCE Setup on the Fragments tab, locate the Product Details fragment and choose customize.  This will create a new fragment called RETAIL_STORE_PRODUCT_DETAILS.


  1. Locate the fragment just created in in Website > Fragments.  Rename it as RETAIL_STORE_CLASS_DETAILS.  Change the description to Class Details.


  1. Choose "Product Detail HTML" for the Fragment Type.  If this Fragment Type is missing, you will need to add it in Fragment Types (not available in client sites; log into the primary client on the server to see this page).  The code for this Fragment type needs to be PRODUCT_DETAIL_HTML.


  1. You can customize the HTML as needed.  The most common change for classes is to remove the product specifications section (code, manufacturer, UPC, etc.) that isn't relevant to classes, as well as location availability. Also, add the following line to change "Out of stock" into "This class is full":
    <p id="_class_empty" class="out-of-stock-message">This class is full</p>


  1. In Product Departments Maintenance, select the Department which the client should have created for their classes.  On the Details tab, for Product Details fragment, select the fragment you just created.

 

The final step is to create a page for a class catalog and/or an event calendar page, which will use the shopping cart to checkout.  Registration can also be done with the eventregistration.php script, which will prompt the customer for payment when they register.  That may be the cleanest solution for dealers with a small number of classes.

 

There are some distinctions between the two methods of registering:

 

  • Using the cart allows the customer to purchase other things. So, they could purchase a handgun, ammo and register for a class. The event registration page ONLY allows event registration.
  • The event registration page allows the merchant to add "options" to the event registration. So, maybe a dealer has a handgun safety class and they offer an option to rent a handgun. That can be done on the event registration page. That cannot be done in the regular shopping cart.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article