Posts by Byron Fitzgerald

    With the basic 2 lines of code Outlook365 thinks the email is spam, this is quite common when not using SMTP to send emails. This would be different for every email client though.

    As with the SMTP issues, this is not an error with Perch but with the SMTP connection. In the debug you have SMTP connect() failed. This indicates that the SMTP server could not be authenticated, this is most likely down to incorrect configuration (incorrect server name, PORT, auth details e.t.c). It could be due to downtime on the SMTP server, but this is unlikely to be the case.

    Maybe I've missed something but I think you might be overcomplicating this a bit.

    If you have a related field in your 'Album' collection you can use that related field in your template to fetch your 'Photo' collection items.

    I'm not sure how your template is set up so the code supplied was a best guess. You can print out the array to check to see exactly how you need to set it. Once the spec_min is set you'll be able to use it in any namespace, but you'll still need to call the scoped namespace to use it. So in your case you'll need to use <perch:productvalues id="spec_min">.

    It could be the case that the spec_min is set in the variants, so you might need to do some more digging in the array.

    Your best option is to then set the spec_min as a global variable. You can run a callback on the 'each' property when fetching the product and find the spec min key and assign it as a global variable there. Something along the lines of the following.

    Think it's an issue with the array map, should probably be

    1. // Map the array like we do in the previously used each property
    2. $comments = array_map( function($post) {
    3. $post['postAgo'] = get_time_ago(strtotime($post['commentDateTime']));
    4. return $post;
    5. }, $comments);

    Hi Glen,

    Had a lovely break thanks, hope you did to.

    I think it might be because the comments app is a bit outdated and doesn't have the full available options when rendering the templates. I'm pretty sure the each option doesn't exists for perch_comments. You'll need to return all the comments, then loop through them, then pass to perch_template. Something like below should work

    I think when the date is stored it's set in the standard format of 'Y-m-d H:i:s'. The formatting of field happens during runtime in the template handler, instead of the save/edit process.

    If that still doesn't work you can check the database, or use the <perch:showall/> to see the unformatted value

    Had a look around for you. The listing page uses the following $Statuses->get_status_and_above('paid') to fetch the orders.

    In the shop admin area you can view all the statuses. In the list of statuses there is an index column. Anything above that has a higher index than the paid status will be shown, anything lower will only be shown in the export.

    You can edit the indexes as you need to show which orders you'd like to see. I'd take a backup before hand as well though as I'm not sure where else the index value is used.

    You have to pass the styles through the elements.create function. You can also style the container with regular css.

    Here's an example from the stripe docs

    If you want more customisation over the layout you can create individual elements separately (card, expiry, cvc, paymentRequest bytton). You can read more about it here

    The issue seems to be based on the attributes templates. Perch will find any files in the perch/templates/pages/attributes folder and list them in the `Edit page` page. The label is a human readable format of the file names in the folder.

    What files are present in your perch/templates/pages/attributes, and what version of perch are you running?

    I've got one site running my solution on production right now, with a second waiting client approval. ellimondo has done some testing and managed to get it to work I believe, but not sure if he is running it in production yet.

    If anyone does try it and has any issues you can throw them up on the Github page. I'll try get back to you as soon as I can, as I know the deadline is shortly approaching