Jump to content

Recommended Posts

In that case there is something else wrong with your setup. It is difficult to tell without seeing/testing on the actual site Any other changes you have made to your template files? Some other modules possibly interfering? What about testing comments + form apart outside of the Blog (non-blog pages)?

Share this post


Link to post
Share on other sites

My template files are very different from the default. ;) I haven't touched the module itself, though. I'd be happy to give you access to my admin if you have the time to take a look. I can post any templates here that you think may be causing the issues.

Form Builder works outside of the blog pages. I don't have comments for non-blog pages, though.

Share this post


Link to post
Share on other sites

Yeah, comments on a non-blog page aren't working, either. Same result. I'll move my questioning to that fieldtype discussion. Thanks kongondo!

Share this post


Link to post
Share on other sites

I got another little issue. If someone uses the quickpost function and fills out quickpost_body all line breaks will be removed.

I don't think that is it necessary to use a rich text area here but maybe you can wrap it in a simple nl2br function?

        //@todo - SHOULD THIS BE A RICH TEXT AREA?
-       $p->blog_body = $this->sanitizer->textarea($this->input->post->quickpost_body);
+       $p->blog_body = nl2br($this->sanitizer->textarea($this->input->post->quickpost_body
  • Like 1

Share this post


Link to post
Share on other sites

Yeah, this has been brought up before but wasn't really sure how to deal with it. Thanks for reminding me :-).

For now, I have decided to convert and store the line breaks in 'quickpost' to paragraphs (instead of <br>) since I believe that is the intended action by the user when they use a line break in 'quickpost' to space out their text. Besides, that is what CKEditor is going to do when the full post is edited. Using nl2br will result in lots of <br> all of which CKEditor will wrap in one paragraph. But thanks to your idea, I am now using a pre_replace to do the job. It works fine.

Committed to dev for now.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks a lot for this quick fix   :)

I checked out the dev branch, reset my deployment script and everything works fine (and all post authors are happy now  ;) ).

  • Like 1

Share this post


Link to post
Share on other sites

For the Categories / Tags and other Page-type fields, the parent of those pages gives blog-author the right to Add Children, and the field has "Allow new pages to be created from field" checked. Anything else I need to check for? I'm able to create new pages as a superuser but my blog-author role users get a little achtung triangle in the AsmSelect field when they type, and nothing is saved. In Select cases, there's no option to add another for blog-author roles. What I glean from this is that there's another permissions setting somewhere, other than the per-template "Add Children" setting for blog-author.

I already started this over once in a new install and ran into the same comments issue before I got very far (managed to reverse the problem by restoring the default templates, so the problem is either with my call to the comments form, or some other module that I call in my template files).

Edited by creativejay

Share this post


Link to post
Share on other sites

Have you given the role 'blog-author' the right site-level permissions? In ProcessWire access is controlled at both site- and template- levels. 

Admin > Access > Roles > blog-author. The permission page-edit is needed...

Share this post


Link to post
Share on other sites

Yes, the blog-author role has page-edit permissions.

There are sub-permissions from page-edit that I do not have checked off:

page-delete

page-edit-recent

page-lister

page-lock

page-move

page-sort

page-template

Share this post


Link to post
Share on other sites

Then the problem is in your blog-tag and blog-category templates. You have two choices:

  1. Set up access to the pages using these templates, i.e. an individual 'tag' and 'category' respectively by setting up access in their respective parents' templates, i.e. 'blog-tags' and 'blog-categories' AND making sure the two child templates 'blog-tag' and 'blog-category' have No checked for their respective 'manage view and edit access for pages using this template?' setting. In that case, pages using 'blog-tag' and 'blog-category' will inherit their parents' access. Then, in 'blog-tags' and 'blog-categories' you will need to check for the role 'blog-author' View Pages, Edit Pages, Create Pages and Add Children. Alternatively:
  2. Set up access on the child templates themselves, i.e. in 'blog-tag' and 'blog-category' templates. In this case, in their parents' templates, 'blog-tags' and 'blog-categories' you would only need to add the access Add Children. In 'blog-tag' and 'blog-category' you would need to grant access to View Pages, Edit Pages and Create Pages

If the above don't work, there could be some access inheritance issues going on...Access issues are of course controlled by ProcessWire itself and not Blog :-)

Share this post


Link to post
Share on other sites

Thanks Kongondo, that confirms what I'd been doing was correct.

I got clarification from the blog-author role user that spotted the problem with creating new pages from fields: she had never been able to do this.  On a hunch I disabled PagesCreatedEdit and sure enough that allowed the user to create their new tags, categories, etc. Unfortunately now blog-author can edit blog posts other than their own created posts. I may make a custom Module based on PagesCreatedEdit to try and make a special exception to the rule for certain templates.

Share this post


Link to post
Share on other sites
Update: Blog Version 2.3.4

Blog now preserves all line breaks as paragraphs for posts created via ProcessBlog's quickpost, thanks to idea by @justb3a

Share this post


Link to post
Share on other sites

Hey Kongondo,

I noticed that when I first installed Blog, probably about 4 months ago, the module was called in my templates as


    $blogOut = $modules->get("MarkupBlog");

And now $blogOut seems to be $blog in your more recent documentation. Is there something in the modules themselves that should compel me to go back to the default templates as a new starting point? (Yes, I'm still struggling with comments and I have narrowed it down to being caused by my template file code...)

Share this post


Link to post
Share on other sites

Nope..you can call it anything you want (as long as it is a valid PHP variable name) - $b, $myBlog, $thoughts, $blahBlah.... :D

RE comments, maybe paste your template code in pastebin and I'll have a look if I can find some time....

  • Like 1

Share this post


Link to post
Share on other sites

Hi,

I am just getting started with PW. I've successfully installed but not yet confirgured the ProcessBlog module and would like to know before I delve further whether or not a single instance of the module can be used to deliver multiple blogs. What I have in mind for the website I am currently working on is both a separate News section and a separate Testimonials section.

Is it actually necessary to completely split the two sections/blogs in terms of the backend? If not, how should I go about setting this up? Can categories be set up to split the data for News and Testimonials? Effectively both pages could be built around the same underlying data structure, for example:

$post-date-time             ( - would like the date|time to appear as yyyymmdd - hh:mm:ss, though)
                                         - do I actually need this field or can this data be retrieved from a built-in PW source??

$post-title

$post-summary

$post-author

$post-category              ( - needed or not?)

In addition, what are the advantages / disadvantages of the different blog styles? Purely from the path name perspective it appears that Blog style 3: /mysite/posts/example-post/ might be the most appropriate.

Otherwise, would Joss's Simple News System be a better place to start?

Any guidance would be greatly appreciated. :)

Edited by kongondo
Moved to Blog's support forum

Share this post


Link to post
Share on other sites

@ridgedale,

Welcome to PW and the forums.

Multiple Blogs:

This issue has been raised a couple of times but I haven't yet resolved how to best implement such a feature:

 
 

Is it actually necessary to completely split the two sections/blogs in terms of the backend? If not, how should I go about setting this up? Can categories be set up to split the data for News and Testimonials?

At the moment it is not possible to have such a split. I am wondering whether this can be achieved by simply adding some field on a post's template to assign it to a particular field...hmm...
 
$post-date-time
Change your date's input/output format in the field 'blog_date'
 
$post-summary
You can have a post summary by using renderPosts($posts, true) - see the Blog documentation. Alternatively, you can create your own summary field and use that.
 
Blog Styles

In addition, what are the advantages / disadvantages of the different blog styles?

Purely user preferences...

Share this post


Link to post
Share on other sites

@kondongo

I am sorry for the delay in replying, I thought I'd raised a new topic (Evidently not! :huh: ) and therefore wasn't looking in the right place for any replies.
Thank you for your very speedy reply and the links.

I had an issue with links between the pages which I appear now to have resolved using:

<a href="<?php echo $config->urls->root; ?>about"</a>

All of those below returned blank pages:

<a href="<?php echo $config->urls->templates; ?>about"</a>
<a href="/about"</a>
<a href="./about"</a>

I'll read through the links you have provided and see how I get on.

In the meantime I've tried working through the Simple News System guide so far without success.
I'm not sure if this is an issue related to the installation path of this instance of PW (in this instance while the site is under development: http://localhost:8888/rcl_pw252/ ) or the fact that I changed the name of the templates, fields and pages.
I'm pretty certain I've updated the news.php, news-index.php and inc/news-fnc.inc files have been updated correctly accordingly, but I still get blank pages being returned which might suggest that the inc/news-fnc.inc file needs to include paths in at least some instances as well.
Any thoughts would be appreciated.

Thanks again. :)
 

Share this post


Link to post
Share on other sites

Hey kongondo, I finally fixed my comments! As usual, it was something completely innocuous: I had a base href tag in my header that was redirecting the #comments to the root URL of the site installation. Deleted that line, and suddenly my comments worked. :frantics:

I was taking a very methodical approach to figuring this out (finally sitting down tonight after weeks of not having time to focus), thankfully my method led to the answer in five steps.

Now that I can finally put in some example comments to play with:

1) If I wanted to notify the admin listed in the blog_comments/Details tab, PLUS the author of the post that received a comment, what would you suggest? I don't want to add every author to the list of those who receive comments as a global setting.

2) I have a custom admin tab that is the admin home of all authors. I'd like to identify any pending comments they should review and output a message such as "You have # comments pending review. Please visit the Comments Manager."  Would you suggest I start with the code from  "public function findComments($selector)" in MarkupBlog.module (line 541 in the latest release version)?

Edited by creativejay

Share this post


Link to post
Share on other sites

Hi,

Can anyone tell me whats wrong with my code here please. I am trying to blog page with images and small text. Small texts are ok but images showing only one. Any help, would be greatly appreciated.

<?php
//CALL THE MODULE - MarkupBlog
$blog = $modules->get("MarkupBlog");
$limit = 10;
$post = $pages->get('template=blog-post, sort=blog_date');
$image = $post->blog_images->first();
?>

<div class="jumbotron">
    <h3><?php echo $page->title ?></h3>
</div>
<!-- /.Header_End -->
<div class="main-content container">
    <div class="row">

        <!-- Blog -->
        <div class="blog-list">
            <div class="row">
                <div class="col-md-6 post-list">

                    <div class="ih-item square effect9 right_to_left"><a href="#">

                            <div class="img img-responsive"><img src="<?php echo $image->url; ?>" alt="img"></div>
                            <div class="info">
                                <div class="info-back">
                                    <h3></h3>
                                    <p></p>
                                </div>

                            </div></a>

                    </div>

                </div>
                <div class="col-md-6 post-list">
                    <?php
                    echo $blog->renderPosts("limit={$limit}", true);
                    ?>
                </div>

            </div><!-- row_end-->
        </div>
    </div>
</div> 

Share this post


Link to post
Share on other sites

@Qurus
 

Hi,
Can anyone tell me whats wrong with my code here please. I am trying to blog page with images and small text. Small texts are ok but images showing only one. Any help, would be greatly appreciated.

<?php
$image = $post->blog_images->first();
?>

 
On that line you are only calling one image....specifically the first one. If you want to output several images you would have to loop through them. Have a read here. something like

$out = '';
foreach($post->blog_images as $img) {

$out .= '<img src="' . $img->url . '" alt="img">';

}
//then output $out later on down...within your <div class="img".......

@creativejay...get back to you later.....

  • Like 1

Share this post


Link to post
Share on other sites

1) If I wanted to notify the admin listed in the blog_comments/Details tab, PLUS the author of the post that received a comment, what would you suggest? I don't want to add every author to the list of those who receive comments as a global setting.

2) I have a custom admin tab that is the admin home of all authors. I'd like to identify any pending comments they should review and output a message such as "You have # comments pending review. Please visit the Comments Manager."  Would you suggest I start with the code from  "public function findComments($selector)" in MarkupBlog.module (line 541 in the latest release version)?

Sorry for the delay.

#1: Am not sure how to do that. It is really a Comments Module question. Maybe Ryan could help there

#2: Yes  :-)

Seem you really have some cool setup there. Would like to see a screen if possible.

Cheers,

/k

Share this post


Link to post
Share on other sites

Thanks! I'm trying to make the site as fun as possible (it's a non-income-generating pet project), to make it emotionally rewarding for the authors that have volunteered to provide content.

I'm attaching a screen shot of the post-login home page for an author (non-superuser). Fair warning, the color scheme may hurt the eyes. I'm going for quirky here.

The challenge area is the 'ticket' system I was referring to.

post-1266-0-31405400-1425998308_thumb.pn

  • Like 2

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 jploch
      Hey folks,
      for a module (a pagebuilder based on PageTable) I need to save some settings as JSON. The values are saved for each page table item (a pw page). It's working well, but I am looking for ways to improve the structure I have. As I'm not that experienced with JSON, maybe someone more experienced can take a look and tell me if my approach is good practice. 

      My goal is to make all the items accessible by page id, without looping over them (using objects instead of arrays):
      // access from template with pw page var $jsonObject->items->{$page}->cssClass; Her is an example of my JSON structure:
      { "items": { "3252": { "id": "3252", "cssClass": "pgrid-main", "breakpoints": { "base": { "css": { "grid-column-end": "auto", "grid-row-end": "auto", "grid-column-start": "auto", "grid-row-start": "auto", "align-self": "auto", "z-index": "auto", "padding-left": "60px", "padding-right": "60px", "padding-top": "60px", "padding-bottom": "60px", "background-color": "rgb(255, 255, 255)", "color": "rgb(0, 0, 0)" }, "size": "@media (min-width: 576px)", "name": "base" } } }, "3686": { "id": "3686", "cssClass": "test_global", "breakpoints": { "base": { "css": { "grid-column-end": "-1", "grid-row-end": "span 1", "grid-column-start": "1", "grid-row-start": "auto", "align-self": "auto", "z-index": "auto", "padding-left": "0px", "padding-right": "0px", "padding-top": "0px", "padding-bottom": "0px", "background-color": "rgba(0, 0, 0, 0)", "color": "rgb(0, 0, 0)" }, "size": "@media (min-width: 576px)", "name": "base" } } }, "3687": { "id": "3687", "cssClass": "block_editor-3687", "breakpoints": { "base": { "css": { "grid-column-end": "span 2", "grid-row-end": "span 1", "grid-column-start": "auto", "grid-row-start": "auto", "align-self": "auto", "z-index": "auto", "padding-left": "0px", "padding-right": "0px", "padding-top": "0px", "padding-bottom": "0px", "background-color": "rgba(0, 0, 0, 0)", "color": "rgb(0, 0, 0)" }, "size": "@media (min-width: 576px)", "name": "base" } } }, "3696": { "id": "3696", "cssClass": "block_editor-3696", "breakpoints": { "base": { "css": { "grid-column-end": "span 2", "grid-row-end": "span 1", "grid-column-start": "auto", "grid-row-start": "auto", "align-self": "auto", "z-index": "auto", "padding-left": "0px", "padding-right": "0px", "padding-top": "0px", "padding-bottom": "0px", "background-color": "rgba(0, 0, 0, 0)", "color": "rgb(0, 0, 0)" }, "size": "@media (min-width: 576px)", "name": "base" } } } }, "breakpointActive": "base", "breakpointActiveSize": "@media (min-width: 576px)" }  
    • By jploch
      Fieldtype Page Table Grid
      This is a sneak preview of a side project I've been working on for quite some time now. A lot of work and thought has gone into this, so I will most likely release this as a commercial module at some point in the near future. 

      As a designer (and developer) I get the appeal of a WYSIWYG editor. After playing around with some WYSIWYG page builder tools, I always felt something was wrong about them. So I decided to build my own PW version based on PageTable.

      Here is a small demo (using AdminThemeCanvas, but its working with other admin themes as well) :
      There is also a complete website that I built for a friend of mine using this module and some custom blocks.
      Concept
      This fieldtype shares a lot of features with PageTableExtended: it's also an extension of PageTable and renders the block templates in the backend and frontend (native PW templates and fields). You can also add your own css via module settings.
      The difference is, this fieldtype also gives you the ability to rearrange and resize elements in a visual way as well as enable inline editing for text, ckeditor and file fields. Similar (and promising) attempts have been made, but I wanted something based on native CSS grid instead of a CSS framework...so I built my own version. Most CSS frameworks are based on flexbox, which is great for layouting elements horizontally. With CSS grid, you can place elements horizontally and vertically, allowing for layouts that were not previously possible with CSS. Similar to webflow, this fieldtype uses javascript (in the backend) to let you manipulate CSS grid in a visual way to design fully responsive websites (or parts of them). It should still be possible to include a CSS framework if you like (just add the classes to your block markup and include the CSS via module settings).
      The CSS grid layout manipulations are saved in a single field as a JSON array and used to generate a dynamic stylesheet that you simply include in your main template (no inline styles). The styles are saved within the breakpoint you select and cascade down to smaller breakpoints. That means you can specify just the basic breakpoint and adjust other breakpoints if needed. The exception is the mobile breakpoint which will display everything in one column as a default (you can change the layout here too).
      The fieldtype also comes with an optional style panel to manipulate some additional CSS properties directly on the page. You can customize the panel or disable it completely from the module settings (and just use a CSS file that you include via module settings). The style panel is based on inputfields (nothing is saved to the database). This means that you just have to install the module and all fields are available to all blocks automatically (this can be customized). It also has the benefit that your installation is not flooded with fields; this module only installs one field.
      Don't want to give your customer all that power? Design features can be disabled for certain roles. The grid editor role can just edit the content and use the inline editing feature to edit content quickly. You can then also grant access individually to the style panel, resize or drag functionality.
      Features
      Blocks are just pages Blocks are defined by native PW templates and fields Manipulate CSS grid in a visual way to design fully responsive websites (or parts of them) Design features can be disabled for certain roles Inline editing of text, ckeditor and file fields The layout is 100% CSS grid (very small css file size) Simply drag and resize to manipulate grid items directly inside the backend Manipulate grid columns and rows directly on the page (use any number of columns you want) All style manipulations are saved as JSON and used to generate a dynamic stylesheet that you just include in your main template (no inline styles) Nested groups/grids (child pages of nested blocks are created under group parent) Global blocks work with page reference field (changes on one page, changes all blocks on all pages) Manual and auto placement of grid items Define custom icons for your blocks via native template settings (template -> advanced -> icon) Option to load lazysizes in the backend to enable lazy loading of assets with class lazyload Works with all default and ui-kit based admin themes If you have any questions or feedback, let me know.
    • By bernhard
      I built this module because I needed a versatile solution to replace tags and simple if-blocks in some E-Mails and PDF documents.
      If you only need to replace static tags (no if-conditions), then you can use default PW api and need no module:
      $str = "My favourite color is {color}."; $texttools = $sanitizer->getTextTools(); echo $texttools->populatePlaceholders($str, ['color' => 'red']); // output: My favourite color is red. Usage:
      See the two example Files in the folder /replacements

       
      Methods:
      replacementsTable()
      Renders an overview of all available replacements (see the example in the Module's config file:
       
      Create new Replacements:
      Simply copy the sample file and adopt to your needs.
       
      Download:
      https://gitlab.com/baumrock/RockReplacer
    • By bernhard
      DEPRECATED
      I'm using this module in several projects, but it will likely not see any updates in the future. I'm not happy with it and I'm looking for ways to develop better solutions. RockTabulator was my first try, but I'm also not 100% happy with that. The tabulator library is great, but my module implementation is not. I hope to get a good solution soon, but it will be a lot of work...
      ---
      Some of you might have followed the development of this module here: https://processwire.com/talk/topic/15524-previewdiscussion-rockdatatables/ . It is the successor of "RockDataTables" and requires RockFinder to get the data for the grid easily and efficiently. It uses the open source part of agGrid for grid rendering.
       
      WHY?
      ProcessWire is awesome for creating all kinds of custom backend applications, but where it is not so awesome in my opinion is when it comes to listing this data. Of course we have the built in page lister and we have ListerPro, but none of that solutions is capable of properly displaying large amounts of data, for example lists of revenues, aggregations, quick and easy sorts by the user, instant filter and those kind of features. RockGrid to the rescue 😉 
       
      Features/Highlights:
      100k+ rows Instant (client side) filter, search, sort (different sort based on data type, eg "lower/greater than" for numbers, "contains" for strings) extendable via plugins (available plugins at the moment: fullscreen, csv export, reload, batch-processing of data, column sum/statistics, row selection) all the agGrid features (cell renderers, cell styling, pagination, column grouping etc) vanilla javascript, backend and frontend support (though not all plugins are working on the frontend yet and I don't plan to support it as long as I don't need it myself)  
      Limitations:
      While there is an option to retrieve data via AJAX the actual processing of the grid (displaying, filtering, sorting) is done on the client side, meaning that you can get into troubles when handling really large datasets of several thousands of rows. agGrid should be one of the most performant grid options in the world (see the official example page with a 100k row example) and does a lot to prevent problems (such as virtual row rendering), but you should always have this limitation in mind as this is a major difference to the available lister options that do not have this limitation.
      Currently it only supports AdminThemeUikit and I don't plan to support any other admin theme.
       
      Download: https://gitlab.com/baumrock/FieldtypeRockGrid
      Installation: https://gitlab.com/baumrock/RockGrid/wikis/Installation
      Quikckstart: https://gitlab.com/baumrock/RockGrid/wikis/quickstart
      Further instructions: https://gitlab.com/baumrock/RockGrid/wikis/quickstart#further-instructions
      German Translation File: site--modules--fieldtyperockgrid--fieldtyperockgrid-module-php.json
      Changelog: https://gitlab.com/baumrock/FieldtypeRockGrid/raw/master/changelog.md
       
      Module status: alpha, License: MIT
      Note that every installation and uninstallation sends an anonymous google analytics event to my google analytics account. If you don't want that feel free to remove the appropriate lines of code before installation/uninstallation.
       
      Contribute:
      You can contribute to the development of this and other modules or just say thank you by
      testing, reporting issues and making PRs at gitlab liking this post buying me a drink: paypal.me/baumrock/5 liking my facebook page: facebook.com/baumrock hiring me for pw work: baumrock.com  
      Support: Please note that this module might not be as easy and plug&play as many other modules. It needs a good understanding of agGrid (and JavaScript in general) and it likely needs some looks into the code to get all the options. Please understand that I can not provide free support for every request here in the forum. I try to answer all questions that might also help others or that might improve the module but for individual requests I offer paid support (please contact me via PM).
       
      Use Cases / Examples:
      Colored grid cells, Icons, Links etc. The Grid also has a "batcher" feature built in that helps communicating with the server via AJAX and managing resource intensive tasks in batches:

      Filters, PW panel links and instant reload on panel close:

      You can combine the grid with a chart library like I did with the (outdated) RockDataTables module:

    • By Paul Greinke
      Hi there. I wrote a custom module for one of my projects. In fact I maybe want to use my module in other projects too. In order to be variable and customizable  I need to implement some custom hooks into my module. So I can afterwards hook into the my functions in order to modify them to match the needs of the new project.
      I tried simply defining functions with the '__' prefix. But that did not work. I'm imagining something like the following:
      <?php class MyClass { public function ___someFunction() { // Do something } } // ready.php $this->addHookBefore('MyClass::someFunction', function($event) { // some customization }); Is there a way to accomplish that? 
×
×
  • Create New...