Jump to content
adrian

Batch Child Editor

Recommended Posts

I'll try to check this tomorrow. I'm currently pretty swamped between my holiday and another vacation coming up.

  • Like 2

Share this post


Link to post
Share on other sites
I'm currently pretty swamped between my holiday and another vacation coming up. 

My heart bleeds for you :)

Whenever you get the chance to look it will be greatly appreciated - turns out to be pretty painful to replicate all the checks in all scenarios - hopefully I have everything covered.

Share this post


Link to post
Share on other sites

Just added some new features and a couple of bug fixes to the dev branch.

  1. Fixes for export mode with certain complex field types
     
  2. Added support for AJAX loading of BCE - especially useful if you are using the "New Tab" position option - requires PW 2.6.11+. This will make Page -> Edit load much quicker when you have lots of child pages.
     
  3. New Lister mode - this allows you to view (and configure the default columns/filters) all children under the current page. If you have ListerPro installed you can also use the Actions on the children. This also supports inline editing which makes for a very quick and easy way to edit the key fields on each child page.

Please let me know how the new AJAX load and Lister mode features work for you - I think I need some wider testing before pushing this to the master branch.

You can define the Lister config settings sitewide, and then provide overrides for each parent page that has been enabled under "Configurable Pages"

post-985-0-61627100-1439912334_thumb.png

This screenshot shows the new Lister mode configured to show a predefined set of columns - a great way to preview the page content of child pages.

post-985-0-89453200-1439904134_thumb.png

This shows the Lister Inline Edit mode - making for very quick editing of key fields in child pages.

post-985-0-03194800-1439919612_thumb.png

  • Like 6

Share this post


Link to post
Share on other sites

seems i've to translate some strings again....you're really getting this as alternative editing interface for childpages instead of the normal pagetree....;)

Thank you very much for this nice piece of work - will testing soon.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks @mr-fan!

I just put together another screenshot showing how you can use BCE as the equivalent of an inline PageTable field interface. 

Obviously these are just child pages and are not callable from a field, but it provides an excellent editing interface in a dedicated tab along with all the filtering options of lister. It also doesn't have any of the problems with a PageTable field regarding editing the content page directly and not having new pages automatically added, etc. The inline ajax editing is also a great bonus over the popup modal editing. 

Of course, this inline editing requires ListerPro, but I think it is worth it :)

post-985-0-14812200-1439922118_thumb.png

  • Like 3

Share this post


Link to post
Share on other sites

Sorry for the stream of updates, but you can now embed BCE into the flow of fields within the Content Tab. This makes for even easier access to inline ajax editing of child pages.

It probably only makes sense for Lister, Edit, and Export modes.

Just pushed this option to the dev branch.

post-985-0-90776500-1439936696_thumb.png

  • Like 4

Share this post


Link to post
Share on other sites

You are a real bad guy....with all this "stream updates" ;)

just one tick while testing...

https://github.com/adrianbj/BatchChildEditor/pull/4

(changes the labels on the field selection in the right language)

The issue with Lister view if there was images is a problem of the actuale PW dev i think?

For BCE i tested today very much and the next days german translation follows....while testing i've to say just one thing but i think i'm repeating me:

THIS IS A SUPER MEGA GREAT ADDON.... ^-^

some little testing things:

- Setting (Editor,Position, Load...) ->Position = Inline Fieldset, Insert After = title, load the fieldset open = true, ....Open Method is hidden if loading the fieldset collapsed but "Normal" or "Ajax" loading should be selectable while this setting enables the inline editing, too not only the loading?

- A "modal option" for lister mode should be a little additional option for the lister edit links, to edit childpages in modal mode...

This is really great if your wanna a easy and nice overview page on such root pages for the same kind of content like team, tags and articles or similar....i'll embed it in my current projects since it is much more flexible that a pagetable for this task!

And a additional call for others to buy Lister Pro...;)

Best regards mr-fan

  • Like 1

Share this post


Link to post
Share on other sites

@mr-fan - thanks for the great feedback, testing, and the PR for language labels. 

  1. Yep - I think the issue with the Lister view not working when there is an images field selected is a problem with PW dev / Lister
  2. I don't quite understand the Normal/Ajax load problem (I am sure I am missing something obvious so will look better later to see if I can figure out why that needs to be an available option when Open is checked.
  3. Yep - I was planning on making the Lister EDIT mode configurable to include the modal option, but there is something stopping it from working properly in modal mode - I think it's because Lister is in an iframe, but I will look again and see if I can get it to work - it would be much nicer for times when inline/ajax editing is not enough (or the user doesn't have ListerPro).

I am also thinking of making it possible to choose a different parent (or maybe even use a full PW selector) so you can make BCE grab children from somewhere else in the page tree - I think this would only work for Lister, Edit, and Export modes, but could be very cool - kinda like the ability of PageTable to specify a different parent, but even more powerful. I'll hopefully play with this in the next few days and post a new dev version then.

  • Like 1

Share this post


Link to post
Share on other sites

Ok, just pushed a new version to dev that adds support for choosing an alternate Parent. This allows you to bring in child pages from any other parent in the page tree (like I mentioned in my previous post above). It's a new option under the Content / Deletion / Protection tab - obviously only available for page specific config settings.

Also added an option to determine whether Filters/Columns/Actions are available in Lister mode - checkbox under the Lister mode settings tab.

This version might require a little extra testing regarding allowed templates for editing/adding pages.

Please let me know how it goes.

  • Like 3

Share this post


Link to post
Share on other sites

Somehow the "Own Tab" setting doesn't seem to work on a 2.6.14 installation, leaving the functionality inside of "Children" does work.

Share this post


Link to post
Share on other sites

Somehow the "Own Tab" setting doesn't seem to work on a 2.6.14 installation, leaving the functionality inside of "Children" does work.

Not sure exactly what changed just yet, but it works for me so long as the Tab / fieldset name is only one word. Not sure if it's a bug that Ryan introduced or what, but if you use a multi word name, I run it through the PageName sanitizer and now it breaks the tab. Will investigate further later, but for now, one word names should work fine. 

Share this post


Link to post
Share on other sites

Sorry for the delay - while I was out for dinner I realized exactly what the issue was - I needed the fieldName sanitizer, not pageName. Not sure why it worked before - I guess 2.6.14 enforced no dashes in fieldset names?

Anyway, it is fixed now on the dev branch. if you don't want to switch to the dev branch at the moment, here are the changes you need:
https://github.com/adrianbj/BatchChildEditor/commit/f1721794a77c1b6dfebcae692485f41ee0df75ea#diff-b79b82291600910335909ae234e40fdb

Share this post


Link to post
Share on other sites

I'm not sure if that's a Lister issue, but by default the pages should really be sorted by "sort" and not "-modified", which makes less sense in the module's context.

Edit: It would also be nice if there would be a way to exclude some fields (e.g. mode) from the new save-reminder functionality.

Share this post


Link to post
Share on other sites

I'm just started to use BCE id a project and I like it, thanks!

One question: do you plan to add a toggle checkboxes to columns, eg. mark all / unmark all?

Sometimes I need to delete tens of pages at a time and this would speed up the process a lot.

(for example 72 pages this time, this happens when my form processor goes wrong :))

Share this post


Link to post
Share on other sites

I'm just started to use BCE id a project and I like it, thanks!

One question: do you plan to add a toggle checkboxes to columns, eg. mark all / unmark all?

Sometimes I need to delete tens of pages at a time and this would speed up the process a lot.

(for example 72 pages this time, this happens when my form processor goes wrong :))

The easiest way to batch delete a huge number of pages is to enable the "Replace" mode and make sure you have the "Text/Paste" option checked under: Data entry / CSV import options > Page data options

Then simply empty the TextArea list of all the child pages and click save!

Please let me know if anything doesn't make sense - the config options in this module can take a while to get the hang of  :)

Share this post


Link to post
Share on other sites

I'm not sure if that's a Lister issue, but by default the pages should really be sorted by "sort" and not "-modified", which makes less sense in the module's context.

Edit: It would also be nice if there would be a way to exclude some fields (e.g. mode) from the new save-reminder functionality.

Sorry for the late response on this one - it is definitely on my list of things to do - unfortunately it doesn't seem to be as simple as it sounds - I am getting conflicts with the main Pages->Find Lister, but when I find some time, I'll definitely see if it can be fixed.

Share this post


Link to post
Share on other sites

Please let me know if anything doesn't make sense - the config options in this module can take a while to get the hang of  :)

Sure it helps, thanks! The module seemed surprisingly simple at first but now I can see the whole beast :)

The thing I was trying to recommend is a checkbox that would toggle all checkboxes in the column, like this:

post-3156-0-44542700-1441908361_thumb.pn

This would require only some lines of JavaScript.

Share this post


Link to post
Share on other sites

Thanks - I do see your point regarding the check all - it would be especially useful for the hidden/unpublished options and I am sure something similar could be done for the delete option in edit view also.

Would you mind adding an Issue on Github for me so I don't forget to do this at some point, or better yet, a PR ;)

Share this post


Link to post
Share on other sites

PR done! Feel free to review.

It doesn't check whether the items are checked or not, just toggles items on/off.

post-3156-0-95916800-1442151817_thumb.gi

  • Like 4

Share this post


Link to post
Share on other sites

I don't think the shift-click is related to this module. That was the first thing I tried before adding the header checkboxes.

The rearrange feature doesn't work here, and clicking on the the headers doesn't sort the columns - I don't know if that is normal.

Share this post


Link to post
Share on other sites

@tpr - thanks very much for the PR - the functionality looks awesome and will be a great timesaver - I'll try to review in the next couple of days. I haven't ever seen the header "order by" icons in BCE - I certainly didn't add them intentionally - have you added these?

@BernhardB - thanks for all the likes :) I just looked at your video and the only issue I can reproduce is the shift-click selecting checkbboxes both hidden and unpublished columns - not sure if I can fix this or not since it is core functionality, but I will take a look. I am not having any issues using the sort/move handles and the Add New is also working fine. I am using the dev version of BCE here, but I know it worked for me with stable before. I would be curious if you have the same issue with the dev version though. Could you also let me know if there are any console errors - looks like the javascript for BCE is not working at all for you. Is anyone else seeing these issues?

Share this post


Link to post
Share on other sites

No, I only added the thead checkboxes, the sort icons were already there. It looks if there was some js file is missing or somehow it is blocked, but no signs of that in the console. I also got all the issues Bernard has. I will try the dev version later. Isn't it some module setting that blocks some features? (eg. add new page button)

Share this post


Link to post
Share on other sites

that's strange. the issues are gone! i'm on 2.6.17 and the dev version of BCE. though i started with the master BCE and maybe the video was taken with that version. i can't remember, sorry :)

  • Like 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Robin S
      First a note about my other modules...
      I have three existing modules that are similar in that they allow restrictions to be placed on repeating inputfields: Limit Repeater, Limit PageTable, Limit Table
      Restrict Repeater Matrix takes a different approach to the module configuration from those other modules. The module settings for Restrict Repeater Matrix are applied in the field settings rather in a module config screen. I think this new approach is better, but it means that it isn't practical to create different settings for different roles via the admin interface. Instead the module has a hookable method, allowing roles to be targeted and other advanced usages to be achieved via a hook. The result is that the module is more flexible.
      I intend to transition my other modules to the same approach over the coming weeks, but because this will result in breaking changes I will be releasing the updated modules under new names ("Restrict Repeater", etc) to avoid users upgrading via the Upgrades module without full awareness of the changes. The old modules will be marked as deprecated.
      Restrict Repeater Matrix
      A module for ProcessWire CMS/CMF. Allows restrictions and limits to be placed on Repeater Matrix fields. Requires ProcessWire >= v3.0.0 and FieldtypeRepeaterMatrix >= v0.0.5.
      For any matrix type in a Repeater Matrix field you have the option to:
      Disable settings for items (cannot change matrix type) Prevent drag-sorting of items Prevent cloning of items Prevent toggling of the published state of items Prevent trashing of items Limit the number of items that may be added to the inputfield. When the limit is reached the "Add new" button for the matrix type will be removed and the matrix type will not be available for selection in the "Type" dropdown of other matrix items. Please note that restrictions and limits are applied with CSS/JS so should not be considered tamper-proof.
      Usage
      Install the Restrict Repeater Matrix module.
      For each matrix type created in the Repeater Matrix field settings, a "Restrictions" fieldset is added at the bottom of the matrix type settings:

      For newly added matrix types, the settings must be saved first in order for the Restrictions fieldset to appear. Set restrictions for each matrix type as needed. A limit of zero means that no items of that matrix type may be added to the inputfield.
      Setting restrictions via a hook
      Besides setting restrictions in the field settings, you can also apply or modify restrictions by hookingRestrictRepeaterMatrix::checkRestrictions. This allows for more focused restrictions, for example, applying restrictions depending on the template of the page being edited or depending on the role of the user.
      The checkRestrictions() method receives the following arguments:
      $field This Repeater Matrix field $inputfield This Repeater Matrix inputfield $matrix_types An array of matrix types for this field. Each key is the matrix type name and the value is the matrix type integer. $page The page that is open in ProcessPageEdit The method returns a multi-dimensional array of matrix types and restrictions for each of those types. An example of a returned array:

      Example hooks
      Prevent the matrix type "images_block" from being added to "my_matrix_field" in a page with the "basic-page" template:
      $wire->addHookAfter('RestrictRepeaterMatrix::checkRestrictions', function(HookEvent $event) { $field = $event->arguments('field'); $page = $event->arguments('page'); $type_restrictions = $event->return; if($field->name === 'my_matrix_field' && $page->template->name === 'basic-page') { $type_restrictions['images_block']['limit'] = 0; } $event->return = $type_restrictions; }); Prevent non-superusers from trashing any Repeater Matrix items in "my_matrix_field":
      $wire->addHookAfter('RestrictRepeaterMatrix::checkRestrictions', function(HookEvent $event) { $field = $event->arguments('field'); $type_restrictions = $event->return; if($field->name === 'my_matrix_field' && !$this->user->isSuperuser()) { foreach($type_restrictions as $key => $value) { $type_restrictions[$key]['notrash'] = true; } } $event->return = $type_restrictions; }); http://modules.processwire.com/modules/restrict-repeater-matrix/
      https://github.com/Toutouwai/RestrictRepeaterMatrix
    • By BitPoet
      Here's a little text formatter module that redirects all external links found in a textarea (e.g. for hit counting) to a given URL.
      TextformatterExternalRedirect
      GitHub repo
      As TextFormatters do, this module modifies the contents of the textarea (HTML) at rendering time. It prepends the given URL to the link address for external links (http and https), optionally makes sure that the link is opened in a new window and allows you to add css classes to such links.
      All options can be configured in the module's configuration settings.
      Usage:
      Download the zip archive and extract it to site/modules, the rename the top folder to TextformatterExternalRedirect Go to the backend and select "Modules" -> "Refresh", then click "Install" for "External Link Redirect" Click "Settings" and configure the module
      Go into the field configuration for the field(s) you want this formatter to apply to and add it from the dropdown
      Done, now any external links in the configured fields will have the configured settings applied Feel free to leave feedback and post and questions you have here.
       
    • By teppo
      Hey folks!
      Took a couple of late nights, but managed to turn this old gist of mine into a proper module. The name is SearchEngine, and currently it provides support for indexing page contents (into a hidden textarea field created automatically), and also includes a helper feature ("Finder") for querying said contents. No fancy features like stemming here yet, but something along those lines might be added later if it seems useful (and if I find a decent implementation to integrate).
      Though the API and selector engine make it really easy to create site search pages, I pretty much always end up duplicating the same features from site to site. Also – since it takes a bit of extra time – it's tempting to skip over some accessibility related things, and leave features like text highlighting out. Overall I think it makes sense to bundle all that into a module, which can then be reused over and over again 🙂
      Note: markup generation is not yet built into the module, which is why the examples below use PageArray::render() method to produce a simple list of results. This will be added later on, as a part of the same module or a separate Markup module. There's also no fancy JS API or anything like that (yet).
      This is an early release, so be kind – I got the find feature working last night (or perhaps this morning), and some final tweaks and updates were made just an hour ago 😅
      GitHub repository: https://github.com/teppokoivula/SearchEngine Modules directory: https://modules.processwire.com/modules/search-engine/ Demo: https://wireframe-framework.com/search/ Usage
      Install SearchEngine module. Note: the module will automatically create an index field install time, so be sure to define a custom field (via site config) before installation if you don't want it to be called "search_index". You can change the field name later as well, but you'll have to update the "index_field" option in site config or module settings (in Admin) after renaming it.
      Add the site search index field to templates you want to make searchable. Use selectors to query values in site search index. Note: you can use any operator for your selectors, you will likely find the '=' and '%=' operators most useful here. You can read more about selector operators from ProcessWire's documentation.
      Options
      By default the module will create a search index field called 'search_index' and store values from Page fields title, headline, summary, and body to said index field when a page is saved. You can modify this behaviour (field name and/or indexed page fields) either via the Module config screen in the PocessWire Admin, or by defining $config->SearchEngine array in your site config file or other applicable location:
      $config->SearchEngine = [ 'index_field' => 'search_index', 'indexed_fields' => [ 'title', 'headline', 'summary', 'body', ], 'prefixes' => [ 'link' => 'link:', ], 'find_args' => [ 'limit' => 25, 'sort' => 'sort', 'operator' => '%=', 'query_param' => null, 'selector_extra' => '', ], ]; You can access the search index field just like any other ProcessWire field with selectors:
      if ($q = $sanitizer->selectorValue($input->get->q)) { $results = $pages->find('search_index%=' . $query_string . ', limit=25'); echo $results->render(); echo $results->renderPager(); } Alternatively you can delegate the find operation to the SearchEngine module as well:
      $query = $modules->get('SearchEngine')->find($input->get->q); echo $query->resultsString; // alias for $query->results->render() echo $query->pager; // alias for $query->results->renderPager() Requirements
      ProcessWire >= 3.0.112 PHP >= 7.1.0 Note: later versions of the module may require Composer, or alternatively some additional features may require installing via Composer. This is still under consideration – so far there's nothing here that would really depend on it, but advanced features like stemming most likely would.
      Installing
      It's the usual thing: download or clone the SearchEngine directory into your /site/modules/ directory and install via Admin. Alternatively you can install SearchEngine with Composer by executing composer require teppokoivula/search-engine in your site directory.
    • By teppo
      MarkupMenu is a markup module for generating menu trees. When provided a root page as a starting point, it generates a navigation tree (by default as a HTML "<ul>" element wrapped by a "<nav>" element) from that point onwards. If you've also provided it with current (active) page, the menu will be rendered accordingly, with current item highlighted and items rendered up to that item and its children (unless you disable the "collapsed" option, in which case the full page tree will be rendered instead).
      Modules directory: https://modules.processwire.com/modules/markup-menu/ GitHub repository: https://github.com/teppokoivula/MarkupMenu Usage
      As a markup module, MarkupMenu is intended for front-end use, but you can of course use it in a module as well. Typically you'll only need the render() method, which takes an array of options as its only argument:
      echo $modules->get('MarkupMenu')->render([ 'root_page' => $pages->get(1), 'current_page' => $page, ]); Note: if you omit root_page, site root page is used by default. If you omit current_page, the menu will be rendered, but current (active) page won't be highlighted etc.
      A slightly more complex example, based on what I'm using on one of my own sites to render a (single-level) top menu:
      echo $modules->get('MarkupMenu')->render([ 'current_page' => $page, 'templates' => [ 'nav' => '<nav class="{classes} menu--{menu_class_modifier}" aria-label="{aria_label}">%s</nav>', 'item_current' => '<a class="menu__item menu__item--current" href="{item.url}" tabindex="0" aria-label="Current page: {item.title}">{item.title}</a>', ], 'placeholders' => [ 'menu_class_modifier' => 'top', 'aria_label' => 'Main navigation', ], 'include' => [ 'root_page' => true, ], 'exclude' => [ 'level_greater_than' => 1, ], ]); Note: some things you see above may not be entirely sensible, such as the use of {menu_class_modifier} and {aria_label} placeholders. On the actual site the "nav" template is defined in site config, so I can define just these parts on a case-by-case basis while actual nav markup is maintained in one place.
      Please check out the README file for available render options. I'd very much prefer not to keep this list up to date in multiple places. Basically there are settings for defining "templates" for different parts of the menu (list, item, etc.), include array for defining rules for including in the menu and exclude array for the opposite effect, classes and placeholders arrays for overriding default classes and injecting custom placeholders, etc. 🙂
      MarkupMenu vs. MarkupSimpleNavigation
      TL;DR: this is another take on the same concept. There are many similarities, but also some differences – especially when it comes to the supported options and syntax. If you're currently using MarkupSimpleNavigation then there's probably no reason to switch over.
      I'd be surprised if someone didn't draw lines between this module and Soma's awesome MarkupSimpleNavigation. Simply put I've been using MSN (...) for years, and it's been great – but there are some issues with it, particularly in the markup generation area, and it also does some things in a way that doesn't quite work for me – the xtemplates thing being one of these. In some ways less about features, and more about style, I guess 🙂
      Anyhow, in MarkupMenu I've tried to correct those little hiccups, modernise the default markup, and allow for more flexibility with placeholder variables and additional / different options. MarkupMenu was built for ProcessWire 3.0.112+ and with PHP 7.1+ in mind, it's installable with Composer, and I have a few additional ideas (such as conditional placeholders) still on my todo list.
      One more small(ish) difference is that MarkupMenu supports overriding default options via $config->MarkupMenu. I find myself redefining the default markup for every site, which until now meant that each site had a wrapper function for MarkupSimpleNavigation (to avoid code / config repetition), and this way I've been able to leave that out 🙂
      Requirements
      ProcessWire >= 3.0.112 PHP >= 7.1.0 If you're working on an earlier version of ProcessWire or PHP, use MarkupSimpleNavigation instead.
    • By teppo
      Hey folks!
      I'm happy to finally introduce a project I've been working on for quite a while now: it's called Wireframe, and it is an output framework for ProcessWire.
      Note that I'm posting this in the module development area, maily because this project is still in rather early stage. I've built a couple of sites with it myself, and parts of the codebase have been powering some pretty big and complex sites for many years now, but this should still be considered a soft launch 🙂
      --
      Long story short, Wireframe is a module that provides the "backbone" for building sites (and apps) with ProcessWire using an MVC (or perhaps MVVM – one of those three or four letter abbreviations anyway) inspired methodology. You could say that it's an output strategy, but I prefer the term "output framework" since in my mind the word "strategy" means something less tangible. A way of doing things, rather than a tool that actually does things.
      Wireframe (the module) provides a basic implementation for some familiar MVC concepts, such as Controllers and a View layer – the latter of which consists of layouts, partials, and template-specific views. There's no "model" layer, since in this context ProcessWire is the model. As a module Wireframe is actually quite simple – not even nearly the biggest one I've built – but there's still quite a bit of stuff to "get", so I've put together a demo & documentation site for it at https://wireframe-framework.com/.
      In addition to the core module, I'm also working on a couple of site profiles based on it. My current idea is actually to keep the module very light-weight, and implement most of the "opinionated" stuff in site profiles and/or companion modules. For an example MarkupMenu (which I released a while ago) was developed as one of those "companion modules" when I needed a menu module to use on the site profiles.
      Currently there are two public site profiles based on Wireframe:
      site-wireframe-docs is the demo&docs site mentioned above, just with placeholder content replaced with placeholder content. It's not a particularly complex site, but I believe it's still a pretty nice way to dig into the Wireframe module. site-wireframe-boilerplate is a boilerplate (or starter) site profile based on the docs site. This is still very much a work in progress, but essentially I'm trying to build a flexible yet full-featured starter profile you can just grab and start building upon. There will be a proper build process for resources, it will include most of the basic features one tends to need from site to site, etc. --
      Requirements and getting started:
      Wireframe can be installed just like any ProcessWire module. Just clone or download it to your site/modules/ directory and install. It doesn't, though, do a whole lot of stuff on itself – please check out the documentation site for a step-by-step guide on setting up the directory structure, adding the "bootstrap file", etc. You may find it easier to install one of the site profiles mentioned above, but note that this process involves the use of Composer. In the case of the site profiles you can install ProcessWire as usual and download or clone the site profile directory into your setup, but after that you should run "composer install" to get all the dependencies – including the Wireframe module – in place. Hard requirements for Wireframe are ProcessWire 3.0.112 and PHP 7.1+. The codebase is authored with current PHP versions in mind, and while running it on 7.0 may be possible, anything below that definitely won't work. A feature I added just today to the Wireframe module is that in case ProcessWire has write access to your site/templates/ directory, you can use the module settings screen to create the expected directories automatically. Currently that's all, and the module won't – for an example – create Controllers or layouts for you, so you should check out the site profiles for examples on these. (I'm probably going to include some additional helper features in the near future.)
      --
      This project is loosely based on an earlier project called pw-mvc, i.e. the main concepts (such as Controllers and the View layer) are very similar. That being said, Wireframe is a major upgrade in terms of both functionality and architecture: namespaces and autoloader support are now baked in, the codebase requires PHP 7, Controllers are classes extending \Wireframe\Controller (instead of regular "flat" PHP files), implementation based on a module instead of a collection of drop-in files, etc.
      While Wireframe is indeed still in a relatively early stage (0.3.0 was launched today, in case version numbers matter) for the most part I'm happy with the way it works, and likely won't change it too drastically anytime soon – so feel free to give it a try, and if you do, please let me know how it went. I will continue building upon this project, and I am also constantly working on various side projects, such as the site profiles and a few unannounced helper modules.
      I should probably add that while Wireframe is not hard to use, it is more geared towards those interested in "software development" type methodology. With future updates to the module, the site profiles, and the docs I hope to lower the learning curve, but certain level of "developer focus" will remain. Although of course the optimal outcome would be if I could use this project to lure more folks towards that end of the spectrum... 🙂
      --
      Please let me know what you think – and thanks in advance!
×
×
  • Create New...