I am trying to add a “Like Button” to a friend’s website (first time trying this). When I first used the code generator a couple of days ago, the generator showed a rendition of the button to the right of the fields.
Now there is no rendition and once I “Get Code” the XFBML, IFRAME and URL links do not work. It also appears that the code generated is not what I requested via the user input fields. (i.e. when selecting Color Scheme Dark I find the following in the code generated data-colorscheme="light" )
Regards
Derek
There appears to be a bug in the developers tool right now. It has been reported to Facebook using their bug reporting tool, and they have confirmed that it's an issue. You can subscribe to the bug report here: http://developers.facebook.com/bugs/321035314684250 . Use the little "Subscribe" button in the upper right corner.
Related
The way that Page Editor handles versions has been causing issues for in one of our Sitecore solutions for a client. I've posted about them here:
Sitecore instance showing incorrect workflow state in Page Editor
Expected usage of Page Editor's Experience date
I didn't get much response on those and so far I've surmised that this is just how Sitecore works. This is less than ideal for our instance, as when publishing restrictions are set, authors don't know which version they're editing which is causing various issues for them.
I'd like to implement a solution(s) to improve the experience provide the following functionality:
Something in the Experience tab that shows the number of the version being viewed.
A button on the Experience tab that resets the Date to the default (this is not simply setting the date to the current date/time, but resetting it to act as it did before a date was manually set).
A custom button in Content Editor which allows an author to open a specific version in Page Editor...set the date automatically when it opens, I guess.
An any one give me some clues on how much of this is possible and where to start?
Thanks.
For the first bullet "Something in the Experience tab that shows the number of the version being viewed", you can add version item in Core database.
Move to "Core" DB in Desktop Mode
Navigate to "/sitecore/content/Applications/WebEdit/Ribbons/WebEdit/Experience/"
Create "Versions" item like this, http://imgur.com/bPEDm7R
Create "Compare" item under "Versions" like this, http://imgur.com/dG8dz2M
The result like this, http://imgur.com/HPu3XAL
The content author can see which version they are using and they can also compare with previous versions.
I am working on some custom Redmine reports. In the generated report, there are numbers that represent things like "number of issues moved to Development during Q3 2013". The report generator knows the issue id of every issue that matches that criteria.
Is there a way to construct a Redmine URL that shows a list of all issues given a list of issue ids? For example, something like (this doesn't actually work):
http://redmine/projects/example/issues?ids=1234,1239,1245
This is similar to existing feature requests such as http://www.redmine.org/issues/10828 but I'm looking for the user-facing HTML version, not an API function. The idea is to allow the user viewing the report to click on the number and to see the corresponding list of issues.
The solution I ended up with was to include the list of issues in a <div> for each number in the report that the user could click on. Then, when the user clicks on a number, the corresponding <div> is displayed using a jQuery UI dialog.
This is not the same as using the Redmine issue list screen to show the issues. However, for this purpose it works well enough.
No, this is not implemented. But for me it should never be necessary in the Gui.
My Solution would be : Build the adequate query. Eventually this will need the addition of a field in Redmine and backporting the information from your tool to Redmine. Generally the need for this feature shows your bug tracker lacks some information that he should track.
So, researched this forum for the same problem, but still without success, any solutions haven't worked for me.
The problem is that we had four pages which ones have had like buttons. So we launched advertisement campaign, have collected some likes (more than 100 likes per page). Now we added one more like button for entire site and likes for these 4 pages now are equal to 0.
How this happened and where the likes disappeared? I'm new to this project so maybe I'm missed something (like metatags, app ids or etc.)?
Reverting project also haven't helped.
The pages I'm talking about (sorry, for separating links, but the editor wont allow me to post more than 2:
http://www.tradicinekolekcija.lt/
- index.php/kolekcijos-alus/old-port-ale/58
- index.php/kolekcijos-alus/baltijos/17
- index.php/kolekcijos-alus/ekstra-draught/16
- index.php/kolekcijos-alus/baltas/15
Your metadata is all right, you can check the data FB is scraping by using the debug tool. Just paste your pages' urls in https://developers.facebook.com/tools/debug.
The problem is that in the like buttons you're always using data-href="http://www.tradicinekolekcija.lt/" so you're always showing the like button and the count of likes for the main page. Just update the code in each of the urls' like buttons to point to the right url (the same url of the page where the like button is).
This should fix the issue!
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.
A week ago, the "Like Button" in a page I'm developping stopped working, whether I use XFBML or social plugins, I get the same result.
When some one tries to click the Like Button, the get an error message, and the link says "This page is either disabled or not visible to the current user."
What couldit be?
Had the same issue recently. If you used the like button generator, this is what solved it for me: you have to have the exact same settings in your iframe and open graph data as you did when you first generated the like button. Not sure why, but this was the only way to get mine to work. I had changed to a different layout and size. Of course, the facebook linter is definitely helpful as well:
http://developers.facebook.com/tools/debug
Put the url into the URL Linter and that should clear the cache. If it is still an issue, perhaps your link got blocked for spam. What is the url?