Leaderboard

The latest post includes coverage of weekly updates to the ProcessWire core, as well as a look at how to create your own custom utility hook functions… https://processwire.com/blog/posts/pw-3.0.28/

Hi MichaPau and welcome to the forums. To change the password requirements go here: /setup/field/edit?id=3 You can access this via Setup > Fields, then under Filters, select built in fields and then edit the pass field. If you are running a recent version of PW 3 or 2.8 you will see these options: Back to your more general question, the ProcessWire Info panel of TracyDebugger (http://modules.processwire.com/modules/tracy-debugger/) will tell you the "Process" of the current page - see the "Process: ProcessUser" entry on the sixth row. That tells you that the User editing page is using the ProcessUser.module at /wire/modules/Process/ProcessUser/ProcessUser.module

Another option is to tar the files locally and extract them on your server. Tar will respect your permissions.

Thanks for the suggestion. Done!

Dynamic Selects Released 27 July 2016 Dynamic Selects is a commercial module that enables the creation of dynamically related/dependent ajax-driven chained dropdown lists (aka cascading selects) for display and storage of multiple types of data. The module can be used both in the front- (display only) and backend (display and storage of data). Setting up Dynamic Selects is very easy. With minimal effort, site developers can set up simple or complex chained selects. By making a selection in a trigger dropdown, via ajax, values are fetched and dynamically populate options in the dependent select. In turn, making a selection in the now populated select triggers the same action further down in a dependent select. The module only uses/stores ID references to selected options in the selects meaning the most current/up-to-date data will always be displayed in the selects. Currently only ProcessWire managed data are supported. If there is enough demand, we may incorporate external data sources (typically JSON). The module consists of 4 modules ProcessDynamicSelects MarkupDynamicSelects FieldtypeDynamicSelects InputfieldDynamicSelects Video Demo: https://youtu.be/wkhx8xQ5ue4 Documentation: http://dynamicselects.kongondo.com/ Shop: https://processwireshop.pw/plugins/dynamic-selects/ Requires: ProcessWire 2.5 or newer and jQuery if using the frontend module (MarkupDynamicSelects) Features Easily create powerful ajax-driven cascading/chained selects/dropdowns Unlimited number of select dropdowns per field Data-mapping made easy thanks to multiple possible combinations of data relationships, triggers and sources Mutlipe data relationships to chose from ID-based data referencing ensures your data values always stay fresh Remote and local caching to speed up data access and reduce ajax-requests to server User-friendly, intuitive and easy to set up IMPORTANT Before using this module in the frontend, you will need to thoroughly read the security section in the documentation.

@Torsten - welcome to the forums. Firstly, PW no longer uses TinyMCE by default - it now uses CKEditor. Here is a post on how to set up RTL for CkEditor: Hope that helps.

Hi everyone, very sorry for the delays - as you may know, I've been too busy of late to attend to Jumplinks 2. I'm making time as a go along, and would like to briefly discuss the current work taking place. I may or may not have mentioned that I'd like the new Jumplinks to be powered by FastRoute. This improves processing time by quite a bit (haven't measured, but there is far less preg_* going on) and makes development somewhat easier. By using it, however, the syntax for each jumplink would change; but I believe this to be a good thing. As you well know, Jumplinks currently uses the {name:type} base syntax, where type is optional (this invokes smart wildcards). By moving to FastRoute, the base syntax would change to {name} only, which catches [^/]+ by default. That regex is typically used in an MVC framework context, and so may not be completely suitable for the purposes of this module - as such, I am sure this can be changed by overriding the RouteParser (we can default to what is currently used for the segment any type: [\w_-]+[\w.-_%\=\]+). Then, the concept of smart wildcards would disappear, and you would be able to specify your own expressions instead - this is done in the format {name:<exp>}, where <exp> is the expression you would normally use inside of a regex capture group, such as [a-z0-9]+. However, we could add support for aliasing expressions so that the module behaves the same way as it currently does, by silently converting the aliases to their respective expressions, but also allowing more complex expressions to be used. (Note that I chose FastRoute as its syntax closely matches the current Jumplinks syntax, and allows for greater flexibility.) Before Jumplinks 2 is launched, the current dev branch (which will then be moved to master) will be updated to include a JSON/CSV exporter to the Jumplinks 2 format. As an example, the exporter will automatically convert {page:segment} to {page:[\w_-]+}. However, if we choose to use the wildcard type aliasing (discussed above), then this exporter need only export the data on an as-is basis. Note: Due to Jumplinks 2 development, all new features requested by the community will not be added to v1, but will be implemented in v2 instead. It will, however, be easy to migrate from v1 to v2 in order to use those features. I also plan on making v2 compatible with only ProcessWire 2.8 and 3.0, and Mapping Collections will still be supported. I'm writing about this now so that we can discuss it - I'd appreciate your thoughts on the change, which I think is beneficial to the module going forward. (I hope everyone is doing well - haven't been around often enough to see new modules and some of the new progress on PW3; but getting there slowly.) Update: I forgot to mention that FastRoute also allows for optional segments which allows us to jump from, say, /page.php?parent={parent}[&child={child}] to either, say, /{parent}/{child}/ or /{parent}/, depending on the input. Sure, I don't see a wide variety of use-cases for this feature, but I'm sure it'll come in handy to some.

This is my most ambitious PW site yet: http://vroom.pt It's an auto ad portal specially designed towards professional dealers. Some highlights you can't really see just browsing the website: Custom CMS for dealers (screenshot); Auto generated, customizable website for each dealer (examples here and here); The dealer can choose between a dark or light theme, then set a tone color; More themes will be added in the future with completely different designs. Optimized search algorithm to keep speed reasonable even when searching through thousands of results.

"Exec" is disabled on my hosting, but I found a way to run shell commands through control panel. Thanks for your suggestion! It saved about an hour for me.

you can just place like a fixperms.php (with the below code) file in the root and load it (then delete it): <?php exec ("find /home/user/public_html/ -type d -exec chmod 0755 {} +"); exec ("find /home/user/public_html/ -type f -exec chmod 0644 {} +"); replace the path with the root of which folders you need to fix. our main host switched like 30 sites to a different machine and the perms were completely messed up after the migration.

AdminOnSteroids Various admin tweaks to enhance ProcessWire admin. http://modules.processwire.com/modules/admin-on-steroids/ https://github.com/rolandtoth/AdminOnSteroids

This module allows the default admin - and other users you specify - to login as any other user as defined in the module config. This could be useful for reproducing errors your users can see on websites or during testing, but I would suggest it is used wisely as there are some obvious snooping abilities in using this. Once installed, you can configure the module to be usable by various members of staff other than the default admin account, as well as define which roles or individual users you will be able to login as. After saving the config settings, you will find a page under the Setup menu in the admin called "Switch User". Selecting a user from the list checks via AJAX whether the user has admin access (this is a basic check for the page-edit permission as by default the admin homepage requires page-edit to load the page tree) and will either allow you to redirect to the homepage or back to the admin depending on that check. Download Here Version History 0.0.6 - Initial release

Hello, I made this clone of the Ghost Blog System (http://ghost.org) for demo of the Wire Render Pattern as well as a multi language site and menu system. https://github.com/NinjasCL/pw-ghost As always MIT licence.

I came across this section again recently and thought I would share. It's geared a little more towards Microsoft stuff but there will be something for everyone here. Enjoy https://www.syncfusion.com/resources/techportal/ebooks

Let's jump right into Stack Overflows new Documentations http://stackoverflow.com/documentation/processwire/commit to spread ProcessWire

The settings for the CKEditor field are viewable in the page source of Edit Page: You could inspect the source to see where any other references to "mystyles" might be coming from.

Hello Adrian, thank you, the BiDi addon works well. I also modified file /wire/templates_admin/default.php: <html lang="<?php echo __('en', __FILE__); // HTML tag lang attribute /* this intentionally on a separate line */ ?>" dir="<?php echo __('ltr'); // HTML tag text direction ltr or rtl /* this intentionally on a separate line */ ?>"> Now i can set text direction in the file translation. Users with arabic language will get RTL support in the admin page too. Perhaps this could be PW standard. Regards Torsten

There's currently only a single type of Inputfield / Fieldtype that does support the pagination feature and that's InputfieldTable (since about a week). But the support for it is in the latest pw version, if you'd like to go for it.

Ah yes, sorry I didn't think to mention that - I think typically it's not something most users will want on the back-end, which is why it's only on the front-end by default.

Hi Adrian, thx a lot for your answer. That works. TracyDebugger is definitely very useful! (I just had to figure out that I have to enable it for the backend...)

Hey, this is something you can do, but unfortunately the only way to do it is to write your own Sql for the Magento DB and some quick PHP in Processwire to loop through and save the products.

Did this problem happen suddenly or has been occurring for some time? Have you recently updated/changed something? Can you please be more specific and give some background on when this started happening?

Can you try the latest version on git? The error should be fixed with version 0.1.0. The latest version also incorporates @tpr's fix for the count() on null problem in case someone removes one of the fields from the MediaLibrary template. @Zeka: I'm still looking into script loading in the frontend question. Currently, it's expected behaviour for an uncoditional autoload module, but I'm of course looking to only have the script loaded when necessary. Might be a while though, as it means a lot of testing and delving through PW's frontend editing code until I know what I'm doing.

I don't think this is quite right. If the image you are uploading is 200px high and the minimum height for the field is 260px then PW will refuse it, regardless of what is set for max width/height. So that part is okay. The problem happens when you set a max width/height and the image you upload is larger than both the max width/height and the min width/height. What happens here is that PW resizes the image to so it is contained by the max width/height while maintaining the image aspect ratio. And depending on the aspect ratio this can result in a resized image where one dimension (width or height) is smaller than the min width/height. So in the example you give... ...PW will actually scale a 1024x768 image down to 320x240, not 320x260. PW doesn't refuse the image because it was larger than the min width/height on upload, but it doesn't check if the resized image will be smaller than the min width/height limits. Arguably this should be checked, but if if what you want is an image cropped to exact dimensions you can just leave the max width/height empty (or some large maximum to avoid overly massive files - I often set max width to 1600px) and crop to your dimensions in your API calls: $image->size(320,260)

I would use a CSS class and CSS background image for the icon, no need for an extra field.

I think this is the same as: https://github.com/ryancramerdesign/ProcessWire/issues/1944 which should now be fixed.

Use the dev branch of ImageExtra - it is supposed to be fixed there: https://github.com/justonestep/processwire-imageextra/issues/18

Now you can see a fully functional website using this profile http://ninjas.cl

$input does also have a url/httpUrl option if you're using urlSegments and you want those to be included.

I once had similar issues where the hosting provider changed permissions. Try re-uploading your original development environment or download a fresh copy. You need to upload these: /wire/ (recursive) index.php .htaccess

Not sure if this is the right place to post this, but the example of the blogprofile seems broken

In the interest of transparency, I would like to state that I made a mistake in editing @Tomasz post. I have personally apologised to him and advised him to use an appropriate board here to air such views. We hope this incident doesn't keep him away from the forums. We are a friendly bunch here but we do make mistakes sometimes. Cheers, Francis

See the docs for inputfield dependencies. and

@Manaus That's great! Here is my hooked method: public function hookInitTwig(HookEvent $event) { $twig = $event->arguments('twig'); $twig->addGlobal('hsaApp', wire('config')->hsaApp); $twig->addGlobal('hsaDist', wire('config')->hsaDist); $twig->addExtension(new \Twig_Extension_Debug()); } The only problem with what you have done is that you have amended the original module. When you update that module, you will lose your added code. If you add to a hooked method outside of the Twig module, your changes will be preserved.

Horst and I would like to announce the release of v1.0.0 of the WireQueue suite of modules. There are now drivers for textfiles, redis and SQLite and the interface has been extended to include the isEmpty(), purgeItems() and getItems() methods. Enjoy!

Here my friends at Jumpitt Labs used Processwire as the Main Framework for their website (because I recommend it to them) http://labs.jumpitt.com They are nice folks and make mobile apps and applications in Valparaíso, Chile. I didn´t make their website, I´m just post it to show it here Verification http://isit.pw/?url=http%3A%2F%2Flabs.jumpitt.com Image

Sometime after 3.0.21, PW had modifications that has messed up how PW's "Markup" field renders descriptions with HTML in them, which also affects MenuBuilder. I've created an issue on the PW Github: https://github.com/ryancramerdesign/ProcessWire/issues/1932

http://processwire.com/api/multi-language-support/multi-language-fields/#multi-language-field-values

If anyone is getting this issue with images not properly uploading in PHP5.6, make sure to set: always_populate_raw_post_data to -1 in your php.ini file. The deprecated notice is causing header issues with the ajax uploader. Hope that helps someone else out

person, do this.you can: $pages->find("template=artwork, sort=artistpage.sort");