LandTech Self Storage API – Automated Storage Management Integration
LandTech Self Storage API is a free foundation plugin that securely connects your WordPress site to the WebSelfStorage API (U-Haul Self-Storage Affiliate Network) for real-time inventory, facility profile display, and seamless data sync. Production API paths can use v3 or v4 when Premium is active (see API version below). Server-side requests use your stored API key and Entity ID—nothing is embedded in page source for visitors. Display facility profile data and move-in / availability inventory on any page via shortcodes. See SHORTCODES.md in the plugin folder for the full shortcode reference. Features API integration: WebSelfStorage API — facility location, move-in inventory, and related calls used by the shortcodes (v3 or v4 paths when configured) Location display: Address, phone, and hours from the API Available units: Move-in inventory (pricing and specs as returned by the API) Admin: LandTech Storage settings for API key and Entity ID; Test Connection validates credentials and probes v3 and v4 test endpoints Shortcodes (public): [landtech_self_storage], [landtech_wss_movein], [landtech_wss_location_sizes] (see SHORTCODES.md) [wss_api_*] shortcodes: Raw JSON wrappers for endpoints—for administrators debugging only; do not use on public pages Responsive CSS for shortcode output Translation-ready — text domain landtech-self-storage-api; default strings are English (see Language support below) Premium-ready: Works alongside Self Storage API Premium for reservations, multi-facility, Gutenberg blocks, waiting lists, and API v4 Features admin Premium Version For reservation forms, multi-facility support, waiting lists, Self Storage API Gutenberg blocks (Storage Units, Unit Types, All Units, Reservation Form, Rental Form, Waiting List — six blocks in Premium 1.4.4+), API v4 Features admin, unit card display options, analytics, and bundled multi-language packages, see Self Storage API Premium. Language support This free plugin is internationalization-ready. WordPress will load a translation if you install a matching landtech-self-storage-api-{locale}.mo (for example in wp-content/languages/plugins/) or when community translations are available for this plugin on WordPress.org. The template for translators (.pot) is included under languages/ in the plugin package. Self Storage API Premium adds Self Storage API Premium-maintained compiled translations for many locales (for example German, Spanish, French, Italian, Brazilian Portuguese, and Japanese), RTL styles for admin and front-end, Self Storage API Gutenberg blocks, API v4 Features admin, a Language support help document under SelfStorage → Documentation, and a much larger set of translatable admin and feature strings (reservations, waiting list, license tools, and more). For the full translated experience across Premium features, upgrade to Self Storage API Premium. Installation Requirements WordPress: 5.0 or higher (tested up to 7.1). PHP: 7.4 or higher (aligns with WordPress 7.0 minimum supported PHP; 8.3+ recommended). Hosting: Outbound HTTPS requests must be allowed so WordPress can call api.webselfstorage.com (the plugin uses wp_remote_get / wp_remote_post, not raw cURL). Credentials: A valid WebSelfStorage API key and your facility Entity ID (from your storage network or U-Haul Self-Storage Affiliate Network account). Install the plugin Upload or install: Add the plugin folder to /wp-content/plugins/landtech-self-storage-api/, or in wp-admin go to Plugins → Add New → Upload Plugin and select the plugin zip, or search for LandTech Self Storage API if installing from WordPress.org. Activate: Go to Plugins, find LandTech Self Storage API – Automated Storage Management Integration, and click Activate. Configure the API connection In the WordPress admin sidebar, open LandTech Storage (top-level menu). The plugin’s settings screen loads there—it is not nested under Settings → General. Enter your API key and Entity ID (facility identifier used in API paths—often a numeric code from your network). Click Save Settings, then Test Connection (same screen) to confirm WordPress can reach api.webselfstorage.com and that the API accepts your credentials. Use shortcodes on your site Edit any page or post and add the shortcodes you need: [landtech_self_storage] — Primary block: facility profile plus optional units (show_location, show_units). [landtech_wss_movein] — Move-in inventory only (useful if you disabled units on the main shortcode to avoid duplication). [landtech_wss_location_sizes] — Size-code / vacant-units table from /v3/location/{entity} for comparison with move-in data. [wss_api_*] (e.g. wss_api_location, wss_api_movein) — Administrators only; outputs raw JSON for troubleshooting. Do not publish on customer-facing pages. Publish or Update the page. Rendering happens in PHP; the API key stays in options, not in HTML source. Troubleshooting (installation) If the test fails, verify PHP allow_url_fopen / firewall rules, that the API key matches your facility, and that the Entity ID matches WebSelfStorage records. For HTTPS or mixed-content issues, ensure your site uses HTTPS for admin if your host requires it. Frequently Asked Questions How do I get an API key? You can obtain your API key from your WebSelfStorage account. Contact your storage network provider for more information about accessing the WebSelfStorage API. What is an Entity ID? The Entity ID is a unique identifier for your storage facility. It’s typically a 6-digit number (e.g., 019109). If you’re unsure of your Entity ID, you can leave it blank and the plugin will attempt to retrieve it from the API. Can I use this with multiple facilities? The free version supports a single facility. For multi-facility support, please check out LandTech Self Storage API Premium. Are translations included? Free: The plugin is translation-ready. English ships by default; you can add custom .mo files or use WordPress.org language packs when available. See languages/TRANSLATORS.txt in the plugin. Premium ships pre-built .mo files for multiple locales and covers the full Premium UI—see Language support in this readme, then Self Storage API Premium to upgrade. What API version does this use? Default: WebSelfStorage API v3. Test Connection also probes v4 (GET /v4/test) and reports whether v4 is live for your API key. Switch to v4 for production requests when using Self Storage API Premium: SelfStorage → API v4 Features → API path, or add to wp-config.php: define( 'LANDTECH_SELFSTORAGE_WSS_API_VERSION', 'v4' ); The free plugin’s API client respects the shared version setting when Premium (or the constant) sets it. See SHORTCODES.md in this plugin folder. How do I display facility information on my site? Use the [landtech_self_storage] shortcode on any page or post. You can customize what’s displayed using the shortcode attributes: * show_location="true" – Display facility location information (default: true) * show_units="true" – Display available units (default: true) Example: [landtech_self_storage show_location="true" show_units="true"] Full attribute list and Premium shortcode pointer: see SHORTCODES.md in the plugin directory (or your copy from GitHub). Changelog 1.0.6 Documentation: Premium Gutenberg block list updated to include Unit Types (six blocks total in Premium 1.4.4+). Readme and upgrade notice refreshed; no functional changes to the free plugin. 1.0.5 API v4 compatibility: Production requests can use WebSelfStorage v3 or v4 paths. The free plugin’s API client reads the shared selfstorage_wss_api_version option (set in Premium SelfStorage → API v4 Features → API path), LANDTECH_SELFSTORAGE_WSS_API_VERSION in wp-config.php, or Premium reservation settings. Test Connection: Reports whether v4 is live for your API key and which path version is active for production calls. Premium-ready foundation: Documented integration with Self Storage API Premium Gutenberg blocks (Storage Units, Unit Types, All Units, Reservation Form, Rental Form, Waiting List) and the API v4 Features admin screen. Documentation: SHORTCODES.md added; readme updated for v3/v4 switching and block editor workflow. 1.0.4 Test Connection probes both GET /v3/test and GET /v4/test so you can see whether WebSelfStorage API v4 is live for your API key. 1.0.3 Hide “Want More Features?” upsell on [landtech_self_storage] and [landtech_wss_movein show_upgrade="true"] when Self Storage API Premium is active. Align plugin header Tested up to with readme (7.1). 1.0.2 Declares WordPress 7.0 compatibility (Tested up to) after testing on WordPress 7.0. Raises minimum PHP to 7.4 to align with WordPress 7.0 (PHP 7.2 and 7.3 no longer supported by core). No functional/plugin logic changes in this release. 1.0.1 Documentation: language support and translation paths for the free plugin; what Premium adds (bundled locales, RTL, in-product help). Version bump to sync readme with WordPress.org and Git. 1.0.0 Initial release Basic API integration with WebSelfStorage API v3 Location information display Available units display Admin settings page for API configuration Shortcode support for displaying facility information External services This plugin connects to an external API to display storage facility information and available units on your site. This is required for the plugin to function. WebSelfStorage API (U-Haul Self-Storage Affiliate Network) — https://api.webselfstorage.com What it is and what it is used for: The WebSelfStorage API is a service provided by U-Haul (eMove, Inc. d/b/a U-Haul Self Storage Affiliate Network). The plugin uses it to retrieve your storage facility’s location details (address, phone, hours) and available storage units with pricing so you can show that information on your WordPress site via the shortcode. What data is sent and when: The plugin sends your API key (in the request header) and your facility Entity ID (in the request URL) to the API. Specifically, it sends the Entity ID to endpoints such as /v3/location/ and /v3/movein/ to fetch location details (address, phone, hours) and available units with pricing. No site visitor personal data is sent. Data is sent when a page or post containing the shortcode is loaded, and when an administrator uses the settings page (e.g. testing the connection). Terms of Service and Privacy Policy (required links): Terms of Service / End User License Agreement: https://webselfstorage.com/EndUserLicenseAgreement Privacy Policy: https://webselfstorage.com/PrivacyNotice U-Haul legal and privacy: https://www.uhaul.com/Legal/
WP Consent API
WP Consent API is a plugin that standardizes the communication of accepted consent categories between plugins. It requires a cookie banner plugin and, at least, one other plugin that supports the WP Consent API. With this plugin, all supporting plugins can use the same set of methods to read and register the current consent category, allowing consent management plugins and other plugins to work together, improving compliance with privacy laws. WARNING: the plugin itself will not handle consent. It will show you how many plugins you have without Consent API support and will improve compliance on your site by ensuring smooth communication between cookie banner plugins and plugins that set cookies or track user data. What problem does this plugin solve? Currently, it is possible for a consent management plugin to block third-party services like Facebook, Google Maps, Twitter, etc. But if a WordPress plugin places a PHP cookie, a consent management plugin cannot prevent this. Secondly, some plugins integrate the tracking code on the clientside in javascript files that, when blocked, break the site. Or, if such a plugin’s javascript is minified, causing the URL to be unrecognizable and won’t get detected by an automatic blocking script. Lastly, the blocking approach requires a list of all types of URL’s that tracks data. A generic API where plugins adhere to can greatly facilitate a webmaster in getting a site compliant. Does usage of this API prevent third-party services from tracking user data? Primary this API is aimed at compliant first-party cookies or tracking by WordPress plugins. If such a plugin triggers, for example, Facebook, usage of this API will be of help. If a user embeds a Facebook iframe, a blocking tool is needed that initially disables the iframe and or scripts. Third-party scripts have to blocked by blocking functionality in a consent management plugin. To do this in core would be to intrusive, and is also not applicable to all users: only users with visitors from opt-in regions such as the European Union require such a feature. Such a feature also has a risk of breaking things. Additionally, blocking these and showing a nice placeholder requires even more sophisticated code, all of which should in my opinion not be part of WordPress core, for the same reasons. How does it work? There are two indicators that together tell if consent is given for a specific consent category, e.g., “marketing”: 1) the region based consent_type, which can be opt-in, opt-out, or other possible consent_types; 2) and the visitor’s choice: not set, allow, or deny. The consent_type is a function that wraps a filter, “wp_get_consent_type”. If there’s no consent management plugin to set it, it will return false. This will cause all consent categories to return true, allowing cookies to be set on all categories. If opt-in is set using this filter, a category will only return true if the value of the visitor’s choice is “allow”. If the region based consent_type is opt-out, it will return true if the visitor’s choice is not set or is “allow”. Clientside, a consent management plugin can dynamically manipulate the consent type and set several cookie categories. A plugin can use a hook to listen for changes or check the value of a given category. Categories and most other stuff can be extended with a filter. Existing integrations Categorized, and sorted alphabetically Example plugin Example plugin. The plugin basically consists of a shortcode, with a div that shows a tracking or not tracking message. No actual tracking is done 🙂 Consent Management Providers Abconsent Sirdata CMP. Beautiful Cookie Consent Banner. Clickio Consent Cookie Consent CMP. Complianz GDPR/CCPA. Consent Studio. consentmanager. Conzent. Cookiebot. CookieFirst. CookieHub. CookieTractor. CookieYes – Cookie Banner for Cookie Consent. GDPR Cookie Compliance. GDPR Cookie Consent Plugin – CCPA Ready. GetTerms. iubenda | All-in-one Compliance. Lawwwing. Pressidium Cookie Consent. TrustArc Cookie Consent Manager Consent Requiring Plugins AddToAny. AFL UTM Tracker Plugin. Burst Statistics. Google Site Kit. Pixel Manager for WooCommerce. Woo. WP Statistics. Demo site wpconsentapi.org Below are the plugins used to set up the demo site: Complianz The example plugin javascript, consent management plugin //set consent type window.wp_consent_type = 'optin' //dispatch event when consent type is defined. This is useful if the region is detected server side, so the consent type is defined later during the pageload let event = new CustomEvent('wp_consent_type_defined'); document.dispatchEvent( event ); //consent management plugin sets cookie when consent category value changes wp_set_consent('marketing', 'allow'); javascript, tracking plugin //listen to consent change event document.addEventListener("wp_listen_for_consent_change", function (e) { var changedConsentCategory = e.detail; for (var key in changedConsentCategory) { if (changedConsentCategory.hasOwnProperty(key)) { if (key === 'marketing' && changedConsentCategory[key] === 'allow') { console.log("just given consent, track user") } } } }); //basic implementation of consent check: if (wp_has_consent('marketing')){ activateMarketing(); console.log("set marketing stuff now!"); } else { console.log("No marketing stuff please!"); } PHP //declare compliance with consent level API $plugin = plugin_basename( __FILE__ ); add_filter( "wp_consent_api_registered_{$plugin}", '__return_true' ); /** * Example how a plugin can register cookies with the consent API * These cookies can then be shown on the front-end, to the user, with wp_get_cookie_info() */ function my_wordpress_register_cookies(){ if ( function_exists( 'wp_add_cookie_info' ) ) { wp_add_cookie_info( 'AMP_token', 'AMP', 'marketing', __( 'Session' ), __( 'Store a unique User ID.' ) ); } } add_action('plugins_loaded', 'my_wordpress_register_cookies'); if (wp_has_consent('marketing')){ //do marketing stuff } Service-level consent In addition to category-based consent, the API supports service-level consent control. This allows consent management plugins to grant or deny consent for specific services (like ‘google-analytics’ or ‘facebook-pixel’) independently from their category. When checking service consent with wp_has_service_consent(), the API first checks if explicit consent exists for that service. If no explicit consent is set, it falls back to the consent status of the service’s category. This enables fine-grained control: a user might accept statistics cookies in general, but explicitly deny a specific analytics service. Service consent can be checked and set both server-side (PHP) and client-side (JavaScript): PHP: //check if a specific service has consent if ( wp_has_service_consent( 'google-analytics' ) ) { //activate google analytics } //check if a service is explicitly denied if ( wp_is_service_denied( 'facebook-pixel' ) ) { //service was explicitly denied by user } //set service consent wp_set_service_consent( 'google-analytics', true ); //grant consent wp_set_service_consent( 'facebook-pixel', false ); //deny consent //listen for service consent changes add_action( 'wp_consent_service_changed', function( $service, $consented ) { error_log( "Service {$service} consent changed to: " . ( $consented ? 'granted' : 'denied' ) ); }, 10, 2 ); JavaScript: //check service consent if ( wp_has_service_consent( 'youtube' ) ) { //activate tracking } //check if explicitly denied if ( wp_is_service_denied( 'facebook-pixel' ) ) { //service denied } //set service consent wp_set_service_consent( 'youtube', true ); //listen for service consent changes document.addEventListener( 'wp_consent_api_status_change_service', function( e ) { console.log( 'Service: ' + e.detail.service + ', consented: ' + e.detail.value ); }); Any code suggestions? We’re on GitHub as well!
