Category Archives: Power

SEO Pages

SEO Pages functionality is part of the Power add-on.  For the  Pages functionality to appear you must enable pages under the General / Data tab.  When “enable pages” is checked your locations will automatically be set to show that they have pages under the locations manager. They are set  as draft by default. They will  have unique ids. You will also see the Store Locator Plus logo with STORE PAGES appear on your WP menu  sidebar.

Continue reading

What To Buy: Filter By Brand

Question

We need to filter our locations by brand.  Does your plugin or an extension to your plugin have this feature?

Assigning Brands To Locations

Power is the right choice for doing that. The Power add-on allows for simple categories or complex parent/child relationships between categories. Locations can be assigned to one or more categories. Your users can then search for locations based on those categories.

Add a category for each brand you offer and your users will be able to filter locations showing only those that offer specific brands.

Add Ons That Support This Feature

Buy The Power Add On

Buy The Power Add On

Import remote file retrieval

The Power Add-on Import allows the administrator to  schedule your Import process from a remote file retrieval to provide more control over recurring imports from a full url where you CSV file resides and allows flexibility for scheduling the time for daily imports.
WordPress cron is not exact, it executes the next time a visitor comes to your site. WordPress times are UTC/GMT time NOT local time. Set to none and leave the URL blank to clear the cron job. Example: 14:25. (Default: empty = do not run daily cron)

Power 4.6 import back end

Checking your server, PHP and MySQL to ensure the character set is correct will go a long way toward importing special characters like registration characters.

Additional Import Data field headers

If you have the Power add-on you will have the ability to import data fields via a properly formatted csv file.  All columns MUST have a header row with the  field name. All fields are short text fields, up to 255 characters, unless otherwise noted.  The header text is NOT case sensitive.

If you are using the category (aka tagalong) functionality of Power you may want to import and assign a category slug on the fly.  The header field name is:

category (or plural categories).

If you wish to import and assign more than one category  per location , you will need to use a comma-separated list for the data field  (category).  Example: My location has more than one category associated with it, I want to indicate it is a hotel,restaurant, and has music.  Category  for that location would show under the column with the header row “category”…. hotel,restaurant,music

Alternatively, to define parent/child relationships , i.e.  hierarchical categories , use a double colon as the separator Example the Parent is Facility, the child is showroom.

Facility::Showroom.

User Interface Settings

Settings that impact how JavaScript works on your site

UI jQuery Version –

reflects the jQuery version that is currently used with  the Store Locator Plus version  you are using. The SLP jQuery versions are in compliance with the WordPress minimal version requirements.

Force Load JavaScript

This settings forces the Store Locator Plus JavaScript (slp.js) to be loaded when your WordPress Theme header is loaded. This is NOT the way to go.  It is recommended that you turn OFF “Force Load JavaScript” and instead contact your theme author. See Troubleshooting for more information
Continue reading

Troubleshooting Large scale Exports

Issue: Exports are Incomplete

Multiple large-scale exports (export function is available with Power Add-on ) have been tested on the Store Locator Plus dev site. On a relatively small server, a virtual machine with 2GB RAM running CentOS 6, we  have been able to export 10,000 locations within 15 minutes with no issues. Special characters and extended data have also exported without issue.

If you are experiencing  issues there are several things to check that can cause problems during an export:

Web Server Process Limits

Apache, and nginx as far as I are aware, have per-process limits. This is built into the web server to prevent “runaway” processes that eat up all of the CPU and memory on the server over time. On shared servers this limit is very low and typically allows 30 seconds to 2 minutes of processing time. Large data sets can use up to 5 minutes or more of processing time. Make sure your server has a high enough limit to allow the entire data export to complete execution.
Continue reading