Posts by tidygraphic

I'm afraid we've just had to tell a customer that we can't confidently upgrade their shop to function with PHP 8 (and certainly not PHP 8.1) after trying out the latest release. We've made plans for other sites not on shop but what we do going forward I'm not sure...

Has anyone been able to get the latest release working well? We can get it to function, after some tweaks, but 🤷‍♂️

I've got to say that without an improved core release there's very little goodwill left in our team to move to a subscription model. I'm not against the idea at all but after months of total silence from the Perch team and a very half-baked "version 4" release (which we can't use on production sites in its current state) we won't be making the jump.

I've always been a fan of Perch and I hope you can get things back on track (not least so we can support our 50+ clients still using your software who are on the verge of being migrated to PHP 8). All the best and I look forward to more regular updates here, maybe...

I'm afraid if you're expecting a response from directors@perchrunway.com you might be mistaken too - I emailed them over a month ago and have heard nothing since...

Hi Hussein,

I've cracked it - as you mentioned, as usual Chrome has the key. So - the console error lead me to a 404 with this require path require (realpath(__DIR__ . '/../../../..//') . '/core/runtime/runtime.php'); inside 'get_asset.php'. I've changed that line to read:

require ($_SERVER['DOCUMENT_ROOT'].'/admin/core/runtime/runtime.php');

Inline assets are now working a treat

Thanks for giving me a nudge in the right direction.

Thanks, Lea.

Thanks Hussein - some answers for you:

• I tested in Chrome as I thought that could be the case and I received a similar error message but referencing JSON. I can dig this out if it helps?
• Seems to be for new or existing assets
• I added your example config just to check this and still had the same result

I'll try this out on our staging server tomorrow to see if I can find any more information.

Thanks for getting back to me.

Good afternoon,

I'd love to use the Pipits Inline Perch Assets on a new site I'm working on but I can't seem to get it to work. I have custom Redactor plugins loading and working fine but adding the Inline Assets plugin doesn't seem to work. I can get the icon to appear but adding an image simply adds a blank line within Redactor and no image.

In the console I end up with Unhandled Promise Rejection: SyntaxError: The string did not match the expected pattern after trying to add an image using the plugin (using Safari, Big Sur).

My Redactor config.js code is below and I'm on the latest version of Perch Runway:

Would love it if Hussein is around and can shed any light on what might be wrong.

Thanks, Lea.

This is still happening by the way but we're no nearer to having any clue what might be causing it

Should have added that a regular old ' REPAIR TABLES' fixes the problem but it keeps coming back...

Morning,

We run around 50-60 Perch installs on a reseller platform (we run our larger Runway sites elsewhere) and since around April we're seeing regular table crashes in MySQL that cause regions in Perch to appear empty for clients updating their sites (front-end remains fine, thankfully). I've been on and off with our host about the problem since it started but we cannot get to the bottom of it.

It seems to be when customers edit content it can crash the _resources or the _content_items tables and it doesn't seem to matter which version of Perch they are running. It's happening on v2 and v3. We're running a pretty normal stack and the hosting runs on PHP 7.2/7.3.

I'm not expecting a fix as I'm pretty sure it's a hosting issue but our host is at a loss to know what to do next as all other sites with databases are running fine. If anyone has any clues as to what might be missing from the environment that would be great. An example diagnostic is below.

Thanks, Lea.

I just thought I'd check in on this. It looks like some progress is being made with Omnipay so I guess we hold on tight for a Perch update to add support to shop when this is stable: https://github.com/thephpleague/omnipay-stripe/pull/128

Thanks Drew - looking forward to hearing more.

Good afternoon,

We have been monitoring a post in the forum from a while back (here) that discusses the upcoming stricter 3D Secure requirements from the EU for payments. We've looked into contingency planning to work the new regulations and requirements from Stripe (and other payment providers) into Perch Shop but it would be great to find out if Perch are planning a point release to cover the new requirements?

The regulations and requirements seem a bit murky but from what we can tell, without support for the new payment processes, Perch Shop customers are going to start seeing a much higher rate of rejected transactions from 14th September once the new regulation come into force. Do you have plans to support Stripe's new SCA ready checkout process in Perch 3?

We'll be looking to communicate any potential costs to our customers sometime in July so an update would really be appreciated.

Thanks, Lea.

PS. Very excited about Perch 4 too.

Yep - I can’t see how, as it was a fresh install from a fresh download. Who knows but it’s all working now but thanks for looking into it

Just to tie off this thread we thought we'd try a belt and braces approach and download a fresh core folder and add that. When we did it reported these files as modified (attached) which is very strange but everything is now functioning as it should.

Unfortunately neither have made a difference - I'm seeing the same behaviour on the staging server (and using private browsing mode).

Yeah this is just on our local server - we haven't launched on a staging server yet (as just wanted to finish this last template).

I can try there and report back though?

So I've just put up a new test region and on this one I can re-order them but when I add a new block, or when I save the region they return to a random order. You can see this happening here. Code for this test region is like so:

I don't know if it's significant but in the debug when I first visit the region in Perch it mentions "Form not posted or did not validate" underneath the "Using template: /templates/content/services/test-block.html" line. When I hit save I get the usual debug stuff and a "Setting alert: Content successfully updated (success)" message.

Could it be something in the database ?

Initially there weren't (in the first example). I've since tried with another block area with a field outside - this is where the even stranger behaviour occurred (see second video). That's where I can re-order the blocks but they also seem to re-order themselves on every save.

Thanks for getting back to me - I'm really puzzled by this one!

I run Ghostery in Safari but I've just tried in Chrome and I'm getting the same behaviour.

OK I've done more testing and with a totally new region I'm now seeing this behaviour where the region now re-orders itself (without me touching it) on every save. That's using this code in a totally new region:

I'd really love to know what's going on - it's the last page template in the project!

Thanks, Lea.