pwFoo

I thought about different cms/f and headless cms (for example directus, cockpit). Processwire can be used as headless cms out of the box (response with json) or with a rest api module. Directus / cockpit looks great, but it would be so much easier to use processwire with custom code / modules to add some server side features I think? Will PW as headless cms bloated by template system and some more non-headless features? Maybe best would be a rest api module with a process module? Would that skip some not needed core parts like template parser? Will that reduce overhead or maybe there isn't really overhead by not needed core features?

Nice to see a push notification module, but I would love a universal webpush api module for that case? Browser dependent push notifications working with edge, firefox, chrome (for android) without forced to use one push service. Just let the browser decide.

Hi, module isn't maintained or tested anymore. I love PW, but at the moment I don't need / use it. Because of missing time I stopped web development / fun tasks some time ago...

It isn't really difficult to setup with php and javascript. Working example: https://webpushdemo.azurewebsites.net/ Custom server php lib for testing: https://github.com/web-push-libs/web-push-php I tried to build it with php and js, which works. But the js part isn't a library for simple use... I tested it some time ago, but the code should work... https://notify.it-dengler.de/index.php Just subscribe / enable notifications and wait 5 seconds (configured delay). It also works if you disable and enable notifications and close the browser during delay. You will get a notification and click opens a new tab.

Hi, gallery, forum and push notifications would be great, but it's to expensive for a small non commercial site for few users.

Hi, I'm searching for a forum software works fine with mobile (responsive) handle attachments (files, images, image albums or slideshows would be great) web push notifications Can anyone recommend a forum software for that use cases?

Yes! 👍 I would love to see such a DB class standalone for small not PW projects! Best ever! In the last time I found some nice frameworks like Flight PHP micro-framework (router, hooks, extendable, views, ...) or db frameworks Medoo, Propel3 and lessql.

@WillyC Haven't checked it... Assumed it because of much work to implement sqlite. So it sounds like compatibility and testing part because pdo sqlite would be possible? PW db / selectors are awesome and complex. So I' think it isn't an easy part with very low priority...

SQLite would be nice, but not really needed. If possible and changes to database abstraction is needed a move to PDO would make it possible. At the moment it would be interesting because of a small private php project which should run on cheap webhostings without extra features. So sqlite would reduce the requirements *g* With a small private projects I would try to keep hosting cost low... But web hostings with mysql isn't expensive today...

Hi, I would use Service worker for additional tasks like push notifications. Instead of build another service worker module it would be great to add (custom) code to the existing service worker?

Nice module, but I would prefer push notifications dependent on used browser only instead of an additional push provider. It works with that demo cross browser (with system-worker web push api support). https://webpushdemo.azurewebsites.net/

Hi @stikki, thanks for take a look into it. Additional / instead of GUI field selection I use a array to filter the fields to convert / output. At the moment I have some other topics and can't work & play with PW. My code seems to work for my needs and I like the multidimensional filter array to filter sub-pages and wirearray / pagearray / image fields too. So if you could implement it a nice and easy way it would be fine. I like to have one module for one job and not some similar modules 😉

UPDATE I can't test self signed certificate to work because WireHttp don't respect given connection port? The following url: https://127.0.0.1:10000/api/... Will return that error message: 2: fsockopen(): unable to connect to ssl://127.0.0.1:443 (Operation timed out), 110: Operation timed out Looks like port 10000 is changed to default https port 443 by WireHttp? php curl is installed and also tried to force it with option 'use' (if it falls back to another method). Need it solved or drop WireHttp for that use ☹️

I won't enable UrlSegments for each template, but have a autoload module with should react based on path / urlSegments. Don't like the way to do it with query string. So allow one urlSegment by name (string) would be nice without the need to activate urlSegments at all.

How to enable urlSegments runtime instead of persistent in template settings? And where to be loaded before the current page returns a 404 error? https://processwire.com/docs/front-end/how-to-use-url-segments/#how-do-you-enable-url-segments