Topic-icon Description text that shows on social media

Active Subscriptions:

None
5 years 7 months ago - 5 years 7 months ago #64521 by SteelMan
I could not find it again for this post, but I'm sure I read earlier that if the meta description is filled in JFBC will use it. It does for the front page, but not the privacy policy. I know I can override, but it's enough to put in meta desc for each article let alone overriding for each.

Edit - found where I read it: If you've already created great title and description meta tags, JFBConnect will automatically use those if the overrides above aren't set.
www.sourcecoast.com/jfbconnect/features/...pen-graph-for-joomla

For example, the meta desc in joomla global is:
We create Local and global, socially responsible products and services that promote Engagement and are FREE or affordable to the “average” person, business or entity.

The meta desc for the privacy policy is:
We take your privacy seriously, but we also like to laugh. Listen to our Comedy Radio Station while you read our Privacy Policy and you'll laugh, too!

The first bit of the privacy policy is:
Effective date: July 2018 LauriTech, Inc. ('us', 'we', or 'our') operates the www.randysteel.com website and the Randy Steel mobile applicatio...

Without having entered the meta desc, I would expect JFBC to enter the first bit of the article, but, having taken the time to enter the meta desc with what I actually want to show in social postings, I would expect it to use that.

Obviously I'm missing something simple.

Please advise at your earliest convenience.

Thanks!
Last edit: 5 years 7 months ago by SteelMan.
The topic has been locked.
Support Specialist
5 years 7 months ago #64524 by alzander
I can see where the confusion lies, and it's based on how our code does stuff for Joomla content (a component type we know) vs 3rd party extensions (which JFBConnect wouldn't know how pick a good description for.

For Joomla Content articles, if you have the Open Graph - Content plugin enabled, JFBConnect use the first 50 words of an article as the description. That's a benefit of the Open Graph content plugin.. it understands how the article is shown on your site and can pick a good description and image on it's own.

If JFBConnect encounters a Joomla component that an Open Graph plugin isn't available for, then in that case, the meta description would be used since it's a good option for all types of web pages.

The best suggestions I'd have from here to enable the meta description as the default text is:
* Disable the Open Graph plugin - Not recommended as this will prevent images from being set and other benefits of the OG Content plugin
* In the Social Meta section of JFBConnect, create a new "Object" and set it to the root (top-level) category of your site. In the options, set the Description to use the Meta Description instead of Introtext. That will have JFBConnect use the meta description for all Joomla content on your site.
** You could also create an Object for just the category of your privacy policy or other categories to be more specific to just those area.

I hope that helps explain, but should you need anything else, please let us know!

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
5 years 7 months ago #64527 by SteelMan
Understood. Thank you.

I would like to suggest, however, that a future version would include the ability to selectively exclude articles, categories, or whatever else is applicable, and that be the exception rather than the rule. As you say, the plugin had several important benefits for general use. With a privacy policy or terms of service and similar articles, though, the first nn words are usually technical and rather uninformative from a search click through or social posting point of view and this suggestion would allow us to sexy it up a bit. If there is a specific place to suggest potential improvements, just point me to it and I'll do it there. One more thought on this, a simple override check box at the meta description field would suffice, as it will be on a case by case basis usually anyway. It could exist at the menu, category and article level giving wide control without the complexity of doing it otherwise. Of course, it's simple in my head—probably not in the plugin or component.

Thanks again.

-rs
The topic has been locked.
Support Specialist
5 years 7 months ago #64531 by alzander
JFBConnect has a strong hierarchy that can be used in various ways to do what you want. Most specifically, at the article level, you can add the following text to the article contents to set a specific meta tag:
{SCOpenGraph description=My description for this article}
You mentioned already that you knew this, which means you feel that's not acceptable.

At a higher level, when creating Objects for your content, as described above, you can create an Object specific to your legalese category (ToS, Privacy policy, etc), assuming they're all in the same category. That object can state that any articles in that category should use the meta description whereas any articles *not* in that category would use the defaults.

Adding more options on a per-article basis gets overly complex. We wouldn't want you to create a specific Object for each article as that's in a whole other section, whereas the body of the article is right in front of you, where you can set a specific description in the text if you want to make an override on a per-page basis.

As for changing the content fields in the Article editor, that's more difficult and error prone than it may seem. I agree a simple checkmark may be beneficial there, but admin templates, differing versions of Joomla and a slew of other nuances make it problematic to try and override some of the core elements.

I hope that helps explain things, but if you have any suggestions, we're always listening.

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
5 years 7 months ago #64536 by SteelMan
Good info. Thank you.
The topic has been locked.
Support Specialist
5 years 7 months ago #64539 by alzander
No problem. We're always happy to explain our logic behind how things work. If you have suggestions though, they're always welcome. We'll be the first to admit that JFBConnect can be complex. Where we can streamline features or improve clarity, we're always listening.

Thanks,
Alex
The topic has been locked.