Forum Activity for @ken-rich

Ken Rich
@ken-rich
07/23/21 08:14:55AM
926 posts

Found bug in metatag module
Design and Skin Customization

It appears that the module needs an update. It is generating tags with the outdated name convention rather than property. Therefore the tags specified by the module are being ignored.

For example, the Facebook Debugger is giving this error on a URL where I used the module to generate tags.

Tag specified as 'name' instead of 'property'
The following meta tags are specified using 'name' instead of 'property' and will be ignored unless specified using the 'property' key: og:image, og:description

It appears these tags are also being ignored in Yahoo mail too as the wrong OG image is being pulled even though it is specified by the module.
updated by @ken-rich: 10/31/21 10:04:28AM
Ken Rich
@ken-rich
07/23/21 08:01:31AM
926 posts

Found Bug in Profile Tags
Design and Skin Customization

If you need an example go to this URL - https://indiegospel.net/ken-rich/tags/gospel

The titles and text are being listed properly but if you click on an item you are not taken to that content.

If you copy (or hover on) the URL to the content you will notice the profile ID is missing. So the URL for the first item, the "Revelation" song is https://indiegospel.net//uploaded_audio/5597/revelation but it should be https://indiegospel.net/1175/uploaded_audio/5597/revelation

With the profile ID missing it defaults to all songs (the main song index) rather than that specific song. The same thing happens with the blog item listed. It goes to all blogs rather than that specific blog because the profile ID is missing.
Ken Rich
@ken-rich
07/23/21 07:37:12AM
926 posts

Found Bug in Profile Tags
Design and Skin Customization

This is in all skins I tried so I am assuming it is somewhere in the jrTags module templates.

Tags work correctly on the homepage of the network, but not in profiles.

In profiles, the tag cloud displays, when a tag is clicked an appropriate list unique to the profile is generated, however when you click on the title of a displayed item, it does not take you to that content.

The profile ID is missing from the URL and you are taken to a general listing on that content type. I can't find where the profile ID fetch is supposed to be added to the templates.
updated by @ken-rich: 10/27/21 02:27:56AM
Ken Rich
@ken-rich
07/22/21 06:52:58PM
926 posts

profile_sidebar.tpl - Headings Question
Design and Skin Customization

Hi Paul,

Thanks for the tip. I'll play with it and see if I can get it to work.
Ken Rich
@ken-rich
07/22/21 07:56:57AM
926 posts

profile_sidebar.tpl - Headings Question
Design and Skin Customization

How can I make a header title not display if there is no content? For example, if someone has just joined but has not generated any stats, how can I prevent the Stats header from displaying in their profile?

I know I must modify this piece of code but I don't know what to add.


  {if isset($_conf.xxComplete_profile_stats) && $_conf.xxComplete_profile_stats == 'on'}
            {if isset($_conf.xxComplete_profile_stats) && $_conf.xxComplete_profile_stats == 'on'}
                    <div class="block">
                        <h3>{jrCore_lang skin=$_conf.jrCore_active_skin id="39" default="stats"}</h3>
                        <div class="block_content mt10">
                            <div style="padding-top:8px">

                                {capture name="template" assign="stats_tpl"}
                                {literal}
                                    {foreach $_stats as $title => $_stat}
                                    {jrCore_module_url module=$_stat.module assign="murl"}
                                    <div class="stat_entry_box" onclick="window.location='{$jamroom_url}/{$profile_url}/{$murl}'">
                                        {$title}: {$_stat.count|default:0}
                                    </div>
                                    {/foreach}
                                {/literal}
                                {/capture}
                                {jrProfile_stats profile_id=$_profile_id template=$stats_tpl}

                                <div class="clear"></div>
                            </div>
                        </div>
                    </div>
                {/if}

I am thinking, adding another && to the first line that basically says "and the stats are greater than zero". However, I don't know how to write it. Something like "&& $_stat.count > 0" but that doesn't work.
updated by @ken-rich: 10/27/21 07:53:40AM
Ken Rich
@ken-rich
07/19/21 05:05:31AM
926 posts

OG Image Issues
Using Jamroom

Also, I have noticed that meta tags I generated by the meta tag module are being ignored on Facebook because they use the old convention of meta name which should now be meta property. Someone on staff should update that module accordingly.
Ken Rich
@ken-rich
07/19/21 05:02:22AM
926 posts

OG Image Issues
Using Jamroom

Thanks, I'll look into optimizing the image size. I also stole code from elsewhere and now have a way to force the OG description to come from the "About Us" section in normal profiles but from the "Bio" section when the profile is created by a power user (since those have no "About Us" only the account tied to them does).

So the code in skins made available to regular profiles is now.

{jrCore_module_url module="jrProfile" assign="murl"}
<meta property="og:title" content="{$profile_name}" />
<meta property="og:url" content="{$current_url|replace:"http:":"`$method`:"}" />
<meta property="og:type" content="website" />	
	
			{capture name="aboutuser" assign="aboutuser_row"}
			    {literal}
			        {if isset($_items)}
			            {foreach $_items as $item}
            			    {$item.user_signup_question_2}
			            {/foreach}
			        {/if}
			    {/literal}
			{/capture}

{jrCore_list module="jrUser" profile_id=$_profile_id template=$aboutuser_row assign="abtuser"}  
   
{if isset($abtuser) && strlen($abtuser) > 0}			    
<meta property="og:description" content="{$abtuser|jrCore_strip_html|jrCore_entity_string|truncate:300}" />	  	
{/if}

<meta property="og:image" content="{$jamroom_url}/{$murl}/image/profile_image/{$_profile_id}/xxlarge" />
<meta property="og:updated_time" content="{$smarty.now}" />

The code in skins made available to profiles created by power users is:

{jrCore_module_url module="jrProfile" assign="murl"}
<meta property="og:title" content="{$profile_name}" />
<meta property="og:url" content="{$current_url|replace:"http:":"`$method`:"}" />
<meta property="og:type" content="website" />

{if isset($profile_bio) && strlen($profile_bio) > 0}
<meta property="og:description" content="{$profile_bio|jrCore_strip_html|jrCore_entity_string|truncate:300}" />
{/if}

<meta property="og:image" content="{$jamroom_url}/{$murl}/image/profile_image/{$_profile_id}/xxlarge" />
<meta property="og:updated_time" content="{$smarty.now}" />

There may be a more "elegant way of doing it but after testing this solution solves all my problems except image cropping.
Ken Rich
@ken-rich
07/18/21 12:49:33PM
926 posts

OG Image Issues
Using Jamroom

I tried the debug after watching the video and reading the help file. Yes, I can see where that would be useful - THANKS AND SORRY FOR LOSING MY COOL...

I think I solved my mystery by comparing the code in the item_detail_meta.tpl to my code then verifying with the debugger.

I was missing the _ in front of the profile _id call. So my code for grabbing the the profile image for the OG image now looks like:
<meta property="og:image" content="{$jamroom_url}/{$murl}/image/profile_image/{$_profile_id}/xxlarge" />

I have tested on the profiles that were failing to load the profile image in the debugger and they now load.

Is there a way to control the size of the profile image besides values like xxlarge or xlarge? Depending on the shape of the uploaded image some are being cropped too much at xx large but that value works better than xlarge in most cases. Is there something in between or an alternative?
Ken Rich
@ken-rich
07/17/21 04:14:42PM
926 posts

OG Image Issues
Using Jamroom

I don't see why a non-programmer like me has to spend all this time trying to figure out how to solve an issue with Jamroom?
Profile index shares have always looked like hell and it is because there is no metadata set up for them (as you have said).

A person's profile index page should generate metadata like any normal website when shared. This is something one of you brainiacs at Jamroom could probably solve in 5 minutes but I have been living with this egregious situation for years. I have already wasted many manhours trying to solve it, days of work just in this last attempt.

Now you want me to waste more time? Michael, I am never going to be a programmer. I don't have time to learn. I barely even have time to keep up with normal network administration tasks. It was a daunting, gargantuan feat for me to make it this far on the issue and I had to steal time away from other projects.
Ken Rich
@ken-rich
07/17/21 01:49:58PM
926 posts

OG Image Issues
Using Jamroom

It should be the artist's profile picture, their name as the title, and in the description whatever they put in their "about me" section (left column), or in the case of accounts created by power users, there is no "about me" so whatever they put in their Bio (with the profile editor).

Look at the difference before and after with my solution - examples attached.

The only problem I see now is that with some accounts the:
 {$profile_id}
part of my OG image fetch does not resolve and the supplied path becomes invalid. The end result becomes:
<meta property="og:image" content="https://indiegospel.net/profile/image/profile_image//xxlarge">


Of course, the // is where the profile ID should be but for some unknown reason there are profiles that consistently return the correct path and others that fail to fetch the ID, even though they are using the same skin. That is puzzling me. I don't understand why???
Screenshot 2021-07-15 at 14-41-55 (11) Ken Rich Facebook.png Screenshot 2021-07-15 at 14-41-55 (11) Ken Rich Facebook.png - 36KB
  6