netcarver

It could be as simple as having an offsite link to the github release page for the version. I believe it could be auto-generated, as they all (currently) follow the same format... https://github.com/<user>/<project>/releases/tag/<upgrade-version> =================================== | Known to PW from the module repository? Updated to add: Yes, just trying the locally and it seems to work. Not difficult to pull the repo URL along with the other data and use it to add a "Changes" link next the new version. A little more use of WireHttp() requests to check if the links are sending back a 200 or 404 page and we'll know which items have release tags.

@Mike Rockett I like the use of release and the changelog - please keep it up. In fact, I think I need to adopt this with my own modules going forward. It would be really nice if ProcessUpgrades - or the PW core - could send us to a module's release notes before we decided to update it.

@Macrura Thanks for the reply. It's good to know that you are having success with the module approach - I did take a brief look at it as I like the idea, but I ended up passing it over when I realised there was no support for images out of the box. Could you perhaps issue a pull-request to the module author with your changes? They sound like a worthwhile addition.

Curious to know what other people are doing for this now - especially in light of the new FunctionalFields feature.

Hmm, now if only the module toolkit were installed by default

I've now merged FlorianA's patch into the allow-blanks branch. Please test and let me know if it works for you.

@FlorianA Sorry for the delay on this. I've been away from the keyboard over the summer holidays and must have missed the notification email from the forum about your post here. Looking at this now.

Hi Ryan, Great to see the registration/login module - very appreciated. In the next version, could you make the createConfirmationCode() method hookable so we can supply our own generators? Actually, only the generation of the code needs to be hookable - the scaffolding in that method to store the generated code could stay as it is. Many thanks!

Thanks for the report @Macrura. If you get a situation with a crashed table again, please could you turn Tracy on and try to get a stack trace for me? (I'm not in the habit of purposely corrupting tables!) I wonder if there is a tool we can use to force/simulate a corrupted table?

Done

You could also try ersch's PagesSum module for this aspect.

@heldercervantes Sounds good. I had a similar need for custom email templates and built a module for that too (along with a helper module.) You might find it useful in your application, too. Both modules are fairly old now - YMMV. Best wishes!

@heldercervantes Sounds like one of my older modules. Welcome to the world of module authorship!

@helmut2509 Ok. I just read the documentation again, and if you don't need an id for the "new" action, you should be able to use... new regex:^edit/[0-9]+ Steve

@helmut2509 Looking at what I wrote again, if you don't require the "new" segment to have an ID, just leave it as "regex:^new".

Hello, I'm a little confused by your description of the problem, but I don't think you have your URL segments set up correctly. In what follows, I am assuming you have edited the URL tab of the template for your page to turn on URL segment processing and you have something entered in the "Which URL segments do you want to allow?" field. I'm guessing that you want to have the first segment be an action - either edit or new - and the second segment to be a numeric id. If that is the case and you want PW to enforce the first segment to be either 'edit' or 'new' then you need to use a regular expression as documented here to match the actual URL you are supplying. More specifically, could you try... regex:^new/[0-9]+ regex:^edit/[0-9]+ Another approach may be to leave that field totally blank and do all the checking yourself, in which case I think macrura's code should work.

BTW, if you have GhostScript installed on your server, you can use it to compress PDFs locally using a command-line call... gs -sDEVICE=pdfwrite -dCompatibilityLevel=1.4 -dPDFSETTINGS=/ebook -dNOPAUSE -dQUIET -dBATCH -sOutputFile=out.pdf in.pdf Source: SuperUser.com (See 2nd answer.)

Hi @matjazp, How did you happen to find out about the compression API at labstack? When I look at the site, there seems to be zero documentation about that feature. Regards,

Hi @Andreas Augustin Thank you for the interest in this module - which is in need of an update. I've been contacted by a couple of other interested parties (see here), and I will be working on an update to this module soon. Personally, I've always preferred using an SSH tunnel to connect to remote redis server instances, but I will certainly take a look at what you've done regarding native authentication suppport. Best wishes, Steve

You may well be right, Guy. You know your application better than anyone else. If you design your cron script to process a small part of the larger picture on each invocation, there's no reason that an invocation has to process the entire input set in a single run. Also, as you already have an exact record of the previous input set in the form of the previously imported CSV file, it should be fairly easy to compare the newly generated file you want to import into PW with the previous one in order to quickly generate your addition, deletion and change lines. This approach does work if the external data set is the master copy and is in sync with any sales that are made through the PW site. If stock levels are independently tracked in PW and/or take some time to back propagate the external data source, then this pre-processing approach can't be used for updates, just for additions and deletions. Also, if a large percentage of the data set is different between imports, then it may not gain you anything to pre-process. Best wishes

Hello Guy, I'd be tempted to look at running your script directly from a cron task, rather than using a trigger URL. Is there a particular reason you couldn't take the cron route? Also, with that many products, it might be beneficial to pre-process the data so you only have PW process lines from the CSV file that represent changes from the previous import - ie, products that have been added, removed or updated. I suspect many of your 50000 line file will be the same between runs of your update script, but I could be wrong as your situation may be different and your data might be changing more rapidly than I've previously experienced (for example for very fluid stock levels.)

@Karl_T, @seddass you should both have collaborator invitations in a moment or two.

@seddass, @Karl_T I'm a little out of the loop regarding Redis, at the moment, but I like the idea of collaborating on this. As I have the original repo on github, how about I add you both as collaborators, and we can make this a more community oriented effort?

My module was very experimental. Very happy for it to have a successor

<moderator hat: on> Hi everyone, Just want to point out that discussion of Ben's module really belongs in its own thread and not under this one - which is specifically for discussing pwFoo's module. If anyone wants to discuss a possible merger between the two modules, please start a new thread to discuss the possibility and then post a single pointer to the new thread here and in Ben's module's thread. Many thanks! <moderator hat: off>