Leaderboard

Hi everyone, This is the new official thread for the module that was previewed some time ago here: https://processwire.com/talk/topic/14117-module-settings-import-export/ Big thanks to @Robin S for help testing and feature suggestions! http://modules.processwire.com/modules/module-settings-import-export/ https://github.com/adrianbj/ModuleSettingsImportExport Module features Ability to copy and paste settings from one PW install to another Optional automatic backup of module settings on uninstall and ability to restore settings if you reinstall the module Backup current settings at any time Restore backed up settings at any time Import option checks module name and version number and warns if importing settings from a different version As always, let me know if you find any problems or have any suggestions!

Last week’s post indicated we may have the first [beta] version of the Uikit admin theme ready, and I’m glad to report that we’ve now got it ready for download on GitHub. In this post, we’ll describe what’s new, how to install it, and how to develop with it. https://processwire.com/blog/posts/processwire-3.0.54-and-adminthemeuikit/

How cool is that! Couple of months before it was on the roadmap and now it is here. Or is time starts going faster as you get older?!

I wasn't aware that the field settings are inherited in the ckeditor dialog, but I should have suspected it. What should work though is adding another image field at the bottom of the template, then going to Modules -> Configure ->ProcessPageEditImageSelect and adding the name of your gallery field where it reads "Field names to skip for selection".

Or if you up are for a little bit of a challenge and great learning experience, you could create your own custom fieldtype based off the Event fieldtype: http://modules.processwire.com/modules/fieldtype-events/

Module has been released and now available over here:

https://github.com/adrianbj/ProcessModuleToolkit It allows bulk automated migration installation and upgrading of modules (and their config settings) from one PW install to another, so it should be very handy in setting up new sites with your standard collection of favorite modules and settings. Allows includes batch installing by a list of module class names. Go to the Setup > Module Toolkit and follow the prompts. During the import, you can choose which modules from the collection to import. You can optionally import the module config settings from the source install. The one caveat is if a particular setting includes a reference to a page, template, or field ID, it won't work, but you can easily update this setting on the destination install. Batch install new modules directly from the modules directory with a list of module classnames or URLs to module zip files. You can optionally, automatically update all of the imported modules (if they are in the ProcessWire modules directory) to their latest available versions. It copies the module files so you can use it to migrate modules that are not available in the PW modules directory, or on Github. Great for all those custom helper modules you've created. Full restore feature in case something goes wrong / you change your mind. I maintain a dedicated test PW install for installing and configuring modules which I can then export for use in my projects using this tool. Please test and let me know what you think!

Been coding days and nights in php and processwire for a long while now. Took a little break and made this.

In terms of the page tree, I took a look around some other CMSs and I've come to a first conclusion. I would like to have the page tree in a sidebar, but not all the time, because a clean Interface is key. I'm more for the option to blend it in like the offcanvas Concrete5 does. If we want to keep the mouseover menu, enough space is necessary, more than in the image below. On the majority of the systems a click on the page name opens the page to edit. Even if it is a parent page. Drag and drop to move pages are just implemented and don't use a additional click. I like the approach of the neos backend there, a click opens the page to edit. Dragging a page just happens naturally. The accordion is activated with a specific icon, not by clicking on the page name.

Hi. From the mentioned blog post

You can put emoji in the database (use it in text fields), but you need to use the utf8mb4 charset for your tables, which you can choose on install. You can change it later as well, but I think there's no official upgrade path to do so.

Hi @adrian, thanks for releasing this module. I really like the concept. I can see this being installed on every site. I was able to copy over my TracyDebugger configs and AdminOnSteroids configs successfully. It may be premature to ask, but is there a way to copy the configs of multiple modules at one time like you can do when you export your field settings?

Unfortunately, that doesn't actually work: https://github.com/ryancramerdesign/ProcessWire/issues/1060 I'd actually like to not only have the ability to have a hidden images field, but also the ability to restrict a CkEditor field to store uploaded images in only designated image fields.

This should be seriously considered, even better: in a configurable way. Best thing would be to support user level configuration, meaning the user could overwrite the default (defined by the site's developer) on its Profile page, similarly to current Default/Reno option, but in this case the base of the layout could be configurable. We even have mockups of this!

The problem turned out to be a bug in PW 2.6.1. I didn't realise my local PW version was on 2.8.35 and not 2.6.1. The bug was in $ad = wire(pages)->get("/ads/")->children->getRandom(); It was not returning an object in PW 2.6.1 despite data being present. Live and (hopefully) learn ....

Hello I made a simple app for reading the main RSS for ProcessWire news. Now you can access ProcessWire Blog, ProcessWire weekly and the Latest Forum Posts in a Single App in your iOS or Android smartphone. Open Source of Course. Made using the http://jasonette.com technology. You can compile your own app if you want. For A Quick Look 1.- Download the Jason App (iOS) https://itunes.apple.com/us/app/jason./id1095557868?mt=8 (Android) https://play.google.com/store/apps/details?id=com.jasonette.jason 2.- Use the Following Url https://raw.githubusercontent.com/NinjasCL/pw-app/master/app.json Source Here https://github.com/NinjasCL/pw-app

I'd like to create custom ajax-driven inputfield. Ajax-driven inpufields where introduced here: http://processwire.com/blog/posts/new-ajax-driven-inputs-conditional-hooks-template-family-settings-and-more/#new-ajax-driven-inputfields-system-wide, but since that time I haven't seen any "how-to" tutorials. I'd like to learn from core code, but can't understand which files to check. Can someone suggest which core/module files I have to check in order to learn from code and be able to create custom ajax-driven inputfields?

Shouldn't it be with quotes around pages? Be it in blog/ or talk/, it seems to always be wire("pages") or wire('pages'), wire("page") or wire('page').

Thanks, I forgot about that - went looking in the field settings - I still think perhaps it would be best to be configurable at the field level.

Yeah, I have and yesterday I decided not to because I didn't want to bloat this will all the tools available in Module Toolkit, but now I am second guessing that decision especially given that Module Toolkit is mostly a Process module so if you don't run it, it's not doing anything. I'll think on this a little more - stay tuned

@adrian haven't you think about merging the two Module-related modules?

I was just reading about that module when you posted. I just tried Module Toolkit...Wow what a time saver! Thanks again adrian.

Just to close out this entry. I can confirm that ProcessWire will install and run successfully on a Synology NAS (DSM 6.1 - 15047 Update 1). This was achieved some time ago and we are now developing a visitor information system using this setup.

This is really the domain of although that module does still need a little attention. That said, there might also be a place for it in this module - let me think on this a little more.

Thanks @szabesz, that is exactly the mock-up I was talking about.

I haven't tested, but maybe this helps: https://github.com/somatonic/ColorPicker/issues/7

So, here is the scenario. I am creating my own little advert management system on my new site. Basically, I have pages under a parent each with ad information in them - google ad code, other ad code, my own ads and so on. On the parent page, I have a little ProFields table. The first column is a selector where I can choose a position on the website. "Home Page 1st Ad Position" for instance. In the second column, I have a page select where I select one of the ads. Simple! Now, just to complicate it, one of my choices I want is "Random". Basically, if I choose this one, for a particular position, then it chooses randomly from all my ads. But how to add a "random" choice? Well, it struck me that I just create a blank ad called "random" and then I can choose that one. In my code I just put "if ad name is random then getRandom()" But then, that random selection would also include the random ad. So, that better be unpublished. Now I need to change my selector in the table to include an unpublished item. But then, would the random choice end up choosing the unpublished random ad.... oh god! I could see me causing myself problems. I scratched my head, stared at errors, walked around the house, shouted at the rain, played some solitaire ... And then it came to me. OBVIOUS!!!! Publish the ad page called "random" and just put an advert in it! DUH!!!!!!

Ah, sorry, I was very succinct. The problem was in the back end when used within repeater matrix and default value was not provided. When I sorted that I think it wasn't giving me the functionality I was after anyway so I ended up just nesting another repeater matrix within the main one. I will try again later and report back with some more detail if I can.

I have searched the forum and google but couldn't find anything related. I want to show all field descriptions in admin forms as tooltips. Has this request really not come up before? I imagine a module that hooks into the Inputfield class, adds the description as title value to the inputfield and then makes use of https://jqueryui.com/tooltip/. Am I on the right track here? EDIT: I made a module "InputfieldHookAddTitle": <?php class InputfieldHookAddTitle extends WireData implements Module { public static function getModuleInfo() { return array( 'title' => 'Inputfield Hook Add Title', 'version' => 100, 'summary' => 'Adds title attribute to inputfields with field description as value', 'singular' => true, 'autoload' => true, ); } public function init() { $this->addHookBefore('Inputfield::render', $this, 'addTitle'); } public function addTitle(HookEvent $event) { $inputfield = $event->object; if ($inputfield->description == "") return; $inputfield->setAttribute('title', $inputfield->description); $event->return; } } This adds title attribute with value description to inputfields. Now I need to get rid of the original <p class="description"> tag which is set in the constructor method. How would I unset this? I don't see a unset method. And how do I add the Jquery tooltip js? EDIT: I managed to add the custom JS to the admin pages, thanks to Soma's blog post. In my site/templates/admin.php I added: // add tooltip JS to admin pages $modules->get('JqueryCore'); $modules->get('JqueryUI'); $config->scripts->add($config->urls->templates . "js/admintooltips.js"); and the admintooltips.js $(function() { var tooltips = $( "[title]" ).tooltip({ position: { my: "left top", at: "right+5 top-5" } }); }); Now I only need to get rid of the original description. Any pointers would be much appreciated.

OK found it - /wire/templates-admin/scripts/inputfields.js line 1015 It is already in the core! The way you enable it is by having $config->debug = true; of course it would be nice to have it optionally on when debug is off too as I find it very useful. https://github.com/rolandtoth/AdminOnSteroids uses its variation too but to enable just this little thing thats already part of the core AOS is a bit of an overkill to say the least..

@adrian I am thrilled by your suggestion and would give it a try once the main functionality is achieved. For the moment both the ingredients and Cooking instructions were completed using a textarea field with 1 ingredient per line. Here is the code in case somebody needs it: <ul class="ingredients"> <?php foreach(explode("\n", $page->recipe_ingredients) as $ingredient) { // Explode function is to get the value before Enter key $incr = $incr + 1; // Increment is used for the checkbox ?> <li> <input id="check-<?=$incr;?>" type="checkbox" name="check" value="check-<?=$incr;?>"> <label itemprop="ingredients" for="check-<?=$incr;?>"><?=$ingredient;?></label> </li> <? } ?> </ul>

@k07n Makes sense, I will update this and release a new version tomorrow. Cheers

Solved, Closed

do you have TracyDebugger installed? you probably need to walk through the code and bd() or l() some variables and such until you can see what is failing. you might want to try bd($mo->folder); bd($f); in their respective locations to see if they are failing; what is $mo->folder?

If Language Support is installed but no additional languages created then there is a PHP error: PHP Warning: Division by zero in ...\FieldtypeSelectExtOption.module:504 Probably not something that happens very often.

Dude it was so much vanilla ProcessWire that it was like plain cheating, heads up to @joshuag who had the actual idea!

It's also perfect for xml, json, [insert any datatype] .... .

Thanks for this. I have done several web forms already, but captcha could be a good idea in the Future.

Hey Kongondo, I think 3rd-party admin themes will be even easier than before. What I meant was that since Reno is kind of a core theme, it doesn't make sense to develop it separately *if* — and it's still a giant *if*— the new default theme allows you to configure a setup that is basically the same as the current Reno theme. We are deeply invested in the Reno theme here, so either the new admin will be customizable to something very similar, or I'll keep developing Reno as separate theme. I have some things I'd like to implement that UIKit will make easier, and I'm excited to dive in once Ryan has a stable base theme to work from.

Hey @renobird - I have one site that is 5 levels deep and I think it would be great. How many levels are you thinking would be too many? What do you think the issue is with too many levels? Maybe I am just not seeing what the issue would be yet? Maybe long page titles (like journal article titles) would be a problem?

Just my 2 cents, but I'd rather see just the one official admin theme that supports top and side menus. The key thing is that I'd like to have that official theme easily skinnable. I would love the options to color and style the theme with CSS while keeping all the html and php standard. The problem with some of the third party themes back in the early PW 2 days was that new features added to the default theme never made it to the third party themes. I'd also love to see the page tree in the sidebar and the other menu items (setup, modules, access) in the top menu. I am not certain, but I think now that the page tree is cached it won't be a performance issue to have it in the sidebar anymore?

also you can always rename namespace use NameSpace\App as EatMe

Always visible page tree has it's merits. But I also find it little overwhelming. When I evaluated different CMS products few years back I did found Silverstripe interesting, but remember that "always visible pagetree" was little messy. PW way is much more "zen" This is how it looks now:

just to clarify: the number of sections is variable each of those sections can choose from 1 of 3 'layouts'; and each of those sections+layouts can accept 4+ types of content. in addition there is a possibility on a page, to include a 'reusable' block, in any of the said positions. thinking about the structure of PW, it would seem that the best way to think of your sections is in fact with pages; because then your users can select a different template according to the type of content; then when they are inputting/editing that content, you could provide a select for them to choose between the three layouts. When rendering each section, you could then easily include the necessary template for that item into the main page, and the from that include file, include the specified layout, or use classes to control the layout, use an if to check which layout they selected. if it is not too complicated with the different content types, you could setup functions to render each content type, like with an include file containing all of the markup for each section.. (i'm not a super php guru, so this code may not be the most efficient...) function renderSectionArticle($item) { $out = " <div{$item->class}> {$item->some_field} </div> // etc "; return $out; } in the template $items = $page->children; foreach($items as $item) { if($item->template == 'article') echo renderSectionArticle($item); elseif($item->template == 'something') echo renderSectionSomething($item); // etc... } this would seem to solve 1, 2, and 3. As far as how intuitive this is, i think that's really just a matter of users getting used to the system, and I wouldn't bother hacking the admin; the only disadvantage might be in not seeing the page as a whole when editing each of the separate pages. I use this method a lot, meaning i have a page which is composed of various elements, each stored in a child page. As far as including that reusable block, that is something that might be best to be selected in the parent item; you could provide a page list select to choose the reusable item, and then have some way of specifying the order. You could use the import array to get that reusable section into your child pages array; then you could sort that array on a custom field, such as 'section_order' where you specify in that field the hierarchy; you could sort the pages in the admin based on that field; they wouldn't see the reusable section though in the admin, but it would appear in the right place on frontend..