ISoft Wiki - User contributions [en]

Internal.XML feeds

2025-12-11T22:23:47Z

Ajohnson: /* Adding a new XML feed or altering an existing feed */

== Adding a new XML feed or altering an existing feed ==

See the confluence wiki at https://isoftdata.atlassian.net/wiki/spaces/HTP/pages/639762435/XML+Sitemap+Script+Setup+for+WordPress+Sites

Wordpress Plugin

2022-12-21T23:12:55Z

Ajohnson:

{{warning|This documentation is for the "original" plugin, and does not cover the "Looper Provider" plugin.}}
Instructions for the "Looper Provider" version are saved in the ISoft Google Drive.
== Installation ==
To install the plugin, just unzip it to your Wordpress plugins directory, like normal. The plugin talks to our HeavyTruckParts.Net API to power its searches and results, so you'll need a bit of configuration after it's installed before it'll actually be useful. You can find these settings in your Wordpress Admin panel under "Heavy Truck Search".

== Pretty Search URIs ==
If you turn on "Pretty Search URIs", it'll use "pretty" links for searches and details, so searches will be based on "/search/<part type>/<manufacturer>/<model>" style links, and item details on "/item/<manufacturer>/<model>/<part type>/<inventory id>" style links. Since these links don't have the name of the page with the search form or the results section, the configuration includes "Search Page Name" and "Details Page Name" entry blanks to let you fill in what you have set up on your site. I would encourage you to avoid naming your search page "search," that can cause issues with the pretty permalink rewriting.

If you want to use Pretty Search URIs, please notify the ISoft web development team so that the HeavyTruckParts.Net API can be configured correctly (or your part types will be "named" by their IDs instead of their names).

== Basic Use ==
Using the plugin is (hopefully) pretty straightforward. This is all documented on the plugin settings page also, if you want to use it for reference. You will need to create a Wordpress Page, and place the shortcodes on it as desired. Usually the search form and the results block are placed on the same Wordpress Page. This is done with the [heavytrucksearch] shortcode and the [heavytruckresults] shortcode. By default, [heavytrucksearch] provides a keyword search with a submit button. If you want a complete search form with drop-down selection boxes for part type, manufacturer, and model, set the "advanced" parameter to "true": [heavytrucksearch advanced="true"].

== Pre-populated searches ==
If you want to link to a pre-populated search (like, say, for Engines), you can link to the results page and add the part_type query parameter (/results-page?part_type=Engine%20Assembly, or, with pretty links, /search/Engine-Assembly). Part type names are based on what the vendor is using in ITrack (that's why the engine link example includes the space, encoded to %20, or as a '-' when using pretty links).

Wordpress Plugin

2022-12-21T23:11:05Z

Ajohnson:

{{warning|This documentation is for the "original" plugin, and does not cover the "Looper Provider" plugin.}}
Instructions for the "Looper Provider" version can be found here: https://docs.google.com/document/d/1jKr1i_ZckyyqCz_-7svn4_1hq7attcXHGCrR8y_V6fQ/edit#heading=h.6chpworgfw6x
== Installation ==
To install the plugin, just unzip it to your Wordpress plugins directory, like normal. The plugin talks to our HeavyTruckParts.Net API to power its searches and results, so you'll need a bit of configuration after it's installed before it'll actually be useful. You can find these settings in your Wordpress Admin panel under "Heavy Truck Search".

== Pretty Search URIs ==
If you turn on "Pretty Search URIs", it'll use "pretty" links for searches and details, so searches will be based on "/search/<part type>/<manufacturer>/<model>" style links, and item details on "/item/<manufacturer>/<model>/<part type>/<inventory id>" style links. Since these links don't have the name of the page with the search form or the results section, the configuration includes "Search Page Name" and "Details Page Name" entry blanks to let you fill in what you have set up on your site. I would encourage you to avoid naming your search page "search," that can cause issues with the pretty permalink rewriting.

If you want to use Pretty Search URIs, please notify the ISoft web development team so that the HeavyTruckParts.Net API can be configured correctly (or your part types will be "named" by their IDs instead of their names).

== Basic Use ==
Using the plugin is (hopefully) pretty straightforward. This is all documented on the plugin settings page also, if you want to use it for reference. You will need to create a Wordpress Page, and place the shortcodes on it as desired. Usually the search form and the results block are placed on the same Wordpress Page. This is done with the [heavytrucksearch] shortcode and the [heavytruckresults] shortcode. By default, [heavytrucksearch] provides a keyword search with a submit button. If you want a complete search form with drop-down selection boxes for part type, manufacturer, and model, set the "advanced" parameter to "true": [heavytrucksearch advanced="true"].

== Pre-populated searches ==
If you want to link to a pre-populated search (like, say, for Engines), you can link to the results page and add the part_type query parameter (/results-page?part_type=Engine%20Assembly, or, with pretty links, /search/Engine-Assembly). Part type names are based on what the vendor is using in ITrack (that's why the engine link example includes the space, encoded to %20, or as a '-' when using pretty links).

Wordpress Plugin

2022-12-21T23:10:17Z

Ajohnson:

{{warning|This documentation is for the "original" plugin, and does not cover the "Looper Provider" plugin. Instructions for the "Looper Provider" version can be found here: https://docs.google.com/document/d/1jKr1i_ZckyyqCz_-7svn4_1hq7attcXHGCrR8y_V6fQ/edit#heading=h.6chpworgfw6x
}}
== Installation ==
To install the plugin, just unzip it to your Wordpress plugins directory, like normal. The plugin talks to our HeavyTruckParts.Net API to power its searches and results, so you'll need a bit of configuration after it's installed before it'll actually be useful. You can find these settings in your Wordpress Admin panel under "Heavy Truck Search".

== Pretty Search URIs ==
If you turn on "Pretty Search URIs", it'll use "pretty" links for searches and details, so searches will be based on "/search/<part type>/<manufacturer>/<model>" style links, and item details on "/item/<manufacturer>/<model>/<part type>/<inventory id>" style links. Since these links don't have the name of the page with the search form or the results section, the configuration includes "Search Page Name" and "Details Page Name" entry blanks to let you fill in what you have set up on your site. I would encourage you to avoid naming your search page "search," that can cause issues with the pretty permalink rewriting.

If you want to use Pretty Search URIs, please notify the ISoft web development team so that the HeavyTruckParts.Net API can be configured correctly (or your part types will be "named" by their IDs instead of their names).

== Basic Use ==
Using the plugin is (hopefully) pretty straightforward. This is all documented on the plugin settings page also, if you want to use it for reference. You will need to create a Wordpress Page, and place the shortcodes on it as desired. Usually the search form and the results block are placed on the same Wordpress Page. This is done with the [heavytrucksearch] shortcode and the [heavytruckresults] shortcode. By default, [heavytrucksearch] provides a keyword search with a submit button. If you want a complete search form with drop-down selection boxes for part type, manufacturer, and model, set the "advanced" parameter to "true": [heavytrucksearch advanced="true"].

== Pre-populated searches ==
If you want to link to a pre-populated search (like, say, for Engines), you can link to the results page and add the part_type query parameter (/results-page?part_type=Engine%20Assembly, or, with pretty links, /search/Engine-Assembly). Part type names are based on what the vendor is using in ITrack (that's why the engine link example includes the space, encoded to %20, or as a '-' when using pretty links).

File:ITrack Pro ecom settings.png

2022-05-18T21:14:23Z

Ajohnson:

Internal.XML feeds

2021-09-28T22:12:20Z

Ajohnson:

== Adding a new XML feed or altering an existing feed ==

Adding a new XML feed requires the company to have their own php export script in the scripts directory off the main heavytruckparts.net directory.

As each of the yards have different needs for the title, links, description, and other data in the XML file, it is best for each productcode to have their own php file.

I will create a template version of the file with CHANGEME marked areas after I return.

After creating the initial file, notify Brian so he can add the script to the cronjob. Currently we are exporting the files once a week, on Sundays.

The XML files are output to the format www.heavytruckpars.net/xml/[companyname]_GMC_feed_rss.xml

Internal.XML feeds

2021-09-28T21:16:49Z

Ajohnson: Adding a new XML feed for Facebook or Google Merchant Center from HTP

Adding a new XML feed requires the company to have their own php export script in the scripts directory off the main heavytruckparts.net directory.

As each of the yards have different needs for the title, links, description, and other data in the XML file, it is best for each productcode to have their own php file.

File:ITrack Internet Home Screen Example.png

2021-09-14T22:38:49Z

Ajohnson:

File:ITrack Internet Sale Document Example.png

2021-09-14T22:38:35Z

Ajohnson:

File:Add to cart - HTP sales history.png

2021-09-14T21:13:11Z

Ajohnson:

File:Add to cart - HTP detail view.png

2021-09-14T21:12:31Z

Ajohnson:

File:Add to cart - HTP search.png

2021-09-14T21:12:14Z

Ajohnson:

File:Add to cart - HTP cart page two.png

2021-09-14T21:10:58Z

Ajohnson:

File:Add to cart - HTP cart page three.png

2021-09-14T21:09:56Z

Ajohnson:

File:Add to cart - HTP cart page one.png

2021-09-14T21:09:41Z

Ajohnson:

File:Add to cart - end customer email.png

2021-09-14T21:09:14Z

Ajohnson: