Hi Tony
One quick win is to prevent bloat by reducing your config's history stack with PERCH_UNDO_BUFFER. I usually set mine to 3 in production and 1 locally. I think its default might be 30 which is a tad excessive!
You can also stop content indexing using the no-index attribute. NB This will also remove the item from search.
https://docs.grabaperch.com/te…butes/no-index-attribute/
Jon
Hi thanks Byron Fitzgerald! – I can confirm that I've got it working but not pushed it live yet. Trying to keep up with bloomin' client stuff! 
.
Hi
I am still getting the following error message with 3.1.7 and php 7.4.7:
Diagnostics:
You might need to run Perch Update again to clear those errors and see if it creates those missing DB columns. You can do that using /perch/core/update/?force=update
Clive's advice above is great btw. Your live site is running 2.7.8 which is pretty ancient so it may take a few incremental upgrade steps to get you up to the php 7 compatible version.
What PHP version is your live site on? I would be surprised if it's on PHP 7 and working correctly.
What about using `perch_content_create` in the header of your template page in the order you want them to appear in the admin page. And then control whether they are required on particular pages using page attributes. Could that work?
I wonder if your local PHP version is too new for your old Perch install. Perhaps you can downgrade PHP to 5.4 or similar while you update the site then switch to 7 once you are up to at least 2.8.34
Convert them to blocks?
Hi Byron Fitzgerald Thanks so much for this. Did you see my issue post on the Github page?
Try <perch:blog id="postID">
Adding <perch:showall> to the bottom of a template will show you what's available.
Hi. You need to update Perch to at least 2.8.34. Your web host has probably upgraded your web server to PHP 7.
Sorry my bad – in my hastily typed example the option should be 'page' not 'path'
The debug output looks like it's looking for /opportunities/job.php [line 13] - are you sure you've got the page path right in your code? I thought it's…/index.php
What do you get when you take out the 2 sort-related lines?
Have you got debug turned on? Are there any errors showing?
Hi
You don't need to create a new region here as it's already created on the index page. You just need to tell Perch where to get the details from:
Sure. You can add as many as you like.
Start by editing the post.html template. Copy the template folder over from the /perch/apps/perch_blog/templates/blog folder into the /perch/templates/blog folder and make your edits there.
A template filter will work well on calculating time to read. There's a free one over here you could try: https://github.com/clivewalker/perchology-links
Hi Tony
You need a space after width="1800" – that might be ballsing up the delete function. But sticky repeaters are definitely an issue I've seen before.
If you're running your site on PHP 7+ then you need to update to at least 2.8.34. You are on 2.8.31. --> https://grabaperch.com/blog/ar…-perch-installs-and-php-7
Hi
It could be that your Perch install is out of date. You're running Perch 2.8.18. If your host has upgraded your hosting to PHP 7 then you need to update to at least 2.8.34 --> https://grabaperch.com/blog/ar…-perch-installs-and-php-7
Not out of the box, no. It's just a simple list of members with name, email, status and date they joined.
Hi Simon
If I understand your question correctly then you can disable the submit button by using the data-callback data-expired-callback attributes in the API.
https://developers.google.com/recaptcha/docs/display
If I recall I got the answer from a post like this one on Stackoverflow -->
https://stackoverflow.com/ques…av2-enable-disable-submit