BuGz
Jamroom Developers
cool.
Forum Activity for @michael
[BUG] Add non-existent Follower
Jamroom Developers
thanks will check this out and add some validation where required.
When updating my account details, as regular user, I am forced to reset my password
Using Jamroom
If you make any field REQUIRED in the form designer that field will need to be filled in when the form is updated.
That is different to the "reauthentication" found at:
https://yoursite.com/user/admin/global/section=account+settings/hl=authenticate
Quote: If this option is checked, when a user attempts to change their email address or password they will have to enter their existing password to continue.
Template customization -> jrGallery -> can't find (datastore key)'s to make correct call
Design and Skin Customization
Try with type="gallery_image"
{if isset($_items)}
{foreach from=$_items item="item"}
<div class="col3">
<div class="wrap">
{jrCore_module_function
function="jrImage_display"
module="jrGallery"
item_id=$item._item_id
type="gallery_image"
size="xlarge"
crop="auto"
class="img_scale"
}
</div>
</div>
{/foreach}
{else}
{jrCore_include template="no_items.tpl"}
{/if}
That is with the proviso that you still need to be inside a jrCore_list call like brian said so that you have images in the first place.
Docs: "{debug}"
https://www.jamroom.net/the-jamroom-network/documentation/module-developer-guide/1477/debug
if you add {debug} to that location you will see what variables you have to work with.
Timeline listing
Design and Skin Customization
a modulus looks like this:
{foreach $_items => $item}
{if $item@first || ($item@iteration % 4) == 1}
THIS IS FIRING ON EVERY 4TH ITERATION.
{/if}
........
updated by @michael: 03/17/17 09:16:06PM
Page Module HTML
Jamroom Developers
ACP -> MODULES -> CORE -> SYSTEM CORE -> QUOTA CONFIG -> allow ALL HTML tags : checked
should bypass any html validation at all. Its something we really didnt want to add in, but got asked so many times, that it now exists with this warning:
Quote:
If this options is checked, then ALL HTML tags will be allowed for profiles in this quota.
WARNING! Enabling this option will allow users to embed HTML tags that could compromise your system security or affect the design and/or layout of your pages.
Enabling this option overrides the "Allowed HTML Tags" option below.
If this options is checked, then ALL HTML tags will be allowed for profiles in this quota.
WARNING! Enabling this option will allow users to embed HTML tags that could compromise your system security or affect the design and/or layout of your pages.
Enabling this option overrides the "Allowed HTML Tags" option below.
with that checked the id will get through to the page.
test: https://hostsaba.com/admin/page/3/test-page-with-div
A better way to do is is to allow the id tag through on divs, in the "allowed HTML tags " add in div.id which will let the id attribute through.
span,strong,em,a,b,u,i,p,div,div.id,br,img,h1,h2,h3,h4,pre,hr,ul,ol,li,sub,sup,table,tbody,th,tr,td
Is There a PDF Version of Documents?
Installation and Configuration
@ultrajam, the biggest issue was getting the docs looking good in a pdf format, the way they are they're not laid out in a PDF style format, so there is a lot of wasted space.
WOW your docs look impressive!
If i had to be pickey....(screenshot)
Treating content after a certain number of page views
Using Jamroom
if they like taking screengrabs, watermark all images for non-logged in users. They'll need to join to get their screengrabs.
Smarty PHP Include
Jamroom Developers
that would be the LAST option I would choose. options I would try before that would be
$_js = array('source' => "{$_conf['jrCore_base_url']}/modules/jrCore/contrib/tinymce/tinymce.min.js?v={$_mods['jrCore']['module_version']}");
jrCore_create_page_element('javascript_href', $_js);
find an event that happens exactly, or close to what you want, all the data for building that event will come in with ($_data, $_user, $_conf, $_args, $event)
so it will be easier to determine if you want to add your code in this instance or not.
If you use 'view_results'. all that data has been transformed into html, so its harder to use to test your variable against.
example:
http://yoursite.com/admin/page/1/testing-how-the-stuff-gets-here
see screenshot for all the events that fire and how many times they fire for that one url load.
a listener on any of them might give you more fine grained options if you find yourself needing more control.
Analytics Comparison
Using Jamroom
http://yoursite.com/core/dashboard/online
will show you each of the users who are online. you can choose between whether to include bots or not.
