cst989

Actually when I got access to the subforum for it, the latest version from there (but not the one emailed to me when I purchased) has a module for discount codes. It is super basic though... but a good insight into how to actually set it up. I think maybe for our use at the moment, Padloper is not going to be user-friendly enough for the clients that we would hand the reigns over too. However, it is clearly a great comprehensive system that I would happily use internally or personally.

I have just purchased Padloper on the basis above, is this still correct though? I cannot see how to add a Discount Code at all.

Thank you @kongondo - even though I had already worked out what to do, it's always good to understand why you had to do it!

Max files is 1. I set it to Single Item to see if that would change anything and it did not. Before that it was set to Automatic which the description suggests should be the same anyway. I am outside a module context if that affects it, this is just a file outside the template entirely that I am calling with ajax.

Ok, I've sort of resolved this... but I'm still confused. I've seen plenty of examples where people have guessed "you've got an array of images, not a single image," however I am certain this is not the case. My image field is set to "1" image, if I upload another, it's replaced. However in my example above, I either had to iterate through with foreach($resource->image as $image) Or use echo $resource->image->first->size(310,200)->url; Can anyone explain to me why this is? It seems counter to what I understand.

I have a file I want to access with ajax: The purpose of this file is to iterate through a repeater, and get the image from each entry. The number of images in the image field is set to 1, and just for good measure, to return a single image. And my code: // site/ajax/processImage.ajax.php?group=1206 require_once($_SERVER['DOCUMENT_ROOT'].'/index.php'); $resourceGroup = (int) $_REQUEST['group']; // get the Repeater field $resources = $pages->get($resourceGroup)->resources; foreach ($resources as $resource) { echo $resource->title; // Works as expected echo $resource->image->url; // /site/assets/files/1259/ echo $resource->image; // filename.jpg echo $resource->image->description; // nothing } See comments above for what is output, why isn't URL giving me a full URL, and no description is available? If I try to access $image->size() I get the following fatal error: Error: Uncaught exception 'ProcessWire\WireException' with message 'Method Pageimages::size does not exist or is not callable in this context' in F:\sites\<sitename>\wire\core\Wire.php:519

After I installed this, I couldn't upload anything, all images failed to upload and the console output Failed to load resource: net::ERR_CONNECTION_RESET for each. After uninstalling, image uploads work again ProcessWire ver 3.0.89

I have a use case, I wouldn't say it's necessarily "good" A client asked me to link one item in a list of siblings to another site. They didn't want to scrap the content, they wanted the title and intro to remain on the listing page, they just wanted to redirect instead of going through to the detail page. That meant I couldn't just put a redirect in the template, instead I added them a new field. An easy fix of course, I just couldn't figure out at first why jumplinks wasn't working for my purpose til I saw a post further up this page. Now, as I've just seen your roadmap, I will happily rescind my request anyway as I see you've got a long list of plans already!

A user is getting these errors all the time in the CMS. It happens when editing pages, making new pages, using modules, uploading images... etc. The thing is it is only happening to them. It doesn't happen to other admins, even those with the same permission settings. I tried following the PW permissions guidelines for directories and files in site/assets (although they were all set to the right settings/owner anyway). I also tried updating the CMS to the latest master release as of today. Anyone have any other suggestions?

This is a great module, thank you! Looking forward to v2. My only addition request would be to forcibly override existing page URLs that do resolve.

Is auto-saving and live preview with repeaters in the pipeline? I nearly jumped in and bought the agency edition today, but it was mainly for live preview and we use a lot of repeaters/repeatermatrixes, glad I spotted that it doesn't do that before I paid! Not that it doesn't look like an incredible module! I'd absolutely love to use it. Must've been quite a feat.

I used this for a while and it was very helpful. But it isn't working for me anymore, has anything changed in a recent PW update that would stop the ready.php hook above working?

Thanks everyone for your input, you've definitely given me some other ideas on how I could approach my particular need for now. Especially happy to discover Connect Page Fields!

Yeah there's various practical ways I could do this to make it easy for myself, but as a user friendly option for a third party, I'd need something a little more robust.

Currently the option to list all pages as checkboxes is very basic: I would really like (please inform me if something like this already exists), something which Has check all/none controls Indents child items/highlights parent items Pagination/load more for long lists An option to check all children of a parent item I know there are other more comprehensive systems, but they are focused on expand/reveal controls, re-ordering etc. The use of this would be if you're creating a page, and you want to determine which other page the content appears on. Edit: I'd also happily take suggestions on better ways to do that! Edit: A better way to word this would be: the Page List Select Multiple input type, but with checkboxes for each item, plus secondary checkboxes on parent pages for selecting all child items. Currently when you pick any option from the list in Page List Select Multiple, it's added to a separate list and the list collapses, meaning you need to re-expand everything just to pick the next page in the list.