Meta Information on Playlist shares
Installation and Configuration
I tried it that way too but it still didn't work. No idea why???
Forum Activity for @ken-rich
Meta Information on Playlist shares
Installation and Configuration
Should the first underscore be a period?
{$item_playlist_description|jrCore_entity_string}{$item.playlist_description|jrCore_entity_string}updated by @ken-rich: 01/02/15 11:26:39PM
Meta Information on Playlist shares
Installation and Configuration
brian:
Yeah - you could just add:
In to your meta.tpl file. Let me know if that works.
Yeah - you could just add:
{if isset($item_playlist_description)}
<meta property="og:description" content="{$item_playlist_description|jrCore_entity_string}" />
{/if}
In to your meta.tpl file. Let me know if that works.
Still not working. I've added it to the meta.tpl, cleared cache, and checked the scraper at Facebook. I still get this warning and it continues to grab the latest comment, even though a description is entered as a form field.
Quote: Inferred Property The 'og:description' property should be explicitly provided, even if a value can be inferred from other tags.
This is the URL I'm using.
http://indiegospel.net/indiegospel/playlist/1/top-10-songs
Meta Information on Playlist shares
Installation and Configuration
For the color I was changing the values in jrAudio_player_dark.css instead of jrPlaylist_player_dark.css
That's why they were not changing (D'OH), so now the color is good.
Meta Information on Playlist shares
Installation and Configuration
Hi Brian,
For the color change, I can do it with the inspect element feature of the browser and see the change. All I do is add !important to:
}
.jrplaylist_player_dark div.jp-type-playlist div.jp-playlist a.jp-playlist-current {
color:#FFF;
}However, if I do it for real in jrAudio_player_dark.css I don't see the change. It is still being overwritten elsewhere.
I don't understand this, it does not compute!!!
Meta Information on Playlist shares
Installation and Configuration
Hi Brian,
I couldn't get either one of those fixes to work. I can have another go at it later.
Meta Information on Playlist shares
Installation and Configuration
Hi Brian,
I know where to find the second one, but where do I enter the first one? Is it the general meta.tpl for the whole skin?
Meta Information on Playlist shares
Installation and Configuration
Hi Brian,
This one is my Top 10 song list - http://indiegospel.net/indiegospel/playlist/1/top-10-songs
While we are at it. Is there a way for me to override the link colors in the player. Blue on black doesn't work well, but it's following the general link color for the whole skin. It needs an independent setting.
Meta Information on Playlist shares
Installation and Configuration
I want to share my community playlists as TOP 10 songs and videos. However, when I share them to Facebook, the scraper does not receive a description. So it shows the last comment, or if no comment, the stats of the profile.
I added a description to the form hoping it would pick it up that way, but did not meet with success.
The meta tag tool doesn't seem to be able to target specific pages or categories like playlists, so I don't know how it can help here.
I think, somehow or another
<meta name="description" content="{$item_playlist_description}" />Perhaps a if/else statement to the meta.tpl, like if this is a playlist, insert $item_playlist_description, else nothing, but I wouldn't know the proper way to write it.
Anyone got any ideas?
updated by @ken-rich: 02/06/15 01:00:09PM
My Developer Tools skin cloner is not working right
Ning To Jamroom
Hi Brian,
Yes, I understand how the compare tool works. I think it's a great feature and I'm glad enhancements are coming. The problem I have is not the tool itself, but with the lack of documentation.
1) We are not given any substantial info about what the changes do. Therefore, as non coders we don't know if it's something we want to incorporate into our clone, or pass on. Non-coders need a plain English statement.
2) Also, template comparisons, don't tell us anything about any CSS or Javascript mods that Jamroom might have made. Those cannot be seen by the tool, so unless they are documented, how do we know?
So what I would like to see, is better accompanying or supplementary information in plain English.
Example: The index file change in this release decreases the width of the site activity feed, and increases the width of the Top blogs feed. A 3D effect is created around the header logo border, by adding this section (XXXXX) to the header.css file found in your c-panel =>public html=>skins=>Ningja 1.12=>css.
===========================================
I wouldn't want to see the "changesets" routine come back again either, since it was hard for non coders to understand and implement. However, some elements of it might be useful in the new system.
For one, the level of documentation and the archive that provided was handy. Also, I fail to see how a somewhat similar procedure can be avoided, for changes outside of the templates - CSS for instance.
