• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

RM 1.1 RM as a classifieds-system - some problems

bart

Active member
#1
I am trying to use the RM as a classifieds-system. I am almost there, but there are some issues left.

- how do I delete the ability to "upgrade" a resource. A classified doesn't have to be upgraded.
- how do I disable the versioning. A classified doesn't have a version.
- how do i disable the ability to follow a resource. Where do I set <xen:if is="{$resource.canWatch}">
- how to disable the tab "most downloaded". Nothing is downloadable.
- how to get rid of the lats-updated-tab. It holds the same as the newest-resource tab.

I can do a lot with template modifications and edits, but I was wondering if there is an easier way.

And is there a way to have a different default icon for every category?

And there is no way to do payments internally? Like through PayPal? This should be done through an external url?

Lastly i would need a way to get rid of resources that are there for x or more days.
 

Jeremy

Well-known member
#2
No, there are no internal payments without an add-on.

You'll need custom CSS to have icon categories, not entirely sure its possible (without looking).

You'll need an add-on to automatically remove resources.

Easiest way to remove everything is with template modifications.
 

bart

Active member
#3
So where do I set this option: <xen:if is="{$resource.canWatch}">. It's not a permission it seems. It would save some template-mods.
 

Jeremy

Well-known member
#4
You'll need an add-on to modify it or edit the core code upon every upgrade (I don't know the file or line number off hand, but it would be a controller).
 

bart

Active member
#5
Got the category-icons figured out in resource_index.

Code:
 <xen:if is="{$categories}">
<ol>
<xen:foreach loop="$categories" value="$_category">
<li class="{xen:if '{$_category.resource_category_id} == {$selectedCategoryId}', selected}">
<a href="{xen:link resources/categories, $_category}" {xen:if $_category.category_description, 'title="{xen:helper striphtml, $_category.category_description}" class="Tooltip" data-tipclass="resourceCategoryTooltip"'}>{$_category.category_title}</a>
<span class="count">{xen:number $_category.resource_count}</span>
</li>
</xen:foreach>
</ol>
<xen:else />
<div>{xen:phrase n_a}</div>
</xen:if>
In this code above I use {$_category.resource_category_id} to give a default category-image.

But the same menu is shown in resource_category, but there it says:

Code:
{xen:raw $categorySidebarHtml}
Where is this "raw" code made? is it possible to edit that code like I edited the resource_index-code? Then where do I do that?

Thanks!


PS: canWatch is indeed in a controler. It just states if the person viewing the resource is loggedin and therefore able to watch. I took the easy way out and blanked the appropriate phrases. That works! :)
 

bart

Active member
#6
Found it.

For anyone looking for soemthing like this:
there is a second template that does about the same as what is done in the resource_index_template: resource_category_sidebar_list

In a template-modification you can then do something like this (in both templates):


<li class="{xen:if '{$_category.resource_category_id} == {$category.resource_category_id}', selected}">
<a href="{xen:link resources/categories, $_category}" {xen:if $_category.category_description, 'title="{xen:helper striphtml, $_category.category_description}" class="Tooltip" data-tipclass="resourceCategoryTooltip"'}>
<img src="images/cats/{$category.resource_category_id}.gif" width=20 height=20 align=absmiddle>
{$_category.category_title}</a>
<span class="count">{xen:number $_category.resource_count}</span>
</li>
 

Ludachris

Well-known member
#7
Hey bart, would you mind sharing your finished product, as I'm about to attempt the same project. You can send me a private note if you prefer.
 

bart

Active member
#8
I'm sorry, but the "finished product" is not in a state I could share. Nor will it ever be, I'm afraid. And furthermore, it hasn't been tested in a production-environment yet.

But if you have certain questions I could maybe point you in the right direction.