Need instructions for adding a Facebook Like button without using Open Graph meta tags - facebook-like

I can't find the specific instructions for adding a Like button to a page without including open graph tags on that page. The page in question is a third-party registration site, and we don't have access to the page header to add meta tags. I believe that there was an older version that didn't use the Open Graph (before it existed?)
Any help or advice appreciated!

You can add a like button without Open Graph tags, however you can not set the title, description and image.
The old version of share buttons is deprecated and will be unsupported soon.

Related

Sitecore 9 - Add an Image to a Link in the Footer

A client is using Sitecore 9 - we are not Sitecore developers.
We've been asked a simple thing: add social media links to the Footer of their Sitecore site.
Its proving more difficult than expected.
I've added the links on other pages by editing the HTML directly via the WYSWIG editor.
But the Footer appears more restricted, only accepting the addition of templates like 'Link'.
The 'Link' template has an option to add an external URL but doesn't have an option to add an image.
The CMS looks like this:
Is there any way to add a link, with an image, via the CMS (without the need to write Sitecore code), so the page chnages from this:
to this:
If you dont want to write Sitecore code, maybe you should think about using frontend.
Find the views that holds the footer (probably Foundation/Footer.cshtml) or something like that.
-To easily find where it is, follow these steps
Go to a content page Presentation Details that has footer (probably any)
Go to Controls
Find the footer rendering in there
Click on it
Grab the Datasource's value
Go to the Datasource's path
There should be a field holding the value of the view.
Add some css class on the div that holds those items, and do your frontend stuff in there...
It is not a scalable solution, so I would highly recommend updating the Footer rendering by adding new fields and adapting the model/view. So that way a content editor could easily add a new value for each socials.

Sitecore 8 Insert link to items in bucket

I am using Sitecore 8.1 and Glass mapper ORM. In page editor mode, I have a link field which can be linked to news article page. The folder structure is
News/News article. News folder is of type Bucket and article is bucketable item.
When I am trying to insert link from other pages to the actual news article I am unable to find search box or expand items under news. Is there any way I can insert link to the news article? Appreciate any help! Thanks in advance.
You have 2 options:
In the content editor in the view ribbon you can enable "Buckets". This will make all bucket items visible again (the bucket is expanded and all folders and items can be seen in the tree). This setting is taken into account in the "insert link" window as well.
Use the search tab in the "insert link" window (normally you should have 3 tabs (link, media items, search). The search tab will let you find the bucketed items as well, but also others - it is not restricted to a bucket.
Edit:
After trying this myself, I noticed that if you edit the link field within the experience editor the search is indeed not provided (not even with the general link with search field). In the content editor the search is present.
A workaround is option1, or use an EditFrame. But I would contact Sitecore Support as well and ask them to add this - I'll do it too.
Edit2 : issue has just been registered as a bug. If you need a fix without waiting for a solution in a future version, you can ask Sitecore Support.

Sitecore Broken Links and Content Editor Issues

We've been noticing an increase in number of broken links on our sitecore website.
Some it is due to
User Training
Publishing Issues (linked page is not yet published)
Maybe content editor issues
It's been hard to verify some of these but sometimes the link might have the authoring page URL (which means someone didn't follow the SOP), sometimes they have a strange url like /shell/Content Editor/...
So we are trying to proactively fix these before the pages go live.
I had a couple ideas like writing a Handler that would look through all "Rich Text Fields" and looking for inconsistencies (like authoring server URL). Also using a crawler-type of validator could help us (http://home.snafu.de/tilman/xenulink.html#Description) but we were wondering what the community was doing to address this issue.
The "internal link checker" usually works well but doesn't detect many of this erroneous setups (as I believe it sees them as 'external links').
Your input is greatly appreciated!
If you have RichText fields and create internal links, your internal link looks like this in the HTML view: "a href="~/link.aspx?_id=EB3AD128E7BF4F3C9F3812F701D7724E&_z=z" and when you hover with your mouse over it, is show "/Sitecore/Shell/Controls/Rich Text Editor/" before the ~/link.aspx. This is normal behavior. This link is modified to a normal link during rendering of the RTE field.
However, be sure to use the Sitecore controls like to render these RTE fields and to render links. Also using sc:fld() in XSLT instead of sc:field() can create strange links because sc:fld is rendering the raw value of the field.
In all of the Sitecore projects I have been working on, I didn't have much issues with broken links.
There is a known bug with copy-pasting links from a rich text editor, where path info is appended to the link (generating the /shell/Content Editor/ stuff).
Sitecore have a fix for it here:
http://sdn.sitecore.net/Products/Sitecore%20V5/Sitecore%20CMS%206/ReleaseNotes/KnownIssues%20Recommended/Copying%20and%20pasting%20link%20in%20rt%20fields%20may%20break%20the%20link.aspx
I would suggest a new Validation Action added to the workflow command before the items are finalized. Then you could actively stop them from being published and give immediate feedback. If you're not using workflows, you could add a new item level validator, but those often get ignored in my experience -- too many false positives on the existing validators.

Need help setting up editing template

I have just started working on a wiki where I want registered users to be able to post stuff. I want to have a link on the site which says something along the lines of
"Create new Entry" which when clicked will take the user to an editing template. When the user is done filling in his information and clicks the save button I want that information to be saved in an own page.
My question: What is the approach to achieving something like this?
tag:MediaWiki 1.19.2
PHP 5.3.14 (apache2handler)
MySQL 5.1.63-0+squeeze1-log
There are many URL parameters for editing pages which can do what you want, especially affecting the edit form. There is also an explicit Manual on creating pages with preloaded text, which includes a list of helpful extensions to do such tasks.
I used MultiBoilerplate for this. This extension is very useful because users can select from a drop down list of templates for various pages which can contain default text which users themselves can define.
Tip: if you use the option:
$wgMultiBoilerplateOptions = false;
in LocalSettings.php then administrators can add new templates via the wiki (so without having to change any configurations in php).

Facebook comments plugin not displaying moderation link

I'm using the Facebook comments box plugin..I have many pages with different get urls (example.com/id.php?id=1,example.com/id.php?id=2), and I'm attempting to give each its own seperate comments box. Everything is working fine except I get a warning telling me to add the href to the like button so I did. The only problem is, now a moderation link doesn't even appear..Here's code
" href="example.com/example.php?id="> ...I also included all meta tags I'm 100% sure..
I figured out the problem..Basically, if the page requires a login of some sort to view the contents, Facebook's bots don't have access to the meta tags.Therefore, you should add the meta tags to the page that a non-logged in user would see..This really caused me trouble and I hope this helps someone!