Posts by ryan

I'm also seeing issues with S3 uploads on later versions of PHP. One issue being:

`Warning /admin/core/runway/apps/perch_s3/lib/guzzlehttp/guzzle/src/Handler/CurlFactory.php67` and `

: count(): Parameter must be an array or an object that implements Countable in`

And another, I think is linked to the S3 library and it's handling of Assets:

https://github.com/aws/aws-sdk-php/issues/1923

I've always been really confident in updating to later versions of PHP with Perch, one of it's major selling points is that it just well, works. Hoping we can see some updates really soon to address these issues and keep Perch stable.

Yep I’d love an update. I’ve got issues with S3 integration with later versions of PHP, and is increasingly becoming more of an issue as I don’t have anything to go back to the client with.

Glad to hear it - well done!

Quote from JordinB

drewm - I understand with your recent new roles, time is a valuable commodity. I'd be more than willing to help on a volunteer basis (no strings attached) to do some PR's to fix bugs anything else you'd need help with.

Me too.

That'd be a really useful addition. Same with collection items too!

Not sure on Redactor, but sometimes the `html` attribute works for me!

I must admit, it's impossible for us developers quoting for projects to consider Perch in upcoming projects with this unknown timetable and uncertainty. As much as I've loved Perch (& Runway) with nearly 70 licenses and becoming a registered developer a few years ago, I'm around 6 weeks away from moving to another provider for new projects.

It's not a decision I've taken lightly, but the choice of product is so critical to the quality of product I deliver. With the recent silence, delays, lack of support and updates, it's one I've had to take. I am the biggest Perch fan going, and will never rule out a return, but in it's current state it just doesn't match my very minimum requirements for a product that I rely upon daily.

+1

Hey,

As the subject states really, when using "Delete all content from this collection immediately", the perch index doesn't seem to drop, resulting in a largely inflated dataset in the collection_index table. Is there any reason for this?

Any help/advice would be much appreciated!

Cheers,

Ryan

I must admit, I haven't got much to add. I think the points covered by hus_hmd and Tobe echo my thoughts. We all want Perch to succeed and we're all very excited to see improvements on the details that really improve the overall product.

The communication side of things is key for me, timescales don't bother me but knowing what's happening and what future plans are is super important for both me and my clients, so we can make decisions and plan future development releases. The lack of updates, radio silence and and social stagnation has almost made Perch untenable for me as a product for my clients, but I'm hoping for some news/announcements early Q1 so I can make an informed decision and hopefully continue to use Perch (it's a fantastic unrivalled product, it just needs some love, care and attention in the details!).

Quote from simplesprout

Hey Ryan,

Does this app work with the Perch Members / Shop Customers registration forms too? I don't think those have a spam section, so I was wondering if this was only for custom Forms such as contact submissions.

Hey,

It doesn't currently, only Perch Forms unfortunately.

I did check the logs, but it's just a pure timeout based on max execution time of 30 seconds, can't see any errors in logs

That was my first port of call - I've reduced to two for now to see if I can get the index down. I'm hoping Perch 4 can bring some improvements and optimisations in this area!

Seen this issue quite a bit lately. So hard to debug, hence not posting on here!

Hi,

I have an issue with reordering items in a collection, where basically the site returns 500 error and a connection timeout upon save of a reorder. The site has over about 10 collections and there's about 1000 items, so it's a larger dataset.

When running a reorder on a smaller collection, there seems to be a specific slow query both on production server and local testing environment:

It takes "2.8132" to execute and is called for each item in the collection I believe? The collection_revisions table has 2928 rows in.

The php function is:

Diagnostics:

Cheers as always,

Ryan

Hey!

Have you set the honeypot field in Perch's settings in admin? Have you updated the form app to `mbk_forms`.

Hi Jakeness,

You'd use the perch:error on the honeypot field, not the g-recaptcha-response field. I'm not sure if Perch natively has an error for the honeypot field, but you could use the following to catch all types of errors:

Hey!

I don't think this feature currently exists, but it'd be awesome if we could add a filter to `perch:related` to choose from a subset of collection items (e.g. exclude items in a collection with a 'hidden' tag).

Cheers,

Ryan

Looks like there's a bit of movement on this:

https://github.com/thephpleague/omnipay-stripe/pull/128