Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 02/20/2023 in all areas

  1. This week we have a new core version available on the dev branch. Relative to the previous version, 3.0.212 contains 32 commits, 16 issue fixes and 3 PRs. Here's a list of what's been added: Improvements were made to InputfieldImage so that you can now add your own image actions with hooks. More details in this post and ProcessWire Weekly #455. Significant refactoring and improvements were made to the ProcessPageEditLink module. One of the most notable is that it now will retain HTML class attributes on links, even if not specifically configured with the ProcessPageEditLink module. This is useful if you've added custom classes for links in TinyMCE or CKEditor, but haven't also added them to the ProcessPageEditLink module configuration. Improvements were made to Text fields so that HTML Entity Encoder is now automatically added. This was covered in detail in last week's post and in ProcessWire Weekly #457. InputfieldEmail has been updated with optional support for IDN emails and UTF-8 local-part emails, per request. Two new $sanitizer methods have been added: htmlClass() and htmlClasses(). These sanitize HTML class attributes, and it's part of what enables us to support the custom class attribute support added in the ProcessPageEditLink updates mentioned above. Added feature request #480 to support configurable file extensions for translatable files (beyond .php, .module and .inc). Added a new uploadName() method/property to Pagefile/Pageimage objects that returns the original unsanitized filename as it was uploaded. Applies only to files uploaded since this feature was added. Be aware the filename is unsanitized so be careful with it. This was to partially answer feature request #56 and this solution was suggested by Bernhard Baumrock. Demonstrating the above, InputfieldFile now shows this original filename if you hover the file icon, and InputfieldImage shows it if you hover the current filename. HTTP requests that contain an accidental double slash in the URL now redirect rather than render the page. The PagesParents class was refactored so that it is now a lot faster in saving its data to the pages_parents table. This is very noticeable if you have a site with more than million pages when changing the parent of existing pages, especially those having children. Previously there was a [potentially very] long delay at large scale, now it is instant. More details on these updates, and additional updates can also be found in ProcessWire Weekly #455, #456 and #457. Thanks for reading and have a great weekend!
    1 point
  2. Not exactly the same scenario but an example of combining repeater items from different sources into a PageArray:
    1 point
  3. Thank you for your help. Meanwhile I have updated Processwire to 3.0.210 which fixes all problems with PHP 8.1!
    1 point
  4. I have just released the newest version 1.2.8 of AppApi. No breaking changes, but it should fix an issue that could lead to installation-errors when the used MariaDB version does not support JSON as db column type. Additionally I have included some bugfixes to the email-authentication logic.
    1 point
  5. @gebeerFor sure I remember you from those days. That's when I jumped over too. For sure I didn't make many sites (one for a soccer club and a shop) but I used PW especially at the time for a setup of touchscreens in a museum I work for. Nearly each room in that museum had a different screen layout being powered by one PW. Even though I'm not a good coder, I even managed to make streetview to look into the right direction in each of the POI's (from a setting in admin). The poi's on the left of the map are more documented but this only shows the power of PW and what it can do: https://durvenleven.be/pw/handelszaken/ In another room there was something like this: https://durvenleven.be/pw/personen/ (truly sorry that I'm out of the tread but I couldn't help it)
    1 point
  6. I've seen a lot of commits to support PHP 8+, so I'd say the core will most likely be stable. I'd be more worried about third party modules that might not have been updated recently, so if you are able to, I'd recommend you make a backup and test first in another install with the same environment.
    1 point
×
×
  • Create New...