How to deploy Flare to your site

Flare installs easily with drag-and-drop. However, every site is coded differently, so you still need to try to place it on the correct element on the page. Typically in most Content Management Systems and theme templates, there are certain HTML elements that always contain your post or main content. This is what you want to aim for.

This is especially true if you're trying to have Flare show on all of your posts or articles especially, here's what you should do.

Here's a demo of how to deploy a Flare bar



  • Step 1: Go to an individual blog post or page, this is the best place to drag-and-drop your Flare bar in most cases. If you want your Flare on every page, including your homepage or your blog, you can skip this step.
  • Step 2: Drag your Flare from the sidebar out and onto your content. 99% of the time, you'll want to drop it on top of the post or article itself. We typically recommend aiming for the first paragraph of the content.
  • Step 3: Use the location filters to remove any pages you may want to add or exclude Flare from. This is especially simple for WordPress users using the Filament WordPress plugin.
  • Last thing - Save and Publish! You should see your Flare live on your site shortly. It may take up to 2-3 mins in some cases, depending on your hosting and cacheing setup.

Flare Position - Not showing in the right place

If you selected top, bottom or left/right adjacent positions for your Flare module, but your Flare bar shows on the far left edge of the screen, it's because Flare couldn't find a common element to bind itself to. This is called Last Resort Positioning. In most cases, this can be fixed by deleting that Flare from the site preview and dragging more carefully onto your main content, as depicted in the animation above. However, certain more complex or non-standard themes may need to used the "Advanced Settings" in the edit panel to save a particular CSS Selector that Flare should bind itself to.

A note about how Flare tracks shares

Flare doesn't store your share counts from the various social networks. It pulls them from the networks based on the URL that the Flare is on. Therefore, it can always only share the URL that the Flare bar initiated the share from.

You may wish to try to have a Flare bar attached to each headline that you have listed on your blog index or homepage. This isn't recommended, since this will always share the page it's on, even though they may have clicked a Flare near a particular blog title. This is way we recommend deploying your Flares directly on the individual post pages.



http://support.filament.io/knowledgebase/articles/353913-why-is-my-flare-bar-stuck-to-the-edge-of-my-browse

Feedback and Knowledge Base