Family Tree API
Genosis
That sucks, I was interested to see what you were going to build.
Time to change hosting companies if they don't provide backups.
Thanks for trying Jamroom.
Forum Activity for @michael
Genosis
That sucks, I was interested to see what you were going to build.
Time to change hosting companies if they don't provide backups.
Thanks for trying Jamroom.
Unable to process your request
Using Jamroom
Check your ERROR LOG and ACTIVITY LOG to see what the error is.
What is highest PHP version for Jamroom 4 ?
Installation and Configuration
php 5.2 is the last one that ran Jamroom 4 correctly. Something changed in php that screwed up the Newsletter system if I recall correctly.
Family Tree API
Genosis
If you could export your .ged file and a .yaml example file I can try to duplicate your setup, that would make helping easier.
compress them to a .zip and upload them here, or if they are more private, then send them to support at jamroom dot net with a link to this thread.
Family Tree API
Genosis
Another idea is that in the ACP there is an export feature that allows you to export the entire site to a GEDCOM file. You might look to see if a converter already exist to convert from .ged to .yaml
Family Tree API
Genosis
The most control you will get is by building a module. Jamroom is VERY module centric, even the core is a module of itself.
Once you have a module created it will serve as the base for all the adjustments you want to make and will allow you to tap into the system on various levels.
Probably what you're seeing with relation to the database being confusing is that each module gets its own 'datastore' which is a special KEY => VALUE type database structure. This is access from php via the jrCore_db_get_item() function and the jrCore_db_search_items() function. and in the templates via the {jrCore_list ..... } template function.
The value of a datastore comes from its ability to add extra "columns" without having to change the database structure.
For example, the jrAudio modules purpose is to allow the user to upload audio files, it uses a datastore. Then the jrTags module comes along and adds the ability for the user to tag audio files. The jrAudio module does not need to know or care whether the jrTags module exists or not. The jrTags module can write its tags to the jrAudio modules datastore so when anyone requests an item from the audio datastore the tags come back with it.
This allows modules to stay independent of each other. You can have regular SQL tables too.
With your own module you could setup its own view to create the output you need on a url that suits you, so maybe call your module xxFullTree and have a view of view_xxFullTree_everything() which would then be viewable at:
http://YOUR-SITE.COM/fulltree/everythingThen it would just be a matter of figuring out what it is you want and in what order inside the view_xxFullTree_everything() function.
If you like I can get that module setup with the file system structure enough to turn it on and have a play with it?
--edit--
Here is the beginning of a module. Upload it to your server then activate it by going to ACP -> MODULES -> CUSTOM -> FULL TREE -> INFO
If you dont see it run an integrity check first.
xxFullTree.zip - 1KBupdated by @michael: 07/18/21 07:31:16PM
OG Image Issues
Using Jamroom
Any of these are valid;
Image Sizes:
24 => 24
xxsmall => 24
40 => 40
xsmall => 40
56 => 56
72 => 72
small => 72
96 => 96
icon96 => 96
128 => 128
icon => 128
196 => 196
medium => 196
256 => 256
large => 256
320 => 320
larger => 320
384 => 384
xlarge => 384
512 => 512
xxlarge => 512
800 => 800
xxxlarge => 800
1280 => 1280
original => (actual size)
Then you can add a width=?? height=?? to adjust from the base image to the size you actually want
{jrCore_module_function function="jrImage_display" module='jrProfile' type='profile_image' item_id=$item._profile_id size="icon" crop="auto" class="img_scale" alt=$item.profile_namee width="48px" height="48px" ext=$item.profile_image_extension _v=$item.profile_image_time}It would not make sense to have a size=1280 then width=48 height=48 because it would only show 48x48 but the 1280 image takes much longer to load and transfer than a smaller image.
Further adjustment can be made if you add a class to it class="some_class" then you can adjust the image via CSS
like this (the name some_class can be anything you like). This is example css:
.some_class{
width: 48px;
height: 48px;
padding: 5px;
border: 2px solid green;
}
CSS gives you a lot of control, almost too much control, because it can get confusing with all the available options.
OG Image Issues
Using Jamroom
Quote: ....be but for some unknown reason....
{debug} is what you're after
Docs: {debug}
https://www.jamroom.net/the-jamroom-network/documentation/module-developer-guide/1477/debug
OG Image Issues
Using Jamroom
Ken Rich:
....For example, item_detail_meta.tpl exists for DETAIL pages but there does not appear to be a template in the profiles module or in the skins for profile INDEX pages.....
....For example, item_detail_meta.tpl exists for DETAIL pages but there does not appear to be a template in the profiles module or in the skins for profile INDEX pages.....
Usually an index page is just a list of all the possible detail pages that changes when a new item is added. It would be unexpected to share that page. That's why there's no meta data by default in there.
eg: for audio files you would have a list of 5 or 10 files on the index page what would be the expected og:image tag?
OG Image Issues
Using Jamroom
Heres the first result on "og tags" search its got a good title and should provide some background on what you're after:
https://ahrefs.com/blog/open-graph-meta-tags/
The source code of the page needs to have a meta tag in it of the image you want to display. Use the Meta Tag Manager module to add tags or adjust the templates.
