Jump to content

Publish to Twitter module


Ferdi Derksen
 Share

Recommended Posts

Hi all,

Just in front of the Easterweekend, my first contribution to the modules section of ProcessWire. I created a module to send Tweets when selected at the page editor. From version 0.8.3 up the module is only to use in v3.x. When using ProcessWire v2.x you should use version 0.8.2.

In short this module offers an option to publish a page to Twitter when the date for publishing is past/scheduled.

After filling out the Twitter credentials, select your preferable template(s) which should have the option added to Tweet the pages using it. Additional select the field to use as publicationdate to check if the Tweet should be send now or later, a field which contains the page title.

Optional you can fill out the name of the website which will be added after the title (in case space is available).

Optional you can select the field where the page image(s) are placed (only one will be tweeted).

Optional you can fill out Bit.ly credentials for shortening URLs.

Includes instructions to set a cron (template or LazyCron), returns log in assets folder.

Uses (included) TwitterOAuth PHP library written by abraham.

http://modules.processwire.com/modules/publish-to-twitter/

https://github.com/FerdiAgrio/PublishToTwitter

Enjoy!

  • Like 14
Link to comment
Share on other sites

  • 4 months later...

Without the namespace, this error is triggered : 

 

Session: error setting certificate verify locations: CAfile: [...]\site\assets\cache\FileCompiler\site\modules\PublishToTwitter\TwitterOAuth\Abraham\TwitterOAuth\cacert.pem CApath: none

 

In TwitterOAuth.php line 353:

CURLOPT_CAINFO => __DIR__ . DIRECTORY_SEPARATOR . 'cacert.pem',

 

Link to comment
Share on other sites

  • 2 months later...
  • 3 months later...

Hi @Ferdi Derksen,

I installed your module on our test location and it works like a charm. Just one additional question. Would it be possible to execute the same code when a page is created and saved via the  (API) $page->save. I added $p->publish_to_twitter = 1; before the $page->save and removed the wire()->input->post->id, but when I open the page just created, the check box is checked, but the page is not (yet) tweeted. Only if I click on save manually again its tweeted. Any idea what I need to amend in the code to get this working? 

Cheers

Link to comment
Share on other sites

Hi @DL7,

First of all I assume you are using the module for version 3.x
I think the first thing to change is the 'autoload' option in the getModuleInfo() method to 'autoload' => true (or add another template you are using for the creation of pages).

Please let me know if that's working for you.

Cheers!

 

  • Like 1
Link to comment
Share on other sites

Hi @Ferdi Derksen,

Thanks. Tried it, and its still not working. I also checked the code and concluded that the somehow the addHookAfter is not triggered, when using the $page->save via the API. I work when using the backend save. Not sure if this is expected behaviour?

Link to comment
Share on other sites

  • 2 months later...

Hello @Ferdi Derksen,

i just installed the module on a pw3.0.62 and set it up, adding a template as the template whose pages should be tweeted, saved. The module settings "page title field" and the "datefield to check for publication" contain both a drop-down with fields of another template, both drop-downs are slightly different, first being a subset of the other.

Would you have an idea of what went wrong?

I would appreciate any help.

Link to comment
Share on other sites

Hi @loukote,

There is no limitation/filtering in fields of the selected template(s). Therefore those drop-downs are selecting fields with type "Text" for "page title field" and type "Datetime" for "datefield to check for publication" so the checks when Tweeting (or selecting which to Tweet) can be done properly.

Cheers,

Ferdi

Link to comment
Share on other sites

  • 1 month later...

not really sure by the docs how to implement this module after adding the settings in the admin. any extra guidance? sorry.

Just saw the Tweet this page check box... and now works, not sure this is mentioned on github however.

Link to comment
Share on other sites

  • 2 months later...
On 5/23/2017 at 9:56 AM, Ferdi Derksen said:

There is no limitation/filtering in fields of the selected template(s). Therefore those drop-downs are selecting fields with type "Text" for "page title field" and type "Datetime" for "datefield to check for publication" so the checks when Tweeting (or selecting which to Tweet) can be done properly.

@Ferdi Derksen Let me come back with the earlier reported issue. I do not know what and how happens but: no matter which template is selected on the PublishToTwitter configuration page in the "Publish to twitter template" field, the "page title" and "datefield to check for publication" fields contain a subset of fields used only in the "user" template like "username", "date joined"... (the user template has few more fields that the standard installation.) The "datefield to check for publication" offers items that are not of a date type. The "page images" field gives only one line, images, which is OK. No matter what template is selected in the "publish to twitter templates" field, the misbehaving fields offer the same items.

Would you have any idea what should I check to correct this issue? Would screenshots help?

Link to comment
Share on other sites

Hi @loukote,

Maybe a stupid question, but you did save the module after selecting a template, right?

The list of fields available is depending on the template(s) you selected at the first place. This should indicate the "user" template is selected now.
On the other hand, the "date" field is build with a selector for fields of type FieldtypeDatetime or FieldtypeText.

Otherwise send/place some screenshots, happy to help!

Link to comment
Share on other sites

Help would be appreciated, so here are the screenshots.

To make sure, I uninstalled the module and installed a fresh from github. Here is how the the config window looks: before selecting any template, the Page title and Datefield to check... are already pre-filled with values that apparently come from the user template.

image.thumb.png.ccfbb8430e2d31cc26af14470e9a0548.png

When the needed template is selected, the options of these two selects do not change. After the config page is submitted/saved, nothing changes -- same old fields as options in the two selects. And they stay the same even when another template is entered and the config page is saved.

Does it help you to help me? ;)

 

 

Link to comment
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
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Similar Content

    • By monollonom
      (once again I was surprised to see a work of mine pop up in the newsletter, this time without even listing the module on PW modules website 😅. Thx @teppo !)
      FieldtypeQRCode
      Github: https://github.com/romaincazier/FieldtypeQRCode
      Modules directory: https://processwire.com/modules/fieldtype-qrcode/
      A simple fieldtype generating a QR Code from the public URL of the page, and more.
      Using the PHP library QR Code Generator by Kazuhiko Arase.

      Options
      In the field’s Details tab you can change between .gif or .svg formats. If you select .svg you will have the option to directly output the markup instead of a base64 image. SVG is the default.
      You can also change what is used to generate the QR code and even have several sources. The accepted sources (separated by a comma) are: httpUrl, editUrl, or the name of any text/URL/file/image field.
      If LanguageSupport is installed the compatible sources (httpUrl, text field, ...) will return as many QR codes as there are languages. Note however that when outputting on the front-end, only the languages visible to the user will be generated.
      Formatting
      Unformatted value
      When using $page->getUnformatted("qrcode_field") it returns an array with the following structure:
      [ [ "label" => string, // label used in the admin "qr" => string, // the qrcode image "source" => string, // the source, as defined in the configuration "text" => string // and the text used to generate the qrcode ], ... ] Formatted value
      The formatted value is an <img>/<svg> (or several right next to each other). There is no other markup.
      Should you need the same markup as in the admin you could use:
      $field = $fields->get("qrcode_field"); $field->type->markupValue($page, $field, $page->getUnformatted("qrcode_field")); But it’s a bit cumbersome, plus you need to import the FieldtypeQRCode's css/js. Best is to make your own markup using the unformatted value.
      Static QR code generator
      You can call FieldtypeQRCode::generateQRCode to generate any QR code you want. Its arguments are:
      string $text bool $svg Generate the QR code as svg instead of gif ? (default=true) bool $markup If svg, output its markup instead of a base64 ? (default=false) Hooks
      Please have a look at the source code for more details about the hookable functions.
      Examples
      $wire->addHookAfter("FieldtypeQRCode::getQRText", function($event) { $page = $event->arguments("page"); $event->return = $page->title; // or could be: $event->return = "Your custom text"; }) $wire->addHookAfter("FieldtypeQRCode::generateQRCodes", function($event) { $qrcodes = $event->return; // keep everything except the QR codes generated from editUrl foreach($qrcodes as $key => &$qrcode) { if($qrcode["source"] === "editUrl") { unset($qrcodes[$key]); } } unset($qrcode); $event->return = $qrcodes; })
    • By Sebi
      AppApiFile adds the /file endpoint to the AppApi routes definition. Makes it possible to query files via the api. 
      This module relies on the base module AppApi, which must be installed before AppApiFile can do its work.
      Features
      You can access all files that are uploaded at any ProcessWire page. Call api/file/route/in/pagetree?file=test.jpg to access a page via its route in the page tree. Alternatively you can call api/file/4242?file=test.jpg (e.g.,) to access a page by its id. The module will make sure that the page is accessible by the active user.
      The GET-param "file" defines the basename of the file which you want to get.
      The following GET-params (optional) can be used to manipulate an image:
      width height maxwidth maxheight cropX cropY Use GET-Param format=base64 to receive the file in base64 format.
    • By MarkE
      This fieldtype and inputfield bundle was built for storing measurement values within a field, rendering them in a variety of formats and converting them to other units or otherwise modifying them via the API.
      The API consists of a number of predefined functions, some of which include...
      render() for rendering the measurement object, valueAs() for converting the value to another unit value, convertTo() for converting the whole measurement object to different units, and add() and subtract() for for modifying the stored value by the value (converted as required) in another measurement. In the admin the inputfield includes a checkbox (which can be optionally disabled) for converting values on page save. For an example if a value was typed in as centimeters, the unit was changed to metres, and the page saved with this checkbox selected, said value would be automatically converted so that e.g. 170 cm becomes 1.7 m.

      A simple length field using Fieldtype Measurement and Inputfield Measurement.
      Combination units (e.g. feet and inches) are also supported.
      Please note that this module is 'proof of concept' at the moment - there are limited units available and quite a lot of code tidying to do. More units will be added shortly.
      See the GitHub at https://github.com/MetaTunes/FieldtypeMeasurement for full details and updates.
    • By tcnet
      File Manager for ProcessWire is a module to manager files and folders from the CMS backend. It supports creating, deleting, renaming, packing, unpacking, uploading, downloading and editing of files and folders. The integrated code editor ACE supports highlighting of all common programming languages.
      https://github.com/techcnet/ProcessFileManager

      Warning
      This module is probably the most powerful module. You might destroy your processwire installation if you don't exactly know what you doing. Be careful and use it at your own risk!
      ACE code editor
      This module uses ACE code editor available from: https://github.com/ajaxorg/ace

      Dragscroll
      This module uses the JavaScript dragscroll available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability to drag the table horizontally with the mouse pointer.
      PHP File Manager
      This module uses a modified version of PHP File Manager available from: https://github.com/alexantr/filemanager
       
    • By tcnet
      This module implements the website live chat service from tawk.to. Actually the module doesn't have to do much. It just need to inserted a few lines of JavaScript just before the closing body tag </body> on each side. However, the module offers additional options to display the widget only on certain pages.
      Create an account
      Visit https://www.tawk.to and create an account. It's free! At some point you will reach a page where you can copy the required JavaScript-code.

      Open the module settings and paste the JavaScript-code into the field as shown below. Click "Submit" and that's all.

      Open the module settings
      The settings for this module are located int the menu Modules=>Configure=>LiveChatTawkTo.

       
×
×
  • Create New...