Forum


Use Feature listing plugin in frontend

More
10 months 2 weeks ago #46641 by webaza
Hello,
there are any possibility to use the plugin Featured Listing in frontend?

I tryed to modify the file: j00005featured_listings.class.php

adding a line:

$jomres_menu->add_item(50, jr_gettext('_JRPORTAL_FEATUREDLISTINGS_TITLE', '_JRPORTAL_FEATUREDLISTINGS_TITLE', false), $task = 'featured_listings', 'fa-star');

But they show me on frontend the menu voice but when i click nothing happens, im redirected to dashboard.

Which files i have to modify?
Please give me a help.

Regards
More
10 months 1 week ago #46652 by Vince Wooll
That's because there's no j06002 task for featured listings, Webaza.

I assume that you're trying to use the plugin in the frontend as a super property manager?

Follow me on twitter
Do not send me PMs, if you need to contact me use the ticket system.
Read this before you customise Jomres files
More
10 months 1 week ago #46654 by webaza
Thanks Vince,
i created a folder copy and changed to j06002 the files and classes and now im able to use in frontend.

:)
More
10 months 1 week ago - 10 months 1 week ago #46655 by Vince Wooll
Given how much you like to customise Jomres, Webaza, when you have a moment take a look at github.com/WoollyinWalesIT/jomres/commit...0fc8bc340b30cfa375d9

You can create shortcodes in template files to include scripts (minicomponents) generated output in different templates. This allows you to build pages in Jomres that are composites of different Jomres scripts, without needing to actually modify any individual minicomponents. All of the requests are done in the template itself.

For example, you can put
{jomres_script show_property_features PROPERTY_UID={UID}}
in list_properties.html inside the patTemplate property_details tag and the result will be the property features inserted into the property information panel/card for each property, if available.
Because of how j01010listpropertys.class.php works, you have to include the {UID} code so that patTemplate will insert the property uid in the template.

In templates that are shown for specific properties, you can use a similar shortcode, for example
both {jomres_script show_property_features PROPERTY_UID=N} and {jomres_script show_property_features PROPERTY_UID={PROPERTY_UID}} will work in the property_header.html template file.

An example of the composite property details template (composite_property_details_notabs.html) I created contains just this code, which allows us to build unique property details pages without any code changes at all, just modifying the markup in the template itself.

It's not designed to be pretty, instead it's an example of what you can do.
<patTemplate:tmpl name="pageoutput" unusedvars="strip">

{jomres_script show_property_main_image PROPERTY_UID=N}

<div class="container-fluid">
	<div class="row">
		<div class="col-md-8">
			{jomres_script show_property_calendar PROPERTY_UID=N&months_to_show=4&show_just_month=1}
		</div>
		<div class="col-md-4">
			{jomres_script show_property_features PROPERTY_UID=N}
		</div>
	</div>
</div>

<div class="btn-group" role="group" aria-label="...">
	<a class="btn btn-primary" role="button" data-toggle="collapse" href="#roomsExample" aria-expanded="false" aria-controls="roomsExample">
		Show rooms
	</a>

	<a class="btn btn-default" role="button" data-toggle="collapse" href="#tariffsExample" aria-expanded="false" aria-controls="tariffsExample">
		Show tariffs
	</a>
</div>

<div class="collapse" id="roomsExample">
	  <div class="well">
		{jomres_script show_property_rooms PROPERTY_UID=N}
	  </div>
</div>

<div class="collapse" id="tariffsExample">
	  <div class="well">
		{jomres_script show_property_tariffs PROPERTY_UID=N}
	  </div>
</div>

</patTemplate:tmpl>

Follow me on twitter
Do not send me PMs, if you need to contact me use the ticket system.
Read this before you customise Jomres files
Last edit: 10 months 1 week ago by Vince Wooll.
More
10 months 1 week ago #46656 by webaza
Thanks Vince, i take a look at this.

ABOUT US

Vince portrait smallaladar

Developed and maintained by Vince Wooll and Aladar Barthi, Jomres was initially conceived in early 2005 as a Mambo based solution to a client’s hotel management needs. While it wasn't originally expected to be an online booking system it quickly morphed into one as users requested more and more features.

As the number of feature requests grew Vince knew that he would need to dedicate more time to the project and in July 2005 Jomres was formally released as a commercial project. Since then, Jomres has become one of Mambo’s, and now Joomla’s, longest running projects. It has survived various versions of Mambo, then Joomla 1.0, 1.5, 1.6, 1.7, 2.5 and 3.

Aladar joined the project in 2010 after using Jomres for his own projects. He was active on the forum, helping other members of the community and eventually Vince invited him to join the team. He has since become an integral part of the project and has contributed significantly to it's development over the years.

Whilst not formally part of the Jomres project, Rodrigo Rocco and the team have become firm friends. Rod is a freelancer who specialises in doing custom work for Jomres users and developing custom plugins for the system that take advantage of it's modular design. He has built many useful extensions including his fabulous new Valentina Template Package.

 

Jomres and the Jomres Logo is trademarked and can't be used without written consent from the owner.

www.jomres.net is not affiliated with or endorsed by the Joomla! Project, Open Source Matters or the WordPress project. The Joomla! & WordPress names and logos are used under a limited license granted by Open Source Matters and the WordPress Projects.

© Copyright 2005 - 2018 Woollyinwales IT.