Leaderboard

I actually think for this module the client expressed interest in us releasing it available for others to use once it's finished. I will confirm though. I used the process outlined on this page (link) to do a lot of it, though admittedly there was also a lot of stuff to figure out with some trial and error.

As far as I can see, it is set in Session.php: https://github.com/processwire/processwire/blob/master/wire/core/Session.php#L263 ... if(ini_get('session.save_handler') == 'files') { if(ini_get('session.gc_probability') == 0) { // Some debian distros replace PHP's gc without fully implementing it, // which results in broken garbage collection if the save_path is set. // As a result, we avoid setting the save_path when this is detected. } else { ini_set("session.save_path", rtrim($this->config->paths->sessions, '/')); } } @session_start(); ... So I guess it is possible to set it in config.php with $config->paths->sessions, see I tried it with absolute path and it works for me, e.g.: $config->paths->sessions = "/Users/user/MAMP/siteroot/site/assets/mysessions"; I think "/tmp" can be the system default which gets purged so that is why you have issues with it. But I'm just guessing, I'm not a Linux admin kind

This week we take a closer look at the useful new page export/import functions that we’re currently building into the core: https://processwire.com/blog/posts/a-look-at-upcoming-page-export-import-functions/

@ryan, stuff like this is super-interesting to us aspiring devs and I for one would give my right arm to take a peek at your code and see how an expert approaches these things. It would be a really great learning opportunity. In general, would your client contracts allow you to share snippets of project code with the community? Would you be comfortable doing that? (not expecting you to reveal all your secrets!) Not in any way that would require you to invest time in making things plug-and-play or offering support for them - just dropping some interesting bits as Gists on Github. A possibility?

Adds a Service Worker to your Processwire site which can be customised. The service worker script itself is heavily based on Jeremy Keith’s work – thank you Jeremy! More information: https://github.com/johannesdachsel/processwire-serviceworker

Thanks a lot for digging into that issue @szabesz. I'm going to try that new setting and will report here !

Howdy @AndySh, You purchased the pro version so you will need to post your request in that private support forum. If you do not have access, then please send Ryan a PM and he will give you access.

If you want to stay compatible with the 2.x branch I'd simply develop on a 2.8 or even 2.7 installation.

There are various 3rd party modules around, which do allow for that kind of navigation. Please consult the modules directory and/or the modules subforum.

@hellomoto This issue was fixed in late 2016 (module version 2.0.0 or 2.0.1). Please update to last version and try again. @PWaddict I pushed a fix and tested the module in 3.0.64. Please update to 2.0.8

Hi szabesz, Good idea : I read "/tmp"... So what does that mean ? Perhaps I can modify that and store them on site/assets/sessions ? The problem is, wherever it's stored today, it doesn't live long enough, and users complain (gently). The problem was "solved" with database sessions, which lived long enough, but the db was hit too much.

I've just extended FieldtypeTime and InputFieldTime by support for blank values Failed to add a push request to https://github.com/netcarver/PW-FieldtypeTime, so please find my patch attached ... Works fine at me. PW-FieldtypeTime-Empty-times.patch

I think get() always returns a single page. Have you tried $pages->find("id=1|2|3"); which will return a PageArray.

This little tipp is not especially for PW, its for all usages. There is a little class called php-store-hours which can be used to easily format opening hours. It is also possible to group days with the same hours like in schema.org markup. There are a lot of render functions available to get the markup that you want. Just take a look. Maybe it is something you are looking for. Best regards Jürgen

We've been using UserGroups for this use case for a few years now. This might be one of those unmaintained projects you were referring to, but if that's the case, it's mainly because it has been working just fine. No need to fix what isn't broken That being said, we haven't been using UserGroups with ProcessWire 3.x, so can't really say for sure how well those two work together.

If there are issues with a given module, you can always post your query/questions in the sub-forum for that module: You can also report technical issues/possible bugs with modules directly at the particular Project Page (Github) location: https://github.com/adrianbj/AdminRestrictBranch On the ProcessWIre Modules Page, for each module --- it lists the links to both the Forum Support and Project Page (Github): http://modules.processwire.com/modules/admin-restrict-branch/ I would encourage everyone to use these essential resources to let the module authors know about bugs, possible changes or any other issues with their module. Most module authors are willing to make changes to how things operate based on the comments or queries from module users.

Take care of yourself. Hopping everything gets better for you soon.

This morning, after some adjustments and tests, the module run smoothly on ProcessWire 2.7, 2.8 and 3.x.

It is only option D that forces the modal dialog editor. Option C allows inline editing - you just have to place edit tags around the individual fields in your repeater rather than around the whole repeater foreach(). For example: <?php foreach($page->my_repeater as $item): ?> <h3><edit <?= $item->id ?>.title><?= $item->title ?></edit></h3> <?php endforeach; ?> You're right that there does seem to be some sort of permissions issue for non-superusers, but rather than change access for the admin template (which non-superusers shouldn't have access to) I suggest you give edit access to your repeater template (select the "Show system templates" option to see repeater templates).

I made a few changes in my fork of the module. I added support for DateTimePicker, Recurring Events and DataTables. Here is it: https://github.com/blackberrymamba/FieldtypeEvents