Jump to content
Wanze

Module: TemplateEngineFactory

Recommended Posts

Hi Sérgio,

As your "normal" template files inside "site/templates" act as controllers, any file you prepend (_init.php) or append (_main.php) works there too. I use the _init.php file to pass any global variables to my loaded view, e.g. main menu items.

You can store your assets anywhere you want and reference them like you did before, you just do this in the view.

If you want to try out the module a bit, I suggest to follow the mini tutorial here: https://github.com/wanze/TemplateEngineSmarty#best-practices

This is for smarty, but it should work for other template engines as well.

Cheers

Share this post


Link to post
Share on other sites

Thank you Wanze!

I though exactly this but for some reason didn't work as expected. But it's probaly my fault as I was very tired yesterday.

I'll take a look on the tutorial and try again later. :)

Share this post


Link to post
Share on other sites

Hi, one little question, maybe I just missed something. Is there a way to use a chunk inside a foreach loop?
I use Twig as TemplateEngine, assume the following:
 
/templates/blog.php ... 
/templates/view/blog.twig

...
{% for post in posts %}
  {% include 'partials/intro.twig' %}
{% endfor %}
...

Inside this partial I need some php logic which I don't want to implement using twig. I've no idea how to archive this. If I need something related outside a loop, I write the logic inside my /templates/[name].php file, if I need some code more than once, I define it in a special prependTemplateFile (at this point I would also prefer using a related php file). I know, I could use TemplateDataProvider Page::renderChunk() method which does exactly what I need, but I would prefer using a built-in way (if there is one). 
 
Using TemplateDataProvider:

{% for post in posts %}  
  {{page.renderChunk('partials/intro.twig', post)}}
{% endfor %}

/dataproviders/IntroChunk.php: Logic/assign variables; /partials/intro.twig markup

Share this post


Link to post
Share on other sites

Hi justb3a,

The module provides the following functionality to load any view (partial), populate the variables and render its output.

$factory = $modules->get('TemplateEngineFactory');
$partial = $factory->load('partials/intro.twig');
$partial->set('post', $post);
$partial->render();

I know that this is not a direct solution to your question. I don't know TemplateDataProvider myself, but I guess you'd have to write some helper functions to achieve the same functionality.

My approach would probably be to prepare the output already in your blog.php template file, where you're getting the posts. Something like this:

// In blog.php

$blogs = array();
foreach ($pages->find('template=blogs') as $blog) {
  $partial = $factory->load('partial/intro.twig');
  $partial->set('blog', $blog);
  $blogs[] = $partial;
}
$view->set('blogs', $blogs);

// In blog.twig

{% for post in posts %}
  {% post.render %}
{% endfor %}

The module definitely needs an update so that multiple variables can be passed to the view....

Cheers

Share this post


Link to post
Share on other sites
// In blog.php

$blogs = array();
foreach ($pages->find('template=blogs') as $blog) {
  $partial = $factory->load('partial/intro.twig');
  $partial->set('blog', $blog);
  $blogs[] = $partial;
}
$view->set('blogs', $blogs);

// In blog.twig

{% for post in posts %}
  {% post.render %}
{% endfor %}

Using this solution I had to loop twice over all blog posts and this is exactly what I want to avoid. I do much more (especially markup stuff) inside the loop which I don't want to construct in php.

I would love to have the possibility to load a related php file for a chunk. $chunk = $factory->load('chunks/pager'); should load /templates/chunks/pager.php where I can do some php stuff and assign variables to /templates/view/chunks/pager.tmpl. Do you see any possibility to achieve this?

By the way: I added a "setMultiple" method inside your factory to be able to submit more than one property at once:

// get posts
$posts = $pages->find("xxx");
$view->setMultiple(array(
  'posts' => $posts,
  'hello' => 'world'
));

// get pager
$factory = $modules->get('TemplateEngineFactory');
$chunk = $factory->load('partials/pager');
if ($chunk) {
  $chunk->setMultiple(array(
    'posts' => $posts,
    'options' => $options->pager
  ));
  $view->set('pager', $chunk->render());
}

If you like it I would send a pull request. But you had to add it to all of your TemplateEngines except TemplateEngineTwig.

Furthermore I updated TemplateEngineTwig: I added Debug-Mode to be able to use {{ dump() }} and I updated the twig version using composer. I could also imagine to implement a little setting "choose twig version" and add the latest versions as you did without composer. If this is fine for you (please tell me which version), I would send a pull request for this, too.  

Share this post


Link to post
Share on other sites
I would love to have the possibility to load a related php file for a chunk. $chunk = $factory->load('chunks/pager'); should load/templates/chunks/pager.php where I can do some php stuff and assign variables to /templates/view/chunks/pager.tmpl. Do you see any possibility to achieve this?

Sounds useful, I will take a look at it. I think it should already be possible as you can load any ProcessWire template and render it, e.g.

Edit: Actually I think the code won't work as the hook to modify the rendered output is attached to Page::render(). It should be possible to move the hook to TemplateFile::render()

$chunk = new TemplateFile($config->paths->templates . 'intro.php');
$chunk->foo = 'bar'; // Can be forwarded to Twig in intro.php
$chunk->render(); // This should return the output of the intro.twig template file

But I never tried it, so not 100% sure it works. A little wrapper on the module class wouldn't hurt though, e.g. $factory->loadController('intro.php').

If you like it I would send a pull request. But you had to add it to all of your TemplateEngines except TemplateEngineTwig.

Perfect, please send a pull request (target dev branch) :)

I'll update ProcessWire and Smarty engines and notify the author of Jade as well.

Furthermore I updated TemplateEngineTwig: I added Debug-Mode to be able to use {{ dump() }} and I updated the twig version using composer. I could also imagine to implement a little setting "choose twig version" and add the latest versions as you did without composer. If this is fine for you (please tell me which version), I would send a pull request for this, too.  

Nice, please send :) Do you see any benefit in having multiple Twig versions available to choose from?

Cheers

  • Like 1

Share this post


Link to post
Share on other sites

I sent two pull requests:

Example: How to use a chunk
In template file: /site/templates/view/template.twig
<?php foreach ($nav_pages as $p): ?>
  <?php $page->renderChunk('chunks/nav-item', array('page' => $p)); ?>
<?php endforeach; ?>
/site/templates/chunks/nav-item.php
<?php namespace ProcessWire;

$foo = 'do some logic // something with the contextual data';
$author = $this->page->createdUser;

$view->setMultiple( array(
  'author' => $author,
  'item' => $this->page,
  'foo' => $foo
));
/site/templates/view/chunks/nav-item.tpl
Author: <?= $author ?> <br />
<a href="<?= $item->url ?>" title="<?= $foo ?>">
  <?= $item->title ?>
</a>
 
  • Like 3

Share this post


Link to post
Share on other sites

I got a question for translating the strings in the template files, as I have a multilanguage site and use the Smarty Engine. The ProcessWire Language Translator module does not list the files in the folder /site/templates/views nor I can select and translate those files with the "translate file" button. I only see .php files under /site/templates/. My template files got the .html extension but with .tpl extension it also doesn´t work. What do I have to do to translate my template files? Here is my actual file /site/templates/views/products.html

{extends file="main.html"}

{block name="content"}
<h1>Check out the following products</h1>
<span>{__('Dieser String muss in alle Sprachen übersetzt werden')}</span>
<ul>
{foreach $products as $p}
<li><a href="{$p->url}">{$p->title}</a></li>
{/foreach}
</ul>
{/block}

{block name="javascript"}
<script type="javascript" src="{$config->urls->templates}js/products.js"></script>
{/block}

Share this post


Link to post
Share on other sites

Hi jmartsch,

One solution would be to set your strings in the products.php template file and forward them to the view, for example:

$view->set('strings', array(
  'hello' => __('Hallo'),
  'test'=> __('Test'),
));

// ... products.tpl

{$strings.hello}

You could also organize all your translations in a single file and reference them via textdomain.

Another possibility would be to register a smarty function which grabs your translation from a central file.

Cheers

  • Like 1

Share this post


Link to post
Share on other sites

Hi Wanze. First, let me say thank you for this module. I was working with a »twig CMS« lately and loved it. So your module is a great and easy way to take this into a PW project.

I am struggling with twig’s template inheritance and the global template file in your module. Perhaps I got it wrong – but I thought I can define »app« as my global template file and put in it my html like …

// templates/views/app.html
<html>
<body>
 <h1>My Site</hi>
 {% block content %}
  <p>My Content</p>
 {% endblock %}
</body
</html>

… and 

// templates/views/home.html
{% extends "app.html" %}

{% block content %}
 <p>My Homepage</p>
{% endblock %}

Apparently the home.html is somewhere loaded (I get an error message if there is an syntax issue in it) but the app.html is rendered (without the markup in home.html)

Do I have to configure something in the controller files?

Does the inheritance work like this within your module?

Share this post


Link to post
Share on other sites

@suntrop

Thanks! If you are using the inheritance feature of Twig, you shouldn't use a global template file, I think that might solve the problem.

At the moment, twig always receives the "app.html" template. But what it needs is to receive the "home.tpl" template file. Twig then sees that this template is inheriting from "app.html" and does its magic :)

Edit:

Maybe this helps https://github.com/wanze/TemplateEngineSmarty#best-practices

It's Smarty, but the template inheritance stuff seems to work the same way in various engines

@szabesz

Cool, nice tutorial! Thanks for sharing the link  ^-^

Cheers

  • Like 1

Share this post


Link to post
Share on other sites

Wanze, thanks for your reply and help. It works now. I think I mixed up global file template and the inheritance of the template engine.

Thanks for the tutorial (and link) as well. Haven't seen it unfortunately. Somewhere about the last sentence made it clear :-)

BTW … it works with PW 3 (just smarty has some Notices, but twig works well so far)

  • Like 2

Share this post


Link to post
Share on other sites

Perhaps I was wrong and it doesn't work well with PW 3. 

{% if page.images|length > 0 %} 

results in …

Fatal error: Exception: An exception has been thrown during the rendering of a template ("Method Page::images does not exist or is not callable in this context")

Share this post


Link to post
Share on other sites

It works well with PW3. This is a twig issue. You have to use:

{% if page['images'] %}

Have a look at this page: How to check if a variable or value exists, this helped me a lot.

Or try to change the Formatted value in the field settings to Array of items. Then you should be able to test using length because this way it returns an empty array.

  • Like 1

Share this post


Link to post
Share on other sites

Sorry to bother you guys again :-) 

I tried to add the Text extension to truncate the body for my articles. In my articles.php (will move it to a better place later) I have:

$page->addHookAfter('initTwig', $twig, 'addExtension');

function addExtension($twig){
	$twig->addExtension(new Twig_Extensions_Extension_Text());
}

… and I uploaded this https://github.com/twigphp/Twig-extensions to /site/modules/TemplateEngineTwig/twig/lib/Twig/Extension

But I still get the message The filter "truncate" does not exist in "articles.twig"

Share this post


Link to post
Share on other sites

Your hook does not work for several reasons, try it like this:

wire()->addHookAfter('TemplateEngineTwig::initTwig', function($event) {
  $twig = $event->arguments('twig');
  $twig->addExtension(new Twig_Extensions_Extension_Text());
});

Share this post


Link to post
Share on other sites

Thank you! This one produces the same error message. Truncate doesn't exist

Path where I saved the extension should be fine: /site/modules/TemplateEngineTwig/twig/lib/Twig/Extension/Extension/Text.php Isn't it?

Share this post


Link to post
Share on other sites

I don't know Twig myself, but I think the problem is that the initTwig() method is called before you are registering your hook, so it is not executed.

Is articles.php your template (controller)? Can you try the following:

wire()->addHookAfter('TemplateEngineTwig::initTwig', function($event) {
  $twig = $event->arguments('twig');
  $twig->addExtension(new Twig_Extensions_Extension_Text());
});

// Trigger initTwig again, just for testing
$factory = $modules->get('TemplateEngineFactory');
$factory->load('articles', true);

This is not nice, if it works, I have to think about other ways...

Share this post


Link to post
Share on other sites

It works well with PW3. This is a twig issue. You have to use:

{% if page['images'] %}

Have a look at this page: How to check if a variable or value exists, this helped me a lot.

Or try to change the Formatted value in the field settings to Array of items. Then you should be able to test using length because this way it returns an empty array.

While this one will work with a simple array, I can't use it to display a multi array

This one produces an error when the form isn't submitted

{{ input.post.name }}

and this one doesn't display anything 

{{ input['post']['name'] }}

Any ideas how to fix this?

Share this post


Link to post
Share on other sites

HI Wanze, many thanks for your help. I didn't get an email … sometimes I feel like the email updates doesn't work quite well.

However, articles.php was my controller file. Unfortunately it doesn't work like that. Had tried Smarty but had problems with it too. Maybe I shouldn't use either of them and go with plain PHP.

Share this post


Link to post
Share on other sites

@suntrop:
 
This is how I add a Twig Extension (in my case the Intl Extension, but this shouldn't matter):
 
add Twig Extensions via composer

{
    "require": {
        "twig/extensions": "~1.3"
    }
}

add Hook after initTwig() (as Wanze said)

$this->addHookAfter('TemplateEngineTwig::initTwig', $this, 'addTranslationFunctions');

add Twig Extension

public function addTranslationFunctions(HookEvent $event) {
    $this->twig = $event->arguments(0);
    if (!class_exists('Twig_Extensions_Extension_Intl')) {
        require(wire('config')->paths->TemplateTwigReplaceLanguageSupport . 'vendor/autoload.php');
      }

      $this->twig->addExtension(new Twig_Extensions_Extension_Intl());
  }

---

To check for a multidimensional array, you could try:

{% if input.post is not empty and 'name' in input.post|keys %}
  • Like 2

Share this post


Link to post
Share on other sites

Hi justb3a

Thanks, that one worked for me! But I removed Twig anyway … it doesn't make sense to me.

Share this post


Link to post
Share on other sites

Hi Wanze,

EDIT: Found the solution by myself. Added to the bottom.

I got a problem with Search and the TemplateEngineFactory (I use Smarty). If I use AJAX my search.php should return a JSON response (with correct headers), if not it should render the template.

The problem is that if I have a template file search.tpl it will always be rendered even if I request with AJAX.

So I renamed the template file and tried to load it on demand in search.php:

if ($config->ajax) {
        header("Content-type: application/json"); // Set header to JSON
        echo $matches->toJSON(); // Output the results as JSON via the toJSON function
    }
    else{
        $factory = $modules->get('TemplateEngineFactory');
        $view = $factory->load('search-results.tpl');
        echo $view->render();
        exit;
    } 

search-results.tpl

{extends file="main.tpl"}
{block name="content"}
    <h1>{$page->title}</h1>
    {$content}
{/block}

Now my AJAX response works and the template gets rendered BUT it seems that variables assignments which I do in the _init.php are not executed. For example I set the browsers title and the main menu structure there, but the menu or the title do not get rendered, although _init.php is prepended because if I do an echo there, it displays on the page.

I hope somebody can help me with this problem.

EDIT: Solution is to just exit at the end of the AJAX clause, so the template does not get rendered :)

if ($config->ajax) {
        header("Content-type: application/json"); // Set header to JSON
        echo $matches->toJSON(); // Output the results as JSON via the toJSON function
        exit;
    }
  • Like 1

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
      After forgetting the class name of the wonderful AdminPageFieldEditLinks module for what feels like the 100th time I decided I needed to give my failing memory a helping hand...
      Autocomplete Module Class Name
      Provides class name autocomplete suggestions for the "Add Module From Directory" field at Modules > New.
      Requires ProcessWire >= v3.0.16.
      Screencast

      Installation
      Install the Autocomplete Module Class Name module.
      Configuration
      Choose the type of autocomplete options list: "Module class names from directory" or "Custom list of module class names". The latter could be useful if you regularly install some modules and would prefer a shorter list of autocomplete suggestions. The list of class names in the modules directory is generated when the Autocomplete Module Class Name module is installed. It doesn't update automatically (because the retrieval of the class names is quite slow), but you can use the button underneath when you want to retrieve an updated list of class names from the directory. The "fuzzy search" option uses custom filter and item functions for Awesomplete so that the characters you type just have to exist in the module class name and occur after preceding matches but do not need to be contiguous. Uncheck this option if you prefer the standard Awesomplete matching. Custom settings for Awesomplete can be entered in the "Awesomplete options" field if needed. See the Awesomplete documentation for more information.  
      https://github.com/Toutouwai/AutocompleteModuleClassName
      https://modules.processwire.com/modules/autocomplete-module-class-name/
    • By teppo
      MarkupMenu is a markup module for generating menu trees. When provided a root page as a starting point, it generates a navigation tree (by default as a HTML "<ul>" element wrapped by a "<nav>" element) from that point onwards. If you've also provided it with current (active) page, the menu will be rendered accordingly, with current item highlighted and items rendered up to that item and its children (unless you disable the "collapsed" option, in which case the full page tree will be rendered instead).
      Modules directory: https://modules.processwire.com/modules/markup-menu/ GitHub repository: https://github.com/teppokoivula/MarkupMenu Usage
      As a markup module, MarkupMenu is intended for front-end use, but you can of course use it in a module as well. Typically you'll only need the render() method, which takes an array of options as its only argument:
      echo $modules->get('MarkupMenu')->render([ 'root_page' => $pages->get(1), 'current_page' => $page, ]); Note: if you omit root_page, site root page is used by default. If you omit current_page, the menu will be rendered, but current (active) page won't be highlighted etc.
      A slightly more complex example, based on what I'm using on one of my own sites to render a (single-level) top menu:
      echo $modules->get('MarkupMenu')->render([ 'current_page' => $page, 'templates' => [ 'nav' => '<nav class="{classes} menu--{menu_class_modifier}" aria-label="{aria_label}">%s</nav>', 'item_current' => '<a class="menu__item menu__item--current" href="{item.url}" tabindex="0" aria-label="Current page: {item.title}">{item.title}</a>', ], 'placeholders' => [ 'menu_class_modifier' => 'top', 'aria_label' => 'Main navigation', ], 'include' => [ 'root_page' => true, ], 'exclude' => [ 'level_greater_than' => 1, ], ]); Note: some things you see above may not be entirely sensible, such as the use of {menu_class_modifier} and {aria_label} placeholders. On the actual site the "nav" template is defined in site config, so I can define just these parts on a case-by-case basis while actual nav markup is maintained in one place.
      Please check out the README file for available render options. I'd very much prefer not to keep this list up to date in multiple places. Basically there are settings for defining "templates" for different parts of the menu (list, item, etc.), include array for defining rules for including in the menu and exclude array for the opposite effect, classes and placeholders arrays for overriding default classes and injecting custom placeholders, etc. 🙂
      MarkupMenu vs. MarkupSimpleNavigation
      TL;DR: this is another take on the same concept. There are many similarities, but also some differences – especially when it comes to the supported options and syntax. If you're currently using MarkupSimpleNavigation then there's probably no reason to switch over.
      I'd be surprised if anyone didn't draw lines between this module and Soma's awesome MarkupSimpleNavigation. Simply put, I've been using MSN (...) for a number of years, and it's been great – but there have been some smallish issues with it, particularly with the markup generation part, and it's also doing some things in a way that just doesn't work for me – the xtemplates thing being one of these. In many ways it's less about features, and more about style.
      In MarkupMenu I've tried to correct these little hiccups, modernise the default markup, and allow for more flexibility with placeholder variables and additional / different options. MarkupMenu was built for ProcessWire 3.0.112+ and PHP 7.1+, it's installable with Composer, and I have a few additional ideas (such as conditional placeholders) on my todo list.
      One smallish and rather specific difference is that MarkupMenu supports overriding default options via $config->MarkupMenu. I find myself redefining the default markup for every site, which until now meant that each site has a wrapper function for MarkupSimpleNavigation (to avoid code / config repetition), and this way I've been able to omit that 🙂
      Requirements
      ProcessWire >= 3.0.112 PHP >= 7.1.0 If you're working on an earlier version of ProcessWire or PHP, use MarkupSimpleNavigation instead.
    • By Robin S
      Repeater Images
      Adds options to modify Repeater fields to make them convenient for "page-per-image" usage. Using a page-per-image approach allows for additional fields to be associated with each image, to record things such as photographer, date, license, links, etc.
      When Repeater Images is enabled for a Repeater field the module changes the appearance of the Repeater inputfield to be similar (but not identical) to an Images field. The collapsed view shows a thumbnail for each Repeater item, and items can be expanded for field editing.
      Screencast

      Installation
      Install the Repeater Images module.
      Setup
      Create an image field to use in the Repeater field. Recommended settings for the image field are "Maximum files allowed" set to 1 and "Formatted value" set to "Single item (null if empty)". Create a Repeater field. Add the image field to the Repeater. If you want additional fields in the Repeater create and add these also. Repeater Images configuration
      Tick the "Activate Repeater Images for this Repeater field" checkbox. In the "Image field within Repeater" dropdown select the single image field. You must save the Repeater field settings to see any newly added Image fields in the dropdown. Adjust the image thumbnail height if you want (unlike the core Images field there is no slider to change thumbnail height within Page Edit). Note: the depth option for Repeater fields is not compatible with the Repeater Images module.
      Image uploads feature
      There is a checkbox to activate image uploads. This feature allows users to quickly and easily add images to the Repeater Images field by uploading them to an adjacent "upload" field.
      To use this feature you must add the image field selected in the Repeater Images config to the template of the page containing the Repeater Images field - immediately above or below the Repeater Images field would be a good position.
      It's recommended to set the label for this field in template context to "Upload images" or similar, and set the visibility of the field to "Closed" so that it takes up less room when it's not being used. Note that when you drag images to a closed Images field it will automatically open. You don't need to worry about the "Maximum files allowed" setting because the Repeater Images module overrides this for the upload field.
      New Repeater items will be created from the images uploaded to the upload field when the page is saved. The user can add descriptions and tags to the images while they are still in the upload field and these will be retained in the Repeater items. Images are automatically deleted from the upload field when the page is saved.
      Tips
      The "Use accordion mode?" option in the Repeater field settings is useful for keeping the inputfield compact, with only one image item open for editing at a time. The "Repeater item labels" setting determines what is shown in the thumbnail overlay on hover. Example for an image field named "image": {image.basename} ({image.width}x{image.height})  
      https://github.com/Toutouwai/RepeaterImages
      https://modules.processwire.com/modules/repeater-images/
    • By EyeDentify
      Hello There Guys.

      I am in the process of getting into making my first modules for PW and i had a question for you PHP and PW gurus in here.

      I was wondering how i could use an external library, lets say TwitterOAuth in my PW module.
      Link to library
      https://twitteroauth.com/

      Would the code below be correct or how would i go about this:
      <?PHP namespace ProcessWire; /* load the TwitterOAuth library from my Module folder */ require "twitteroauth/autoload.php"; use Abraham\TwitterOAuth\TwitterOAuth; class EyeTwitter extends WireData,TwitterOAuth implements Module { /* vars */ protected $twConnection; /* extend parent TwitterOAuth contructor $connection = new TwitterOAuth(CONSUMER_KEY, CONSUMER_SECRET, $access_token, $access_token_secret); */ public function myTwitterConnection ($consumer_key, $consumer_secret, $access_token, $access_token_secret) { /* save the connection for use later */ $this->twConnection = TwitterOAuth::__construct($consumer_key, $consumer_secret, $access_token, $access_token_secret); } } ?> Am i on the right trail here or i am barking up the wrong tree?
      I don´t need a complete solution, i just wonder if i am including the external library the right way.
      If not, then give me a few hint´s and i will figure it out.

      Thanks a bunch.

      /EyeDentify
    • 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 (has been tested up to v3.3), 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.


×
×
  • Create New...