I’m not sure if this has already been shared; I didn’t see anything about it here, so I thought I’d post it just in case

When using the Listings Adv. Filtering widget and enabling a custom field as a filter in Theme Customization, for example, using: [filter name="jr_color"]

JReviews generates URLs with parameters like:  /category/?jr_color=red

From an SEO point of view, it’s usually better not to index these filtered URLs to avoid duplicate content and diluted category authority.

In my case I kept:

* Categories → indexable

* Listings → indexable

* Filter URLs → noindex, follow

I added this small snippet to the theme's functions.php:

add_action('wp_head', function() {
    if (!empty($_GET)) {
        echo '<meta name="robots" content="noindex, follow">' . "\n";
    }
});

Everything works perfectly and doesn’t affect JReviews functionality at all.

Hope it helps someone

i'm inspired from the latest yootheme pro template Oakville within the article map view for joomla. i have the idea to show listings from jreviews on the map element, as it is shown here:
https://demo.yootheme.com/joomla/themes/oakville/living-in-oakville/oakville-map

In this demo, the items have all been stored manually. So my goal would be to display them automatically using the YooTheme Pro add-on from jreviews listings.  To do this, I have combined my custom fields for jr_latitude and jr_longitude in a banner field for output in order to use this in the YooTheme page builder element in the dynamic source.
Has anyone already tried this and got it to work to show listings from jreviews within the yootheme map element?

Right now, no listings are displayed, and I suspect that this may have something to do with the output of the coordinates: by default, the map element uses this format for the coordinates: "44.3046100,15.4769690". However, from the banner field, I get this formatting: "44.3046100 ,15.4769690": the difference is the space before the comma.

This is not a full marketplace implementation, but a lightweight, centralized setup designed for a specific use case.

In short, this code does the following:

1. Listings are created by users (each listing belongs to a seller)
2. Sellers can optionally enable a “Shop now” button using a custom radio field
3. The button only appears if: "a price is set" and "a supported shipping option is selected"
4. Shipping is chosen from a predefined list (package size/weight), and the actual cost is calculated in PHP
5. Clicking the button redirects the buyer to a custom Stripe Checkout session
6. The platform receives the payment first and handles delivery confirmation and payouts later

This results in a lightweight, centralized marketplace flow: no carts, no WooCommerce, no forced checkout, just listings with an optional purchase path.

Below is a simplified example of the template logic used to display the button.

Step 1: Define price and shipping using custom fields

The first step was to define price and shipping logic using JReviews custom fields.

I created:

1. A decimal custom field for the product price
2. A single-select custom field for shipping, where the listing owner selects a predefined package type (size/weight)

The shipping example shown here works for my specific use case, where shipping is limited to a single country. Shipping costs are predefined and managed centrally, which keeps the setup simple.

Different setups may require different shipping logic depending on their needs.

Step 2: Conditional “Shop now” button in details.thtml

In this step, I add a conditional “Shop now" button to the listing detail page.

The "Shop now" button:

1. Is optional and controlled by the listing owner using a radio custom field (“activate / don’t activate”).
2. Only appears if a valid price and a supported shipping option are set
3. Calculates the shipping cost internally based on a predefined option
4. Redirects the buyer to a custom Stripe Checkout endpoint

This keeps checkout logic centralized and avoids exposing pricing rules to users.

<?php
$payment_option = $CustomFields->fieldValue('jr_opcionescobrar', $listing);
$precio_raw     = $CustomFields->fieldValue('jr_precio', $listing);
$opcion_envio   = $CustomFields->fieldValue('jr_gastosdeenvioespana', $listing);

$precio = (float) str_replace(',', '.', $precio_raw);

// Predefined shipping prices (mapped internally)
$precios_envio = [
    'envio-gratis'        => 0,
    'envio-ligero'        => 2.95,
    'paquete-pequeno'     => 4.95,
    'paquete-mediano'     => 6.95,
    'paquete-grande'      => 8.95,
    'voluminoso-especial' => null
];

// Resolve shipping cost
$envio = null;
if (isset($precios_envio[$opcion_envio])) {
    $envio = $precios_envio[$opcion_envio];
}

/* ----------- start internal CTA ------------ */

// Show button only if secure payment is enabled
// and the listing has valid price + supported shipping
if (
    $payment_option === 'pago-seguro'
    && $precio > 0
    && $envio !== null
) :

    $url_pago = home_url('/pago-seguro?') . http_build_query([
        'anuncio_id'  => (int) $listing['Listing']['listing_id'],
        'precio'      => $precio,
        'envio'       => $envio,
        'titulo'      => sanitize_text_field($listing['Listing']['title']),
        'artesano_id' => (int) $listing['Listing']['user_id']
    ]);
?>
<p>
    <a class="wp-block-button__link wp-element-button"
       href="<?php echo esc_url($url_pago); ?>"
       style="display:block;width:100%;text-align:center;"
       aria-label="Shop now">
        <strong>Shop now</strong>
    </a>
</p>
<?php endif; ?>

Step 3: Create a Stripe Checkout session

This endpoint is called when the buyer clicks the “Shop now” button.

Its responsibility is intentionally small and focused:

1. Receive the listing data from the button (ID, price, shipping, seller)
2. Build Stripe line items for product and shipping
3. Create a Stripe Checkout Session
4. Redirect the buyer to Stripe to complete the payment

The buyer only pays product + shipping.
No marketplace fees are shown during checkout.

<?php
/**
 * Technical endpoint to create a Stripe Checkout session
 * This is not a visual page and does not load headers or footers
 */

// Load Stripe
require_once get_template_directory() . '/stripe/init.php';

// Stripe API key (stored in wp-config.php)
\Stripe\Stripe::setApiKey(STRIPE_SECRET_KEY);

// ===============================
// Read parameters from the button
// ===============================
$anuncio_id  = isset($_GET['anuncio_id']) ? (int) $_GET['anuncio_id'] : 0;
$precio      = isset($_GET['precio']) ? (float) str_replace(',', '.', $_GET['precio']) : 0;
$envio       = isset($_GET['envio']) ? (float) str_replace(',', '.', $_GET['envio']) : 0;
$titulo      = isset($_GET['titulo']) ? sanitize_text_field($_GET['titulo']) : 'Product';
$artesano_id = isset($_GET['artesano_id']) ? (int) $_GET['artesano_id'] : 0;

// ===============================
// Basic validation
// ===============================
if ($anuncio_id <= 0 || $precio <= 0) {
    wp_die('Invalid payment parameters.');
}

// ===============================
// Build Stripe line items
// ===============================
$line_items = [];

// Product
$line_items[] = [
    'price_data' => [
        'currency' => 'eur',
        'product_data' => [
            'name' => $titulo,
        ],
        'unit_amount' => (int) round($precio * 100),
    ],
    'quantity' => 1,
];

// Shipping
if ($envio > 0) {
    $line_items[] = [
        'price_data' => [
            'currency' => 'eur',
            'product_data' => [
                'name' => 'Shipping',
            ],
            'unit_amount' => (int) round($envio * 100),
        ],
        'quantity' => 1,
    ];
}

// ===============================
// Create Stripe Checkout session
// ===============================
try {

    $session = \Stripe\Checkout\Session::create([
        'locale' => 'es',
        'mode' => 'payment',
        'payment_method_types' => ['card'],
        'line_items' => $line_items,

        'success_url' => home_url('/gracias-por-tu-compra/?session_id={CHECKOUT_SESSION_ID}'),
        'cancel_url'  => home_url('/pago-cancelado/'),

        'metadata' => [
            'anuncio_id'  => $anuncio_id,
            'artesano_id' => $artesano_id,
            'buyer_id'    => get_current_user_id(),
        ],

        'customer_creation' => 'always',

        'shipping_address_collection' => [
            'allowed_countries' => ['ES'],
        ],

        'phone_number_collection' => [
            'enabled' => true,
        ],
    ]);

    // Redirect to Stripe Checkout
    wp_redirect($session->url);
    exit;

} catch (\Exception $e) {
    wp_die('Error creating payment: ' . esc_html($e->getMessage()));
}

Final notes: 

The checkout flow also relies on standard WordPress pages for handling success and cancellation states (for example “Payment successful” and “Payment cancelled”), which are used as return URLs from Stripe Checkout.

The endpoint file lives in themes/your-theme/

The Stripe PHP library is included inside the theme (for example in themes/your-theme/stripe/)

The Stripe secret key is defined in wp-config.php

define('STRIPE_SECRET_KEY', 'your key here');

1. Download this free quality plugin https://extensions.joomla.org/extension/akeeba-sociallogin/

2. create override file for /components/com_jreviews/jreviews/views/themes/default/elements/_signup.thtml 

3. add the plugin button codes to the position you like

<?php if (class_exists('Akeeba\\SocialLogin\\Library\\Helper\\Integrations')) 
  echo \Akeeba\SocialLogin\Library\Helper\Integrations::getSocialLoginButtons(cmsFramework::getCurrentUrl()) ?>

1. EasySocial

OK, this was a tough decision. EasySocial is an incredible component that cannot be replicated and I knew Jreviews would not be able to replace it. I have thousands of registered users, and most of them had avatars and cover images and activity from when I was allowing social media registrations (which I stopped allowing in 2021). The community was large even though most people never did anything more than sign up and ask a question in the forum or post a picture in the community. It's really incredible what StackIdeas has done with EasySocial but for my particular case I didn't think it was worth maintaining anymore. My community was not active so I just ended up with thousands of stale community pages covering photo albums, forum posts, etc... There was zero interaction between users. I had no choice but to totally nuke it. I deleted the component, did a wildcard redirect of all ES pages to my forum, and left it at that. I would have loved to have built a bustling, active community but it just wasn't happening. EasySocial was/would have been perfect for that. Since it wasn't happening for me, I chose the nuclear option. The only thing I have replaced it with is Jreviews Engage Users and Jreviews User Profiles which gives me author profile functionality, a site activity stream, and the ability for users to subscribe to categories and posts. That's about 1% of what EasySocial is capable of, but it's fine for my particular case.

2. EasyBlog

This was an easy decision to make, and while Jreviews is not considered blogging software it gets the job done just fine (and much better than core Joomla). I have 255 blog posts and researched the possibility of migrating, but there is no direct migration from EB to core Joomla. All of the migration options involved migrating through another 3rd-party component such as K2. If I had thousands of blog posts I would have set up a migration somehow, but given the relatively low number of blog articles to port, I decided to bite the bullet and do it manually. Ctrl-C/Ctrl-V 255 times. At least that way I was able control the control URLs and review the content while I was re-building the blog. Here is an example of a Jreviews blog post: https://coinvalues.com/blog/to-my-young-brothers-and-sisters-at-reddit. This one has a couple of comments (which were in Komento). I'll get to the Komento migration later.

3. EasyDiscuss

This was also an easy decision since Jreviews and its comment system (read: reviews without ratings) is perfectly tailored to a user post followed by chronologically-ordered comments. Once again, I decided to do this manually for 221 forum posts. Here is an example: https://coinvalues.com/forum/1955-silver-wheat-penny. That post has a few replies and you can see how seamlessly users can comment and upload images. I miss being able to tag and quote people but for my purposes Jreviews is perfectly adequate for my forum.

4. Komento

This is the migration I dreaded. Komento is a great commenting component and while I knew it wouldn't be a problem to replace my EB comments with Jreviews comments, I have a series of coin info sheets that are the bread and butter of my site, and many of them get comments. Most of the comments are in the form of questions and the ability of Komento to nest comments allowed me to show the parent comments and their replies in reverse chronological order where the most recent was first. You see, my site deals with coin values, and values of coins change constantly. I absolutely cannot have the oldest comment as the first with pricing information from 10 years ago. Therefore I couldn't use the simplistic approach I used for the forum because if I ordered comments chronologically, the "Answers" would be shown before the "Questions". I knew Jreviews was just not going to be able to replace Komento 1:1. The lack of nested comments in Jreviews was really presenting me with a problem here. And that's fine, because Jreviews is not commenting software. As much as I have always hated the "review discussion" functionality of Jreviews where it takes you to a separate page to see the replies to reviews (which is fine and the way it should be for review comments but sucks for general commenting), I quickly realized that format would fit my "Q&A" sessions quite well. So, for each of the hundreds of comments I had in Komento, I took each original comment and made it a review (without ratings of course). And each nested reply in Komento I made it a review discussion for the original "review". It's not ideal but it turns out that it works pretty well for my site. Here is an example of how a Jreviews "review detail" page can be a valuable Q&A page after I lost access to nested commenting from Komento: https://coinvalues.com/kennedy-half-dollar/1964. That is a coin info sheet with two questions, each having various answers. Again, not ideal, but I am happy with the result. Many of these Q&A "review detail" pages are getting search hits from Google now. 

5. Post-Data

As stated above, this is not an anti-StackIdeas post. However, since my main reasons for doing this were to simplify and optimize the site and reduce my dependence on 3rd-party software, I will show you some data of the size of my Akeeba backup:

Backup size went from 290MB to 104MB after uninstalling EasySocial, EasyDiscuss, EasyBlog, Komento, and deleting media folders.
Backup size went from 104MB to 63MB after dropping EasySocial, EasyDiscuss, EasyBlog, and Komento database tables.

That's a 129% reduction in size!

This change also greatly reduced the number and size of JS files that were blocking page rendering. The speed increase I saw after performing this change was notable. It even inspired me to completely rethink my entire web footprint strategy. I was using AWS EC2 as a server, RackSpace for email, and GoDaddy for DNS. Well, I nuked RackSpace and GoDaddy as well, and now have my entire web ecosystem in AWS. I placed the EC2 instance behind a load balancer and added a WAF with a load of security protections and the site is faster and more secure than ever. And as a bonus I have eradicated the bot traffic from China that had exploded in volume in September which was skewing my Analytics data.

To close I would like to send a hearty thank you to Alejandro at Jreviews for this wonderful software which has allowed me to do incredible things for my own site as well as my former clients' sites over the years, as well as a shout out to Mark at StackIdeas (I believe he is no longer part of the organization) for years of great software and support.

I would like to suggest you add /modules/ and /libraries/ to the proposed robots.txt you posted in that Announcement, to cover customers who use libraries like Gantry and modules like JFBConnect, EasySocial & AJAX Search. Also don't forget about the JReviews AJAX trigger (first line below):

User-agent: Mediapartners-Google
Allow: /
User-agent: *
Allow: /index.php?option=com_jreviews&format=ajax
Allow: /components/*.js
Allow: /components/*.css
Allow: /components/*.png
Allow: /components/*.jpg
Allow: /components/*.gif
Allow: /components/*.woff
Allow: /components/*.svg
Allow: /components/*.eot
Allow: /components/*.ttf
Disallow: /components/
Allow: /templates/*.js
Allow: /templates/*.png
Allow: /templates/*.jpg
Allow: /templates/*.gif
Allow: /templates/*.css
Allow: /templates/*.woff
Allow: /templates/*.svg
Allow: /templates/*.eot
Allow: /templates/*.ttf
Disallow: /templates/
Allow: /media/*.js
Allow: /media/*.css
Allow: /media/*.png
Allow: /media/*.jpg
Allow: /media/*.gif
Allow: /media/*.woff
Allow: /media/*.svg
Allow: /media/*.eot
Allow: /media/*.ttf
Disallow: /media/
Allow: /images/*.png
Allow: /images/*.jpg
Allow: /images/*.gif
Disallow: /images/
Allow: /modules/*.js
Allow: /modules/*.css
Allow: /modules/*.png
Allow: /modules/*.jpg
Allow: /modules/*.gif
Allow: /modules/*.woff
Allow: /modules/*.svg
Allow: /modules/*.eot
Allow: /modules/*.ttf
Disallow: /modules/
Allow: /libraries/*.js
Allow: /libraries/*.css
Allow: /libraries/*.png
Allow: /libraries/*.jpg
Allow: /libraries/*.gif
Allow: /libraries/*.woff
Allow: /libraries/*.svg
Allow: /libraries/*.eot
Allow: /libraries/*.ttf
Disallow: /libraries/
Disallow: /administrator/
Disallow: /cache/
Disallow: /cli/
Disallow: /includes/
Disallow: /installation/
Disallow: /language/
Disallow: /logs/
Disallow: /plugins/
Disallow: /tmp/
Disallow: /?
Disallow: /component/
Disallow: /images/sampledata/
Disallow: /images/watermarks/
Disallow: /*by:
Disallow: /*order:
Disallow: /*type:
Disallow: /*user:
Disallow: /*view:
Disallow: /*by=
Disallow: /*order=
Disallow: /*type=
Disallow: /*user=
Disallow: /*view=
Disallow: /*month=
Disallow: /*url=
Disallow: /*wid=
Disallow: /*?searchword
Disallow: /*search-results?=
Disallow: /*sort=
Disallow: /*option=
Disallow: /*component/content/article
Disallow: /component/jreviews/upload/
Disallow: /?page

From "Disallow: /?" on down are some of my suggestions to stay out of trouble with some common Joomla SEO pitfalls and also prevent so many JReviews pages getting indexed, for example all the ordered pages. Be sure to remove any of the lines of items you would prefer to be indexed.

I think this is a pretty good robots.txt for JReviews users. If anyone has anything to add/criticize feel free to share.

i have a custom fields with more then 250 options (A) and i am looking to create custom listings pages in combination with the other custom field B (15 options)

Do i need to create 250 x 15 menus items manualy or there is a way to automate ? 

Clickfwd\Hook\Filter::add('listing_save_pre', function($data, $params) 
{

    if (! $params['is_new']) {
            return $data;
    }
    else {

        // Get the category
        $category = $data["Listing"]["catid"];

        switch ($category) {

            case "18": // Alaska
                $data["Field"]["Listing"]["jr_location"][0] = "172"; // North America
                $data["Field"]["Listing"]["jr_location"][1] = "171"; // United States
                $data["Field"]["Listing"]["jr_location"][2] = "47"; // Alaska

            break;
            case "21": // Alberta
                $data["Field"]["Listing"]["jr_location"][0] = "172"; // North America
                $data["Field"]["Listing"]["jr_location"][1] = "1086"; // Canada
                $data["Field"]["Listing"]["jr_location"][2] = "50"; // Alberta
            break;
	//case "":
	//break;
            default:
                      return $data;
                  }
        return $data;
    }
});

Change out each case with the category id you'd like to assign related listing data to. It was helpful to create a master index list so I could quickly copy each id and would write as much code as possible without data such as $data["Field"]["Listing"]["jr_location"][] = "" so that I only had to place in the listing id's and index arrays. Alternatively could keep each full index for each listing followed by leaving the index blank for a quick copy and paste fest. You can do this for other custom fields, default locations such as coordinates. Can easily be done for multi-select variations too.

Have any of you guys used one of these programs to translate your JReviews site into a different language:

GTranslate

Pro gtranslate.io Budget-friendly, good compatibility, quick setup, requires Pro version for SEO features.

Weglot weglot.com

Premium SaaS solution, very high quality, excellent SEO support, but slightly more expensive.

Linguise linguise.com

Solid mid-range option, full SEO support, good pricing for large websites, fast performance.

Any advice?

I tried in output format but dont work

I would like to know if it’s possible to limit the use of certain addons to specific Joomla user groups (for example, only premium members).

More specifically, I want to restrict access to the following addons:

• MyLists (create and manage lists)
• ListingResource (add external links)
• EngageUsers (Receive notification)
• Dashboard (I saw that this one can be managed using access permissions for the Analytics page as its a separate page)

Seems that JReviews dont offer a built-in way to handle this, any idea to achieve this would with external solution or customization?
If you has already set up this kind of restriction, I would really appreciate any advice or pointers.

Thanks in advance for your help!

It's super fast, super fair and super convenient! 🙃

Alejandro wrote most of the following code and gave me great pointers/code blocks to make it work for listing media. I simply wrote a loop, a few conditions, object buffer, and minor formatting to make it work for uploaded media. Be sure your Media Settings > Attachments > Allowed File Extensions allow: json, geojson so that file.geojson can upload.

/* Add geojson support to module/widget */

/* Ref: https://gist.github.com/jreviews/4f85f94606f7dc41c15c1318cb586e92 */

function add_geojson_layer_to_map_module($output, $params)
{
	$asset_manager = S2Object::make('asset_manager');
	
	// Add the current listing jrMedia paths to an array
	$request = new FWD\Illuminate\Http\Request($params['params']);
	
	if ($request->option != 'com_content' || $request->view != 'article' || ! $request->id) {
		return $output;
	}

	$attachments = JReviews\App\Models\Media::query()
			->attachment()
			->published()
			->where('listing_id', $request->id)
			->get();

	$urls = $attachments->pluck('original')->toArray();
    
    ob_start();
    foreach ($urls as $map_source) {
      if ( str_ends_with($map_source, '.geojson') ) {
          $geojson_file_source = ltrim($map_source, '/');
          echo "{ filename: '$geojson_file_source' }, ";
      }
    }
    $geojson_file = ob_get_contents();
    ob_end_clean();
    
    // load the page script

	$script = "
	<script>
	const jrGeojsonStyles1 = function(feature) {
		switch (feature.properties.type) {
			case 'Type 1': return {
				stroke: true,
				weight: 0.5,
				color: '#ff0000',
				fillColor: '#ff0000',
				fillOpacity: 0.3
			};
			case 'Type 2': return {
				stroke: true,
				weight: 1,
				color: '#09b838',
				fillColor: '#09b838',
				fillOpacity: 0.3
			};
			default: return {
				stroke: true,
				weight: 1,
				color: '#fcba03',
				fillColor: '#fcba03',
				fillOpacity: 0.3
			}
		}    	
	}
	const jrGeojsonStyles2 = function(feature) {
		return {
			color: '#ff7800',
			weight: 5,
			opacity: 0.65
		};
	}
	const layers = [
		$geojson_file

	];
    document.addEventListener('jr-map-initialized', function(event) {
    	console.log('Geojson Filter: map initialized');
    	layers.map(layer => jreviews.addGeoJSONLayer(event.target, layer))
    });
	jreviews.addGeoJSONLayer = function(target, layer) {	
		async function loadGeojson() {
			const response = await fetch('/'+layer.filename);
			const data = await response.json();
			return data;
		}    
		loadGeojson().then( (geojson) => {
			console.log('GeoJSON layer '+layer.filename+' was loaded');
			let map = jQuery(target).data('map');
			const options = {};
			if ( layer.stylesFn ) {
				options.style = layer.stylesFn;
			}
			L.geoJSON(geojson, options).addTo(map);
		});   
	};	
	</script>
	";

	return $output.$script;
}
 
Clickfwd\Hook\Filter::add('after_filter_output_module_maps_index', 'add_geojson_layer_to_map_module', 10);

Enjoy! 😊

1. Read through the notes on the document, they will guide you through the first few steps. 
2. Then, you will need to upload the attached "featured_random.php" file to jreviews_overrides/filters
3. Next, you need to call this filter for use by creating a filter_functions.php file with this: 

<?php
defined('MVC_FRAMEWORK') or die;

require 'featured_random.php';

Place this filter_functions.php file into the same /filters folder.

You may notice that your featured listings initially disappear, that is because they have no value. In order to start the script, run your cron script manually (just click on your cron script link), you should get a success message. You should see your featured listings at this point. If your page's featured listings don't shuffle order on their own after this then check your cron script.

This code works for me but can't guarantee that it will work for you. Make sure to take a full server backup before you begin since the first step has you modifying your database. 

Use this code at your own risk, what worked for me may not work for you.

Good Luck!

filter_functions.php

1. Via the PHPMYADMIN navigate to the database for the website with the modules you want to export

2. Navigate to _modules

3. Select the rows for the modules that you want to export

4. Scroll down to the bottom of the page/rows and click Export

5. Select Custom under Export method

6. Under Output check Rename exported databases/tables/columns and add the new database

7. Under Object creation options uncheck Add CREATE TABLE statement 

8. Then export as MySQL

9. Import the MySQL file into the _module table of the database for the new website

I've created a short screen capture video here of me doing this. Hopefully it saves you some time if you've got a bunch of modules that you need to export/import!

I have some custom fields (banner type) and instead of text links I want to display them as images. The closes I have got to displaying the image is with this code:

$photoLink = cmsFramework::route("index.php?option=com_easysocial&view=photo=s&type=user&uid={$listing['User']['user_id']}&Itemid=4964"); echo "<a href='{$photoLink}'><img src=\media\hotlinks\"homelogo.jpg\"  /></a>";

This link works but it doesn't display the actual image - just the missing image placeholder. 

I have followed the instructions here: https://www.jreviews.com/docs/custom-fields#change-anchor-text-for-website-field and also checked out some past posts on here but cannot get my code to work correctly. 

I have switched to using the new webp in Jreviews would this be a reason the image isn't showing?

I am on Joomla 4, Latest Jreviews and php 8.1

Kind regards

• keyID as API Key
• applicationKey as API Secret
• endpoint
• bucket names

This isn't a tutorial on using hooks. If you need help getting started refer to the Hooks developer documentation

<?php
defined('MVC_FRAMEWORK') or die;

Clickfwd\Hook\Action::add('inquiry_form_top', function($params)
{
	$Form = new FormHelper();
	?>
	<div class="jrFieldDiv">
	 
		<label for="jr-inquiry-phone">
			<?php __t("Phone Number");?><span class="jrIconRequired"></span>
		</label>
	 
		<?php echo $Form->text('data[Inquiry][phone]',[
			'id'=>'jr-inquiry-phone',
			'class'=>'jrText',
		]);?>
	 
	</div>

	<div class="jrFieldDiv">
	 
	    <label for="jr-inquiry-checkbox_example">
	    	<?php __t("Checkbox Example");?> <span class="jrIconRequired"></span>
	    </label>
	 
	    <?php echo $Form->checkbox('data[Inquiry][checkbox_example]',
	    	[
	    		'one'=>'One',
	    		'two'=>'Two',
	    		'three'=>'Three'
	    	],
	    	[
	    		'id'=>'jr-inquiry-checkbox_example',
	    		'option_class'=>'jr-option jrFieldOption',
	    	]
	    );?>
	 
	</div>

	<div class="jrFieldDiv">
	 
	    <label for="jr-inquiry-select_example">
	    	<?php __t("Select Example");?>:
	    </label>
	 
	    <?php echo $Form->select('data[Inquiry][select_example]',
	    	[
	    		''=>'Select Option', 
	    		'one'=>'One',
	    		'two'=>'Two',
	    		'three'=>'Three'
	    	],$selected = '',
	    	[
	    		'id'=>'jr-inquiry-select_example',
	    		'class'=>'jrSelect',
	    	]
	    );?>
	 
	</div>		

	<div class="jrFieldDiv">
	 
	    <label for="jr-inquiry-date_example">
	    	<?php __t("Date Example");?>
    	</label>
	 
	    <?php echo $Form->text('data[Inquiry][date_example]',[
	    	'id'=>'jr-inquiry-date_example',
	    	'class'=>'jrDate jr-date'
	    ]);?>
	 
	</div>	
	<?php
});

Clickfwd\Hook\Filter::add('inquiry_submit_validation', function($validation, $params)
{
	$required = [
		'phone' => 'Phone Number',
		'checkbox_example' => 'Checkbox Example',
		'select_example' => 'Select Example',
	];

	foreach($required as $key => $text)
	{
		$found = S2Array::get($params,"data.Inquiry.{$key}");

		if ( !$found ) 
		{
			$validation[] = "{$text} is required";
		}
	}

	return $validation;
}, 10);

Clickfwd\Hook\Action::add('inquiry_email_extra_fields', function($extra_fields, $params)
{
	$fieldLabels = [
		'phone' => 'Phone Number',
		'checkbox_example' => 'Checkbox Example',
		'select_example' => 'Select Example',
		'date_example' => 'Date Example'
	];

	if (empty($extra_fields))
	{
		return;		
	}

	foreach ($extra_fields as $key => $value):
	?>
		<p><?php echo $fieldLabels[$key]; ?>: <?php echo is_array($value) ? implode(', ',$value) : $value; ?></p>
	<?php
	endforeach;
});

A filter can help deal with this if you have a specific need different from the core functionality like redirecting the URLs to the detail page. Of course you can also add a wildcard line to your robots.txt file to tell search engines to stop indexing these pages if that's what you want.

Here's the redirect filter https://www.jreviews.com/docs/hooks/before_theme_render_viewvars

Clickfwd\Hook\Filter::add('before_theme_render_viewvars_discussions_review', function($viewVars, $params) 
{
	$url = \Joomla\CMS\Router\Route::_($viewVars['listing']['Listing']['url']);
	cmsFramework::redirect($url, 301);
  	die;
});

This goes in the jreviews_overrides/filters/filter_functions.php file per the documentation https://www.jreviews.com/docs/developers/hooks

First create an empty banner custom field with no description and the following php output format so the field is hidden by default.

return $text ?: false;

Then you can use the post list page and detail page query filter hooks to add an output for the banner field. 

Clickfwd\Hook\Filter::add('post_get_listings_listpage_query', function($listings, $params) 
{
  foreach($listings as & $listing) {
  	$listing['Field']['pairs']['jr_bannerfield']['description'] = 'your fantastically generated output';
  }

  return $listings;
});

Clickfwd\Hook\Filter::add('post_get_listing_detailpage_query', function($listing, $params)
{
  $listing['Field']['pairs']['jr_bannerfield']['description'] = 'your fantastically generated output';

  return $listing;  
});

If you do use an external API for this, making sure your calls are efficient or cached is outside the scope of this tip and the implementation is entirely up to the reader 😎.

Clickfwd\Hook\Filter::add('post_get_listing_detailpage_query', function($listing, $params) 
{
  foreach (['Cover', 'Logo'] as $function) {

    if (!isset($listing[$function])) continue;

    if ($listing[$function]['main_media']) {
       unset($listing['MainMedia']);
    }

    $listing['Media']['photo'][] = $listing[$function];
  }

  return $listing;
    
});

There's a bit of extra code there to ensure that if the photo is not only a cover or a logo, but also the main media, it also shows in the gallery in the detail page.

In cases where you might want to programmatically generate dynamic page headings, you can use the following filter combination. First it stores a copy of the original title, then it modifies the page heading. The stored copy of the original title needs to be restored in the second filter to be used by the dynamic Pate Title logic.

<?php

class JReviewsCustomHeadings {

	static $title;

	public function __construct()
	{
		Clickfwd\Hook\Filter::add('before_theme_render_viewvars', [$this, 'pageHeading']);
		
		Clickfwd\Hook\Filter::add('after_filter_output', [$this, 'pageTitle']);
	}

	public function pageHeading($viewVars, $params)
	{		
		if ($params['route'] == 'com_content.com_content_view') {
			/**
			 * You can easily replace a hardcoded value with a dynamic value coming from a custom field,
			 * or change the hardcoded value based on the listing type, category
			 */ 
			 // $postfix = $viewVars['listing']['Field']['pairs']['jr_titlepostfix']['value'][0] ?? '';
			$postfix = ' - with a postfix';

			static::$title = $viewVars['listing']['Listing']['title'];
			
			$viewVars['listing']['Listing']['title'] .= $postfix;
		}

		return $viewVars;
	}

	public function pageTitle($output, $params)
	{
		// Restore the listing title to original value to be used by Page Title logic for SEO
		if ($params['route'] == 'com_content.com_content_view') {
			$params['viewVars']['listing']['Listing']['title'] = static::$title;
		}

		return $output;
	}
}

new JReviewsCustomHeadings();

You can find the complete list of supported sites here https://wordpress.org/support/article/embeds/#list-of-sites-you-can-embed-from

To take advantage of this functionality in JReviews listings using a website field. Just add the following code in the PHP output format:

return $GLOBALS['wp_embed']->run_shortcode('[embed]'.$value.'[/embed]');

That's it. Now you can embed anything from the list of supported sites. Here's what comes out when I use "https://twitter.com/getJReviews"

I did make a small edit for this particular output by using the "height" attribute of the embed shortcode. So my code looks like this:

return $GLOBALS['wp_embed']->run_shortcode('[embed  height="300"]'.$value.'[/embed]');

Keep in mind that if this field is open to anyone submitting listings they will be able to paste URLs there for any of the supported sites. If you want to limit the functionality to specific sites you can use the field's validation regex setting. So for example, to limit the field to Twitter embeds only, the regex would look something like this:

^https://twitter.com(.*)

You can disable those links if you want directly within the add-on settings, and use code below to output the content directly within the profile page. The code can be added to your theme's functions.php file or to a custom plugin.

<?php

function jreviews_peepso_profile_header($active) {
  echo PeepSoTemplate::exec_template('general', 'navbar');
  echo PeepSoTemplate::exec_template('profile', 'focus', ['current'=> $active]);
  PeepSoTemplate::exec_template('activity', 'dialogs'); // Fix share button
}

function jreviews_peepso_profile_userid() {
    $profile = PeepSoProfile::get_instance();
    return $profile->user->get_id();
}

/**
 * Adds the My Listings, My Favorites and My Reviews links to profile navigation
 */
add_filter('peepso_navigation_profile', function($links) {
    $links['mylistings'] = [
        'label' => __( 'My Listings', 'jreviews' ), 
        'href' => 'mylistings',
        'icon' => 'gcis gci-file-alt'
    ];

    $links['myreviews'] = [
        'label' => __( 'My Reviews', 'jreviews' ), 
        'href' => 'myreviews',
        'icon' => 'gcis gci-star'
    ];

    $links['myfavorites'] = [
        'label' => __( 'My Favorites', 'jreviews' ), 
        'href' => 'myfavorites',
        'icon' => 'gcis gci-bookmark'
    ];

    return $links;
});

/**
 * Registers profile segment mylistings
 */
add_action('peepso_profile_segment_mylistings', function() {
    ?>

    <div class='peepso ps-page-profile'>
        <section id='mainbody' class='ps-page-unstyled'>
            <section id='component' role='article' class='ps-clearfix'>
                
                <?php echo jreviews_peepso_profile_header('mylistings'); ?>

                <div class="peepso-jreviews">
                    <?php
                    require_once( ABSPATH . 'wp-content/plugins/jreviews/jreviews/framework.php');

                    $query_vars = array('module'=> [],'data'=> []);

                    $params = [
                        'community' => 1,
                        'show_numbers'=> 0,
                        'listings_order' => 'latest',
                        'fields'=>'',
                        'summary' => 1,
                        'summary_words' => 50,
                        'show_category' => 0,
                        'tn_mode' => 'crop',
                        'tn_size' => '125x125',
                        'tn_show' => 1,
                        'tn_position' => 'left',
                        'columns' => 1,
                        'orientation' => 'horizontal',
                        'slideshow' => 0,
                        'slideshow_interval' => 6,
                        'limit' => 10,
                        'module_total' => 10,
                        'nav_position'=>'bottom',
                    ];

                    $query_vars['module'] = $params;

                    $query_vars['user'] = jreviews_peepso_profile_userid();

                    $query_vars['module_id'] = 'mylistings'.$query_vars['user'];

                    $query_vars[S2_QVAR_PAGE] = 1;

                    $query_vars['secret'] = cmsFramework::getConfig('secret');

                    $query_vars['token'] = cmsFramework::formIntegrityToken($query_vars, ['module','module_id','form','data'], false);

                    $query_vars['data']['controller'] = 'community_listings';

                    $query_vars['data']['action'] = 'mylistings';

                    $Dispatcher = new S2Dispatcher('jreviews');

                    $content = $Dispatcher->dispatch($query_vars);

                    echo $content;      
                ?>
                </div>

            </section>
        </section>
    </div>   

    <?php
});

/**
 * Registers profile segment myfavorites
 */
add_action('peepso_profile_segment_myfavorites', function() {
    ?>

    <div class='peepso ps-page-profile'>
        <section id='mainbody' class='ps-page-unstyled'>
            <section id='component' role='article' class='ps-clearfix'>
                
                <?php echo jreviews_peepso_profile_header('myfavorites'); ?>

                <div class="peepso-jreviews">
                    <?php
                    require_once( ABSPATH . 'wp-content/plugins/jreviews/jreviews/framework.php');

                    $query_vars = array('module'=> [],'data'=> []);

                    $params = [
                        'community' => 1,
                        'show_numbers'=> 0,
                        'listings_order' => 'latest',
                        'fields'=>'',
                        'summary' => 1,
                        'summary_words' => 50,
                        'show_category' => 0,
                        'tn_mode' => 'crop',
                        'tn_size' => '125x125',
                        'tn_show' => 1,
                        'tn_position' => 'left',
                        'columns' => 1,
                        'orientation' => 'horizontal',
                        'slideshow' => 0,
                        'slideshow_interval' => 6,
                        'limit' => 10,
                        'module_total' => 10,
                        'nav_position'=>'bottom',
                    ];

                    $query_vars['module'] = $params;

                    $query_vars['user'] = jreviews_peepso_profile_userid();

                    $query_vars['module_id'] = 'favorites'.$query_vars['user'];

                    $query_vars[S2_QVAR_PAGE] = 1;

                    $query_vars['secret'] = cmsFramework::getConfig('secret');

                    $query_vars['token'] = cmsFramework::formIntegrityToken($query_vars, ['module','module_id','form','data'], false);

                    $query_vars['data']['controller'] = 'community_listings';

                    $query_vars['data']['action'] = 'favorites';

                    $Dispatcher = new S2Dispatcher('jreviews');

                    $content = $Dispatcher->dispatch($query_vars);

                    echo $content;      
                ?>
                </div>

            </section>
        </section>
    </div>    
    
    <?php
});

/**
 * Registers profile segment myreviews
 */
add_action('peepso_profile_segment_myreviews', function() {
    ?>

    <div class='peepso ps-page-profile'>
        <section id='mainbody' class='ps-page-unstyled'>
            <section id='component' role='article' class='ps-clearfix'>
                
                <?php echo jreviews_peepso_profile_header('myreviews'); ?>

                <div class="peepso-jreviews">
                    <?php
                    require_once( ABSPATH . 'wp-content/plugins/jreviews/jreviews/framework.php');

                    $query_vars = array('module'=> [],'data'=> []);

                    $params = [
                        'community' => 1,
                        'reviews_order' =>'latest',
                        'show_numbers' => 0,
                        'fields' => '',
                        'show_comments' => 1,
                        'comments_words' => 50,
                        'tn_mode' => 'crop',
                        'tn_size' => '125x125',
                        'tn_show' => 1,
                        'tn_position' => 'left',
                        'orientation' => 'horizontal',
                        'slideshow' => 0,
                        'slideshow_interval' => 6,
                        'columns' => 1,
                        'limit' => 10,
                        'module_total' => 20,
                        'nav_position' => 'bottom'
                    ];

                    $query_vars['module'] = $params;

                    $query_vars['user'] = jreviews_peepso_profile_userid();

                    $query_vars['module_id'] = 'myreviews'.$query_vars['user'];

                    $query_vars[S2_QVAR_PAGE] = 1;

                    $query_vars['secret'] = cmsFramework::getConfig('secret');

                    $query_vars['token'] = cmsFramework::formIntegrityToken($query_vars, ['module','module_id','form','data'], false);

                    $query_vars['data']['controller'] = 'community_reviews';

                    $query_vars['data']['action'] = 'index';

                    $Dispatcher = new S2Dispatcher('jreviews');

                    $content = $Dispatcher->dispatch($query_vars);

                    echo $content;      
                ?>
                </div>

            </section>
        </section>
    </div>    
    
    <?php
});