ማብራሪያ

Jane is an eCommerce company that operates in the US and Canada.

Our customers are stores, and our software connects to their POS systems, syncs in their product catalog, and creates an online storefront where end users can shop for products.
When a user makes a purchase, we push data back to the POS system so that the customer can either pick up the order in-store or get their order delivered.

This plugin allows our customers to easily deploy Jane menus into their websites

External services

This plugin displays a store menu provided by Jane, and uses Algolia to look up product details for page metadata. It does not work without them.

Jane

Jane runs the store menu this plugin embeds.

When a visitor opens a page you have set up as a store menu, your site’s server requests the menu from the Proxy URL you entered in Store Configs, usually on api.iheartjane.com. The request is made on every such page view. It contains only that URL and standard request headers, which include your site’s address. The plugin sends no information about the visitor.
On product pages (a URL containing /products/<id>/), your site’s server also requests the store’s public profile from Jane to fill the page’s og:site_name tag. The request contains the Jane store ID.
When an administrator enters a Proxy URL on the Add New or Edit screen, your site’s server requests that URL to check that it matches the page’s path.
The menu is Jane’s storefront application. It runs in the visitor’s browser and loads from Jane’s servers, so Jane receives what the visitor does in it, including browsing, cart, and checkout details such as the contact and order information they enter. The storefront may also load third-party services for fonts, analytics, advertising measurement, and payment processing, as described in Jane’s privacy policy.

Jane terms of service: https://www.iheartjane.com/terms
Jane privacy policy: https://www.iheartjane.com/privacy-policy

Algolia

Jane’s product catalog is served through Algolia’s search service.

On product pages, your site’s server queries Algolia (algolia.net) for the product’s name, brand, description, and image, to set the page title and social sharing tags. The request contains the Jane store ID and product ID, and no information about the visitor.

Algolia terms of service: https://www.algolia.com/policies/terms/
Algolia privacy policy: https://www.algolia.com/policies/privacy/

Reviews

There are no reviews for this plugin.

Contributors & Developers

“Jane Menu” is open source software. The following people have contributed to this plugin.

Translate “Jane Menu” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

1.5.1

Fixed: The sitemap index line in robots.txt could be joined onto the previous line when another plugin or host removed the trailing line break.
Fixed: On multisite, generating robots.txt could leave the request on a different site than the one it started on.

1.5.0

Security: Strengthened permission checks in the plugin’s admin screens. Updating is recommended.
Hardened input sanitization and output escaping, and resolved WordPress Plugin Check findings across the plugin.
Fixed: Saving a store config for a page without a store path, or whose page returns an empty response, showed a fatal error instead of a message.
Fixed: An empty response from the Jane proxy caused a fatal error on the store menu page and when verifying a store path.
Tested with WordPress 7.1

1.4.8

Added: Errors that occur during rendering will now be sent to the error log

1.4.7

Tested with WordPress 6.7.2

1.4.6

Fixed: Permalink manager bug preventing editing menu configs

1.4.5

Added: Smartcrawl support
Added: Support hierarchical content types
Added: Overwrite permalink manager
Fixed: Bug with WP_Sitemaps_Provider implementation

1.4.4

Intentionally skipped due to partner modifications

1.4.3

Fixed: PHP 7.4 compatibility

1.4.2

Added: Additional sitemap compatibility for Yoast plugin
Added: Product meta data in header
Fixed: Output from Yoast SEO removed

1.4.1

Intentionally skipped due to partner modifications

1.4.0

Intentionally skipped due to partner modifications

1.3.13

Fixed: Don’t add custom content to the page if it has already been added with shortcode

1.3.12

Fixed: Squirrly SEO Plugin canonical url compatibility
Fixed: Unnecessary query parameters removed from product canonical url
Fixed: Shortcode only gets injected once

1.3.11

Fixed: Rank Math Plugin canonical url compatibility
Fixed: SEO Press Plugin canonical url compatibility

1.3.10

Fixed: Fallback to the replacing the entire content if the shortcode is not present
Fixed: Yoast specific canonical filter set

1.3.9

Fixed: Synchronize deployment discrepancy

1.3.8

Added: Inject a tag with the plugin version into the tag

1.3.7

Added: Wrap the tag with Jane Menu Plugin

1.3.6

Added: Warning message is now displayed in the admin, if other plugins are detected to be filtering ‘get_canonical_url’
Fixed: If current page/post is a Jane Menu, the full canonical_url is properly set, otherwise WordPress handles.

1.3.5

Added: Support for any Custom Post Type
Fixed: The shortcode [jane_menu_shortcode] is now the only way to output the body HTML, but can be used outside of the_content(), eg. with do_shortcode()

1.3.4

Intentionally skipped due to partner modifications

1.3.3

Added: The Sitemap index location in Settings
Fixed: The Sitemap index gets generated even if the plugin is updated

1.3.2

Added: Sitemap index with remote sitemap URLs generated in the uploads folder
Added: The compatibility feature for Yoast where canonical URLs are not used on pages with store menus
Fixed: The issue where sites with Elementor wouldn’t display the menu

1.3.1

Added: Store menu gets injected into the existing page instead of overwriting it
Added: The shortcode [jane_menu_shortcode]

1.3.0

First published version on WordPress.org
Old plugin rewritten from scratch with a new structure encapsulated in namespaces
Store paths are defined by selecting and existing Page instead of custom relative paths