Jump to content
Soma

MarkupSocialShareButtons

Recommended Posts

MarkupSocialShareButtons
 
This module outputs a list of share links for the following services by default
 
* E-Mail (kinda extra)
* Facebook
* Twitter
* Google+
* LinkedIn
* Thumblr
* Reddit (off by default)
* Pinterest (off by default)
 
Usage examples

echo $modules->MarkupSocialShareButtons->render();
 
This outputs a simple UL list with links

<ul class='MarkupSocialShareButtons cf'>
  <li class='mssb-item mssb-facebook mssb-popup'><a href='url'><i>facebook</i></a></li>
  etc ...
</ul>

Config Screen

post-100-0-26660100-1416777905_thumb.png

See more details and examples on github or modules directory

https://github.com/somatonic/MarkupSocialShareButtons

http://mods.pw/8j

  • Like 16

Share this post


Link to post
Share on other sites

@sinnut, yeah that's the purpose of why I made the module public. Donations welcome ;)

  • Like 1

Share this post


Link to post
Share on other sites

Nice!

I just did all this (build SN links) manually with a new site last week...

Look forward to checking this module out...

  • Like 1

Share this post


Link to post
Share on other sites

Thanks for this Soma. For some reason apart from the 'email', all the other social shares are hidden. The <ul><li> is output but the inner <a> and <i> are hidden, e.g. <i class="icon-twitter">twitter</i> is hidden (CSS). 'Twitter', 'facebook', etc are not shown. Same thing happens if I use icons. The <svg> are hidden. What am I missing?

Share this post


Link to post
Share on other sites

There's nothing in my module that makes them hidden, so it must be your CSS? E-mail has no "popup" class for example. Can you verify?

Share this post


Link to post
Share on other sites

I am testing on a template with hardly any CSS at all. For good measure, I even deleted the CSS with the same results. Below is my output. See the greyed out output for the Social Shares below after email. Yes, email has no 'popup' class.

post-894-0-79517300-1416589913_thumb.png

Edited by kongondo

Share this post


Link to post
Share on other sites

I'm not seeing anything here. Well I'm innocent and it doesn't make sense as there is nothing. Have you installed ad blocker or any plugins ? What browser? 

  • Like 1

Share this post


Link to post
Share on other sites

Sorry for wasting your time!!! Triple facepalm!!!! :-[  -_-  :ph34r:  :blink: Agghhhhhhhhhhhh!!!! Bitten once again!!!! I am going to hide under a rock and will not come out soon. ABP - guilty again! :biggrin:

Your module works a treat! See example below, working together with Blog Module. Will post example code later in Blog thread...Thanks!

post-894-0-34243700-1416591180_thumb.png

  • Like 2

Share this post


Link to post
Share on other sites

No problem. I was waiting for your facepalm post :P

Looks nice!

  • Like 1

Share this post


Link to post
Share on other sites

That's great and will surely become handy soon.

May i suggest namespacing the css classes? Item, Facebook or Twitter are classnames that are potentially already beeing used across several frameworks and applications.

  • Like 2

Share this post


Link to post
Share on other sites

Sorry for wasting your time!!! Triple facepalm!!!! :-[  -_-  :ph34r:  :blink: Agghhhhhhhhhhhh!!!! Bitten once again!!!! I am going to hide under a rock and will not come out soon. ABP - guilty again! :biggrin:

That's why I use a different browser for dev than for web browsing :)

  • Like 2

Share this post


Link to post
Share on other sites

Actually I have no AB anymore since 1-2 years.


That's great and will surely become handy soon.
May i suggest namespacing the css classes? Item, Facebook or Twitter are classnames that are potentially already beeing used across several frameworks and applications.

What framework? :P

Yeah it's only half namespaced, I was about to add it but thought hmm it's so nice and short! :) The UL has the module class name, i'll add them to all classes or make it a var so it could be configured in case.

Share this post


Link to post
Share on other sites

I completely rewrote the module kinda. 

New version just committed earlier:

See readme here for more infos:

https://github.com/somatonic/MarkupSocialShareButtons

There comes now a GUI in the module config screen to select themes (with live preview), and configure all options like links and url params.

Theming has changed a little to make things easier, and the bundled themes use PNG icons instead of SVG.

Edit: updated first post too.

  • Like 4

Share this post


Link to post
Share on other sites

Just when you think you got it you see something you forgot. :)

I just commited a few corrections to descriptions and fixes and missing stuff, minor. If you already got it the moment before you may update.

Share this post


Link to post
Share on other sites

Sorry for writting this without actually downloading and trying out your module, but does it allow to add other (custom) social services?

  • Like 1

Share this post


Link to post
Share on other sites

Sorry for writting this without actually downloading and trying out your module, but does it allow to add other (custom) social services?

Did you read somewhere that it's possible? No it's not, but feel free to make suggestions what to add. There's already all available social media icons included so only a matter of adding them. https://github.com/somatonic/MarkupSocialShareButtons/tree/master/themes/black/png

Share this post


Link to post
Share on other sites

I am talking about social share buttons specific to country. There are a few of them in Russia. And it so happened they are not on the list of availiable icons )) I do not know if they are going to be important to someone outside Russia so would not suggest them.

As it is your module, I just thought that this could be possible it already has interface for extension.

Share this post


Link to post
Share on other sites
Just committed little update


- some minor fixes and improvements

- added config for what fields module searched on {title} and {text} placeholder fields

- added placeholder field „media“ => pinterest

- added services tumblr, reddit (off by default) and pinterest (off by default) 

- updated themes with {themeUrl}

- updated readme

  • Like 8

Share this post


Link to post
Share on other sites

Hi Soma, 

found a little syntax error

MarkupSocialShareButtons.js

$(function(){

    $('[name=theme]').on("change", function(){

    });
}

I think there are two missing characters?

); 

Fixed file

$(function(){
    $('[name=theme]').on("change", function(){

    });
});

Share this post


Link to post
Share on other sites

Thanks. But this script isn't used, so it's kinda leftover.

  • Like 1

Share this post


Link to post
Share on other sites

Soma, I just got around to using this module, and it's great!

It makes setting all these up SO much easier.

Thanks man.  ^-^

  • Like 1

Share this post


Link to post
Share on other sites

Thanks from me as well.

These lines in my template file plus adding alt to the img tags in the theme made my good friend the W3C validator happy.

$options = array('title' => str_replace(' ', '%20', html_entity_decode($page->headline)));
$soc = str_replace('&', '&', $modules->MarkupSocialShareButtons->render($options));
  • Like 3

Share this post


Link to post
Share on other sites

Hi Soma !!

Very nice module... help me a lot !

I'm trying to create my own theme (color) and when I call : 

$content .= $modules->MarkupSocialShareButtons->setTheme("css/color")->render();

I got 

Error: Exception: Method MarkupSocialShareButtons::setTheme does not exist or is not callable in this context (in D:\xampp\htdocs\PWGriffConvites\wire\core\Wire.php line 326)
 
#0 D:\xampp\htdocs\PWGriffConvites\site\templates\convite.php(34): Wire->__call('setTheme', Array)
#1 D:\xampp\htdocs\PWGriffConvites\site\templates\convite.php(34): MarkupSocialShareButtons->setTheme('css/color')
 
css/color are folders, and inside color folder I have theme.php and png folder also.
 
Am I doing something wrong ?
 
Thank you !

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Robin S
      A community member raised a question and I thought a new sanitizer method for the purpose would be useful, hence...
      Sanitizer Transliterate
      Adds a transliterate method to $sanitizer that performs character replacements as defined in the module config. The default character replacements are based on the defaults from InputfieldPageName, but with uppercase characters included too.
      Usage
      Install the Sanitizer Transliterate module.
      Customise the character replacements in the module config as needed.
      Use the sanitizer on strings like so:
      $transliterated_string = $sanitizer->transliterate($string);
       
      https://github.com/Toutouwai/SanitizerTransliterate
      https://modules.processwire.com/modules/sanitizer-transliterate/
       
    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version to 2.10, add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "http://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


    • By thomasaull
      I created a little helper module to trigger a CI pipeline when your website has been changed. It's quite simple and works like this: As soon as you save a page the module sets a Boolean via a pages save after hook. Once a day via LazyCron the module checks if the Boolean is set and sends a POST Request to a configurable Webhook URL.
      Some ideas to extend this:
      make request type configurable (GET, POST) make the module trigger at a specified time (probably only possible with a server cronjob) trigger manually Anything else? If there's interest, I might put in some more functionality. Let me know what you're interested in. Until then, maybe it is useful for a couple of people 🙂
      Github Repo: https://github.com/thomasaull/CiTrigger
    • By Robin S
      I created this module a while ago and never got around to publicising it, but it has been outed in the latest PW Weekly so here goes the support thread...
      Unique Image Variations
      Ensures that all ImageSizer options and focus settings affect image variation filenames.

      Background
      When using methods that produce image variations such as Pageimage::size(), ProcessWire includes some of the ImageSizer settings (height, width, cropping location, etc) in the variation filename. This is useful so that if you change these settings in your size() call a new variation is generated and you see this variation on the front-end.
      However, ProcessWire does not include several of the other ImageSizer settings in the variation filename:
      upscaling cropping, when set to false or a blank string interlace sharpening quality hidpi quality focus (whether any saved focus area for an image should affect cropping) focus data (the top/left/zoom data for the focus area) This means that if you change any of these settings, either in $config->imageSizerOptions or in an $options array passed to a method like size(), and you already have variations at the requested size/crop, then ProcessWire will not create new variations and will continue to serve the old variations. In other words you won't see the effect of your changed ImageSizer options on the front-end until you delete the old variations.
      Features
      The Unique Image Variations module ensures that any changes to ImageSizer options and any changes to the focus area made in Page Edit are reflected in the variation filename, so new variations will always be generated and displayed on the front-end.
      Installation
      Install the Unique Image Variations module.
      In the module config, set the ImageSizer options that you want to include in image variation filenames.
      Warnings
      Installing the module (and keeping one or more of the options selected in the module config) will cause all existing image variations to be regenerated the next time they are requested. If you have an existing website with a large number of images you may not want the performance impact of that. The module is perhaps best suited to new sites where image variations have not yet been generated.
      Similarly, if you change the module config settings on an existing site then all image variations will be regenerated the next time they are requested.
      If you think you might want to change an ImageSizer option in the future (I'm thinking here primarily of options such as interlace that are typically set in $config->imageSizerOptions) and would not want that change to cause existing image variations to be regenerated then best to not include that option in the module config after you first install the module.
       
      https://github.com/Toutouwai/UniqueImageVariations
      https://modules.processwire.com/modules/unique-image-variations/
    • By Sebi
      I've created a small module which lets you define a timestamp after which a page should be accessible. In addition you can define a timestamp when the release should end and the page should not be accessable any more.
      ProcessWire-Module: http://modules.processwire.com/modules/page-access-releasetime/
      Github: https://github.com/Sebiworld/PageAccessReleasetime
      Usage
      PageAccessReleasetime can be installed like every other module in ProcessWire. Check the following guide for detailed information: How-To Install or Uninstall Modules
      After that, you will find checkboxes for activating the releasetime-fields at the settings-tab of each page. You don't need to add the fields to your templates manually.
      Check e.g. the checkbox "Activate Releasetime from?" and fill in a date in the future. The page will not be accessable for your users until the given date is reached.
      If you have $config->pagefileSecure = true, the module will protect files of unreleased pages as well.
      How it works
      This module hooks into Page::viewable to prevent users to access unreleased pages:
      public function hookPageViewable($event) { $page = $event->object; $viewable = $event->return; if($viewable){ // If the page would be viewable, additionally check Releasetime and User-Permission $viewable = $this->canUserSee($page); } $event->return = $viewable; } To prevent access to the files of unreleased pages, we hook into Page::isPublic and ProcessPageView::sendFile.
      public function hookPageIsPublic($e) { $page = $e->object; if($e->return && $this->isReleaseTimeSet($page)) { $e->return = false; } } The site/assets/files/ directory of pages, which isPublic() returns false, will get a '-' as prefix. This indicates ProcessWire (with activated $config->pagefileSecure) to check the file's permissions via PHP before delivering it to the client.
      The check wether a not-public file should be accessable happens in ProcessPageView::sendFile. We throw an 404 Exception if the current user must not see the file.
      public function hookProcessPageViewSendFile($e) { $page = $e->arguments[0]; if(!$this->canUserSee($page)) { throw new Wire404Exception('File not found'); } } Additionally we hook into ProcessPageEdit::buildForm to add the PageAccessReleasetime fields to each page and move them to the settings tab.
      Limitations
      In the current version, releasetime-protected pages will appear in wire('pages')->find() queries. If you want to display a list of pages, where pages could be releasetime-protected, you should double-check with $page->viewable() wether the page can be accessed. $page->viewable() returns false, if the page is not released yet.
      If you have an idea how unreleased pages can be filtered out of ProcessWire selector queries, feel free to write an issue, comment or make a pull request!
×
×
  • Create New...