Leaderboard

Today Kalmar County Museum released a small campaign site where people can vote for their favorite building in the city of Kalmar (Sweden). The site uses latest PW dev version and Somas excellent Pollino module. The maps are powered by Leaflet and map tiles are from Mapbox. http://kvarnholmen.kalmarlansmuseum.se/

Hi, and welcome to the forums! That isn't something ProcessWire would do, as PW leaves the design of your site to you. You more than likely have a print stylesheet somewhere that is making the links show... That's the only explanation. Edit: I've scoured your code, and it appears that you have a stylesheet containing the following: a[href]:after{content:" (" attr(href) ")"} That's the culprit. As you're using AIOM, I can't tell which file it is... Edit: It appears that Foundation is doing this (I think Bootstrap does too - or it used to.) You can override it like this: @media print { a[href]:after { content: none !important; } }

@chrizz You can set the permissions for files/folder required by your webserver in the config.php file. Most of the time, this is 644 for files and 755 for folders. Example: Some folders must be writeable for ProcessWire, therefore the system tries to change the permissions of those folders. In this case, the problem is (most likely) that your user executing the script on the webserver does not have write permission on a file/folder where ProcessWire tries to change the permissions. How did you upload the files to your staging environment? Maybe you need to set the correct permissions before uploading or correct the permissions on the server. Cheers

Update: version 0.0.8 Added an 'include_children' feature, thanks to ideas by @dazzyweb. Added sister options 'm_max_level' and 'b_max_level' that control how deep to fetch descendants if using 'include_children'. Default is 1 (i.e. only include immediate children); 2 means go up to grandchildren, etc. As part of ideas above, also added a 'current_class_level' that lets you specify how high up the ancestral tree to apply a 'current_class'. This is like an 'active parents' setting. The default setting is 1. A value of 2 means apply class to current item and its parent; 3 means apply to the item, its parent and grandparent, etc. Only applies to menus (not breadcrumbs). Added a permission 'menu-builder-include-children' in relation to above 'include_children' feature (this permission is required to set and use the feature). This is currently in the dev branch only. Please thoroughly read the updated docs about these new features (especially the first) before attempting to use them. Although covered in the docs, I would like to repeat this here: Use the 'include_children' feature with caution. You can end up unwittingly including hundreds of child pages in your menu! Currently there are no code-checks in place to prevent such a situation (difficult to impose an arbitrary figure) so we leave this to your better judgement. Also note that the setting cannot be applied to a menu item made up of your 'homepage'. If you enable the 'include_children' feature (it is off by default), your main settings, PageAutocomplete/AsmSelect and menu item advanced settings will change from this: to this: and your menu output to something like this...(from only two items in the visual Menu Builder) Please test and let me know if there are any issues. Thanks.

What version of PHP are you running ?

That's a double-edged sword, no doubt about that. By offering something for a price too low you might get kicked from the race altogether (based on the argument that "you probably misunderstood the scope of the project", which might or might not be true), and on the other hand price is often a big factor, and you should aim for the lower end of the "acceptable range" if you want to impress the client. Pricing projects is hard work

Hi Andi, 1) Thanks for the links and for the useful part of the informations. 2) I (personally) allready haveused GraphicsMagick a year ago. In the above post it was said in the past (at least I tried to do so). Besides that: I have used a lot of other image processors in the past 15 years too. But I cannot see any usefullness with installing a software that only integrates image processors. If I want to evaluate the quality of image processors, I use the image processors. 3) GraphicsMagick does a (maybe very) good job, but IMHO it isn't the best tool out there. The best tool in regard of visually quality for photos is NETPBM! - if one know how to use it. 4) And sorry if I have posted in a way that not let you see what I have meant in the first place. What I have tried to do with the imagickresizer, and also have tried to say in the newer posts here, was to bring in a next step of image processing for a wide range of users. It should not only be available for those who are on their own servers. So using apt-get install... isn't an option for all that are not on their own servers. 5) Please do not assume what I have done, nor what I have done not. This is neither purposeful nor pleasing to read. My short and precious free time I like to spend rather different. Maybe with programming something (or doing other) that is useful for PW and a wide range of PW-users. 6) I'm available for paid PW modules development. I allready have built some nice custom ones in regard of image processing. Horst

Hey marcus, all, Is there anyone played with the importing / exporting of the fields and templates via json and keeping them on the module. May be we can make that a wireshell command . I was looking at continuous integration of fields and templates.

I did another quick module, which plugs something I always kinda missed in ProcessWire. It's just a raw overview over the access management from the templates. Nothing fancy, but useful. The visible roles and the visibility of system templats can be setup in the modules settings. I'll add this to the modules directory later. But for now it would be great to hear if anyone is missing anything or if someone does have a better idea how to name the module. 12.03.15: Renamed the module and fixed wrong information for superusers and inherited rights from the required guest role. GitHub: https://github.com/LostKobrakai/ProcessAccessOverview

Whoa quick response! Thanks. PHP Version 5.3.5

Version Bump to 1.1.3 Error-control for REQUEST_URI (previously threw an exception regarding it being undefined when using wireshell) No schema changes

Greetings, Yes, as Teppo said, "pricing projects is hard work"! I think this part of the project development process is a bit of an art. I'm good at designing/developing, but I'm not always great at getting the best price for my work. Lately, I've partnered with a couple of other people who are the opposite -- they are good at negotiating. I've sat in the table and watched them magically get a better price. Thanks, Matthew

It is. Sort of. https://processwire.com/talk/topic/8298-list-your-5-must-have-modules/?p=81262

You may want to eventually replace any Repeater solution you may have with a Page Table.

You could also set this with your config.php: ini_set('xdebug.max_nesting_level', 200);

Hey @mindplay.dk, I like to have a look at code, and if possible will try to contribute . Thank you. Like @joe_g mentioned, I was also having a similar thought of exporting the json via API and keeping on the module. And later exporting via the api than doing via the GUI . May be we can somehow add it to Wireshell ?

New version 0.7.1 and added the FormHelperExtra (proof of concept!) module to handle removed features.

@joe_g this is basically what the module I've been working on does - except, it writes this file for you (as flat JSON files for source-control friendliness) creating a repeatable record of every change made to templates and fields. I don't work with ProcessWire in my day job anymore, and probably won't get around to finishing this... I wonder if I should go ahead and release it as-is. Would anyone be interested in taking over this project?

with the horst's help I found out the problem is related to the watermark jpg file, when pim tries to access to the jpg, this cause the javascript to generate the error, I'm still investigating more but at this point pim is not the direct cause, just to be clear

EDIT, seems like the answer to my question is yes: https://github.com/jeanrajotte/upgradewire ----- Hi there, Slight newbie question about continuous integration: Sorry if this has been covered already - lengthy thread! Isn't it the case that if I would use the API to add/edit my fields and templates, (Everything can be done from the API, I guess?) I could script and automate any data model migration? Not using the GUI seems like a small price to pay for being able to do something similar to "migrate up" and have the server apply the latest data model changes? I could, already today, have a control file that look like something like: Current version: 2 version 1 migrate up: add field X migrate down: remove field X version 2: migrate up: rename field X to Y migrate down: rename field Y to X The import / export json thing is super awesome, but it's not for automated migration, I guess? Would this work? What do you think about it? J

Repeaters are not officially supported by inputfield dependencies.

If you like you can write me a PM in german - to clear open questions. Welcome to processwire forum - be not afraid - asking for help here.

Big update! Version 0.3.0 comes with: a new "NewCommand" provided by HariKT! Big thanks again. This contribution should lead to a better workflow with Wireshell since it opens up the possibility to install PW via command line in a convenient way A command for creating fields A command for assigning fields to existing templates A generic backup command (DB dump) Commands for en/disabling modules (downloading them via Wireshell is still on my bucket list) A little command outputting the currently installed ProcessWire version An unified approach to naming commands and classes: entity:verb, so for example user:create I dropped the "(Experimental)" from the topic's title Read more about the available new commands and their options in the readme. If you have an older version of Wireshell installed, make sure you "$ composer update" it in order to get the new dependencies. And we're on packagist now: https://packagist.org/packages/wireshell/wireshell

Thanks. Your example didn't work as-is (determining if customrole is in the array), so I did some research and came up with this (makes use of jQuery in the CSS loading part): $(function () { var customrole = 'superuser', info = config.AdminCustomFiles; function getRole(){ var arr = info.roles; for(var j = 0; j<arr.length;j++ ){ if(arr[j] == customrole){ return true; } } } if (getRole() === true) { loadCSS = function(href) { var cssLink = $("<link rel='stylesheet' type='text/css' href='"+href+"'>"); $("head").append(cssLink); }; loadCSS("/site/templates/AdminCustomFiles/piilota-kielet.css"); } else { console.log("Don't do it!"); } }); CSS for hiding all but default language: .LanguageSupport { display: none; } .LanguageSupport:nth-of-type(1) { display: block; } Edit: switched from :first-child to :nth-of-type(1) so that we can see the Name field when adding a page. Edit 3 years later: the new version changed the JSON data, so info.user.roles is now simply info.roles

This is the organization we've put in place at work. The structure is pretty much fixed now, we're still grabbing parts of things we like elsewhere. It's basically a bootstrap kit. Workflow goes at this : 1) clone latest pw and setup project with https://github.com/plauclair/pwscripts 2) clone our site profile 3) remove extra, configure grid or else from less mixins, select which layout to use and import html presets that match these 4) marvel at all the time saved 5) code 6) ?? 7) happy customers, happy devs! templates/ |-- styles/ | |-- styles.less // general styles, calls parts in inc/ | |-- styles.css // compiled from styles.less | |-- inc/ | | |-- layout-one-pager.less // standard layouts | | |-- layout-standard.less | | |-- content.less // regular h1, p, ul, etc.. | | |-- template-name.less // each template has its own less file | | |-- template-...less | | |-- vendor/ // decoupled parts from different frameworks | | |-- bootstrap/ | | |-- grid.less // decoupled grid system, generator w settings | |-- images/ // images called from css | | |-- scripts/ | |-- main.js // main js stuff for global things | |-- vendor/ | |-- vendor-name/ | |-- files... | | |— inc/ // php includes, has ready-made classes like a recursive menu generator and other helpers |-- views, controllers, classes, etc../ // depends on the project's complexity | |-- _header.php | _init.php // config->prepend |-- template-name.php // typical PW template files |-- template-...php

I do not update older installations with new releases until I want to add some of the newer features. I today run sites with PW 2.3. There is no security reason to update those.

The other tool to add to your belt is ModulesMigrator: https://processwire.com/talk/topic/8410-modules-migratorinstaller/ It will install, configure settings, and update to the latest versions all modules that you have selected. I have tagged it as alpha, but mostly because I haven't had any feedback on it. Maybe if this brings it back to life and I get some reports on it, I can get it released - it really is pretty straight-forward.

Here is my proposal. The HTML is in attachments. There are multiple ways how to install the module. Installing from directory (recommended) -------------------------------------- If the module is uploaded in the official *ProcessWire Modules/Plugins Directory* (http://modules.processwire.com), you can use this method. 1. Log in to your ProcessWire admin and go to the *Modules* page. 2. Go to the *New* tab and expand the *Add Module From Directory* section. 3. Enter the *Module Class Name* (can be found in the module's detail page, e.g. FieldtypeMapMarker). 4. Click the *Download and Install* button. Installing from URL ------------------- If the module is not in the official *ProcessWire Modules/Plugins Directory* (http://modules.processwire.com), but the module ZIP is accessible from URL, use this method. 1. Log in to your ProcessWire admin and go to the *Modules* page. 2. Go to the *New* tab and expand the *Add Module From URL* section. 3. Enter the *Module ZIP file URL* (can be found in the module's detail page, e.g. https://github.com/ryancramerdesign/FieldtypeMapMarker/archive/master.zip). 4. Click the *Download* button. 5. The downloaded modules are now listed on top of the page. Click the install button next to any of the new modules that you want to install. Installing from upload ---------------------- If the module ZIP file is not accessible from web or you have it already downloaded, you can upload the file. 1. Log in to your ProcessWire admin and go to the *Modules* page. 2. Go to the *New* tab and expand the *Add Module From Upload* section. 3. Select the *Module ZIP file*. 4. Click the *Upload* button. 5. The uploaded modules are now listed on top of the page. Click the install button next to any of the new modules that you want to install. Installing manually ------------------- If any of the above methods isn't suitable for you, you can install the module manually. 1. Place the .module file in your /site/modules/ directory. If the module contains more than one file (like supporting .css or .js files for example), it should be created in it's own directory under /site/modules/ with the same name as the module (.module file). For instance, the FieldtypeMapMarker module and supporting files should be placed in /site/modules/FieldtypeMapMarker/. 2. Log in to your ProcessWire admin and go to the *Modules* page. 3. Click the *Check for New Modules* button. 4. New modules are now listed on top of the page. Click the install button next to any of the new modules that you want to install. *Note: All third party modules should be placed in /site/modules/. You might also notice that ProcessWire keeps core modules in /wire/modules/ – You should avoid installing your modules there, as that location is reserved for core modules.* How to uninstall a module ------------------------- 1. Log in to your ProcessWire admin and go to the *Modules* page. 2. Find and click the module name that you want to uninstall. 3. Expand the *Uninstall* section, check the checkbox. 4. Click the *Submit* button. 5. It is now safe to remove the module's files from /site/modules/ if you want to. how-to-install.html

@sarah_hue Also, if you're not wanting to match partial words you don't need to do the explode/foreach. The ~= operator will match multiple whole words in any order.

Sarah, in your case, the selector ~= should work title~=$term

Woohoo! Got it. Thank you Soma. So much to learn! Solution: do as you say above and make the field Single page (Page) or empty page (NullPage) when none selected, then in the template: <p class="type"><?=$child->fields->property_category->label?>: <?=$child->property_category->title?></p> Still had to put $child->fields->property_category->label but all part of the learning process. Cheers

you mean you want to apply the "active" class only to the first item? maybe something like this <?php $active = ' active'; // set active for first item foreach($page->images as $img) { ?> <div class="item<?= $active ?>"> <img src="<?php echo $img->url; ?>" /> <div class="container"> <div class="carousel-text"> <h2><?php echo $img->description; ?></h2> </div><!-- /carousel-text --> </div><!-- /container --> </div><!-- /item --> <?php $active = ''; // remove class "active" for following items } ?> i like to use short tags <?= $var ?> instead of <?php echo $var; ?> maybe you have to change this depending on your server

What about this: $np = $pages->clone($page); $np->of(false); $np->title = 'New Page'; $np->name = 'newpage'; $np->save();

by members of the community with perfect pw-integration: https://minimize.pw/