Thanks George G
I really appreciate the update and keeping us in the loop. Makes it much easier to keep using the CMS if we know what the plan is and how it is progressing.
Thanks George G
I really appreciate the update and keeping us in the loop. Makes it much easier to keep using the CMS if we know what the plan is and how it is progressing.
George G Thank you sir I do look forward to the progress and the updates
ex-jedi Good question I'm wondering the same thing. A plan, where we are in the process, anything?
Mikeymu I think you will enjoy it. I have enjoyed working with Perch for about 5 years now.
That would be slick
drewm and rachelandrew thank you for your work. I really enjoy using the Perch CMS and I'm still using it with my clients. I'm looking forward to seeing the changes and updates with the new ownership.
Here are a few that I like
jonathanhazelwood I use that admin style for all of my projects and it is pretty outstanding IMO
I also believe that if we the users want to see Perch stick around then we probably have to agree that we all need to pay for the continuous maintenance updates and probably and increase in license fees. Money is a requirement for time invested.
The technical functionality of Perch is truly outstanding and although I've only been using it since 2016 I still find new stuff all the time. However, I feel Perch needs some marketing help in order to grow the user base and also more admins on the forum so people with questions can get them answered more quickly. I would be willing to kick in some marketing hours every month and I'm sure many people around here would kick in time to help with the forums as well. Just something to think about.
drewm Thank you sir I appreciate your work. If I can get PHP 7.4 & then 8 to be bug free I'm good to moving forward.
rachelandrew My main question is will you make sure that Perch keeps pace with PHP? I like it and want to continue using it but as PHP versions advance there have been issues that pop up with Perch. Perfect example is PHP 7.4 I have noticed a few issues so I reverted to older versions of PHP to make sure Perch was compatible. I create smaller mom and pop sites so it will work for me as it is, but it will become untenable if it doesn't keep pace with PHP.
drewm Thank you for the update. I appreciate the heads up.
hus_hmd I totally agree that Shop should be a paid add on. It is a massive undertaking. I have no problem adding that to the bill for my clients. They want a shop they should have to pay for it.
ellimondo I should have been more clear that I may be in the minority considering I've only been using Perch for 3 years. Feels like most users have been using the product longer than I have. I went and compared Perch to Craft and most of the other decent CMS systems available including many free options. I could not find a product that gave better value than Perch.
My main point was after research, I hitched my wagon to Perch 3 years ago and I would hate to have to change now.
I might be in the minority, but I spent a great deal of time researching CMS systems about 3 years ago because I wanted to find one solution that would work for my small practice. After spending literally days doing cost/ benefit and pros / cons I went with Perch. I haven't been disappointed. Even today I am anxiously awaiting Version 4 but I'm not disappointed with Version 3 as it does everything I need it too.
Is it perfect? No it isn't but for the price I pay and my clients it is just what I need. I am a user of regular Perch and not Runway so that is my frame of reference. I have made adjustments over the years and spent time learning the way Perch works. I have customized it to fit my clients and I have heard nothing but great reviews from my clients.
I fully understand the need for Perch to change it's model so it can be more sustainable. Also, I want to thank Drew and Rachel for their work in putting together a great product.
Syntax error on my end. Need to have php on payment page direct to failure and success pages. I had an action added to the stripe payment form that was executing prior to the payment.
Drew, can you just take a minute and look at my code and see if anything pops up to you as looking wrong. I really don't want you to spend more than a minute or two. Just let me know if you see anything that you think might be a problem. I understand you are busy, but I would really appreciate it. If it is more extensive then I would be willing to pay for support.
Drew I'm not sure. Let me bullet point the situation.
/perch/config/shop.php (the below secret and publishable key I have changed to the ones Stripe gave me)
Payment Page on website. First code chunk is in the head and the second is in the body. (I copied and pasted the code and didn't make any changes). I am wondering if I need to change the return_url & cancel_url
/perch/templates/gateways/stripe_payment_form.html (only thing I changed on this page was action="/shop/result"). I am wondering if the action should =#?
My Hosting companies have it available and on by default.
I have my Perch Shop up and running and everything seems to be working fine, except for testing transactions using Stripe. The first transaction I did went through and showed up in Perch as an order and it showed in Stripe as an order as well, but I've tried to do about 5 additional transactions and none of the other test transactions are working. I looked in the Stripe logs and they look good to me, in fact I matched up the successful transaction with the other transactions that failed and everything looks the same in the log.
Has anyone else had this issue with Stripe testing? Or What would be the best way to trouble shoot the issue. Any help would be appreciated.