dimitrios

AutoFbPost

Recommended Posts

Hello,

I have created a module that, given a Facebook app ID and secret, posts on Facebook on behalf of a user profile or page after a PW page is saved.

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

post-4087-0-60791400-1457660876_thumb.jp

Usage

edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, a token is kept.

 
post-4087-0-78890000-1457661715_thumb.jp
 

Note: Facebook SDK for PHP is used.

post-4087-0-60791400-1457660876_thumb.jp

post-4087-0-78890000-1457661715_thumb.jp

Edited by dimitrios
updated module
  • Like 15

Share this post


Link to post
Share on other sites

Hello dimitrios,

Thank you for developing this! Could you also post it to the modules directory? Doing so makes it easier for people to locate and install your module.

Share this post


Link to post
Share on other sites

Hello netcarver,
 

you are absolutely right, I just updated my post. I have submitted the module and it is currently pending approval. Thank you!

  • Like 3

Share this post


Link to post
Share on other sites

I use PW3 and I always get this error message if I try to login in backend after uploading the module to the server:

post-2257-0-21694000-1458315891_thumb.jp

Is this module not compatible with the latest PW version?

Best regards Jürgen

Share this post


Link to post
Share on other sites

Removing the session_start() from the AutoFbPost.module at the beginning solves this problem

  • Like 2

Share this post


Link to post
Share on other sites

Hello Juergen,

I am sorry for such a late answer. You are right, this is not needed since PW manages the session.
I will try to test this module with various PW versions and update it. Thank you for your post!

  • Like 1

Share this post


Link to post
Share on other sites

Hi,

seems this is written for php 5.4... I'm not on that yet :-)

Would you consider making it < 5.4 compatible?

regards

Share this post


Link to post
Share on other sites

Hello,

I will consider it, although I am on a tight schedule lately. However, I'm not sure if it would be wise, because the old Facebook PHP SDK v3 is now deprecated, so there will be zero maintenance from their part.

Share this post


Link to post
Share on other sites

Hey,

First off, thanks for this great module.

I was just wondering where the On/off checkbox is meant to show as every time I save the page at the moment it gets posted to Facebook and I'd rather have it that you check that checkbox and it stops posting to facebook?

Thanks!

 

Share this post


Link to post
Share on other sites
42 minutes ago, alexmercenary said:

where the On/off checkbox is meant to show

You need to create a new checkbox field, give it a name like autofbpost and add the field to your template. Next configure the module: in the inputfield On/Off Checkbox, enter the name of the field you created.

 

Share this post


Link to post
Share on other sites

Hello,

thank you for your kind words @alexmercenary, I'm glad it was of use to you. @flydev, that is absolutely right, you need to create a checkbox field as with any other field or use an existing one and insert it into the template.

Share this post


Link to post
Share on other sites

cant seem to get it working with facebook. keeps giving me this error:

AutoFbPost: post failed; click here to log in with Facebook.

URL blocked: This redirect failed because the redirect URI is not white-listed in the app's client OAuth settings. Make sure that the client and web OAuth logins are on and add all your app domains as valid OAuth redirect URIs.

my settings: https://www.dropbox.com/s/y4ajeac4wwlyup4/Screenshot 2017-07-07 16.53.23.png?dl=0

and platform the website url.

any help would be appreciated

Share this post


Link to post
Share on other sites

This module seems not compatible with the latest Facebook policy. If you want to post something through a Facebook app, you need to apply for the permission. Otherwise, it ask for login every time just as your case.

Gideon

Share this post


Link to post
Share on other sites

Anyone noticing that the module isn't posting the images or description?

If so is there any fix or anything I am missing? 

Share this post


Link to post
Share on other sites

@videokid yeah I do have opengraph in the header but it isn't detecting the image field, it's just using the site logo as the post image and the default site description as the description. It's weird.

Share this post


Link to post
Share on other sites

I do: https://www.featherbow.co.uk/gallery/cherington-open-plan-kitchen/

By the way thanks for the help on this.

I'm using MarkupSEO which is auto detecting the image field as it turns out so I don't actually need to add anything into the AutoFbPost field for image field name etc. Although I have anyway. The default 'images' field.

Thank you for your time

Share this post


Link to post
Share on other sites

Well I don't see anything wrong....
But it is your default description indeed [MarkupSEO isn't picking up body/description field?].

Personally I'm not using MarkupSEO, I have everything in my _init.php configured and, so far at least, it is working....
It's a pretty old website, still running pw 2.7.1/2..... Haven't tried it on pw 3.x yet, but I guess this has nothing to with pw...

I had a strange experience once where FB wasn't picking up any opengraph whatsoever, and I actually had to create a facebook app id for that site, but so far I've encountered it only once.... that was very weird too.... 

Sorry I can't be more informative....

  • Like 1

Share this post


Link to post
Share on other sites

Weirdly it's working now... Or at least the image is loading the correct one.

I have just cleared the default meta description from the MarkupSEO module settings and added directly to the homepage and then used the body as the smart description so it is used for open graph description and meta description for all other pages and that isn't showing the correct description yet when being posted but perhaps Facebook caches the results for a while?
 

Either way you have been a BIG help and I can't thank you enough for taking the time to take a look with me!

Thank you @videokid

  • Like 1

Share this post


Link to post
Share on other sites

Hello,

this module has been updated and it is now compatible with Graph API version 2.10.

Parameters 'description' and 'name' are not supported by the new Graph API version. Therefore, fields for description and name cannot be provided anymore.

  • Like 4

Share this post


Link to post
Share on other sites

Hi,

I have problems to connect the module to FB app, I get the error mentioned by benbyf her above: AutoFbPost: post failed; click here to log in with Facebook. Then the error message says: "App not configured. This App is still in development mode and you can't access it"...

Is there anything else I need to set in facebook? I've tried all possible configuration and I don't know where to check now. Screenshot attached. Thanks a lot for any help.

 

fb.png

fb1.png

fb2.png

fb3.png

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By BitPoet
      I'm really in love with FormBuilder, but the one thing missing to match all my end users' expectations were repeatable field groups. Think repeaters, in ProcessWire terms. Our primary application of PW is our corporate intranet, so "lines" of fields are quite common in the forms I build. We have all kinds of request forms where the information for a varying number of colleagues needs to be entered (from meal order to flight booking request) and where it is simply impractical to send a form for each, and I don't want to clutter my forms with multiple instances of fields that may only get used ten percent of the time.
      That's why I started to build FormBuilderMultiplier (link to GitHub).
      What it does:
      Adds an option to make a regular Fieldgroup repeatable Lets you limit the number of instances of a Fieldgroup on the form Adds an "Add row" button the form that adds another instance of the Fieldgroup's fields Adds a counter suffix at the end of every affected field's label Stores the entered values just like regular fields Makes the entered values available in preview and email notifications Supports most text based fields, textareas and selects (really, I haven't had enough time to test all the available choices yet) What it doesn't do (yet):
      Support saving to ProcessWire pages (i.e. real Repeaters) I haven't tested all the validation stuff, Date/Time inputs etc. yet, but since I'm utterly swamped with other stuff at work, I didn't want to wait until I have it polished. Any feedback is welcome. There might also be some issues with different output frameworks that I haven't encountered yet. The forms I work with mostly use UIKit.
      Status:
      Still alpha, so test well before using it in the field.
      Known issues:
      When rows are added, the form's iframe needs to be resized, which isn't completely clean yet.
      How it works:
      The Fieldgroup settings are added through regular hooks, as is the logic that adds the necessary field copies for processing the form and displaying previews.
      "Multiplied" field instances are suffixed with _NUM, where NUM is an incremental integer starting from 1. So if you have add two fields named "surname" and "givenname" to a fieldgroup and check the "multiply" checkbox, the form will initially have "surname_1" and "givenname_1" field (I'm still considering changing that to make the risk to shoot oneself into the foot by having a regular "surname_1" field somewhere else in the form less likely).
      When a "row" is added, the first row is cloned through JS and the counter in the fields' IDs, names and "for" attributes as well as the counter in the label are incremented before appending the copies to the Fieldset container in the form.
      To keep backend and frontend in sync, a hidden field named [name of the fieldset]__multiplier_rows is added to the form. Both the backend and the frontend script use this to store and retrieve the number of "rows".
      ToDo:
      Naturally, add the option to store the data in real repeaters when saving to pages. Do a lot of testing (and likely fixing). Make a few things (like the "Add row" button label etc.) configurable in field(set) context. Add a smooth API to retrieve the multiplied values as WireArrays. The mandatory moving screenshot:

    • By MoritzLost
      Hello there,
      I'm working on a tiny textformatter module that searches the text for titles of other pages on your site and creates hyperlinks to them. I'm not sure if something like this exists already, but I haven't found anything in the module directory, so I wrote my own solution 🙂
      It's not properly tested yet and is still missing some functionality I would like to implement, so at the moment it should be considered in BETA. Features include limiting the pages that will get searched by template, and adding a custom CSS class to the generated hyperlinks. As I'm writing this I noticed that it will probably include unpublished and hidden pages at the moment, so yeah ... it's still in development alright 😅
      You can download the module from Github:
      https://github.com/MoritzLost/TextformatterPageTitleLinks
      There's some more information in the readme as well.
      Anyway, let me know what you think! I'm happy about any feedback, possible improvements or ideas on how to improve the module. Cheers.
    • By adrian
      This module provides a way to rapidly generate Page fields and the required templates and pages for use as a drop down select (or any other Page field type).
      This module will let you create a full page field setup in literally a few seconds 
      To use, run Page Field Select Creator from the Setup Menu
      Enter a Field Title, eg: Room Types Select Options - These will become the child pages that will populate the page field select options. There are two different options.
       
      Option 1. TITLE FIELD ONLY - enter one option per line, eg:
       
      Single
      Double
      Suite
       
       
      Option 2. MULTIPLE FIELDS - the first line is used for the field names and the first field must be 'Title'. Subsequent lines are the values for the fields, eg:
       
      Title, Number of Beds, Number of People, Kitchen Facilities
      Single, 1, 1, Fridge Only
      Double, 2, 2, Fridge Only
      Suite, 3, 6, Full Kitchen
        Choose the parent where the page tree of options will be created, eg a hidden "Options" parent page Select a "Deference in API as" option depending on your needs Choose the input field type Check whether "Allow new pages to be created from field?" should be enabled. As an example, if you entered "Room Types" as the field title, you would end up with all of the following automatically created:
      a fully configured page field called: room_types MULTIPLE FIELDS OPTION - 3 additional fields - number_of_beds, number_of_people, kitchen a parent template called: room_types a child template called: room_types_items (with either just a title field, or with the 3 additional fields as well) a parent page called: Room Types a series of child pages named and titled based on the per line entries in the Select Options textarea The templates are configured such that the "room_types_items" child template can only have the main "room_types" template as a parent, and vice versa.

      Then all you have to do is add the newly created page field to any template you want and you're ready to go!
       
      You can grab it from:
       
      Modules directory: http://modules.processwire.com/modules/process-page-field-select-creator/
      Github: https://github.com/adrianbj/ProcessPageFieldSelectCreator
       

    • By bernhard
      WHY?
      This module was built to fill the gap between simple $pages->find() operations and complex SQL queries.
      The problem with $pages->find() is that it loads all pages into memory and that can be a problem when querying multiple thousands of pages. Even $pages->findMany() loads all pages into memory and therefore is a lot slower than regular SQL.
      The problem with SQL on the other hand is, that the queries are quite complex to build. All fields are separate tables, some repeatable fields use multiple rows for their content that belong to only one single page, you always need to check for the page status (which is not necessary on regular find() operations and therefore nobody is used to that).
      In short: It is far too much work to efficiently and easily get an array of data based on PW pages and fields and I need that a lot for my RockGrid module to build all kinds of tabular data.

      Basic Usage

       
      Docs & Download
      https://modules.processwire.com/modules/rock-finder/
      https://github.com/BernhardBaumrock/RockFinder
       
      Changelog
      180817, v1.0.6, support for joining multiple finders 180810, v1.0.5, basic support for options fields 180528, v1.0.4, add custom select statement option 180516, change sql query method, bump version to 1.0.0 180515, multilang bugfix 180513, beta release <180513, preview/discussion took place here: https://processwire.com/talk/topic/18983-rocksqlfinder-highly-efficient-and-flexible-sql-finder-module/
    • By BitPoet
      MediaLibrary
      Update: MediaLibrary can now be found in the official module list.
      Out of necessity, I've started to implement a simple media library module.
      The basic mechanism is that it adds a MediaLibrary template with file and image fields. Pages of this type can be added anywhere in the page tree.
      The link and image pickers in CKEditor are extended to allow quick selection of library pages from dropdowns. In the link picker this happens in the MediaLibrary tab, where you can also see a preview of the selected image. In the image picker, simply select a library from the dropdown at the top, everything else is handled by standard functionality.
      I've put the code onto github. This module is compatible with ProcessWire 3.
      Steps to usage:
      Download the module's zip from github (switch to the pw3 branche beforehand if you want to test on PW 3.x) and unpack it into site/modules Click "Modules" -> "Refresh" in the admin Click "Install" for MediaLibrary For testing, create a page with the MediaLibrary template under home (give it an expressive title like 'Global Media') and add some images and files Edit a differnt page with a CKEditor field and add a link and an image to see the MediaLibrary features in action (see the screencap for details) Optionally, go into the module settings for MediaLibrary Note: this module is far from being as elaborate as Kongondo's Media Manager (and doesn't plan to be). If you need a feature-rich solution for integrated media management, give it a look.
      Feel free to change the settings for MediaFiles and MediaImages fields, just keep the type as multiple.
      There are some not-so-pretty hacks for creating and inserting the correct markup, which could probably be changed to use standard input fields, though I'm a bit at a loss right now how to get it to work. I've also still got to take a look at error handling before I can call it fit for production. All feedback and pointers are appreciated (that's also why I post this in the development section).

      Edit 09.03.2016 / version 0.0.4: there's now also a "Media" admin page with a shortcut to quickly add a new library.

      Edit 01.05.2016:
      Version 0.0.8:
      - The module now supports nested media libraries (all descendants of eligible media libraries are also selectable in link/image picker).
      - There's a MediaLibrary::getPageMediaLibraries method you can hook after to modify the array of available libraries.
      - You can switch between (default) select dropdowns or radio boxes in the module configuration of MediaLIbrary to choose libraries.
      Edit 10.10.2018:
      Version 0.1.3:
      - Dropped compatibility for ProcessWire legacy versions by adding namespaces
      - Allow deletion of libraries from the Media overview admin page
      - Added an option to hide media libraries from the page tree (optionally also for superusers)