gresakg
Forum Replies Created
-
Thanks for giving us a heads up Rick! It works and I am so happy to have the latest version installed.
I have the same problem.
OMG, sorry. I messed up big time. I was looking for support for Brevo plugin and I made a search that included something about permissions, and this was in the results. I was sure the results were for the Brevo plugin, so I didn’t even check. Must have been late. Sorry!
Sorry. I probably miss understood the thread. However, it is about write access. Here’s the context
$service_worker_file = str_contains($site_url, self::URL_CHECK_STAGING) ? self::PUSHOWL_STAGING_URL : self::PUSHOWL_PRODUCTION_URL; $js_content = "importScripts('" . $service_worker_file . "');"; $service_worker_script = fopen($service_worker, "wb"); fwrite($service_worker_script, $js_content); fclose($service_worker_script);
Where $service_worker is
const SERVICE_WORKER_FILE_URL = "/js/service-worker.js";
$service_worker = __DIR__ . self::SERVICE_WORKER_FILE_URL; if ( ! file_exists($service_worker)) { self::install_service_worker_script($service_worker); }
So obviously the plugin is trying to write to the file
wp-content/plugins/mailin/js/service-worker.js
And that’s what’s written
const PUSHOWL_PRODUCTION_URL = "https://cdn.pushowl.com/latest/sdks/service-worker.js";
- This reply was modified 6 months, 1 week ago by gresakg.
Thank’s for your answer and help!
That’s not how it looks:
PHP message: PHP Warning: fopen({...}/wp-content/plugins/mailin/js/service-worker.js): failed to open stream: Permission denied in {...}/wp-content/plugins/mailin/sendinblue.php on line 647
This error stopped when I switched “Activate Marketing Automation through Brevo” to “No”
I have the same problem. However I deliberately won’t let “plugins” directory to be written by the server. If a plugin needs to write something, it should write it to the “uploads” directory. It works for all other plugins and themes except for this one. You should consider writing service-worker.js in the uploads directory and serve it from there.
Also Wordfence and other scanners issue warnings if the files in the plugin directory are different from the ones in the repository.
Meanwhile, how can I simply disable this feature and thus not get push notifications I don’t need anyway?
Thanks for thew quick reply. The problem is I can’t get rid of the RC. Bellow is the console output
[user@server]$ wp plugin get post-smtp --format=yaml --- name: post-smtp title: Post SMTP author: Post SMTP version: 2.5-rc.4 description: | Email not reliable? Post SMTP is the first and only WordPress SMTP plugin to implement OAuth 2.0 for Gmail, Hotmail and Yahoo Mail. Setup is a breeze with the Configuration Wizard and integrated Port Tester. Enjoy worry-free delivery even if your password changes! status: active [user@server]$ wp plugin update post-smtp --format=summary Omogo?anje vzdr?evalnega na?ina ... Prena?anje posodobitve iz https://downloads.www.ads-software.com/plugin/post-smtp.2.5.0.zip ... Using cached file '/home/gregor/.wp-cli/cache/plugin/post-smtp-2.5.0.zip'... Raz?irjanje posodobitve ... Name??anje zadnje razli?ice ... Odstranjevanje stare razli?ice vti?nika ... Vti?nik je uspe?no posodobljen. Onemogo?anje vzdr?evalnega na?ina ... Post SMTP updated successfully from version 2.5-rc.4 to version 2.5.0 Success: Updated 1 of 1 plugins. [user@server]$ wp plugin get post-smtp --format=yaml --- name: post-smtp title: Post SMTP author: Post SMTP version: 2.5-rc.4 description: | Email not reliable? Post SMTP is the first and only WordPress SMTP plugin to implement OAuth 2.0 for Gmail, Hotmail and Yahoo Mail. Setup is a breeze with the Configuration Wizard and integrated Port Tester. Enjoy worry-free delivery even if your password changes! status: active
Obviously I installed it at an unfortunate moment. I guess I’ll just ignore the notif untill the next minor/patch version.
Forum: Plugins
In reply to: [Simple Lightbox] Fatal error when upgrading with wp-cliUpdate: it’s a problem of symlink resolution. /var links to /data
Changing the command to$ wp plugin update --all --path=/data/www/html/webroot/
did the job.
Still, it is interesting that this was not a problem until the very last update.
Hi, thanks for the hint!
So I guess this is a file permission problem. Where does the plugin want to write to?Forum: Plugins
In reply to: [Linear Checkout for WooCommerce by Cartimize] Create account?How about “external service calls”? I quoted it above.
Forum: Reviews
In reply to: [Linear Checkout for WooCommerce by Cartimize] Requires subscriptionI would gladly try your checkout and tell you about my experience if, you would make the login optional. Then, I can decide if I want to subscribe or not.
I could even opt for a Pro version, if it was worth it, I have no problem with that. But asking mandatory subscription for using a free plugin is not acceptable.
It is about the functionality of the plugin: make login optional.
Forum: Plugins
In reply to: [Linear Checkout for WooCommerce by Cartimize] Create account?In this case this is a violation of www.ads-software.com requirements. Notably this one
Links such as a “powered by” link, or advertising, or external service calls are prohibited unless it is clearly documented and explicit user permission is granted.
https://developer.www.ads-software.com/plugins/wordpress-org/
Any help or hint would be apreciated.
That’s good news! Thanks a lot!
Hi, could any of the plugin developers look at this please?
thaks, Grego