Posts by ellimondo

    The standard php GD image library is pretty pants. It adds all sorts of artefacts to images. Try installing (or getting your host to install) imagemagick. It does a much better job of compression on pngs and gifs. You can then turn this on in Perch config using PERCH_IMAGE_LIB.

    If that's not possible then try using sharpen="0" in the image field. Or, finally, you can add separate (different ids) img fields for 500 and 1000 that don't do any resizing on the original image.

    I think you'd need to query each product, count the variants in each product, add that product to an array, and then when you've reached 12 variants, output that custom array.

    But I am not sure that perch pagination will work with this as the product function will still just count 12 products.

    Yes, you can create as many as you like. Just use the same id for the images e.g:

    1. <perch:content id="gallery_image" type="image" label="Image" width="150" density="1" bucket="gallery">
    2. <perch:content id="gallery_image" type="image" label="Image" width="150" density="2" bucket="gallery">

    The images will then be created when the original image is uploaded through assets.

    There are lots of options for cropping and resizing:…sponsive-images-in-perch/

    The default Author template is in the perch/template/blog folder and it's called "author.html'. I believe you could then add a select field to achieve this or even add a category.

    If it helps, I tend to set up my own custom fields or collections (for Runway sites) and ignore the internal author functionality. Blog ties a Perch user's name to the post and I (and others) have found that just doesn't work well in the real world. In the real world I've found that editors often post on the behalf of someone else and so this functionality becomes rather restricting.

    Personally I would use flex box to do this along with Jordan's suggestion above. Then the logo element can be outside your list markup. You can use order to change the order of the items in the flex container. The advantage of this is that you can change the order for mobile view.

    Rough example below:

    Log into Perch and look at the diagnostics page under settings.

    If you can't log in then I know (in version 3 at least) if you view source from the log-in page you can see the version number under under the style line of code e.g. /perch/core/assets/css/styles.css?v=3.1.2


    You haven't said which version your site is on but, assuming you're on 2 point something, you just need to replace the core folder with the one from 2.8.34. This is available in the download section of your Perch account page.

    I think there was an issue with a plug-in around 2.8.15 so you need to replace these files too. Read through the changelogs for more information:

    Then follow the instructions to move up to v3:

    It goes without saying that you should backup and do this offline or on a staging server with the PHP version set to as close as possible to your live server. Not on a live site.

    NB 7.3 is very new so I am not sure how Perch works with that. I haven't ventured beyond 7.2 yet.

    Thank JordinB I will give it a look over. Most of my clients tend to come with their own email setups so I am bound to them. But for me this looks like a perfect solution.

    Oh well I am glad it's working for you. I'm surprised it works well on just the form pages as it's meant to be deployed to all pages on the site.

    Be aware that even invisible recaptcha will still inject an image-based captcha if it doubts the veracity of the user (i.e. they are not logged into Google in the browser.)



    Just a heads up to app devs and Perch HQ drewm – I had an email from Google this morning announcing the end of Less Secure Apps (LSA). I know that Gmail uses LSA so this announcement will affect a lot of Perch users in the future.


    Dear Administrator,

    We’re constantly working to improve the security of your organization’s Google accounts. As part of this effort, and in consideration of the current threat landscape, we’ll be turning off access to less secure apps (LSA) — non-Google apps that can access your Google account with only a username and password, without requiring any additional verification steps. Access through only a username and password makes your account more vulnerable to hijacking attempts. Moving forward, only apps that support a more modern and secure access method called OAuth will be able to access your G Suite account.

    Access to LSAs will be turned off in two stages:

    1. June 15, 2020 - Users who try to connect to an LSA for the first time will no longer be able to do so. This includes third-party apps that allow password-only access to Google calendars, contacts, and email via protocols such as CalDAV, CardDAV and IMAP. Users who have connected to LSAs prior to this date will be able to continue using them until usage of all LSAs is turned off.
    2. February 15, 2021 - Access to LSAs will be turned off for all G Suite accounts.


    Spam sucks but is really quite inevitable. I for one would like to see future versions of Perch's form functionality tighten up on this.

    In the meantime, how are you implementing Recaptcha? I've found that V3 is pretty useless for small sites and needs to be installed on all pages to work correctly (which is kind of creepy). V2 has a much better response on single page forms in my most humblest opinion.

    Another layer of defence is that you can also implement spam detection at the mail server level - For instance, Gmail and 365 have these built in.