Error: Query Error: The table 'jr_jrcore_cache' is full
Installation and Configuration
Don't know sorry, Server optimization isn't my strong suit. Brian's the smartest guy I know in that area.
Forum Activity for @michael
Installation and Configuration
Don't know sorry, Server optimization isn't my strong suit. Brian's the smartest guy I know in that area.
Image gallery only works with https websites
Ning To Jamroom
yes the image gallery will work without the Adobe editor. It will just be missing the button on the individual photo update screen that allows the photo to be edited.
You can see the editor at 2:30 ish of this video:
Jamroom 5 : jrGallery module overview
That button will be missing, thats all.
tinyMCE on Mobile Devices
Jamroom Developers
First thing that comes to mind is to not return TRUE for "is this a mobile device"
That looks doable by setting the 'jrcore_is_mobile_device' flag to "no"
jrCore_set_flag('jrcore_is_mobile_device', 'no');and perhaps disable tablet detection as well:
jrCore_set_flag('jrcore_is_tablet_device', 'no');One place to put this to make sure it always ran would be into the config.php file at:
/data/config/config.php
Add it to the bottom.
( Have tried it to check it works, but have not thought any further about the consequences of doing it. Expect that it would break the mobile menu system, possibly other things, not sure. )
Jamroom 6.1 has been released!
Announcements
If you have custom skin templates that override the jrVideo item_detail.tpl file, then the change that you probably need to make is search for "flv" and change it to "m4v".
The reason is m4v is now the default version.
video modules 'item_detail.tpl' page used to have:
{elseif $item.video_file_extension == 'flv'}{elseif $item.video_file_extension == 'm4v'}Some of the jamroom skins over-ride the default video detail page with a template at:
/skins/(some skins)/jrVideo_item_detail.tpl
So if you've cloned a skin that has that file, it probably needs the update.
Docs: "Using the Compare tool to keep cloned skins up to date"
https://www.jamroom.net/the-jamroom-network/documentation/jamroom-admin-handbook/2394/using-the-compare-tool-to-keep-cloned-skins-up-to-date
Goodbye, Facebook and your useless results.
wow you are full of interesting links today
I like that professor, very humanitarian.
Would like google more if they offered a per action service rather than a per click service. Nobody wants clicks, they want sales.
Goodbye, Facebook and your useless results.
Even google is setup greedy though. Their used to be a lot more freedom in search terms:
yellow painted wagon
painted yellow wagon
wagon painted yellow
But whenever you type in google it 'suggests' what your after which means instead of there being 3 terms to bid on with equal spread, there is now only 1 term to bid on with the concentration of three terms.
Means there is more competition bidding so they get a better price.
Googles no saint.
Goodbye, Facebook and your useless results.
Thats real interesting Jimmy, thanks.
I'd read/watched another similar opinion piece,
(there was another but this is the only link I can find right now http://www.greysquall.com/2016/06/wasting-money-advertising-on-facebook.html )
But your's i so totally right on target for Jamroom, it surprised me.
Goodbye, Facebook and your useless results.
LOL, the domain name looked familiar boonex.com
Quote: ....as the UNA Facebook Page, articles at UNA.IO, articles at Boonex.com related to UNA an......
They make the Dolphin CMS which is a direct competitor to Jamroom.
Continuing to read...
Couple of gallery delete issues
Using Jamroom
go to:
ACP -> MODULES -> SITE -> SITE BUILDER -> TEMPLATES -> menu.tpl -> MODIFY
/modules/jrSiteBuilder/templates/menu.tpl
and delete the code that reads
<span class="notifications none">0</span>
User Registration
Design and Skin Customization
Just seeing the jrLaunch page.
Will check it out here to see what I see. (have added the selection form into the signup widget in jrUser 2.2.2)
--edit--
This is also fixed in jrUser 2.2.2.
If you want to patch your jrUser module before the current one is released, in the view_jrUser_signup_save() function around line 1033 of:
/modules/jrUser/index.php
Locate this code
// Create our user account
$_data['user_password'] = $pass;
$_data['user_language'] = (isset($_post['user_language']{0})) ? $_post['user_language'] : $_conf['jrUser_default_language'];
$_data['user_active'] = 0;
$_data['user_validated'] = 0;
$_data['user_validate'] = $code;
// Create our user account
$_data['user_name'] = $_post['user_name'];
$_data['user_email'] = $_post['user_email'];
$_data['user_password'] = $pass;
$_data['user_language'] = (isset($_post['user_language']{0})) ? $_post['user_language'] : $_conf['jrUser_default_language'];
$_data['user_active'] = 0;
$_data['user_validated'] = 0;
$_data['user_validate'] = $code;
The issue is, because the form is not coming in from a jamroom created form the form validation system is not seeing that its valid.
updated by @michael: 09/18/17 11:18:57PM
