kongondo

Update: Menu Builder Version 0.1.8. Changelog Added support to disable menu items + related (required for this) permission 'menu-builder-disable-items'. Thanks @cjx2240 Support not to show menu items (pages) not listable to current user. Needs option 'check_listable' => 1 in $options Array. Thanks @Peejay 'current_class' now also applies to Breadcrumbs as well. Thanks @Jonathan Lahijani Note Disabling a menu item cascades the status to all its descendants. In Build Menu view (backend), disabled items displayed with strike-through. Currently available in dev branch only. Please test and let me know, thanks. Screenshots

Technically, nothing is stored in a page, but a field. 10,000 rows of entries in one field is nothing really. MySQL can easily handle millions of rows. The crucial question is usually how you are going to query those rows in a fast and efficient manner. One can't and shouldn't query all the rows. Instead, it usually boils down to using a combination of limit (number of queried rows) and caching. Welcome to the forums .

Update: Merged dev 2.4.1 to master. Changelog New, cleaner Backend UI. Better sorting of Posts, Categories and Tags in their dashboards. New option for posts: post_edit. Allows top or bottom placement of link to edit post for logged in users or non-display of link for all users. Thanks @antoiba86 Code refactoring. Screenshots in this post:

$articles = $pages->find('template=article, sort=-published, limit=10');// latest first //$articles = $pages->find('template=article, sort=published, limit=10');// oldest first foreach ($articles as $a) { echo $a->title . ': ' . date('d F Y', $a->published) . '<br>'; } Is that what you are looking for?

Maybe something like this? $news_member = $pages->find("template=news, body*=$page->title, publish_from>=$year, sort=-publish_from, limit=10"); $content = ''; $newBadge = "<span class='tag is-success'>New</span>"; $lastMonth = 'SomeDate'; if ($news_member->count()) { foreach ($news_member as $n) { if($n->publish_from>=$lastMonth) $content .= $newBadge; $content .= "<p><a href='{$n->url}'>{$n->title}</a></p>"; } } Untested.

Welcome to the forums @fabjeck. If you are using native ProcessWire published page property: echo date('d F Y', $page->published);// e.g. 07 January 2017 I can't remember when 'published' property was added to ProcessWire, but hopefully it should work in the version you are running.

It should, though I don't know how to make it switch to ListerPro....not sure it would be automatic.

Thanks for reporting back...

Here it is...version 3 of Visual Page Selector has this feature....

Visual Page Selector version 003 (released (07/07/2017) Happy to announce that the latest release of Visual Page Selector is now available for Download/Purchase. Documentation is also complete! This is a major update. Visual Page Selector can now be used as a normal but enhanced page field! There are 2 views each for inputfield (page edit) and the page selector modal. These can be combined to suit your workflow as explained in the docs here. As a normal page field, you can opt to view the selected pages as a simple list and add pages to your page field using a ProcessWire Lister modal. This opens so many possibilities, including nuanced differentiation of pages to add to your page field, for example, making use of Lister columns and other page properties. For those that want to use Visual Page Selector as a 'one-page-per-image' solution, you can carry on as normal, with the added benefit of different view combinations In page edit, selectable pages are not loaded directly in the Inputfield allowing you to have hundreds of thousands, nay, unlimited numbers of selectable pages without experiencing any slowdowns (@note: What you see in the screenshot below is not AsmSelect or PageAutocomplete; just a custom list that blends in with the rest of ProcessWire). Please note that there were a few inevitable changes to the field settings. The Lister settings are now separated into individual settings. In addition, there was a typo in the 'vps-delete-page' permission. That should be 'vps-delete-pages'. Due to these, if upgrading from version < 3, please test thoroughly and fix any brokenness before using in production. If you need any help please let us know. Changelog Lister view for an enhanced page field experience. Combine different views as you wish. Faster Inputfield load times in page edit. UX changes. Lister and list view demo

Hi. The documentation is still incomplete, sorry. That and similar options found in MarkupBlog.module should be passed to the respective methods. In this case, the method renderPosts(). Its third argument is $options. For instance: $blog = $modules->get('MarkupBlog'); $options = array('post_comments' => 1, 'post_author_text' => 'Authored by'); $posts = $pages->find('template=blog-post, limit=10r'); echo $blog->renderPosts($posts, false, $options); Please see the method MarkupBlog::getPostsOptions for all available options.

Glad the module is of use to you. Unfortunately, I have never had the need to use Formbuilder. Maybe you could try and let us know? Thanks.

Quick note for those following this. As per @Macrura's request above, VPS has received a major upgrade; It can now be used as a normal page field pages' selector or in a 'one-page-per-image' strategy as before. Working on the final release now. Hope to release next week.

Hi @zkriszti. Seems you installed blog with the option 'blank template files', hence there is no demo content. Blog's documentation, found here, should help you along. It's incomplete but sufficient to get you started.

Hi @Jan Fromm and @oma, Sorry I have been away. I'll have to look into Padloper and get back to you. Thanks

Hi @bernhard, I'll have a think. If you have the time, could you please add this as a feature request in the project page? Thanks.

I realise this was a one-off but just wanted to point out that calling the get() inside the foreach loop is not very efficient. It is better to do that (once) outside the foreach since it is the same template you are retrieving each time.

Thanks Adrian, I'll have a look. Sorry for the late reply Longtom. Here's a code snippet:

Moved to Module/Plugin Development forum since these are work-in-progress and do not yet have support forums.

Hi @Juergen, Thanks for this. I have moved your topic to Dev Talk as I don't think it meets the criteria for a ProcessWire Tutorial.

Hi @Robin S, Thanks for the suggestion. Will consider it.

Variations 001 has been released! Please see its official support thread here. Thanks for your patience! This thread is now closed.

Variations Released 29 May 2017 Variations is a simple yet powerful commercial ProcessWire module that allows website editors to create attributes and their values and from those generate variations of any entity, most notably products. The module consists of FieldtypeVariations and InputfieldVariations as well as a ProcessVariations for managing variations configurations and attributes. Setting up the field is quite easy. First, create a field of type Variations. Define some custom inputs that will need to be directly edited on the page containing the field, for instance a product price, SKU, etc. Secondly, via the Inputfield, create a couple of attributes. Thirdly, create a variations configuration and add the attributes and values you want in the configuration. Link that variations configuration to your page and the module will automatically generate all possible combinations (variations) of the attribute values in that configuration. These, together with the custom inputs you created when setting up the field will be displayed on the page (e.g. a product page), ready for editing. This makes this module quite unique; variations are defined at the page-level rather than at the field level. This presents lots of possibilities such as infinitely reusable attributes and variations configurations. For those using Padloper, integration with the e-commerce platform is quite simple as demonstrated in this tutorial. The module consists of 4 modules ProcessVariations FieldtypeVariations InputfieldVariations VariationsCustomTableManager (autoload module, working behind the scenes) Video Demo: https://youtu.be/T93nn96UL8o Documentation: https://variations.kongondo.com/ Shop: https://processwireshop.pw/plugins/variations/ Requires: ProcessWire 2.5 or newer Features Easily create variations of anything, including products for e-commerce websites, etc Create an attribute once, use it everywhere, multiple times, picking and choosing all or only the attribute values you want Bulk editing of variations configurations and attributes Reusable variations configurations Works with Padloper out-of-the-box with minimal coding User-friendly, intuitive and easy to set up

PM or email @ryan

Hi @fredmv, Welcome to the forums. If you have an active ProCache licence then it is best to post your question in that module's VIP forum. Ask @ryan for access if you don't have one yet.