FlatPress support forum

Perhaps a plain-text note in the browser would suffice.

That sounds like a great option that wouldn't compromise security - a message that the base url may need to be updated. That would provide much more useful information than what currently happens:
Fatal error: Uncaught Error: Failed opening ...

I figured there was a good reason for it. Instead of upgrading my 1.3.1 I made a fresh install of 1.5.1. Then, following instructions from the wiki, I copied over the fp-content folder and it blew up. Putting back the original (fresh) fp-content folder it would work again, so I knew it had to be ...

I've been using 1.3.1, and one of the things I loved about it was that I could take the complete blog folder and move it anywhere - different folder, copy it to localhost or upload to a new site, and it just worked - no fiddling required.

I upgraded to 1.5.1, and that is no longer true. If the ...

- Tests have shown that file permissions should have octal 0666 and directory permissions octal 0777
- It can't hurt to recreate the index in the admin area in the "Maintain" menu and then empty the theme and template cache.
Please report whether these measures have been successful.
With best ...

I maintain a mirror of my online blog on my local PC. I have a recent blog entry where the images will show on my local computer, but not on the hosted version. Both are using the latest version (1.3.dev [master]). Php 8.1.17 at home, 8.0.29 on the hosted (problem post) version. The images were ...