Leaderboard

The invoices application site profile that I uploaded last week now has a companion blog post: https://processwire.com/blog/posts/invoices-site-profile/ Thanks for reading and have a great weekend!

https://www.cognition-labs.com/introducing-devin Well I guess that's it then. It was nice riding with you folks. I am out...? Oh, wait a minute. There's still hope. I just need to learn ML... ?

I'd like to introduce you to my newest employee: Devin

This week the new ProcessWire Invoices site profile has been released on GitHub here: Invoice Application Site Profile. This particular profile is much broader in scope than the others I've developed for ProcessWire, so will benefit from more descriptive information about what it includes, how to use it and modify it, and how you might build further from it. That info will all be coming next week in a new blog post. But feel free to download and install the site profile sooner if you'd like. If you are already familiar with ProcessWire, then perhaps most of it will be self explanatory. While this site profile doesn't cover everything that you might do with an invoicing application, it does cover everything that I've needed over the last year of using it with my clients. Though admittedly, I don't have a lot of clients, nor do I send a lot of invoices. Given that, when my existing invoicing service raised the monthly rate from $3/month to $20/month (a year or so ago), that's what motivated me to build this site profile. And it does everything my previous invoicing service did, and in fact does it better. While much of it was built several months ago, major improvements have been made to it over the last couple of weeks, preparing for it for release as a ProcessWire site profile. My hope is that you'll find this site profile easy to work with, and easy to build out further where needed. For instance, I imagine some may want to add in the ability to pay an invoice. It would be relatively simple to add in FormBuilder with its Stripe Processor plugin, or perhaps some other payment solution. But all my clients pay by check, whether physically or digitally, so I've not needed to add payment ability to the application yet. In any case, I hope that you find this site profile useful, and please let me know if you run into any issues with it or have suggestions for future upgrades to it. Thanks for reading and have a great weekend!

I want to limit the purchase of some 'event'-typed product to 1 per user. Currently when an event is purchased the user get's added to a pagearrayfield which in turn grants them access to some pages. How could I limit the amount of a product to be added to the cart to 1? And after they bought it, how can I prevent them from buying it again?

Nice, for a beginner it's a nice way to quickly discover PW mechanics. And probably an experimented user can also find some interesting features he doesn't already know (I already see some of them). ?

I'm using a single 4k OLED 42" C2 tv as monitor for over a year now. Using same distance as normal dual monitors I wouldn't go any larger True and 5. If you have no direct window behind you, the glossy screen is great (there are some matte monitors with 4k out there right now, but I personally would go for oled for the deep blacks, which are not that deep on matte screens.. There is also coming an oled monitor from LG with glossy). No burn-in, I do have screensavers and hide the taskbar just in case. Burn-ins really should only occur when something is there for a VERY long time. My pc is on all day long. ^ I have no problem myself I have 120hz, personally I really like that when I move windows around it's a bit smoother Autodimming can be disabled for mine (some program is needed) Small fonts not looking great when it's a particular color combination, like red on yellow. This might be different for different TV panel types. I'm usually splitting the screen in 2, but this is particular a personal preference. (It's possible to have 25%/50%/25% but the 25% would be a bit narrow for a code editor) Perhaps looking at the new (and not yet released) 4k oled monitors could be an option. If OLED is a no-go then I would still have a 42" monitor. One thing; if you are used to this, working on dual monitors is not very pleasant (especially 2x 1080p).

@horst I've added multi-language support on both signature fields and sent you a pull request.

@kongondo I just switched for the last project from MODX to Processwire and for the next bigger project a media manager is crucial. Your screencast, the ideas and conversations look very promising and I would love to buy and use the new version already. But unfortunately no progress on this for a long time. Can you surprise us?? Can I test or buy the current/old version of the media manager? Your shop seems to be in maintenance mode for a long time, if I‘m not wrong!? Thanks in advance & Cheers Sebastian

I've just had the same error and realised that if you just simply download the module and install it, it installs v1. So you have to go to Modules > New, uninstall v1 and install v2 as both versions are included in the module folder. Of course the new version only works with the pim2Load() method so you have to change that too.

I really can't tell if this is a bug or feature, to be honest. I talked about this with @ryan and he wasn't sure either back when I found this issue. And yes, that was about at least 2 years back. So... right now... this seems only to affect PW-sites that were single-language and then were migrated to multi-language support. Which is probably the case here too. I almost never stumble over this, due to my profiles I use for new projects, but YES... it could and will be... kind of a show-stopper in a setup once in a while - as we see here. But here is the "easy fix"... never use title somewhere else outside of default templates. I know it sounds weird as re-using fields is such a common task nowadays (for good), but... I learned about the years that title is more or less not a field, rather a tool to define name-based default IDs (besides the regular page ID). I see the title field as something like fkTitle (foreignKeyTitle) which I used to use in Oracle DBs back in my agency times. Way less strict and only applicable with additional selector-queries, but... it's close enough in my use-cases. In my setups I ALWAYS use headline, subline, topline and similar fields instead of title. Especially in RepeaterMatrix to create unique jumplinks. tl;dr (my definition for the title-field) Use title in your templates but never in an ongoing or extended way like using it in RepeaterMatrix Blocks or similar. It's a system field for a reason. Almost like a human-readable ID. That how I handle it.

For a basic approach: $breadcrumbs = $page->title; foreach($page->parents() as $parent) { $breadcrumbs = "<a href='{$parent->url}'>{$parent->title}</a> / " . $breadcrumbs; }