Please review your code before release!

Hi,

I understand your side.

But here my side:

I am the only one, no team.

I do the development, support, testing, writing the blog, etc …

This is beside my full-time job and family.

I released the version yesterday at 1:00 am when your mind is not so clear and that was my mistake. I just wanted to fix and release a nice feature.

Other SMTP plugins are premium or have solid companies behind them, for now, I still want to stick the open source spirit but I need the users to be patient even when stuff goes wrong :-).

Hi Yehudah,

Thanks for your fast reply, I’m not blaming you as you are creating free software, which should be highly complimented. I also understand, open source are like a hobby of the developers, for users like us really appreciate the work and hope the open source can be better.

I just want to mention that open source could be better and professional. I didn’t know you are one person and did the great work. Thanks for your work and I’m patient. Don’t worry, I’m not blaming anyone, just to hope open source can be better.

Agree, you can be sure after open eye my eyes in the morning and saw the number of messages my panic level was crazy.

I didn’t wash my face yet!

I’m using plugin auto update and my post-man plugin was auto updated late night

@gbpsports Despite that I would also like to see a more controlled release mechanism for WordPress plugin and theme related updates (that’s only a wish), I would like to tell you one thing:

Even I don’t have the guts, to enable auto updates on a live website. That is a ticking time bomb and you should NEVER do that, because this isn’t the only case, when a simple WordPress plugin or theme update breaks something. There are a lot of such cases.

PS: Some psychos enable this feature for the whole server, in the same time not realizing what harm it could make, and then one day they wake up, and see that 100+ of their websites are not working. Only imagine how many hours are needed to fix such a mess.

• This reply was modified 6 years, 10 months ago by WEBHAUS.
• This reply was modified 6 years, 10 months ago by WEBHAUS.

@webhaus, Thanks for your suggestion, I only enabled minor updates and disabled development update and I have auto backup everyday. Before enable auto update, I also do manual update everyday. For this lesson I learnt maybe need to do backup before manual update everyday, or do you have any good experience to share?

@gbpsports

The way I do these things is:

-) I never use any kind of auto update mechanisms for WordPress related things (as I said previously: It’s a ticking time bomb);
-) Updating WordPress themes and plugins every day surely is an overkill. Updating plugins once a week is enough for me, and for some highly customized websites I’ve even disabled updates at all. (it’s really not a security risk, if you know what you are doing and have proper security measures in place)
-) Usually making a database backup before plugin updates is enough (since you can always revert to older version, if something goes wrong), but for theme – make sure you backup its directory too, before updating it.
-) I try to make these kind of changes in night hours, when there are less people active on websites;

And if we are speaking about critical / highly important websites, then you must always make changes on a working test version (beta version, clone, staging mode, whatever you call it), before actually updating something on the live website. Full backup in this case is a must have, and no auto updates!

@webhaus

Thanks for your tips, it really helps!