Jump to content
MadeMyDay

Module: PageTableExtended

Recommended Posts

PageTableExtended

 

Download here: http://modules.processwire.com/modules/fieldtype-page-table-extended/

 

Extends the Processwire PageTable field for rendering table row layouts. This is great for editors, because they actually see at a glance what the table rows consist of.

What it does

 

Turns the Processwire Fieldtype "Page Table" from this:

git1.jpg

 

into something like this (sorting capabilities of course still functional):

 

git2.jpg

See it in action:

Requirements

  • FieldtypePageTable installed (part of the core since Processwire 2.4.10.)
  • Templates used for PageTable need a file associated (otherwise nothing gets rendered)
  • This render method is meant for sites where the PageTable templates only render part of the layout, not complete websites. But you also can define what will be rendered (see below).

Options

git3.jpg

Render Layout instead of table rows

Check this for seeing the rows rendered. You can easily turn off the complete functionality by unchecking this.

Path to Stylesheet

Since the parts are unstyled by default, it is a good idea to define styles for them. All rendered templates are encapsulated in a div with the class "renderedLayout" so you can style them with:

div.renderedLayout h2{
color: green;
}

The path is to be set relative to your templates' folder.

Reset Admin CSS

Since the parts are rendered inside the Admin, common styles of the Admin Interface apply also to your layout parts. This is not a bad thing, because especially text styles are well integrated in your admin's theme. But if you like to override the admin styles in your table rows completely (more or less), just check this box. Don't forget to define a custom CSS then!

Advanced

 

Since this module is meant for parts of your layout you already have defined for your frontend templates, it is a good idea to use a preprocessor like Stylus, Sass or Less for building the custom CSS file. Just outsource your layout part definitions in an extra file, compile that in a separete CSS file and use this as custom CSS for this module. Since your CSS is should be built in a modular way, this works pretty well ;-) Will write a tutorial with a use case once finished testing.

 

Notes:

 

Github: https://github.com/MadeMyDay/PageTableExtended

 

If you want to get rid of the unnecessary step for entering a title before editing the page, just set the "autoformat" value as suggested in the PageTable settings. If you don't want to use a title field at all, see this post from Soma

 

Will put it in the module repository once finished testing. Please test it and give feedback. I haven't used GitHub for a long time, please check if everything is in place and if this will work with the modules manager and the new core module installer once added to the repository. Have fun :)

 

Module is in the repository now: http://modules.processwire.com/modules/fieldtype-page-table-extended/

 

Please use GitHub for instructions, I made some additions there.

  • Like 34

Share this post


Link to post
Share on other sites

Awesome! - only one suggestion - it would be great to have text fields editable inline, with ajax save - might be beyond the scope of what you want, but I think it would be cool :)

Share this post


Link to post
Share on other sites

Awesome! - only one suggestion - it would be great to have text fields editable inline, with ajax save - might be beyond the scope of what you want, but I think it would be cool :)

I am a bit ambivalent regarding such a feature. Of course it would be nice, but also would add a lot of overhead to this specific module. If there would be an existing solution for that (for the frontend), it would be easy to integrate it as well in this module (including necessary js and css files should be enough), because the layouts are rendered as in the frontend.

  • Like 1

Share this post


Link to post
Share on other sites

I guess I am mixing purposes a bit here - your goal was to style the output exactly as it will appear on the frontend, but I guess I am looking more for replicating the ease of editing that repeaters have. Maybe I'll make a different extension for PageTable that works more that way. Maybe not worry about the ajax saving and just use the page save to save each of PageTable components. I'll mull over it for a bit.

  • Like 2

Share this post


Link to post
Share on other sites

I totally agree. I was waiting for a configurable repeater (with different templates to choose from) for ages. Now PageTable has this feature, so I went with this ;) But hey, never say never. Question is... When do you want to save the changes? Autosave? No good idea as long there are no draft versions. So this is getting complicated. Either you provide a save button on each row (easy to implement, but hard to understand for editors) or you save the entries on page save (easier to understand but harder to implement). You then would have to monitor the changed fields, look for their page, save the fields on each page... well.

Share this post


Link to post
Share on other sites

Hi Marc, you know - I don't have any experience with PageTable field.

I've installed the module and added the templates. Everything works fine for me. The Elements are there, I can add content und frontend shows everything.

In your folder are two Modules.

PageTable Renderer (Renders PageTable entries in admin) and PageTable render (Adds render functionality for PageTable fields). First one is installed. The second one requires InputFieldPageTable which I can't find. I thing thats the reason, why I have no settings.

The rendering doesn't work for me yet and I've a little understanding problem, how I got this working for me…

Share this post


Link to post
Share on other sites

@yesjoar

You need to install the dev version of 2.4 instead of the stable one. PageTable is a new Fieldtype which is only available with the dev version.

Share this post


Link to post
Share on other sites

@yesjoar

You need to install the dev version of 2.4 instead of the stable one. PageTable is a new Fieldtype which is only available with the dev version.

I have the latest dev version. PageTable is installed and everything works fine for me. Like I said. ;)

But the rendering in the page itselfs doesn't work for me. Also I can't install the second rendering module.

Share this post


Link to post
Share on other sites

Have you installed the new fieldtype FieldtypePageTableExtended? And then created/changed the field with "PageTableExtended" ? It's a new field.

Share this post


Link to post
Share on other sites

Hi Yesjoar,

PageTable Renderer (Renders PageTable entries in admin) and PageTable render (Adds render functionality for PageTable fields). First one is installed. The second one requires InputFieldPageTable which I can't find. I thing thats the reason, why I have no settings.

Okay, I pushed an update to GitHub. The dependencies of the modules were not clear and the titles misleading. Please try to override the modules with the new ones.

Share this post


Link to post
Share on other sites

nice module/feature!

i use PageTable for the same kind of modular content building.

how do you render your PageTable templates in the frontend?

thanks!

Share this post


Link to post
Share on other sites
Hi Tobaco,
 
my setup is always the same. Doesn't matter if I use PageTable or not. Here it goes (simplified):
 
/templates
- basic-page.php
- home.php
- /tpl 
   - main.php
   - mainnav.php
   - subnav.php
   - footer.php
 
 
The tpl/main.php is the overall template like:
 
<?php
include('tpl/mainnav.php');
include('tpl/subnav.php');
include('tpl/slider.php');
?>
<!DOCTYPE html>
<html class="no-js">
    <head>
        <meta charset="utf-8">
        <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
        <title><?= $page->title ?></title>
        <!--- styles and scripts -->
    </head>
    <body class='<?= $bodyclass ?>'>
        <header>
            <div class='wrap'>
                <a href="/"><img src='/site/templates/img/logo.png' class='logo' alt="Logo"></a>
                <nav class='main'>
                    <?= $mainnav ?>
                </nav>
            </div>
        </header>
        <?= $slider ?>
        <?= $subnav ?>
<section class="content">
            <div class="wrap group">
                <h1 class='v2 hide'><span><?= $page->title ?></span></h1>
                <?= $content ?>
            </div>
        </section>
        <footer>
            <div class="group">
                <?php include ('tpl/footer.php'); ?>
            </div>
        </footer> 
        <script src="/site/templates/dist/all.min.js"></script>
    </body>
</html>

basic-page template looks like this (every template renders the content and then includes the main template):

<?php
/**
 * basic page template
 *
 */
$bodyclass='inner';

$content = $page->body;

include('tpl/main.php');
 
With PageTable the structure looks like this:
 
/templates
- basic-page.php
- home.php
- part_text.php
- part_columns.php
- part_gallery.php
- /tpl 
   - main.php
   - mainnav.php
   - subnav.php
   - footer.php

The part_* templates are templates only for PageTable. part_columns.php could look like this:

<?php
$headline1 = "";
$headline2 = "";
if(!$page->checkbox1) $headline1 = "<h2>{$page->title}</h2>";
if(!$page->checkbox2) $headline2 = "<h2>{$page->text1}</h2>";

// Output

echo "
<div class='pageTableSection {$page->template->name}'>
    <div class='inner'>
        <div class='col one-half'>
                {$headline1}
                {$page->body}
         </div>
        <div class='col one-half'>
            {$headline2}
            {$page->textarea1}
        </div>
    </div>
</div>

";

And the basic page template gets enhanced by ("layout" being the PageTableExtend field):

<?php 

/**
 * basic page template
 * including PageTable layout parts
 */
$bodyclass='inner';

$content = "{$page->body}";

if(count($page->layout)>0){
     foreach($page->layout as $l){
         $content .= $l->render();
     }
}

include('tpl/main.php');
 
That way, the layout parts are easily renderable in the Admin with PageTableExtended.
 
While writing this, I want to point to another feature of the module. If rendered by PageTableExtended, the template gets an option 'pageTableExtended' which you can use in your part template:
 
// Output

echo "
<div class='pageTableSection {$page->template->name}'>
    <div class='inner'>
        <div class='col one-half'>
                {$headline1}
                {$page->body}
         </div>
        <div class='col one-half'>
            {$headline2}
            {$page->textarea1}
        </div>
    </div>
</div>

";

if(!$options['pageTableExtended']){ 
    // we are not in the Admin, so we include our social media buttons which we only need in our frontend
    include('social/socialmediabuttons.php);
}

Hope that helps.

  • Like 12

Share this post


Link to post
Share on other sites
Since your CSS should be built in a modular way, this works pretty well ;-)

Ha! that *wink* should be bigger. :P

BTW, this is so awesome!

  • Like 2

Share this post


Link to post
Share on other sites

Awesome stuff! This is one of the features i was always missing in pw. Great Job MadeMyDay.

  • Like 2

Share this post


Link to post
Share on other sites

I hadn't actually realised you could specify more than one template for a PageTable field! Did that get snuck in after one of the early versions or am I just blind in general? :)

It actually makes an "article" system a lot easier to build where an editing user might want to dump in some text, then an image, then some more text exactly as you have, but with your module it's one step better as it's pretty much WYSIWIG.

Inline edits would be nice as folks have said, but this is still really, really useful!

  • Like 1

Share this post


Link to post
Share on other sites
I hadn't actually realised you could specify more than one template for a PageTable field! Did that get snuck in after one of the early versions or am I just blind in general?
 
Wasn't there from the beginning. But as owzim posted this: https://processwire.com/talk/topic/4189-flexibility-in-page-design/page-4#entry63924 I knew, this is the key to my always wanted flexible layout parts :)
 
It actually makes an "article" system a lot easier to build where an editing user might want to dump in some text, then an image, then some more text exactly as you have, but with your module it's one step better as it's pretty much WYSIWIG.
 
exactly.
 
Inline edits would be nice as folks have said, but this is still really, really useful!
 

Of course they would be. But as I said: If there would be a solution for the frontend, it could easily be applied to this module. I think developing a solution only for this module would be out of scope.

Will try to include Apeisa's Fredi. If that works without hazzle, any inline solution should work.

Share this post


Link to post
Share on other sites

So behind the times :(

@MadeMyDay - just submitted a pull request to fix some freaky things I was experiencing either due to a template delegation situation or some freaky admin code I've done but I think it could affect certain people in certain scenarios so best to be safe.

And because I'm nice I made sure it was all still compatible with your instructions afterwards ;)

  • Like 1

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 joshua
      ---
      Module Directory: https://modules.processwire.com/modules/privacy-wire/
      Github: https://github.com/blaueQuelle/privacywire/
      Packagist:https://packagist.org/packages/blauequelle/privacywire
      Module Class Name: PrivacyWire
      Changelog: https://github.com/blaueQuelle/privacywire/blob/master/Changelog.md
      ---
      This module is (yet another) way for implementing a cookie management solution.
      Of course there are several other possibilities:
      - https://processwire.com/talk/topic/22920-klaro-cookie-consent-manager/
      - https://github.com/webmanufaktur/CookieManagementBanner
      - https://github.com/johannesdachsel/cookiemonster
      - https://www.oiljs.org/
      - ... and so on ...
      In this module you can configure which kind of cookie categories you want to manage:

      You can also enable the support for respecting the Do-Not-Track (DNT) header to don't annoy users, who already decided for all their browsing experience.
      Currently there are four possible cookie groups:
      - Necessary (always enabled)
      - Functional
      - Statistics
      - Marketing
      - External Media
      All groups can be renamed, so feel free to use other cookie group names. I just haven't found a way to implement a "repeater like" field as configurable module field ...
      When you want to load specific scripts ( like Google Analytics, Google Maps, ...) only after the user's content to this specific category of cookies, just use the following script syntax:
      <script type="text/plain" data-type="text/javascript" data-category="statistics" data-src="/path/to/your/statistic/script.js"></script> <script type="text/plain" data-type="text/javascript" data-category="marketing" data-src="/path/to/your/mareketing/script.js"></script> <script type="text/plain" data-type="text/javascript" data-category="external_media" data-src="/path/to/your/external-media/script.js"></script> <script type="text/plain" data-type="text/javascript" data-category="marketing">console.log("Inline scripts are also working!");</script> The data-attributes (data-type and data-category) are required to get recognized by PrivacyWire. the data-attributes are giving hints, how the script shall be loaded, if the data-category is within the cookie consents of the user. These scripts are loaded asynchronously after the user made the decision.
      If you want to give the users the possibility to change their consent, you can use the following Textformatter:
      [[privacywire-choose-cookies]] It's planned to add also other Textformatters to opt-out of specific cookie groups or delete the whole consent cookie.
      You can also add a custom link to output the banner again with a link / button with following class:
      <a href="#" class="privacywire-show-options">Show Cookie Options</a> <button class="privacywire-show-options">Show Cookie Options</button>  
      I would love to hear your feedback 🙂
      CHANGELOG
      You can find the always up-to-date changelog file here.
    • By joshua
      As we often use Matomo (former known as Piwik) instead of Google Analytics we wanted to embed Matomo not only in the template code but also via the ProcessWire backend.
      That's why I developed a tiny module for the implementation.
      The module provides the possibility to connect to an existing Matomo installation with the classical site tracking and also via the Matomo Tag Manager.
      If you have also PrivacyWire installed, you can tell MatomoWire to only load the script, if the user has accepted cookies via PrivacyWire.
      To offer an Opt-Out solution you can choose between the simple Opt-Out iFrame, delivered by your Matomo installation, or a button to choose cookies via PrivacyWire.
      You'll find the module both in the module directory and via github:
      ProcessWire Module Directory MatomoWire @ GitHub MatomoWire @ Packagist ->installable via composer require blauequelle/matomowire I'm looking forward to hear your feedback!


    • By Robin S
      If your module has a lot of config fields you might want to divide them into groups inside a tabbed interface. Here is a demonstration module showing how this can be done.
      https://github.com/Toutouwai/ModuleConfigTabs

      Thanks to @kixe for providing my starting point in this forum topic.
    • By FireWire
      Hello community!

      I want to share a new module I've been working on that I think could be a big boost for multi-language ProcessWire sites.

      Some background, I was looking for a way for our company website to be efficiently translated as working with human translators was pretty laborious and a lack of updating content created a divergence between languages. I, and several other devs here, have talked about translation integrations and have recognized the power that DeepL has. DeepL is an AI deep learning powered service that delivers translation quality beyond any automated service available. After access to the API was opened up to the US, I built Fluency, a DeepL translation integration for ProcessWire.
      Fluency brings automated translation to every multi-language field in the admin, and also provides a translation tool allowing the user to translate their text to any language without it being inside a template's field. With Fluency you can:
      Translate any plain textarea or text input Translate any CKEditor content (yes, with markup) Translate page names for fully localized URLs on every page Translate your in-template translation function wrapped strings Translate modules DeepL offers translations to the following languages: English (US), English (UK), German, French, Spanish, Portuguese (EU), Portuguese (Brazil, Italian, Dutch, Polish, Russian, Japanese, Chinese (Simplified)
      Installation and usage is completely plug and play. Whether you're building a new multi-language site, need to update a site to multi-language, or simply want to stop manually translating a site and make any language a one-click deal, it could not be easier to do it. Fluency works by having you match the languages configured in ProcessWIre to DeepL's. You can have your site translating to any or all of the languages DeepL translates to in minutes (quite literally).
      Let's break out the screenshots...
      When the default language tab is shown, a message is displayed to let users know that translation is available. Clicking on each tab shows a link that says "Translate from English". Clicking it shows an animated overlay with the word "Translating..." cycling through each language and a light gradient shift. Have a CKEditor field? All good. Fluency will translated it and use DeepL's ability to translate text within HTML tags. CKEditor fields can be translated as easily and accurately as text/textarea fields.

      Repeaters and AJAX created fields also have translation enabled thanks to a JavaScript MutationObserver that searches for multi-language fields and adds translation as they're inserted into the DOM. If there's a multi-language field on the page, it will have translation added.

      Same goes for image description fields. Multi-language SEO friendly images are good to go.

      Creating a new page from one of your templates? Translate your title, and also translate your page name for native language URLs. (Not available for Russian, Chinese, or Japanese languages due to URL limitations). These can be changed in the "Settings" tab for any page as well so whether you're translating new pages or existing pages, you control the URLs everywhere.

      Language configuration pages are no different. Translate the names of your languages and search for both Site Translation Files (including all of your modules)

      Translate all of the static text in your templates as well. Notice that the placeholders are retained. DeepL is pretty good at recognizing and keeping non-translatable strings like that. If it is changed, it's easy to fix manually.

      Fluency adds a "Translate" item to the CMS header. When clicked this opens up a modal with a full translation tool that lets the user translate any language to any language. No need to leave the admin if you need to translate content from a secondary language back to the default ProcessWire language. There is also a button to get the current API usage statistics. DeepL account owners can set billing limitations via character count to control costs. This may help larger sites or sites being retrofitted keep an eye on their usage. Fluency can be used by users having roles given the fluency-translate permission.

      It couldn't be easier to add Fluency to your new or existing website. Simply add your API key and you're shown what languages are currently available for translation from/to as provided by DeepL. This list and all configuration options are taken live from the API so when DeepL releases new languages you can add them to your site without any work. No module updates, just an easy configuration. Just match the language you configured in ProcessWire to the DeepL language you want it to be associated with and you're done. Fluency also allows you to create a list of words/phrases that will not be translated which can prevent items such as brands and company names from being translated when they shouldn't

       
      Limitations:
      No "translate page" - Translating multiple fields can be done by clicking multiple translation links on multiple fields at once but engineering a "one click page translate" is not feasible from a user experience standpoint. The time it takes to translate one field can be a second or two, but cumulatively that may take much longer (CKEditor fields are slower than plain text fields). There may be a workaround in the future but it isn't currently on the roadmap. No "translate site" - Same thing goes for translating an entire website at once. It would be great, but it would be a very intense process and take a very (very) long time. There may be a workaround in the future but it isn't on the roadmap. No current support for Inline CKEditor fields - Handling for CKEditor on-demand hasn't been implemented yet, this is planned for a future release though and can be done. I just forgot about it because I've never really used that feature personally.. Alpha release - This module is in alpha. Releases should be stable and usable, but there may be edge case issues. Test the module thoroughly and please report any bugs via a Gitlab issue on the repository or respond here. Please note that the browser plugin for Grammarly conflicts with Fluency (as it does with many web applications). To address this issue it is recommended that you disable Grammarly when using Fluency, or open the admin to edit pages in a private window where Grammarly may not be loaded. This is an issue that may not have a resolution as creating a workaround may not be possible. If you have insight as to how this may be solved please visit the Gitlab page and file a bugfix ticket.
      Requirements:
      ProcessWire  3.0+ UIKit Admin Theme That's Fluency in a nutshell. A core effort in this module is to create it so that there is nothing DeepL related hard-coded in that would require updating it when DeepL offers new languages. I would like this to be a future-friendly module that doesn't require developer work to keep it up-to-date.
      It's Free
      This is my first real module and I want to give it back to the community as thanks. This is the best CMS I've worked with (thank you Ryan & contributors) and a great community (thank you dear reader). The only cost to use this is a subscription fee for the DeepL Pro API. Find out more and sign up here.
      Download & Feedback
      Download the latest version here
      https://github.com/SkyLundy/Fluency-Translation/archive/main.zip
      Github repository:
      https://github.com/SkyLundy/Fluency-Translation
      File issues and feature requests here (your feedback and testing is greatly appreciated):
      https://github.com/SkyLundy/Fluency-Translation/issues
       
      Thank you! ¡Gracias! Ich danke Ihnen! Merci! Obrigado! Grazie! Dank u wel! Dziękuję! Спасибо! ありがとうございます! 谢谢你!

    • By Robin S
      An inputfield module that brings EasyMDE Markdown editor to ProcessWire.
      EasyMDE is a fork of SimpleMDE, for which there is an existing PW module. Inputfield EasyMDE has a few advantages though:
      EasyMDE seems to be more actively developed than SimpleMDE, which hasn't seen any updates for several years. You can define options for Inputfield EasyMDE. Inputfield EasyMDE can be used in Repeater fields and in custom fields for File/Image fields.  
      Inputfield EasyMDE
      EasyMDE (Easy Markdown Editor) as an inputfield for ProcessWire.
      EasyMDE is a Markdown editor with some nice features, allowing users who may be less experienced with Markdown to use familiar toolbar buttons and shortcuts. More information is at the EasyMDE website.

      Installation
      Install the Inputfield EasyMDE module.
      Usage
      Create a new textarea field, and in the "Inputfield Type" dropdown choose "EasyMDE". Save the field and if you like you can then configure the EasyMDE options for the field as described below.
      To convert Markdown to HTML you can install the core TextformatterMarkdownExtra module and apply the textformatter to the field. Alternatively you can use $sanitizer->entitiesMarkdown() on the field value, e.g.
      echo $sanitizer->entitiesMarkdown($page->your_field_name, ['fullMarkdown' => true]); Configuration
      On the "Input" tab of the field settings you can define EasyMDE options for the field in JSON format. Refer to the EasyMDE documentation for the available options. Keys in the JSON must be surrounded with double quotes.
      Example:
      "toolbar": ["bold", "italic", "heading", "|", "side-by-side"], "sideBySideFullscreen": false  
      https://github.com/Toutouwai/InputfieldEasyMDE
      https://processwire.com/modules/inputfield-easy-mde/
×
×
  • Create New...