Posts by Byron Fitzgerald

    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

    The order of the results is determined by how close they match the search term. If you want to add custom sorting you'd need to do that on the returned array instead.


    How are are you filtering so that you only get 9? The pagination is based on the initial set of returned results from the search function, filter after the function call will not effect the pagination

    To get the post date rather than using the data option you can use the each option like below.

    Code
    1. perch_blog_custom([
    2. 'sort' => 'postDateTime',
    3. 'sort-order' => 'DESC',
    4. 'count' => 3,
    5. 'template' => 'home_main_headlines.html',
    6. 'each' => function($post) {
    7. $post['postAgo'] = get_time_ago(strtotime($post['postDateTime']));
    8. return $post;
    9. },
    10. ]);

    I'm more than happy for Drew (or anyone) to use my solution and adapt it as he sees fit.


    The main issue is testing the other gateways as Omnipay needed to be bumped up to v3, along with all the Gateway drivers. Whilst probably not too difficult I can imaging it would be extremely time consuming. As I haven't had any experience with using the other gateways, my change didn't take into consideration them.

    As it looks like some people missed my original post, I'll stick it here as well.


    I've created an initial release for an update to Perch Shop to let stripe take 3DS2 payments. You can find the repo here. Everything you need should be there, and the README provides an overview of the changes and what you need to do to get it up and running.


    I've tested this locally but have yet to use this live, so I'd hold off on production use for now, though I have yet to experience any problems. If I could get any feedback on whether you guys can get it working that would be great. I've got some more tests myself to do and once everything is looking good I'll create a production ready release.


    You can also just grab the download here.