Celeste - Shareaholic
Forum Replies Created
-
Hi @yetiyeti,
I just installed Graphene on our test blog, and out-of-the-box, our plugin is fully compatible with this theme. Have you checked for plugin conflicts? This is easily accomplished by deactivating all plugins other than Shareaholic (clear all caches in any caching plugins before deactivating them), emptying your browser cache, reloading one of the posts on your site and checking for this problem again.
If all plugins are deactivated and you are still running into the problem, you can check whether the issue is related to your theme by switching to Twenty Ten momentarily. If this does correct the problem, have you made any custom modifications to Graphene, like embedding JS?
I’d love to take a closer look at your site if possible. Thanks!
Hi @easilyamused,
I’ve tried reproducing what you have reported. I went into the Post Edit screen and checked the ‘Hide Share Buttons’ box, saved changes, and refreshed the Post Edit screen, and the box was checked. I then unchecked the box, saved changes, and refreshed the Post Edit screen again, just to see if that change was applied, and it was.
Now, if you are trying to disable/enable our apps on custom post type content, these toggles will not work. Our plugin does not support custom post types, but we do offer a manual shortcode for all configured apps that can be included directly in your preferred template files to customize placement.
You’ll find the shortcode at the bottom of the Edit pane in square brackets. It will look similar to:
[shareaholic app="share_buttons" id="xxx"]Each app has its own ID number to store the unique configuration. If you need help with identifying which template file to modify, this list is very informative.
I’m sorry, @aldabergr. I am unable to locate our plugin script on either of your sites in order to take a closer look at the Related Content data and perform a reset.
As for how the app works, it ties in with your site’s Analytics when generating recommendations. The caching speeds up the loading of the application on your site and allows us to improve what content is recommended while we collect interaction data.
Hi again, Osckar!
Sorry for any confusion yesterday. You can edit the headline text for your Related Content app straight from its Edit screen under Headline Text. This will allow you to customize the text displayed for each app separately, providing you with more options.
Hi Osckar,
Our previous versions did offer automagic translation. In our latest release (v7+), we are accepting translation submissions. If you are interested in submitting a translation contribution, here’s a submission guide: https://shareaholic.com/tools/wordpress/translate
With our recent changes, on the frontend, the tool-tips simply provide the name of the sharing network, which works for all languages, and the Headline text for the Related Content app is fully customizable so that you can use any text you wish. You can find this option within ‘General Website Settings’ on the Available Apps screen.
And on the backend, our plugin will automatically use the language configured for your WordPress Admin panel if this translation is available within our plugin files. 🙂
Hi! First, it looks like you are running an older version of our plugin. I’d love to have you update and preferably to our version 7 release as this is in active development.
The first link you provided takes me to a 404 Error Page. Have you run the URL through the Facebook Debugger Tool (Data Scraper) to see what Facebook has on file for these user contributed pages?
When you run a URL through this tool, you are prompting Facebook to scan the page again and refresh their data. If all looks good on the results page, head back to the user contributed post (the URL you just had Facebook scan), reload the page and try sharing to Facebook again. Let me know if this corrects the problem. Thanks!
Hi! Make sure you have our newest release installed (currently 7.0.3.3), and there are a few other things to check: first, clear your browser cache and reload the settings page to see if this fixes the problem. If it doesn’t, check that JavaScript is enabled in your browser options. If you have any browser extensions installed, disable these to check if there is interference.
Is the problem only happening when you try to edit the ‘Above Content’ options or is this happening on ‘Below Content’ and ‘General Website Settings’ as well?
Hi Dvaer,
Thanks for your feedback. The Twitter button goes through OAuth, the same as it has for the past two years. The only difference is that we updated the Twitter sharing interface back in a later release of version 6 (a couple months before version 7 was introduced) to include the multisharing option, and we integrated the multisharing interface into the Facebook button while releasing version 7, but have since reverted the change where multisharing is only available through the Twitter button.
The OAuth process allows our application to connect with your Twitter account, which provides more freedom in design and additional functionality when customizing our application through the utilization of Twitter’s API. It also helps us to provide you with specific Analytic data so that you’ll know which of your readers are sharing your content on Twitter, just in case you’d like to reach out to them and say ‘Thanks!’
Contrary to recent forum discussion, our plugin has functioned this way for quite some time. The change was in extending the share panel options to enhance the sharing experience by integrating a joint Facebook-Twitter multisharing capability for those who use both social media networks and would like to share content with them more quickly.
Hi Mydien! The new version has been enhanced to provide greater customization possibilities for designers and developers. You can adjust the styles for the share buttons in your theme’s styles.css file by targeting specific classes, which you can find using the element inspection utility in your browser.
To move the entire share bar container, the class is: shareaholic-share-buttons-container
You’ll need to fiddle with the different CSS classes used by our apps and apply your own styles to override our stylesheet.
Inspect Element is your friend. You can play around with the styles loaded on any page and make changes to see how things will look before you even make a single hardcoded change to the document itself. I’d recommend this.
Have fun and good luck!
Hi Jaime,
Open one of the posts on your site where our share buttons are present and right-click your mouse. From this menu, select the option to view the page source. Then, perform a ‘Find’ in your browser menu to locate the following text:
og:image
If you find a matching string, visit the Facebook Debugger Tool and input the URL of the post. Look for any open graph errors and check if an image appears in the results. It should match the URL that you saw when you found og:image in your page source.
By using this form, you are resetting Facebook’s cache of your page data and prompting them to scan the page again. If an image is present in the results (without any error notices concerning the size), reopen this post in your browser (or reload the post if you still have it open in another tab) and try sharing again. Does the image appear?
If it does, you’ll need to prompt Facebook to scan other pages of your site to update their cached data by using the Debugger Tool. If this didn’t fix the problem when you shared with Facebook, I’ll need to take a look at the post you are testing. Thanks!
@didier77 (and everyone else)
We just made some changes in our code. Please, empty your cache and let us know if you are still running into the problem. We’re standing by!
If anyone else is encountering a similar problem in the Firefox web browser where buttons are failing to display, and the issue is not present in other web browsers, such as Chrome, please let us know. Other cases will likely help us isolate the problem more quickly. Thank you.
For your reference, the ticket ID that corresponds to your bug report is PLG-462. We are currently investigating and appreciate your patience while we look into the issue.
There are two bug tickets in our system awaiting further investigation concerning the backend and the frontend issues you have reported.
For your personal reference and future correspondence, the ticket codes are:
PLG-466 (backend editing capability)
PLG-467 (frontend app visibility)Hi @didier77,
I apologize for the delay. I didn’t catch your response. We have created a bug ticket with your issue from a new thread that was opened by you recently. I’ve been able to verify and our engineers are looking into the problem.
Just to make sure that another plugin isn’t somehow interfering with our buttons, please disable any other active plugins (clear any caches in your caching plugins before deactivating them) and empty your browser cache, then check to see if the problem is still present.
I just want to make sure we document the problem fully (in case there is another plugin we need to test alongside). Thanks for looking into this for us 🙂