Peter

mmhh… so how does WP update the plugins themselves? I think you will find many do write to folders other that the uploads.

Out of the 30+ plugins we use, none need to write to their folder in plugins. ACF writes to a folder in the current theme.

WP doesn’t update the plugins. Our updates are either managed via wp-cli or, where we need to test plugin updates do not cause regressions before putting live, by updating the site’s composer.json and redeploying (we use https://roots.io/bedrock/). The latter is becoming our usual procedure.

So I assume even your WP upgrades must done manually…

Yes. Minor upgrades are done via wp-cli run regularly via cron; major ones are manually done and tested before putting live.

Hi Aurovrata,

sorry to read of your troubles. Is this on a local machine or a remote server?

It’s occurring on both my local Vagrant machine and my remote server.

Seems like a configuration issue with your Apache server, which is really beyond the scope of this plugin support.

I respectfully disagree, as a plugin should not assume it can write to its directory. Instead, it can use wp-content/uploads or the Filesystem API. For security we run PHP as a different user to the file-owner, and only keep the uploads directory writable by PHP.

Please follow the instructions in the 2nd question of the FAQ section to remedy this issue.

Thank you, I will do so and confirm that it’s worked tomorrow.

Best regards,
Peter

Spot on, thanks – I’d created the post type but tried to set everything up before I entered content.

I’m having the same issue. It’d be great if CodePress could tell us if custom columns are/are not supported on custom post types – it’s looking like they’re not.

Thanks, I’d missed this – personally I prefer a separate field (a concise summary is different to the excerpt of a post) but this will do until I figure it out.