Early Access Features

Test new JReviews features before they become the default

#Overview

Early Access in JReviews 6 allow us to take an incremental approach towards modernization. As we continue to re-write other areas of the JReviews frontend, these will also be included in Early Access. The features are opt-in, so you can easily upgrade from JReviews 5 without having to make any changes.

#How to Enable Features

Early Access features can be enabled in the JReviews administration. Many features feature can be enabled independently, allowing you to test specific improvements without affecting other parts of your site.

#Available Features

#New Listing Detail Page

• Complete rewrite that also includes rewrites for listing detail page addon integrations
• New listing media manager
• New map features: full screen control, automatic KML/GPX/GeoJSON attachment loading as route layers. New elevation profile when elevation data is detected, and a route player/scrubber map control
• New comment/review form

#New Listing Form

• Integrated media uploads allowing creating/updating listings and uploading media in the same form

#Structured Data Setup

• New administration page for mapping custom fields to Schema.org properties
• Uses of LD+JSON format tag independent of listing detail page template
• Only works when new listing detail page is enabled

#PaidListings Checkout

• New streamlined checkout one-step checkout flow. When using the new checkout experience that is automatically activated with the new listing detail page, there are some required changes needed for the PayPal and Stripe integrations:
  • Updated PayPal integration to use the modern PayPal hosted checkout experience. This requires Details on new setup requirements can be found within the PayPal handler settings in PaidListings
  • Updated Stripe integration. Handler settings remain the same, but the integration now only uses two Stripe events. The events names are listed in the Stripe handler setting and need to be enabled for your webhook in the Stripe developer dashboard.

#JSON Query Builder

• Replacing the custom where and custom order settings, there's a new JSON-based custom query builder
• At this time the setting is only available for the detail page related listing widgets and used when the new listing detail page is enabled in early access

Read JSON Query Builder documentation →

#Customizations

• The listing detail page, listing form, and PaidListings checkout use a new template system (Blade) and language system (PHP arrays) that differ from the legacy JReviews 3/5 approach
• Old .thtml templates and .po language files will not work with these Early Access features

Read customizations documentation →

#Developer Hooks

• Similar to the template system, the re-written functionality also implements a new system for hooks. This means that any previous hooks available for the listing detail page and listing form will not work when the early access versions are enabled. There is already a long list of new hooks implemented to replace the previous ones.

Read hooks documentation → | Browse all v6 hooks →

#Blade Template Formatting for Custom Fields

When the new listing detail page is enabled, custom field output formatting uses a new Blade template system that replaces the legacy PHP format system. The Blade template system uses different syntax and variables than the PHP format system.

Who is affected: Only users who have added custom code in individual custom field's Advanced Settings using the "PHP output format" editor or "Field output template" dropdown. Fields without custom code in these settings continue working normally.

Important: When you enable Early Access, custom code in "PHP output format" and "Field output template" will be ignored. These fields will fall back to their "Output format" setting (the simpler HTML/tags option) until you migrate the code to Blade syntax using the new "Blade template code" and "Field output Blade template" settings.

Read Custom Field PHP Formatting documentation →

#Migrating Existing Customizations

If you have existing customizations for listing detail pages or listing forms, review this checklist before enabling Early Access features:

• [ ] Template overrides - Review documentation to migrate your .thtml customizations to the new Blade template system. See customization guide →
• [ ] Language string overrides - Review documentation to migrate your .po language customizations to the new PHP array system. See language overrides →
• [ ] Hooks - Review documentation to migrate your hooks to the new hook system. See hook migration guide →
• [ ] Custom field PHP formatting - If you have custom code in "PHP output format" or "Field output template" settings, migrate to Blade syntax. See PHP formatting migration guide →