Callum Macdonald
Forum Replies Created
-
Could be, I’m not sure how the other plugins send emails, so can’t say about that. I understood from reading the thread that everything used to work, and since upgrading the plugin to 0.9.3 it stopped working, but it seems like that’s not correct.
Personally, I’m using the plugin on WP 3.7.1 and v 0.9.3 and everything works fine. But I’m only sending mail to localhost, no authentication.
So whatever issue you’re having is not related to the new release of the plugin, but has always been there, and it’s not an issue with the plugin itself, but something in the setup.
@eitanc: You posted an error message that says “cannot authenticate”. That’s probably an issue with your SMTP username and password settings, or the server or port you’re using.
Try installing version 0.9.1, does the issue you’re experiencing go away?
http://downloads.wordpress.org/plugin/wp-mail-smtp.0.9.1.zipThere were no changes to the logic, 0.9.2 and 0.9.3 were just bugfix releases. So upgrading shouldn’t have broken any SMTP functionality.
Sorry for the issues you’ve been experiencing. Just seeing these messages now and I’ve pushed a new version 0.9.3 which should address this issue.
I’m not sure why the update triggered this issue as it’s been in the code for some time. I also wasn’t able to replicate it locally, but it might be because I’m using an older PHP version.
Hopefully the issue is now fixed. I’ll be watching this thread for the next few hours in the case of any further issues.
Again, apologies for the issue.
Thanks for the heads up, the depreciation notices need my attention, I’ve been remiss in getting to those. I’ll release an update by the end of the year.
Symmetric encryption is an interesting idea. One of my goals with this plugin is to keep it as light as possible. It really doesn’t do anything other than enable some options already provided by WordPress. When I wrote the plugin I figured that eventually the SMTP options would land in core, but that doesn’t seem to be the case.
I’m not sure if adding encryption would make sense in this plugin, it feels like it might be better suited to a separate plugin. I’d be happy to post a link to folks who are looking for such a feature in the plugin description, and be happy to ensure compatibility between the plugins.
What do you think?
Forum: Plugins
In reply to: [Question and Answer Forum] How to remove ?post_type=question from urlI found this thread searching for a similar issue. I posted my eventual solution here:
http://wordpress.org/support/topic/removing-post_typefoo-from-the-url-for-custom-taxonomiesHope it helps somebody else stumbling upon this thread trying to remove
?post_type=blahfrom their urls.Love & joy – Callum.
To be clear, the plugin doesn’t actually send any email. It simply tells WordPress to send the mail by SMTP instead. There is nothing in this plugin that controls email sending, generates emails, or otherwise. WordPress includes the ability to send emails via SMTP, this plugin just activates that feature. So whatever email issues you are having, it’s most likely they’re caused by something other than the plugin.
This is a very commonly quoted issue, and it’s 100% nonsensical.
Let’s think this through. In order to send an email WordPress needs to know the password. Therefore, we need to store the password so that WordPress can use it later in plain text. So, it’s not possible to encrypt it, secure it, or otherwise hold it “safely” short of some incredibly complex solution which won’t work on shared hosting, would require extensive server configuration, etc.
Thus, as the plugin developer, I have 2 choices. Choice one, I could put add the type=”password” and then the ignorant user thinks, oh awesome, my password is “safe”. But anyone who looks at the source code of the page, or at the /options.php page easily finds the password. Or, I could simply leave the password in plain text as it must be stored anyway.
I’m about to release a new version which makes it clear on the admin page to avoid this issue. Seems like many people don’t bother looking up or thinking through the issue and just complain.
@jmdodd: Is your plugin a sensible starting point to build this feature?
It seems to be bbPress’s biggest missing point for me. I provide plugin support and many users come, post once or twice, and never return. Creating a whole account for that seems like redundant effort. But if there’s no other way…
Forum: Requests and Feedback
In reply to: Old plugins are unfairly blacklisted :-(@ipstenu: Ahh, my bad, you’re absolutely right! I was so impressed by the action on my last post here I thought I’d go around again. I completely forgot I’d already posted on the same topic, apologies.
If it’s a bug, fair enough, makes sense. I’ve pushed version updates to almost all my plugins which qualify by now anyway. I noticed a couple of Matt Mullenweg’s plugins were in the same boat!
Thanks for the confirmation, glad to hear a fix is in the works. 🙂
Forum: Hacks
In reply to: This plugin hasn't been updated in over 2 years.I accidentally cross posted this to the feedback forum, there’s a known bug and it’ll hopefully be resolved at some point. More here:
https://wordpress.org/support/topic/old-plugins-are-unfairly-blacklisted-Forum: Requests and Feedback
In reply to: Hypocrisy of the plugin hosting terms@ipstenu: Awesome, glad to hear something positive has come out of the discussion. I look forward to checking out the changes.
In fairness to WordPress and Automattic in general, the few times I’ve flagged up inconsistencies have generally been met with a positive response and on occasion, positive change. There were still big parts of the code running wp.com / other WP sites that weren’t GPL last I checked, but I dare say it’s a work in progress… 🙂
Forum: Requests and Feedback
In reply to: Hypocrisy of the plugin hosting terms@ipstenu: I think it’s one of these things that only a small minority care about. I think that WordPress holds itself to a higher standard than most, which is a wonderful thing. So anything we can do to further that is a step forward.
Your proposed paragraph sounds like a positive step forward. It’s not an all out opt-in, but I’d say it’s definitely better than at present. 🙂
Forum: Requests and Feedback
In reply to: Hypocrisy of the plugin hosting terms@esmi: Nowhere on the privacy page does it tell me that by installing WordPress, it is going to phone home. It makes only passing reference to “a web service used by WordPress installations to check for new versions of WordPress and plugins.”
I offered practical suggestions about how the phone home could be improved at the time, when it was being introduced. Now, years later, when I discover that WordPress is yet again holding itself to a different standard, I choose to bring it to people’s attention. (Let’s not get into how much of WP.com is not GPL, despite Matt’s campaign that all plugins / themes need be GPL!)
@ipstenu: Strictly speaking, it’s not possible opt-out 100% with a plugin, because in order to activate the plugin, one needs to log into the admin, by which time, WP has already phoned home once. 🙁
You mention that the phoning home behaviour is documented. May I ask which documentation you’re thinking of? I’m guessing it’s covered somewhere on the codex, but I wasn’t aware that users were made aware of this behaviour anywhere during the download / install process. Perhaps I’m mistaken.
Forum: Requests and Feedback
In reply to: Hypocrisy of the plugin hosting terms@esmi: Is that relevant to the discussion? To answer your question, no, I haven’t had a plugin rejected.