Skip to main content
edited tags
Link
avpaderno
  • 97.9k
  • 15
  • 164
  • 284
deleted 9 characters in body; edited tags; edited title
Source Link
Sage
  • 2.5k
  • 27
  • 46

Creating A better way to show a Set of Sharing Buttonsnode-based field in the Footer that Dynamically References the Page a User is Onregion outside of the node itself

I want to include social sharing buttons inI'm using the footer'AddThis' sharing module with Facebook and Twitter so that when a user is on all the pagesa page of mythe site they will be able to share it with others. ButtonsThis would include such obvious things as Facebook, Twitter, Pinterest, Email, etcthe front page.

Depending on the page a user happensThe problem I'm discovering is that to be on on the site when they click one of those buttons I want ituse this module you have to reference the page they are onadd it as a field for sharing purposesa content type. So if they are on the home page and click the 'Facebook' icon for instance..so I can basically add it would prompt them to shareall pages EXCEPT the home page of the site on Facebook. And so on...

I tried to set this upPutting aside the issue with several of the front page for a moment, I'd like the sharing modules but when they arebuttons to actually appear in the footer and, not connected to a content type they just seem to referencein the footernode body itself. The footer is a totally different region. Would this entail me using my .which is of course not what I wanttpl files to change where this specific field appears (ie. hiding it and then showing it again but in the footer for the node)?

IsOr is there a better way to dohandle this through code (or some other method)?

Creating a Set of Sharing Buttons in the Footer that Dynamically References the Page a User is On

I want to include social sharing buttons in the footer on all the pages of my site. Buttons would include such obvious things as Facebook, Twitter, Pinterest, Email, etc.

Depending on the page a user happens to be on on the site when they click one of those buttons I want it to reference the page they are on for sharing purposes. So if they are on the home page and click the 'Facebook' icon for instance it would prompt them to share the home page of the site on Facebook. And so on...

I tried to set this up with several of the sharing modules but when they are in the footer and not connected to a content type they just seem to reference the footer...which is of course not what I want.

Is there a way to do this through code (or some other method)?

A better way to show a node-based field in a region outside of the node itself

I'm using the 'AddThis' sharing module with Facebook and Twitter so that when a user is on a page of the site they will be able to share it with others. This would include the front page.

The problem I'm discovering is that to use this module you have to add it as a field for a content type...so I can basically add it to all pages EXCEPT the home page.

Putting aside the issue with the front page for a moment, I'd like the sharing buttons to actually appear in the footer, not in the node body itself. The footer is a totally different region. Would this entail me using my .tpl files to change where this specific field appears (ie. hiding it and then showing it again but in the footer for the node)?

Or is there a better way to handle this?

Source Link
Sage
  • 2.5k
  • 27
  • 46

Creating a Set of Sharing Buttons in the Footer that Dynamically References the Page a User is On

I want to include social sharing buttons in the footer on all the pages of my site. Buttons would include such obvious things as Facebook, Twitter, Pinterest, Email, etc.

Depending on the page a user happens to be on on the site when they click one of those buttons I want it to reference the page they are on for sharing purposes. So if they are on the home page and click the 'Facebook' icon for instance it would prompt them to share the home page of the site on Facebook. And so on...

I tried to set this up with several of the sharing modules but when they are in the footer and not connected to a content type they just seem to reference the footer...which is of course not what I want.

Is there a way to do this through code (or some other method)?