Leaderboard

This week we’ll take a brief look at a powerful new ProFields module for ProcessWire that’s just around the corner—the Combo field: https://processwire.com/blog/posts/about-the-new-processwire-profields-combo-field/

Thanks for the new module @ryan, it sounds great! Could you say something about any potential downsides to this way of storing field data? E.g. situations where it wouldn't be optimal to use it. Or to put the question another way: why isn't all field data for every template stored this way by default in PW?

Basically, you are doing something like this: <?php namespace ProcessWire; $someVariable->isLoggedin(); // BUT the value of $someVariable is a string, e.g. "some_string" // IT NEEDS to be an object of type User Hence, you get an error since a string cannot have properties or methods (functions). It would have been better to see your code ( your custom login/register system. ) but even without that, what you need to do is to check if $someVariable is an object of type User before calling isLoggedin() on it.

@flydev ?? ? The home page has no caching. It's pure HTML & CSS including the gallery slider above the footer. CSS is such a powerful beast and HTML now has image lazy loading. The images in the slider, subsets of party packs, list of suburbs & featured customer love change on every page load which is a testament to the power & speed of PW

Sorry, it appear that I was not seeing that the browser was still loading assets (got some connection issues this afternoon). Just checked now and the site is loading fast, with scrollbars ?‍♂️?

As we often use Matomo (former known as Piwik) instead of Google Analytics we wanted to embed Matomo not only in the template code but also via the ProcessWire backend. That's why I developed a tiny module for the implementation. The module provides the possibility to connect to an existing Matomo installation with the classical site tracking and also via the Matomo Tag Manager. If you have also PrivacyWire installed, you can tell MatomoWire to only load the script, if the user has accepted cookies via PrivacyWire. To offer an Opt-Out solution you can choose between the simple Opt-Out iFrame, delivered by your Matomo installation, or a button to choose cookies via PrivacyWire. You'll find the module both in the module directory and via github: ProcessWire Module Directory MatomoWire @ GitHub MatomoWire @ Packagist ->installable via composer require blauequelle/matomowire I'm looking forward to hear your feedback!

Announcing the current status, planned release, roadmap and preview of Padloper 2. Status Feature freeze. Full multilingual support. Only PHP 7.2+ supported. Support for ProcessWire 3.0 only. Backend support for modern browsers only (that support JavaScript ES6 modules). Current Work Finish work on admin/backend. Work on installer and uninstaller (including configurable availability of some features). Work on UI/UX improvements. Start work on documentation with special focus on technical documentation. Continue work on Padloper API and data/model component. Roadmap Please note that these ARE NOT hard and fast targets. The roadmap may have to be adjusted to accommodate technical and non-technical constraints. Q1 2021 Inbuilt support for (latest) PayPal (full rewrite, no external modules required). Additional work on Padloper API. Invite a limited number of early alpha testers (fully-priced product). Soft and closed release of Padloper 2. Q2 2021 Start work on relaunch of Padloper website. Inbuilt support for Stripe (no external modules required). Future Plans Support for more Payment Gateways. Support for order, customers, etc imports and exports. Support for AdminThemeReno and AdminThemeDefault. Separate fully-featured frontend shop module. Consider support for multiple currencies. FAQ 1. Have you abandoned this project? No. 2. When will Padloper 2 be released? First early alpha release is scheduled for Q1 2021. This target may change depending on circumstances! Access will be by invite only for this first release. 3. What is the pricing model of Padloper 2? Three licences: Single Site, Developer and Agency licences (12 months’ updates and VIP support). 4. How much will Padloper 2 Cost? No price has been set yet. It will cost more than Padloper 1. 5. Can we upgrade from Padloper 1? No. 6. Will existing users of Padloper 1 get a discount for Padloper 2? No, this will not be possible. Apologies for the earlier announcement. It was unrealistic and unworkable. 7. Can we pay for Padloper 2 in advance? No. 8. Does Padloper 2 render markup/templates in the frontend? No. Access to all data you need to build your shop’s frontend is via the Padloper API. 9. Can we keep sending you ‘Are we there yet’ messages? No, please. Preview Here is a video preview of the current state of the backend/admin of Padloper 2. Please note the following: This is early alpha. There are bugs! It even includes WIP/notes!! FOUC, misaligned things, etc. The video shows the near-raw implementation of Vuetify UI. The UI/UX improvements work is yet to start. What you see here is the development version. Some of the incomplete features may not be available in the early releases. Most of the features you see will be optional to install.

Yes, I remember that there were some core updates has to be made between PHP 7.2 - 7.4.This must have been somewhere at PW version 3.0.98 ? or 3.0.128 ?, don't remember exactly, but the PW core 2.7 does not have these changes! Why do you not want to upgrade to PW 3? From PW 2.7 to PW 3 is to 97.5 % just switching the wire folder! And another question in this regard: are you sure that your site profile code is PHP 7.4 ready? ?

Thanks @kongondo It worked, I had to do the changes three times.

Definitely excited by this - seems like potentially some huge performance gains depending on how you are querying and rendering the field data. Just wondering how far one might take this - I can imagine sometimes using it for all fields on certain templates. There are a few times I have used a Profields Table field but limited it to just one row so that I have a simpler way to query those subfields directly with SQL, especially when I want to summarize numeric data across many pages. Anyway, thank you very much for this!

Thanks @flydev ?? and I'll check what's happening in Safari (the new IE ?) Edit: Scroll bar works on my MAC with Safari 14.0.1 so not sure why it's not working for you

This could be someone who probably develops PHP apps using Laravel and has probably never even used ProcessWire. I'd expect something similar from a developer whose tool of choice is WP ?. So, unless they show you some benchmarks, I wouldn't necessarily believe it. Having said that, I don't know if ProcessWire is faster than Laravel or not. About stability, ProcessWire is very stable and reliable, although I am not sure what definition of stable we are using here. This really depends on your needs. I don't understand what you mean by 'wanting to setup a directory'. Both ProcessWire and Laravel have their strengths depending on the type of application or website you want to build. Laravel is a fine piece of kit just like ProcessWire is, however, the entry levels differ as well as their out-of-the-box experiences. The fact that you went to Fiverr tells me that you want somebody else to build the 'directory' for you? In that case, ask yourself questions such as long term support: which system (community) will serve you better in this case? E.g., if your developer 'vanished', will you still be able to use the system, get the support needed? What about scalability? Are we talking hundreds, thousands, millions of records/pages? There are many other questions but rather than throw the kitchen sink at this, maybe tell us a bit more about your 'directory' ?. Just my 2p.

Looks like you bumped into a Laravel coder who does not know Processwire. Why don't you first ask for guidance in the forum ? What do you mean by: I want to setup a directory ?

@psy cool website, on Safari 14.0.1 I can't get the scrollbar, didn't checked other browsers - just letting you know ?

Hi @panx, Apologies for the issue you are facing. @toni's issue was resolved by following steps similar to what you tried above. It was caused by the ProcessWire tags issue discussed here and reported here. I have now set up a troubleshooting guide (WIP) in the documentation to help with this. Please try that first and let me know if your issue is still unresolved. Thanks.

Modern PHP Cheat Sheet A to-the-point summary of all awesome PHP features https://front-line-php.com/cheat-sheet

I haven't used the DataSet XML import for a while. Let me know if it needs some polishing.

Thanks for reporting this. Probably a core compatibility issue. Fixed now. Pull the updated module from github or delete from your site/modules and reinstall it.

Yes, Yes and ?‍♂️ It should be a good task candidate for the following. ? Give a try to the modules developed by @mtwebit DataSet and Tasker Configure it and let the thing running the night or a good nap. A preview :