Posts by Hoops78

When you've made the changes to your htaccess are you checking in an incognito window? As a change might have worked, but the sites using the cached version.

No probs. Glad you got it sorted.

I think that might be the routes on the archive... I remember it caused me grief trying to sort that out;

https://docs.grabaperch.com/addons/blog/runway/config/ (Archive page routes and Update links in the templates sections)

I emailed about 10mins after the pricing email was sent and I got a reply. Maybe you have to get in quick while they are in a posting mood.

Actually, the routing might be old when I was trying blogSlug as its not mentioned anywhere else.

Is it down to the routing in your runway.php file in Perch>config? TBH I've only done a couple of runway sites, so I'm not 100% sure on this. I have the following in my runway.php file;

I've also included the blog settings of my site where its working

Hi

Is this Runway? If so, have you done the routes on the post page. For example here are mine;

Also. If it is Runway, you don't need the post rewrite in the htaccess. This is for regular Perch.

Edit. Ignore the Runway question.. just re-read your post title. lol.

I’ve experienced this when I’ve downloaded a site from my hosting to a local build. The cause was additional code in the htaccess, but looking at yours, I don’t think it’s that.

Is there any difference in the htaccess to a freshly installed one?

Plus this forum is now branded as Runway (instead of Perch), which points to the direction they are going. Still would be nice to be told... or given notice that a product was being ended.

Try this link;

https://join.slack.com/t/perch…t0-k5zc8Fz1sCBpjmm4sNbWJw

I'm not concerned about the now. But in 6months - 1year with around 50 Perch sites I will be.

80% of the site are on my server, so I can control when it goes to 8. But the other 20% are on hosting where they just update and then I get an email from the client asking why there are warnings on there site. I know you can roll back, but its not a great situation. I'd rather get the sites php8 ready before its needed. If that means paying someone to do it, I would rather do that then be in the same situation as the SCA mess.

The fact I asked a legit support question last month (not asking for time-scales) about whether it was being worked on and didn't get a reply, shows I'm better off looking after myself.

Changing the 'Live Domain' under the License settings is all you'll need to do to log back in.

I'm currently in the process of getting php8 versions. I can't remember of the top of my head which ones aren't. A while ago I tested a few sites my upping the php in MAMP and it threw up deprecation warnings. The apps haven't been updated for quite a while, so I'm thinking they are all going to need looking at. The plan is to get a full set, so if I need to use any in the future I can.

Quote from Hoops78

Let me know either way.

Or not. *sigh*

I know you can't give any timescales, but are making the apps php8 compatible being worked on?

A client has forwarded an email from their hosting saying they are upgrading to php8 from the first week of November.

At the moment I'm thinking I'm going to hire a third party developer to create me a set of php8 compatible apps. This will leave me with a set I'll no longer be able to update and also out-of-pocket. But if this is the only option I'm prepared to do this.

Let me know either way.

Made a coffee and came back and realised I've put the perch runtime in the header instead of on the first line

Hi

I've built a site on my development server and just uploaded it to the clients cheap shared hosting with one.com and I'm seeing the following errors;

Warning: Cannot modify header information - headers already sent by (output started at /customers/2/7/b/cosmic-people.co.uk/httpd.www/about-us/our-promise-to-you.php:1) in /customers/2/7/b/cosmic-people.co.uk/httpd.www/perch/core/lib/PerchUtil.class.php on line 1399 Warning: Cannot modify header information - headers already sent by (output started at /customers/2/7/b/cosmic-people.co.uk/httpd.www/about-us/our-promise-to-you.php:1) in /customers/2/7/b/cosmic-people.co.uk/httpd.www/perch/core/lib/PerchUtil.class.php on line 1400 Warning: Cannot modify header information - headers already sent by (output started at /customers/2/7/b/cosmic-people.co.uk/httpd.www/about-us/our-promise-to-you.php:1) in /customers/2/7/b/cosmic-people.co.uk/httpd.www/perch/core/lib/PerchUtil.class.php on line 1401 Warning: Cannot modify header information - headers already sent by (output started at /customers/2/7/b/cosmic-people.co.uk/httpd.www/about-us/our-promise-to-you.php:1) in /customers/2/7/b/cosmic-people.co.uk/httpd.www/perch/core/lib/PerchUtil.class.php on line 1409

I remember ages ago I had a similar issue and it was white space at the top of the index file, but this time this isn't the case, so I'm not sure what to try? It mentions /about-us/our-promise-to-you.php but that file doesn't have any white space at the top either;

https://www.dropbox.com/s/uoac…%20at%2016.17.29.png?dl=0

I always refer to your excellent blog post Clive Walker when creating a perch sitemap;

blog post

Thanks Hussein.

I'd forgot about showall, I'll try that today.

I've got file upload in my form working OK and it attaches to the admin email. I'm using this in my form;

The admin email gets the file, but I'd also like a mention in the customer email. Not the actual file, just the filename of the document they have uploaded. I added this to the email template;

But nothing is outputted. How do I get the filename of the file they uploaded. For example mycv.doc