Jozsef

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'm not sure but is that a mistake in the readme? The image, width, height and options all equal to $event->arguments(0) in the hook example.

Thanks a million, I know it will be a staple for me from now on.

@Robin S, thank you very much, that is such a nice gesture of you. I'll try this right away. 🙂

Dimensions are available since they are based on image presets and Drupal includes width and height attributes I believe. We can do the same in ProcessWire but the page is not even sent until all the images in the template got resized that can take minutes for a gallery page. When including links to larger image variations, even images in the links get resized before the page can load even though they are not displayed immediately and could wait until someone clicks the link.

Thanks @szabesz, I'm aware that it's possible but I don't want to pre-generate all image sizes for all images automatically. For example Drupal 7 resizes images on the fly too, based on image presets, yet the page displays and images load as they are generated. I am just hoping that it's possible to achieve something like this in template files.

I love ProcessWire and I've been using it almost exclusively for the last 8 years. One thing that has never improved though is how the page loading is blocked while waiting for ALL images to be resized in the frontend. This is ok for a basic page with a single hero image and another 2-3 in the content but is seriously problematic for gallery pages or sites with loads of images. First page load can be incredibly long, or potentially time out. Would it not be much more user friendly if the page would display and images would appear when they are available in the requested size? I came from Drupal 7 where this was the normal behaviour, it was a shock with ProcessWire and unfortunately this is still the case. Is there a technical reason why it MUST be like this? While ideally this would be a feature in the core, what workaround do you all use to display the html/css/javascript while images are getting resized? Is there a module I've missed before?

Hi there, I can't wrap my head around this one, can someone help me with sorting this multi value field? Pages created by PageTable are hidden so they don't mix with "real" pages in the admin. I get the page content with $page->getUnformatted("field") and the use a foreach loop to display the content. It used to work just fine but on the last two websites the pages are all mixed up. Using the selector sort=sort displays them in the order they are listed in the admin, not in order they are listed in the PageTable field. I don't know how to access the "internal" sorting as per screenshot. Again, it used to work just fine, i don't know what has changed. Does anyone have any idea how to get the front end follow the order of the PageTable field content?

I'm having trouble displaying a pagetable field in the same order as it appears on the page edit screen. The child pages are hidden so I use $page->getUnformatted("field") to get the array of pages but a foreach loop outputs them in completely random order. When I try sort("sort") it then appears in the order of the child pages in the page tree so that "sort" refers to the order from the Pages table. I never had trouble with this in earlier versions, this random order appeared in the last two websites I'm developing. Is there a way to access the internal sort of the actual pagetable field as per screenshot?

I see, thanks. I'm looking for something to be used with ProMailer the client already uses to email users based on criteria.

@bernhard, thanks for the suggestion, I was also looking for a low cost (possible free) alternative to SMTP for the client who very occasionally need to send larger campagins (around 8k). MailerSend's free tier does seem to be very good. Thanks for sharing your module too, however since it does not extend WireMail, RockMailerSend can only be used for custom solutions. There's no way to send all transactional emails from Processwire via MailerSend using your solution, correct?

Thanks Bernhard, I'll try it in my next project. I did the exact same thing in most past projects, a headline text field in the format of *Bold Text* in the headline. As wbmnfktr I used the core markdown textformatter but in the template file I had to strip all tags apart from <em>. It was necessary because the core formatter adds paragraph tags around the headline that doesn't play well inside heading tags. Another negative about this approach is that I can't use front end editing. Your readme doesn't say anything about usage, does that mean I can just simply output the text field as $page->headline ? Or even $page->edit("headline")?

Thanks everyone, a lot of learning to do, I'll look into the suggestions. I've never used UIKit but Sortable looks the bill. Updating data would be the real challenge with my skills. @bernhard, such a module would be awesome. ?

Hi everyone. My clients wants me to build a CRM app connected to their existing client site so they have all data in one place. One of their requirements is to have a drag and drop kanban board interface to update their sales status. Does anyone have any recommendation for an existing JS or jQuery library that could be integrated into the PW backend and could update data in real time? Have you done anything like this before? Or does PW have built-in tools for this? I know you can update page parents by drag and drop but can that be reused somewhere else? I'm sorry for the lame question, I'm not very fluent in JS.

I'm in a similar situation where the client asked me to integrate their sales into the existing client facing site since half of the data is already there. Silly question but would it be bad practice to store data as pages? I mean ProcessWire can do all the content types, fields and page references already, would it still be better to store data in the database directly?