Bug in Admin approving pending Events?
Using Jamroom
Your right, it should work. Its a bug, thanks for reporting it. We'll get it fixed.
Forum Activity for @michael
Using Jamroom
Your right, it should work. Its a bug, thanks for reporting it. We'll get it fixed.
JrCore_list in email template
Jamroom Developers
What we have is:
* jrCore_list calls that are not firing for some reason.
Given that the calls are exactly the same all the time they should produce the same results all the time.
If the calls did not contain any variables then we could easily conclude that the issue is not with the calls.
What we are trying to figure out is if its the calls that are the problem or somewhere else that is the problem.
Latest chat updates
They have that in IRC. Its the first thing I turn off when setting up my IRC client.
In a quiet room where there is no conversation all you get is:
"jimmy has joined the room"
"jimmy has joined the room"
"brian has joined the room"
"bob has joined the room"
"jimmy has left the room"
"michael has joined the room"
"bob has left the room"
.....
Bug in Admin approving pending Events?
Using Jamroom
Guessing the issue doesn't occur if there are more than one item, say if there are 2 items and you check them.
We'll check it out.
JrCore_list in email template
Jamroom Developers
Go for the second idea then to identify which ones are firing and which aren't.
hosting questions
Jamroom Hosting
The way I would do it if I had my SQL and data but my old site was not online anymore would be to use the install that is created when you fire up a new domain on Jamroom Hosting, then SFTP all the data up to the /data folder and use the mysql tool at:
ACP -> DEVELOPER -> DEVELOPER TOOLS -> TOOLS -> DATABASE ADMIN
And import your SQL.
JrCore_list in email template
Jamroom Developers
It looks like it should work the same whether the user is logged in or fired by daily maintenance.
Good explanation of the problem.
Seams like the issue is those 3 lines are not getting output but there are 5 jrCore_list calls, so the first thing to do is figure out which are firing which are failing.
(guess, because i've not checked it) try adding $_params.search2 in at the beginning of the template to see which one is which.
{capture name="s_tpl" assign="s_tpl"}
{literal}
THE SEARCH IS: {$_params.search2} <br>
{if isset($_items)}
{foreach $_items as $item}
{if $item.event_type == 'marriage'}
{if $item.profile_gender == 'female'}
{$item.event_date|jrGenCore_get_day} {$item.event_date|jrGenCore_get_readable_month} {$item.event_date|jrGenCore_get_year} {$item.profile_first_name} ve {$item.event_linked_person|iyelikin} evlilik yıldönümü
{/if}
{else}
{$item.event_date|jrGenCore_get_day} {$item.event_date|jrGenCore_get_readable_month} {$item.event_date|jrGenCore_get_year} {$item.profile_name|iyelikin} {if $item.event_type == 'birth'}doğumgünü{elseif $item.event_type == 'death'}ölüm yıldönümü{/if}
{/if}
{/foreach}
{/if}
{/literal}
{/capture}
So you know the {jrCore_list} calls are firing even though they are returning no results that fit your if/else conditions to display a line of text. Try that.
--edit---
Alternatively make a copy of the template for each jrCore_list with an identifier in it if $_params.search2 doesnt output anything.
updated by @michael: 07/17/16 01:54:09AM
ProJam Comment Delete
Using Jamroom
ok, instead of commenting it out, wrap it in an if user is admin for the update button
{*{jrCore_item_update_button module="jrComment" profile_id=$_params.profile_owner_id item_id=$item._item_id}*}
{if jrUser_is_admin()}
{jrCore_item_update_button module="jrComment" profile_id=$_params.profile_owner_id item_id=$item._item_id}
{/if}
--edit---
Yeah I got your meaning from your first post. If you're having that kind of issue, then the profile owner is just out to cause trouble, and remove their privileges to delete.
updated by @michael: 07/17/16 01:37:53AM
ProJam Comment Delete
Using Jamroom
Understand your issue, but I think its done that way on purpose. Imagine this scenario:
A user posts a really relevant and useful comment to your profile, its long and the only issue you have with it is that it contains an affiliate link. You as the owner of the profile have the option to: IGNORE IT/ DELETE IT, which do you choose......?
What you really want to do is update it to remove the affiliate link. Thats the reason the option is given.
If you want to disable that option for your site you can change the template at:
/modules/jrComment/templates/item_list.tpl around line 74 that looks like this:
{if jrUser_is_admin() || !isset($item.comment_locked)}
{if $_params.profile_owner_id > 0}
{* profile owners can delete comments *}
{jrCore_item_update_button module="jrComment" profile_id=$_params.profile_owner_id item_id=$item._item_id}
{jrCore_item_delete_button module="jrComment" profile_id=$_params.profile_owner_id item_id=$item._item_id}
{else}
{* site admins and comment owners see this button *}
{jrCore_item_update_button module="jrComment" profile_id=$item._profile_id item_id=$item._item_id}
{jrCore_item_delete_button module="jrComment" profile_id=$item._profile_id item_id=$item._item_id}
{/if}
{/if}
and comment out the update button so it looks like this:
{if jrUser_is_admin() || !isset($item.comment_locked)}
{if $_params.profile_owner_id > 0}
{* profile owners can delete comments *}
{*{jrCore_item_update_button module="jrComment" profile_id=$_params.profile_owner_id item_id=$item._item_id}*}
{jrCore_item_delete_button module="jrComment" profile_id=$_params.profile_owner_id item_id=$item._item_id}
{else}
{* site admins and comment owners see this button *}
{jrCore_item_update_button module="jrComment" profile_id=$item._profile_id item_id=$item._item_id}
{jrCore_item_delete_button module="jrComment" profile_id=$item._profile_id item_id=$item._item_id}
{/if}
{/if}
and that will remove that button.
--edit--
Alter it by any of the means outlined here:
Docs: "Altering a Modules Template"
https://www.jamroom.net/the-jamroom-network/documentation/development/1051/altering-a-modules-template
updated by @michael: 07/15/16 10:05:37PM
JrCore_list in email template
Jamroom Developers
paste the function your trying to use in here.
What I normally would do in this situation would be to create a junk.tpl page for my active skin and check that the jrCore_list function works there first. If it does, then put it into the email template and wait for it to fire.
If it didn't work I would put a {debug} into the email template to see what variables I was trying to use and expected to be there werent there.
The debug would come out as html code, but if you take that code and put it into an html file and open it in a browser you can see it as normal.
Another idea would be to put the jrCore_list call into an email template you can fire at will so you dont have to wait a day to see if it works.
