Carl Alberto

Awesome, thanks!

Hi @stevenayers63

Sorry for the delay and thanks for following up.

Just to explain further the platform, has 2 filesystem modes, Read-only & Writable.

Multidevs & Development environment that is in SFTP mode is writable by default.

Read-only environments are environments in Git mode, Test and Live environments
In this mode, regardless of the permissions, even if you override it with any permissions, the only path that will be writable is wp-content/uploads

All environments and mode should have these permissions by default:
All directories (default) – 755
All files (default) – 644
wp-config.php – 644
symlinks – 777
Uploads Directories – 770
Uploads Directory files – 770
(any other specific files that need specific perms) – none so far as we can check

Hope that clears up but I think your latest plugin seems to flag files and folders safely correctly now, I might have flagged it incorrectly since I have used an older installation, upon checking on a freshly installed site, everything seems to look good:

Core:

Themes:

Uploads:

Plugins:

Thanks for the reply @erickfogtman, sent you an email, and happy to move forward things from there ??

Hi @stevenayers63, sorry for the delayed response.

It seems it is not erroring anymore on the WP core folders, few things that we have noticed:
– core files in the root are flagged as error
– symlinks that are 770 are reported as warnings

Can those be also hosting specific exempted? It may not be relevant since the live site’s core files will always be read-only in Pantheon even if the permissions are being overridden to be lower than 755

Hi @vishal13m,

Have you tried updating the pantheon.yml file and having some values for the protected_web_paths eg:

protected_web_paths_override: true
protected_web_paths:
  - /private
  - /wp-content/uploads/private

Then it should be pushed from the dev environment up to live

We have this proposed in the Pantheon docs already https://github.com/pantheon-systems/documentation/pull/6184#issuecomment-801541965 so would like to confirm if this works from your end

Thanks!

Hi @stevenayers63,

Thanks for the update, but upon checking, it still has a different error https://www.screencast.com/t/xaAkvjiono

If it would help to have a test site from us, would love to create one from you, just let me know your email so I can send the creds. Thanks!

Thanks for the quick reply @stevenayers63 and for accommodating our request.

You can use $_ENV['PANTHEON_ENVIRONMENT'] to check if you are hosted in the platform, there are sample codes in here https://pantheon.io/docs/environment-specific-config#define-wp_debug-to-perform-actions-based-on-environment

Also, you can sign up for free https://pantheon.io/register in the platform and spin up a sandbox site to test out your code and plugin

Hmm, this sad, same feedback from their GitHub repo https://github.com/sendgrid/wordpress/issues/87 ??

Cool @penbailey, glad to hear that you were able to sort it out! ??

Thanks @kimvt1991 !

What import method are you doing?

How big is the file that you are importing?

Have you checked(or checked with your hosting company) any relevant error logs regarding this issue?

Have asked your host to increase the PHP timeout/max exec time if possible?

Thanks for the awesome feedback my man @slick2! You rock!

Thanks for the awesome feedback @tbream !

Thanks for the reply @gioni, is there an option to disable the spam engine at the moment as temporary mitigation to the performance related issue?

Adding this plugin for later reference https://www.ads-software.com/plugins/matomo/

target: ../../uploads/app
link: wp-content/plugins/matomo/app