Jump to content

Recommended Posts

You won't find anything specific to Blog. I suggest you search the forums at large for something like this:

'limit page editing to the user that created that page'

https://processwire.com/talk/topic/3271-can-i-limit-page-editing-to-the-user-that-created-that-page/

Read that whole thread and modify the autoload module to suit your needs. 

  • Like 1

Share this post


Link to post
Share on other sites

Thanks! I edited my question above to include the link to the discussion whose module I used.

I'm reaaaaally close! Of course not as close as I thought I was about 5 hours ago.. XD

Share this post


Link to post
Share on other sites

Regarding "Related Posts", I have been able to implement this using one line of code :-), OK, not quite but I have chosen a different route from the previously suggested code. Thanks for the inspiration and ideas though!  I will wrap this in a new renderRelatedPosts() method in MarkupBlog. In case you are wondering, the most important line of code is this:

$related = $pages->find("template=blog-post, blog_categories=$page->blog_categories, blog_tags=$page->blog_tags, id!=$page->id, limit=3, sort=-blog_date");

I'll post details later but I will make this configurable in the new method, i.e. add options to find related posts by 'tag' OR by 'category' OR 'by both tag AND category'. There will also be an option for limit as well as sort, i.e. if limiting, e.g. to 3 related posts, what's the criteria for your '3 most important related posts'? The default will be 'most commented on related posts' sort by latest posts (blog_date).

Then, similar to the 'Related Categories', 'Related Tags' and 'See also' output that you can see in the demo Blog template files running on the left hand side navigation, one will simply need to use the method renderNav() to display Related Posts as follows in the template file 'blog-post.php':

$subNav .= $blog->renderNav(__('Related Posts'), $related);

Just wanted to post these ideas before I finalise the code in case there is something I am missing? Thanks.

Edited by kongondo
  • Like 1

Share this post


Link to post
Share on other sites

Sounds good!

In my installation I deactivated comments, that's why I havn't though about the option 'most commented on related posts' (but I really like the sort option). I have not that much blog posts so I need the following combination: find related posts by 'both tag AND category', by 'category' and by 'tag' (in that order) to fill my list.

  • Like 1

Share this post


Link to post
Share on other sites

Good catch; sorting by 'most commented on related posts' cannot be the default since not everyone will have activated Blog Comments. I have changed the default to sort by latest post...

Share this post


Link to post
Share on other sites

Update: Blog version 2.3.2
 
Additions
Thanks to idea by @justb3a, I have added a new method renderRelatedPosts() to MarkupBlog.  The method returns a PageArray of posts related to the post currently being viewed or the specified blog post/page. (if related posts found, otherwise returns null). It takes four arguments as follows:


renderRelatedPosts(Page $post = null, $relatedBy = null, $limit = null, $sort = null) 

1. $postThe post whose related posts will be returned. Defaults to the current page if none specified
 
2. $relatedBy: This sets the criterion for determining how other posts are related to the current post. There are 3 possible options here:
 
a. $relatedBy = 1: posts are related by both tags AND category. This means that in order to be considered as related to the specified post, the posts to be returned must have at least one tag and at least one category in common with the specified post. This is the default relation criterion.
 
b. $relatedBy = 2: posts are related by tags ONLY. Means that at least one tag has to match the specified post's tags.
 
c. $relatedBy = 3: posts are related by categories ONLY. Means that at least one category has to match the specified post's categories.
 
3. $limit: Number of related posts to retrieve. Defaults to 3 posts.
 
4. $sort: This determines the related posts to prioritise in the find. It is especially useful when you set a $limit. It defaults to sort by blog_date DESC, meaning latest posts. You can use any other valid ProcessWire sort value, e.g. sort by title, sort by 'most commented on posts' [see example below], sort by random, etc.
 
The method returns no markup and its output can be used in a variety of ways.
 
Examples

#RELATED POSTS

##1. used in conjuction with MarkupBlog's renderNav()
##similar to 'Related Categories' in the left-hand navigation in demo Blog 'blog-post.php' template file

//CALL THE MODULE - MarkupBlog
$blog = $modules->get("MarkupBlog");

//use defaults. Related posts limited to 3, related to this post by BOTH tags AND categories, ordered by blog_date DESC
$related = $blog->renderNav(__('Related Posts'), $blog->renderRelatedPosts());

//use renderNav() markup
echo $related;

//find the 'most commented on' posts related to this post by category
$related = $blog->renderNav(__('Related Posts'), $blog->renderRelatedPosts(null, $relatedBy=3, null, '-blog_comments.count'));

//find 7 posts, ordered Alphabetically by title, related to this post by tag
$related = $blog->renderNav(__('Related Posts'), $blog->renderRelatedPosts(null, $relatedBy=2, $limit=7, 'title'));

##2. used outside blog-post.php or even outside Blog pages

$post = $pages->get(2550);

//find 5 random posts related to the specified post by BOTH tags AND categories
$related = $blog->renderNav(__('Related Articles'), $blog->renderRelatedPosts($post, null, $limit=5, 'random'));

//find the 3 'least commented on' posts related to the specified post by tags
$related = $blog->renderRelatedPosts($post, $relatedBy=2, null, 'blog_comments.count');

//find 3 posts related to the specified post by tags AND categories
$related = $blog->renderRelatedPosts($post);

//use custom markup
foreach($related as $r) echo $r->title . '<br>';

Screenshot
post-894-0-13002400-1422301690_thumb.png
 
Currently in dev branch only for testing.

  • Like 2

Share this post


Link to post
Share on other sites

Here's a quick question...

I have the URL structuring set up as option 1

So blog/posts/post but would like to change to blog/post

Can I just move the posts out of the post parent page. Or would I be right in assuming it would be better to use a htaccess rewrite and rewrite blog/posts/post to blog/post ?

Thanks all

Share this post


Link to post
Share on other sites

Is this already live? Are you not able to reinstall and select style 2?

Share this post


Link to post
Share on other sites

Having a problem uninstalling. When you uninstall you have to manually delete fields etc, BUT as you have already uninstalled you cannot access blog-> cleanup.

Could you please add a link or text above uninstall to ask "Would you like to delete the fields as well?"

as I cannot now reinstall:

SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'blog-author-30' for key 'name_parent_id'

Tried manually deleting everything in the database but still get this error

Thanks

Share this post


Link to post
Share on other sites

Having a problem uninstalling. When you uninstall you have to manually delete fields etc, BUT as you have already uninstalled you cannot access blog-> cleanup.

Well this is not true...at least not if you followed the instructions to the letter  ;).

The instructions are very clear. There is no need to manually uninstall anything in Blog 2. Uninstall is a two step process

(i). Use the Cleanup first

(ii) Uninstall the module

https://github.com/kongondo/Blog#uninstall

Uninstalling Blog is a two-step process. If you are logged in as a superuser, you will see a Blog menu item called Cleanup. It will lead to a screen with info about all the Fields, Templates, Pages and Role you are about to delete. It will also list the Blog Template Files that, if you wish, you can also delete. This utility is also useful when you want to try out the different Blog styles without uninstalling the whole Blog module. It returns Blog to the state similar to when you first installed the module. Of course, in case you want to remove Blog as well, just go ahead and uninstall in the normal way but AFTER you have cleaned-up.

To remedy your situation, you need to delete the role 'blog-author'. 

Share this post


Link to post
Share on other sites

I'm fully aware its a two step process. However I forgot about the cleanup and clicked uninstall. This is about usability and this is not usable. Considering the average user is not expected to look at the uninstall page to uninstall a module with a button called uninstall on it.
 

"Uninstall this module? After uninstalling, you may remove the modules files from the server if it is not in use by any other modules.

Uninstall

This will also uninstall other modules - MarkupBlog, BlogPublishDate"

Where does it say anything about Cleanup here?

I have already deleted the role blog-author and still get the same error. I tried deleting everything manually, twice and still get this error.

I have checked every table and field I can think of and cannot find blog-author-30.
 


 

Share this post


Link to post
Share on other sites

There should be a link back to the Cleanup which is external from the 2nd step of the install process.

1. Uninstall.
2. Install.

3. See install failure due to not cleaning up.

4. Cannot reach Cleanup page as not installed. I would put the cleanup page with the install page so it can be accessed.

5. Manually delete everything, if you miss one thing, you have to start all over again.

Solution: Create a separate link to the cleanup page highlighting the SQL syntax to drop all relevant data.
 

  • Cannot install Blog fields. Some field names already in use. These are: blog_body, blog_categories, blog_comments, blog_comments_view, blog_comments_max.

  • A role called 'blog-author' already exists!

  • Due to the above errors, the install wizard did not run. Make necessary changes and try again.

  • SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'blog-author-30' for key 'name_parent_id'

    this is after manually uninstalling and deleting everything 4 times now.

    During the install it stops halfway through saying the field already exists from the >>>CURRENT<< install attempt.

    How could it? I checked the fields it references, deleted the field and ran it again. It now says a different field already exists.

Share this post


Link to post
Share on other sites

I think with all complicated systems, and this is considerably more complicated that your average little textformatter, it is always worth reading all relevant documentation before doing anything drastic.

I speak as one who has often messed up because I didn't! :)

Like all those times in front of clients I ranted and raved because yet again, the huge tape machine in our studio was not working! 

Only for the maintenance man to come all the way up to the top floor just to turn the mains switch on.

Oops.

Share this post


Link to post
Share on other sites

This is about usability , no rants and raves and it's a very simple solution.

With all complicated systems we code and focus on documentation and quirks later which stops adopt-ability. I code to make it fool-proof. It saves a lot of time in support etc later on.

Share this post


Link to post
Share on other sites

Update: Blog version 2.3.3

In addition to the very clear instructions on how to uninstall Blog (README), I have added an even clearer textual reminder/warning in Blog's module configuration screen to first run the in-built Cleanup Utility before uninstalling the module. 

post-894-0-70552800-1422577885_thumb.png

Committed to master...(including the new renderRelatedPosts()method discussed a couple of posts up.)

See next post about a utility to help when disaster strikes, aka, despite the very visible new warning text and despite the clear instructions you somehow find yourself with Blog components left in your hands having made the mistake of first uninstalling Blog and now you can't reinstall it without going through some very tedious manual cleanup....

  • Like 1

Share this post


Link to post
Share on other sites

DISCLAIMER:

The Blog Module already provides an in-built Cleanup Utility that enables you to remove all its components. As per the instructions in the module's README, which must be thoroughly read before using the module (as instructed in the first post in this thread and in various other places), in case you wish to uninstall Blog, you FIRST have to run the Cleanup Utility whilst logged in as a Supersuser. Further, as of this writing, a clear warning text is now visible right above the uninstall button in Blog's module configuration screen reminding you of this fact. Failure to follow the correct uninstall routine means that you will not be able to reinstall Blog until you (often manually) delete all the leftover components (that the Cleanup Utility would have removed for you) - a tedious, frustrating and painful exercise. 

In case, for some reason, you did not adhere to the above instructions, I am providing in the link below code to help you automatically remove any Blog leftovers in order for you to reinstall the module (if you wish, of course) or in case you just want to clean up. 

On install, Blog stores the IDs of its main pages in its configuration settings. Uninstalling Blog means those settings are lost. Hence, if using this code, the only way to find Blog pages is by their templates which in some cases, may not be very foolproof. This and others issues are documented in the utility code linked to below. 

This code is provided as is, with no obligation on my part, without any warranty, implied or otherwise. In plain English; whilst I have thoroughly tested the code, you will be using it at your own risk for which I will bear no responsibility :-).

The code should ONLY be used in case you reversed the uninstall procedure; otherwise use the normal procedure (see README) to uninstall Blog.

Link: blogCleaner

Instructions:

  1. Back up your database and template files
  2. Log in as a Supersuser
  3. Copy and paste the Cleaner code in the link above at the very top of a template file
  4. Save the template file
  5. On the frontend, visit a page that uses that template file
  6. The Cleaner's screen will be loaded
  7. Tick the checkbox to agree you 'know what you are doing, etc..'
  8. Complete the questions about the type of Blog you had before the uninstall
  9. Run the Cleaner
  10. If no errors found a success message will be displayed
  11. In your Admin, check that things went OK (and if need be  re-run the Cleaner)
  12. Restore the template file in #3 to its previous state
  13. Save the template file
  14. Reinstall Blog (optional :-))

Screens

post-894-0-32132500-1422580593_thumb.png

post-894-0-86703200-1422580594_thumb.png

------------------------

PS: I hope none of the above comes across as rude or forceful. I'll read this again in the morning just to be sure or in case someone PM's me, whichever is the sooner :-). I will then amend as appropriate.

  • Like 2

Share this post


Link to post
Share on other sites

I have a series of blog posts on my blog.php.

It's just rendering a preview image, date, title and summary.

I want to control the order of the posts but neither 

sort=-date

or

sort=sort

is working when added to my two selectors.

         <!-- CENTRE COLUMN - MAIN -->               
          <div class="small-12 medium-9 large-9 columns ">
                <!-- START Nested Column containing featureimage and post-summary -->            
                    <?php $blogposts = $pages->find("template=blog-post"); foreach ($pages->find("template=blog-post,") as $b) {
                    echo "
					   <div class='row row-spacer'>
					     <div class='small-12 large-6 columns'><img src={$b->blog_images->first()->url} /></div>
					     <div class='small-12 large-6 columns'>
						 <div class='posts-date'>{$b->blog_date}</div>
						 <h3><a href='$b->url'>{$b->title}</a></h3>
						 {$b->blog_summary}</div>
					   </div>
					";
					} ?>
                <!-- END Nested Column containing featureimage and post-summary -->    
          </div>

Share this post


Link to post
Share on other sites

You can only sort by fields that exist in that template or internal properties (e.g., sort). There is no field called 'date' in the template 'blog-post'...unless you added it yourself? Otherwise, the following should work.

I don't know why you had two $pages->find()? Did you also add the field 'blog_summary'?

<!-- CENTRE COLUMN - MAIN -->               
<div class="small-12 medium-9 large-9 columns ">
    <!-- START Nested Column containing featureimage and post-summary -->            
        <?php $blogposts = $pages->find("template=blog-post, sort=-blog_date, sort=sort");

        foreach ($blogposts as $b) {
	        echo "
			   <div class='row row-spacer'>
			     <div class='small-12 large-6 columns'><img src={$b->blog_images->first()->url} /></div>
			     <div class='small-12 large-6 columns'>
				 <div class='posts-date'>{$b->blog_date}</div>
				 <h3><a href='$b->url'>{$b->title}</a></h3>
				 {$b->blog_summary}</div>
			   </div>
			";
		}
		?>
    <!-- END Nested Column containing featureimage and post-summary -->    
</div>

Share this post


Link to post
Share on other sites

@Kongondo

Thanks for the quick reply. I assumed the Date field was called date. As you point out, it's actually "blog_date". 

I've installed Somas Helper Field Links and this has made the field names more obvious.

I don't know why you had two $pages->find()

I'm not sure either. I don't do this in my current projects and I wondered if it was a legacy piece of code. Clearly just an error though.

Did you also add the field 'blog_summary'?

Yes, we use it for a tiny summary on the blog overview page. You probably have something like this native now but this is an older version of Blog Module I've yet to update.

Also, wanted to apologise for the abrupt request for help in the original post. My client is presenting this at 10AM this morning and informed me 30 mins prior to the meeting that they needed the posts in a particular order. The order had been fine for the past few days. Anyway, thanks again.  ^-^

Share this post


Link to post
Share on other sites

Hi Kongondo. I attempted to comment on a blog post and was redirected to [root]/#CommentForm which just booted me back to the home page.

My blog-post.php template file contains only the following code regarding blog comments:

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

and

echo $page->blog_comments->render();

echo $page->blog_comments->renderForm(); 

$numComments = $page->blog_comments->count();

Here's the markup that the site outputs for the form.

<div id='CommentForm' class='CommentForm_new'>
<h3>Post Comment</h3>
<form id='CommentForm_form' action='./#CommentForm' method='post'>
	<p class='CommentForm_cite'>
		<label for='CommentForm_cite'>Your Name</label>
		<input type='text' name='cite' class='required' required='required' id='CommentForm_cite' value='' maxlength='128' />
	</p>
	<p class='CommentForm_email'>
		<label for='CommentForm_email'>Your E-Mail</label>
		<input type='text' name='email' class='required email' required='required' id='CommentForm_email' value='' maxlength='255' />
	</p>
	<p class='CommentForm_text'>
		<label for='CommentForm_text'>Comments</label>
		<textarea name='text' class='required' required='required' id='CommentForm_text' rows='5' cols='50'></textarea>
	</p>
	<p class='CommentForm_submit'>
		<button type='submit' name='CommentForm_submit' id='CommentForm_submit' value='1'>Submit</button>
		<input type='hidden' name='page_id' value='1449' />
	</p>
</form>
</div><!--/CommentForm-->

Without changing the module I'm not sure how to fix this. I checked the Settings in Blog Admin but nothing seems to control the form directly.

Share this post


Link to post
Share on other sites

Not sure what funkiness is going on there. Have a look at the demo blog-post.php. All you need to render both comments and the form is MarkupBlog's method renderComments() (form will only be displayed if the page uses the template blog-post).

$blog = $modules->get("MarkupBlog");
echo $blog->renderComments($page->blog_comments);
Edited by kongondo

Share this post


Link to post
Share on other sites

Thanks Kongondo. I replaced my code with yours, but the result of attempting to post a comment is the same.

Share this post


Link to post
Share on other sites

Aah, I think I know what is happening....It is not directly related to Blog but the settings of your comments field. Edit the field blog_comments. Go to..

Admin > Setup > Fields > Edit Field: blog_comments. Go to the Details tab. In the second row on that settings page, under Redirect after comment post?, I think you have that checkbox checked. Read the info there and decide whether you want to have it redirect or not. 

Share this post


Link to post
Share on other sites

I hadn't checked all those settings before! Redirect after Comment was not checked, and playing with the settings there had no effect. The comment is not posted and the user ends up on the site front page (/#CommentForm).

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 Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-07-03 -- SnipWire 0.8.7 (beta) released! Fixes some small bugs and adds an indicator for TEST mode 2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  

       
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By Sten
      Hello
      Till now I hacked something with the twig template but it works no more with new PW versions so I look forward to create a module. I am working on a site in multiple languages : French, English, Italian, German, Spanish, Portuguese, Hebrew, Russian. The new posts are entered in any language with a field for language. Till now, I got twig files to get the translations with constants defined for each part of the pages.
      So I'd like to create a module to include theses files added according to the url /fr/en/...
      Have you some observations to do before I begin about the direction to take ?
      Thank you
    • By ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      Adding custom path not supporting anymore !
      // Add your custom path inside your module class`init` function, didn't tested outside public function init() { $path = __DIR__ . DIRECTORY_SEPARATOR . 'configs' . DIRECTORY_SEPARATOR; Mystique::add($path); } Mystique module will search site/modules/**/configs/Mystique.*.php and site/templates/Mystique.*.php paths for Mystique config files.
      All config files need to return a PHP ARRAY like examples.
      Usage almost same with ProcessWire Inputfield Api, only difference is set and showIf usage like on example.
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
    • By Robin S
      This is a module I made as an experiment a while ago and never got around to releasing publicly. At the time it was prompted by discussions around using Repeater fields for "page builder" purposes, where the depth feature could possibly be used for elements that would be nested inside other elements. I thought it would be useful to enforce some depth rules and translate the depth data into a multi-dimensional array structure.
      I'm not using this module anywhere myself but maybe it's useful to somebody.
      Repeater Depth Helper
      This module does two things relating to Repeater fields that have the "Item depth" option enabled:
      It enforces some depth rules for Repeater fields on save. Those rules are:
      The first item must have a depth of zero. Each item depth must not be more than one greater than previous item depth. It provides a RepeaterPageArray::getDepthStructure helper method that returns a nested depth structure for a Repeater field value.
      Helper method
      The module adds a RepeaterPageArray::getDepthStructure method that returns a multi-dimensional array where the key is the page ID and the value is an array of nested "child" items, or null if there are no nested children.
      Example

      The module doesn't make any assumptions about how you might want to use the depth structure array, but here is a way you might use it to output a nested unordered list.
      // Output a nested unordered list from a depth structure array function outputNestedList($depth_structure, $repeater_items) { $out = "<ul>"; foreach($depth_structure as $page_id => $nested_children) { $out .= "<li>" . $repeater_items->get("id=$page_id")->title; // Go recursive if there are nested children if(is_array($nested_children)) $out .= outputNestedList($nested_children, $repeater_items); $out .= "</li>"; } $out .= "</ul>"; return $out; } $repeater_items = $page->my_repeater; $depth_structure = $repeater_items->getDepthStructure(); echo outputNestedList($depth_structure, $repeater_items);
       
      https://github.com/Toutouwai/RepeaterDepthHelper
      https://modules.processwire.com/modules/repeater-depth-helper/
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
×
×
  • Create New...