Proxima User With Profile Name
Proxima
Also seeing this.
Forum Activity for @michael
Proxima User With Profile Name
Proxima
Without digging deep into it I would say no. When you're creating a user, the profile is auto-generated for that use via hooks.
With a custom module you definitely could by listening for the same events that the profile listens for when the user is created and search for your incoming proxima variable, then setting that.
Without a custom module I don't believe a profile_name variable being passed in will be accepted.
So you could get around it by either a custom module doing the listening, or resending a second request after creation with an UPDATE to the profile datastore.
Facebook Share - Error
Using Jamroom
might not be able to find it. you GAVE me the link to that URL. If I was browsing the site by myself, the link probably would not have been shown to me in any list. (because I can not see it if i clicked)
Facebook Share - Error
Using Jamroom
Looks like the quota has a maximum number of items allowed.
Best guess: The profile was in a quota that allowed for 100 or more or unlimited uploads. They uploaded heaps, then they were changed to a different quota that only allowed 4, or other low number.
Installing Facebook Pixel In Meta.tpl issues.
Installation and Configuration
You're assuming people reading this know what the "Facebook pixel tracking code" is. I don't know what that is, but the error in the screenshot looks like it probably requires a {literal} wrap. Try this:
Docs: "{literal}{/literal}"
https://www.jamroom.net/the-jamroom-network/documentation/module-developer-guide/3011/literal-literal
problem with clone skin tool
Using Jamroom
Yes, just hit the "execute" button. You should see a line of green saying x rows effected.
It reads: "change the strucutre of the jr_jrcore_skin database. Add a new column with the title skin_cloned_from. Things added to that column can be any character, but only up to a limit of 128 characters. If no input comes in when a row is created, dont write NULL instead, just put the contents that you find within these two apostrophes. (which is an empty set)"
After that the cloning of a skin should work without error.
jrSearch errors in Activity Log
Using Jamroom
Im using:
mysql Ver 15.1 Distrib 10.1.22-MariaDB, for debian-linux-gnu (x86_64) using readline 5.21.6.5 is where I got the code from.
Checking here:
https://blogs.oracle.com/mysqlinnodb/entry/innodb_full_text_search_is
It looks like you're JUST below the cut-off point.
Quote:
InnoDB Full-Text Search is in MySQL 5.6.4
.........
InnoDB Full-Text Search is in MySQL 5.6.4
.........
But its also written in 2011. any chance of upgrading mysql?
Timeline refers to gallery name, not item
Using Jamroom
You can adjust it so it works that way for your site. The main reason for it being as it is I would think is that its not certain that each photo will have a title.
When you create a gallery you can upload 10 images at a time. None of those images have titles at this point. To give them a title you'd need to edit the individual image in the gallery and give it a title.
Should be able to adjust it in the jrGallery -> item_action.tpl file.
jrSearch errors in Activity Log
Using Jamroom
the current version of the jrSearch module has this as its schema.php file
/**
* db_schema
*/
function jrSearch_db_schema(){
.............
// Full text search
$_tmp = array(
"s_module VARCHAR(64) NOT NULL DEFAULT ''",
"s_id INT(11) UNSIGNED NOT NULL DEFAULT '0'",
"s_mod TINYINT(1) UNSIGNED NOT NULL DEFAULT '1'",
"s_text TEXT NOT NULL",
"UNIQUE s_unique (s_module, s_id, s_mod)",
"FULLTEXT s_text (s_text)"
);
// NOTE: MySQL 5.6+ and MariaDB can use InnoDB
$_db = jrCore_db_query("SHOW VARIABLES WHERE Variable_name = 'version'", 'SINGLE');
if ($_db && is_array($_db) && isset($_db['Value'])) {
$ver = $_db['Value'];
}
else {
$msi = jrCore_db_connect();
$ver = mysqli_get_server_info($msi);
}
if (strpos($ver, '-')) {
list($ver,) = explode('-', $ver);
}
$engine = 'MyISAM';
if ($ver && $ver > 5.5) {
$engine = 'InnoDB';
}
jrCore_db_verify_table('jrSearch', 'fulltext', $_tmp, $engine);
.........
}
So it seams like the issue you're hitting is taken into account on the current repo version. Probably that hasn't been released in your version.
Solution is:
* wait for the next release OR
* add that code to your jrSearch/schema.php OR
* upgrade your database version to MySQL 5.6+
