Leaderboard

Hi guys / gals. Rimaa deals with logistics and moving products around. They needed an interface for their clients to check the status on their orders and that's where I came in. Not much you can see just by visiting the site, because this is actually a private mobile oriented web-app. But see some screenshots below. This project features some cool things under the hood: First, the content is managed from a Google Spreadsheet. PW connects to the spreadsheet on an interval (that can be configured), parses the sheet and updates the orders list. So the various people that share that spreadsheet and keep it updated for internal control, are also maintaining this platform without even knowing it. PW users templates was modified to allow for this platform's different roles: Client : only sees his orders Agent : has a set of clients he can overview Super-agent : sees all clients Updated orders visual cue: Comparing the current version of an order (by $page->modified) with last viewed version's date (stored in an repeater on each client), the app turns on a visual cue that the order has been updated since it was last seen. Viewing an order is an accordion-style CSS toggle, so at that point an Ajax call tells PW to update the last version viewed by the current user. All in all, a very little project that once more shows the flexibility we get from this awesome API. Being able to modify users to have the fields we need to get something like this working is a beautiful thing.

This is a tricky one, and the solution on the CMS side depends on how you want to do the frontend. You will not find a module that gets interactive 3d working on your frontend. PW modules mostly offer you ways of storing and retrieving info, but don't actually generate frontend widgets like slideshows and that kind of thing. First of all, the repeater is a go to module that you'll probably need somewhere along the road. Then just remember you can use file fields for storing 3d models or even JS that you load dynamically on the frontend, image fields for textures, and you have other field types for just about anything you can think of. For example, look at the nib selector on step 3 of your example. You can use a repeater to store each nib. Inside each repeater item you put in a title, an image file for the thumbnail, and a file field for the 3d model in whatever format you're going to use. Then you just have to figure out how to output that in your frontend so that the nib options can be managed from the CMS. Start by getting your frontend working statically. From there you'll see how to divide it into smaller chunks that can be served by PW and take it from there.

Hello Andreas_D and welcome to PW community Is this http://github.hubspot.com/pace/docs/welcome/ what you're looking for?

TracyDebugger's "production" mode has the option to email for various error types. https://processwire.com/blog/posts/introducing-tracy-debugger/#production-mode-error-logging-and-email-notification

Here's the solution I've found: disabling tags on the image field sorted all problems. Tags were enabled for that image field but not used.When I disabled tags, everything came back to normal and the site shred off all excess processing time. First byte time is 1s or less now. @ryan, is it a bug or there's an explanation for this behaviour? Enabling tags brings back the slowness again. All of that is happening on A2 reseller hosting (shared hosting with LiteSpeed, PHP 7.1 running as lsphp process) while speeds were satisfactory on my small VPS (2 cores, 2Gb RAM, Apache + PHP 5.4).

Dynamic Selects version 005 (released (16/07/2017)) Glad to announce that the latest release of Dynamic Selects is now available for Download/Purchase. Changelog Dynamic Selects is now fully multi-lingual! Thanks @eelkenet for reminder . Relevant fields and labels now shown in user's language if available, with fallback on default if not. Screenshots Backend Dynamic Selects Fields Demo Backend Dynamic Selects Page Edit Frontend Dynamic Selects

GitHub: https://github.com/Toutouwai/TemplatesChildPages For any page, allows the restricting of templates that may be used for child pages. Usage Install the TemplatesChildPages module. The module adds an AsmSelect inputfield "Template restrictions for children" on the Children tab of Page Edit. Use the inputfield to select from existing templates and any child pages added subsequently will be limited to those selected templates. Note that any template restrictions added via this module are in addition to any "Family" restrictions set for the child and parent templates. In other words, if template Family restrictions prevent a template being selected for a given page you can't override this simply by including the template in the parent's "Template restrictions for children" field. Why use this module? The module allows you to add child page template restrictions without having to create new or duplicate templates for the parent page. This forum post explains the situation well. Similarly, it makes it possible to use the "Add New" page feature without an unnecessary proliferation of templates. If you specify a single template as restriction for child pages you can add a Page Add Bookmark for that parent page that allows site editors to easily add a new page using the right template for the location.

The value of each Roles checkbox is the ID of the role, so you must use ID(s) in your "show if" condition. Then the field with the show-if dependency will save as expected.

+1 Displaying a changelog before upgrading a module or even the core is badly needed. Also the changelog should be visible everytime on a module detail page.

How can I find such a hook? I don't have much experience with them yet. Very nice idea regarding weekly emails! Wow nice module, didn't see this one before. I will check it out for sure. Thank you!

Hey PWaddict, yes that's it . Thanks for the quick reply and for the nice welcome!

You can get the total number of pages found by a selector with a limit applied by using getTotal()

No PW plugin there...but some frontendstuff that could may be usefull: http://www.ajax-zoom.com/index.php?cid=examples&lang=en https://codecanyon.net/item/expo360-360-product-viewer/2531771?s_rank=7 I doubt that there we be an opensource solution for such a complex ajax thingi that is mostly used in $hops there will be money to pay... Best regards mr-fan

Is this commit https://github.com/processwire/processwire/commit/faf1efc0495704c21b373dd424ce57df45605970 related to this?

If I understand your setup correctly you could do one field for each language then? Modified de ... Timestamp Modified en ... Timestamp You could populate all fields on save and then just sort on the appropriate field ('..., sort=modified_' . $lang)

You can check all the time formats for strftime here.

Thank you teppo!. Now the app is fully working with the latest news

Here is the solution: <?php $oldtime = strftime("%X", $page->getUnformatted("tour_date")); echo $newtime = substr($oldtime, 0, strpos($oldtime, ':', strpos($oldtime, ':')+1)) . " " . strftime("%p", $page->getUnformatted("tour_date")); ?> Now I'm getting the time formats based on each locale without the seconds: Locale en_US.utf8 = 12:00 AMLocale es_ES.utf8 = 00:00Locale el_GR.utf8 = 12:00 πμ If you know a better method please feel free to share it!

There could be a lot of people using the module version for image tags; I will revise the module code to check the core version or the is_dir and then load from core – it does seem that your tweaks are going to be essential for this, as that behavior of it submitting is definitely a problem, that i hadn't noticed (i always assumed that users would click and select, but now i see that they can type stuff in and try and hit enter..) Another issue is that there is the other module that uses selectize, namely the InputFieldSelectize (and the multiple version) which are page reference fields, and those also load the selectize library. I'm pretty sure there are at least a handful of people actively using that fieldtype, so maybe I will also need to use your modified version of the seletize library in the JquerySelectize base module, so that the selectize family of modules will all behave the same way, whether the library is loaded from the core or from the module, and in situations where someone is using InputfieldSelectize, but not image tags. if the core version of the library could include the skins, and in addition, your modified skin, then the module version could allow skin to be chosen (if it is installed), but if not installed, then the core version uses the default skin. In the module config for the JquerySelectize, besides offering the option of changing the skin (existing and new PW admin theme neutral version), that could be a place to specify which selectize library to load (core or module), to allow users with an existing setup to gracefully test and transition to the core version. Once they have tested their setup using the core version as specified in the module's config, they could choose to keep the module installed (for the extended skin options) or uninstall it and use the default skin.

hi alyxgd and welcome to the forum besides all the links you already got i would recommend you proceed like this: backup your existing site bring a copy of your existing site to your local computer do your changes on your local computer create a copy of your website on your web-server (eg on a subdomain: new.yoursite.com) bring your local copy to your live server and test if everything works if everything works, overwrite your old site with the new one caution: all data that is created between downloading the website and uploading it again will get lost. so if you have something like a guestbook or any other user generated content that could maybe get lost or you would have to deactivate your site for that time. if you only have a simple site (like it sounds from your description) that will not be an issue. people here are always really quick with answering questions so i'm sure you will always find a helping hand. if you want to save time and only focus on point 3 i'm sure you'll find someone here that can help you and has all the other points done in under 2 hours... good luck and i hope you enjoy processwire...

Welcom @AlyxGD! I recommend starting with these, in this order: https://processwire.com/docs/tutorials/but-what-if-i-dont-know-how-to-code/ http://www.how-to-build-websites.com/ https://processwire.com/docs/tutorials/hello-worlds/ https://www.youtube.com/watch?v=-3Fwyd5Okrg&list=PLXlVJXqzkgyqQJyxkb4hai3WgoPoD8osO&index=1 https://processwire.com/docs/tutorials/installation-moving-and-troubleshooting/ If after checking these above you still feel like diving into web development, I recommend installing ProcessWire on your own machine to play with it a little bit to get the hang of it. If you don't feel like dealing with all you've seen above, I recommend looking for a ProcessWire web developer: https://processwire.com/talk/forum/22-jobs/

$coaches = $pages->get("/coaches/")->children($selector);

In addition to all the above. @Sipho If you want to make sure hidden pages never show up accidentally (say they have a template, guest access, and someone happens to know/figure out its URL) then you can turn hidden into password protected with @adrian's great PageProtector module easily: Another tip when dealing with related data: you might want to take a look at @Robin S's cool module: Hope this helps too.

I'm working on a PW 3.x version of the module in this branch: https://github.com/gRegorLove/ProcessWire-Webmention/tree/master-pw3. It's in beta currently; it should generally work, but if you run into any problems, let me know. Also, I realized it was not obvious that the webmention endpoint requires a template file in order for this plugin to work. Otherwise the endpoint would return 404 to any requests. I've added a sample template file here and info in the README: https://github.com/gRegorLove/ProcessWire-Webmention/blob/master/Webmention/extras/site/templates/webmention-endpoint.php I hope to release 1.1.4 soon along with an official PW3 version.

Can't we use upgrade() function inside modules to achieve this? It's not as eloquent as having the changelog available before downloading new version, but developers can use it to display certain info, and request confirmation during/abort if possible. Something like this: <?php namespace ProcessWire; class MyModule extends Module { // ... // (module implementation) // ... public function upgrade($from, $to) { // TODO: remove after v2.0 // upgrading to v2.0, show warning about breaking changes if(strpos($from, '1.') === 0 && strpos($to, '2.') === 0) { $this->warning("New version includes <strong>breaking</strong> changes. See module info page for details.", Notice::allowMarkup); // create some info page, display compiled output of README.md // not sure how to display info on Process pages if (!$accepted) { throw new WireException('Cannot install without confirmation'); } } return $to; } }

Version 1.1.3 is out: http://modules.processwire.com/modules/webmention/ Fixed fatal error on install (thanks @Jason Huck!) Improved validation of source, target, and vouch parameters Enabled sending webmentions to links that have been removed from a post Added hookable methods for image caching Fixed handling of HTTP 410 Gone responses This works on version 2.6, 2.7, and 2.8. It does not work on on 3.x yet. I'll make a branch with a 3.x compatible version soon, though. As usual, if you're using this plugin I'd love to hear from you. Feel free to send webmentions to this post: https://gregorlove.com/2017/03/webmention-for-processwire-update/

I'd rather like to see the reference to the map being removed from the css file. Sass maps are there for development, but not for production usage.

Feature request: Would it be possible to define an aspect ration (16:9, 4:3, …) instead of using px values? I have a case where I want to output different resolutions for retina/desktop/mobile/… and want to avoid a loss of resolution due to cropping (putting high px doesn't make sense either because not always the client has high resolution images at hand…)

If you wanted all grandchildren, and nothing deeper, you could do this: $page->find("parent=$page->children"); If you wanted grandchildren and anything deeper, you could do this: $page->find("parent!=$page"); If you wanted children, grandchildren and anything deeper, you could do this: $page->find('');