oolongm
Forum Replies Created
-
I didn’t post the correct command here, please try:
rsssl update_option --dismiss_all_notices=1This did the trick, thanks.
@oolongm I have an improvement ready for this part of the script that’s currently being tested. It will probably be included in the 6.2.1 release (not today’s 6.2.0).
Running the activation twice works for now. Will give feedback again once this is released. Thanks!
I’ve changed the command pattern a bit, as this seems more intuitive, and also allows for multiple option updates in one line:
rsssl update_option --dismiss_all_notices=trueThank you so much for adding this, however it doesn’t seem to have any affect for me on the popup that comes after first login and the notices that show up. Is it supposed to let this all disappear?
This will be included in the update next week.
I just tested the latest release (6.1.1) and it seems like there is a regression for the ssl activation. It still says “Success: SSL activated successfully” in the console, however in the wp backend it says “ssl not activated” :/
Now the new thing is that if I run the activation command a second time, it seems to work. Also if after the first (failed) attempt, I uninstall the plugin with the option “Delete all data on plugin deletion” activated – and then I try the whole process again it seems to work on the first attempt.
Any ideas about this?
Thank you @rogierlankhorst, issue seems to be gone now 🙂
I have created a branch that includes this fix, and also some logging in case there’s something else as well: https://github.com/Really-Simple-Plugins/really-simple-ssl/tree/logging-for-wp-cli
@rogierlankhorst I can confirm the ssl activation works again on this branch. Thanks a lot for finally fixing this. I’m looking forward to have this released, so our custom wp installation routine will succeed again.
As for the notifications: we try to balance between upsells and offering a great free tool without too many notices.
I understand that you need to make some money too, maybe I was a little too harsh with my criticism out of frustration with the wp cli activation not working.
My problem with notifications may be specific to our use case, because sometimes I set up batches of 30 or more WordPress systems at once. When each installation brings 5 notifications that need to be dealt with, you can perhaps understand how annoying they become.
Now, one could argue that we should just buy the Pro version (assuming that the notifications will go away in this case), but unfortunately we already have another plugin with similar security features in use, so we don’t really need it.
Maybe you could consider a wp cli action to disable notifications for power users. If not, I guess we just start living with them, just like the other hundred notifications we see from other plugins :p
Anyway, although the code changes took several attempts to fix the problem, I am very pleased with the response times of your support and the detailed explanations you gave. That’s why I changed the rating to 4 stars. I will also gladly change the rating to 5 stars another time if you do find a solution to our notification problem 😉
One month and one major release later:
wp-cli.phar rsssl activate_ssl
Error: SSL activation failedJust this time without any debug/error messages.
- This reply was modified 3 years, 4 months ago by oolongm.
I can confirm the language issue is gone in the latest version.
The cli activation however still doesn’t work. You really don’t have a system where you could test it?
PHP Fatal error: Uncaught Error: Call to undefined function rsssl_uses_htaccess() in /public_html/wp-content/plugins/really-simple-ssl/settings/config/disable-fields-filter.php:10
Stack trace:
#0 /public_html/wp-includes/class-wp-hook.php(308): rsssl_remove_fields(Array)
#1 /public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters(Array, Array)
#2 /public_html/wp-content/plugins/really-simple-ssl/settings/config/config.php(1109): apply_filters(‘rsssl_fields’, Array)
#3 /public_html/wp-content/plugins/really-simple-ssl/settings/settings.php(536): rsssl_fields(false)
#4 /public_html/wp-content/plugins/really-simple-ssl/class-admin.php(356): rsssl_update_option(‘redirect’, ‘wp_redirect’)
#5 in /public_html/wp-content/plugins/really-simple-ssl/settings/config/disable-fields-filter.php on line 10- This reply was modified 3 years, 5 months ago by oolongm.
Hi @rogierlankhorst,
I just tested your code, unfortunately it doesn’t work yet.
It also includes your suggestion for feedback on SSL activation failure.
This part basically works, however you return the error instead of success state. You probably meant to write !$error here: https://github.com/Really-Simple-Plugins/really-simple-ssl/blob/master/class-admin.php#L387
With this line changed the cli action completes and outputs the success message, however in the wp backend the ssl activation state is still deactivated afterwards. I’m afraid you will actually have to run this code to see what’s going on – or what is not 😛
I also noticed another bug: The plugin localization doesn’t respect the user language, but only the wp core language. So for example if I have a french wp site, but my wp user has en_US as language, because my french is poor, then the backend is all english besides RSSSL UI what is still in french.
Thanks for this super fast reply! I’ll try it soon, next time I’ll setup some new sites. But the code looks like it should solve the problem.
Forum: Plugins
In reply to: [Classic Editor] Incorrect line in plugin filebut I think there is a way to set it as false-positive. That’d be less trouble
Yes it’s possible, however if you run hundreds of wordpress instances, it’s not that easy without wasting hours.
So please @azaozz listen to my fellow commenters and don’t modify released software. Even if it’s not affecting executable code, it’s a bad practise and causes unnecessary trouble like this 🙁
Forum: Reviews
In reply to: [Enable Media Replace] Causing data loss!!!As you can imagine, we did not code our plugin to delete your images on purpose, so we would’ve appreciated if you could’ve sent us a short e-mail telling us about the issue so we could fix it, instead of writing a 1-star review straightaway. I can assure you that our priority is for our clients to be satisfied.
My intention was to do a bug report and to warn other users in the same time. Once this is fixed, I’m happy to reconsider my rating.
Hi @erwincloudinary,
I’m having a clean installation of wp 5.6 with no other plugins installed than cloudinary 2.5.0. I can give you access to the wp, if you want to check yourself, but maybe we can figure out those details in a pm.
Regards,
Ronny
Hi @erwincloudinary,
like I wrote earlier, nothing that is not a picture, uploads to cloudinary through the wordpress plugin (at least for me). Therefore I followed the workaround described in this forum, to upload the pdf file directly to cloudinary through the management console.
I do see the pdf file in the cloudinary UI, I see it in the ‘cloudinary tab’ with in the insert media dialog in wordpress, but I’m not able to insert it into a wp post/page.
Do you have any idea how to figure that out?
Regards,
Ronny
Hi @loiccloudinary,
unfortunately that doesn’t work either. Clicking ‘insert’, switches back to the media library tab. I see a new attachment there, it has the title of the pdf file, however the url is empty and therefore it can’t work I guess. I took a screenshot: https://snipboard.io/aYBL78.jpg
Regards,
Ronny
Hi @loiccloudinary,
thanks for your fast reply. I tried your workaround, however when inserting the image into the post, in the cloudinary tab the select button in the lower right corner stays grayed out, no matter what I select (pdf, txt, picture).
If I switch to the ‘media library’ tab on the other hand, I can insert the pictures just fine, but the non image files don’t show up there.
I’m using wp 5.6 and cloudinary 2.5.0. Is there any specific plugin setting to make that work? I’m using ‘Cloudinary only’ as storage setting.
Thanks for your help,
Ronny
Hi @loiccloudinary @jaycloudinary,
I just tested it with v2.5.0 and it doesn’t work for anything that is not a picture (txt, pdf). Files are just added to wp media library 🙁
I don’t see a reason why you wouldn’t allow uploads of certain file types through the wp plugin, that you otherwise support if directly uploaded to cloudinary.
Our use case is, that we want to run wp with read only filesystem and manage all the content in the database/cloud. This increases security, makes scaling to several servers way easier as well as the support of dev/staging environments.
Files will only be uploaded by our wp developers, not by users. If you don’t want to make this available to everybody, you could consider a opt-in in the plugin settings.
Please let me know if management of different file types will be possible, or if we need a different solution than cloudinary.
Regards,
Ronny