Can Wordpress automatic update harm my website? - wordpress

Recently I got to know that my Wordpress site is automatically updating itself when a new version of Wordpress is available. I know that this automatic feature is available in
Wordpress since sometimes back. But I have some questions about this
1) Can this be risky in any case?
2) Doesn't it a matter the way how we have installed Wordpress? (e.g plugins and security settings)
3) Does Wordpress have a way to recover our website if anything happen?
4) Don't they keep any backup before do the update?
Could you please give me your answers to the above?

I'll answer each of your questions to the best of my knowledge:
1) Can this be risky in any case?
The automatic updates are mostly security updates. Though you can never be 100% sure it doesn't break anything, security updates don't deprecate functions or change much on how the CMS works. This means that nearly every plugin and theme can still use the same functions without issue.
2) Doesn't it a matter the way how we have installed Wordpress? (e.g plugins and security settings)
This ofcourse matters, to some extend. But if a site is working in Wordpress 3.8.3, it will still work in Wordpress 3.8.4. If a site however uses functions that will be deprecated, you might have problems when upgrading from 3.8 to 3.9. However, major updates aren't done automatically, and still need to be done manually, giving you the opportunity to make a backup beforehand.
3) Does Wordpress have a way to recover our website if anything happen?
No, it doesn't. You CAN however turn of the automatic updates. But, as stated at question 1, the risks aren't very big with the security updates.
4) Don't they keep any backup before do the update?
No they don't. It is your own responsibility to keep backups of your website.
I hope this answers your questions. If something is unclear, please let me know in the comments, and I'll look into it for you.

If your themes and plugins use functions from Codex then I think your are much safer. Make sure the plugins and themes are using functions to get directories and URI's through functions defined by Codex, what I mean to say is:
use: get_template_directory_uri();
instead of xyz.com/wp-content/themes or even home_url('/wp-content/themes'); and other things like that.

yes sometime it can create a mess and it won't allow to admin to login.
most command questions asked are
Can't login after automatic update
login failed after wordpress update.
here is a very quick fix for all of them.
http://onl9class.com/solved-cant-login-after-wordpress-update/

Here is all answer of your questions, please check below:
1. Can this be risky in any case?
The automatic updates are good for security purpose but some times it will break our function work in website because some plugin developer will not update own code according to wp updates so it would be good you can manually updates all things after checking plug-ins compatibility with new version.
2. Doesn't it a matter the way how we have installed Wordpress?
No it always matter, because some times wordpress core developer changes the function and they will be depreciate in new version so it would be good, always take backup of website and manually do the updates.
3. Does Wordpress have a way to recover our website if anything happen?
No, but you can install wp plugin and schedule it to take backup in each week.so you can at-least get the latest backup of website. I always use the back up plugin in my websites.
4. Don't they keep any backup before do the update?
No they don't take backup of website. but wp always show notification when you start update please take backup.
Thanks

Related

Is it ok to build an entire site with Advanced Custom Fields?

I'm creating a new site in Wordpress and found out this plugin is very powerfull and ended up creating customs fields for almost every part of the website, I've even placed WYSIWYG editors instead of built in ones because it's easier for me to code my templates.
Is it ok to build an entire site with Advanced Custom Fields or it may become an issue in the future?
Since the webpage is based on static products data, WP or plugins updates will rarely be needed.
Is it ok to build an entire site with Advanced Custom Fields
IMO
It is "ok" to build an entire site with a plugin, but would I recommend it? probably not.
The only reason is because you never know what might happen to your site, if you install a "bad" plugin that breaks ACF plugin.
Or let say for some odd reason they stop providing support for ACF or updating it for whatever reason.
I've seen a lot of apps that have a good support system die out or get bought up by conglomerate companies and they stop public development and support.
WP or plugins updates will rarely be needed.
Regardless you should keep updating your wordpress to current versions, you never know about a security exploits people find, wordpress core dev push out new versions to battle those exploits.
This can apply to plugins as well.
Personally
I like to build things myself without the reliance on plugins in general.
That way I only have the tools that I need, instead of extras that a plugin may come with.
Sometimes a few lines of code can go a long way instead of depending on plugins that may have thousands of lines of code.
Let alone wordpress has a lot of native options baked in that you can rely on or extend as opposed to relying heavily on ACF or any other plugin.

Easy maintainance of database-based CMS sites (WordPress...)?

Well, with entirely file-based CMS you can easily put the whole directory into version control system to record any changes to the site. The synchronization with the server would be also trivial because it would only involve uploading the files via ftp.
With these benefits in mind, I am a little puzzled about the popularity of databases as the only storage mode, even when the CMS in question is meant to be used by amateurs for small websites.
How does your versioning and synchronization workflow looks like?
What kind of simplified versioning/synchronization workflow would you suggest for a casual, non-tech, WordPress user, to give them the benefit of working locally and encouraging them to have a backup of their site?
Most CMS systems nowadays tend to have some or other backup solution in place to help you. Since Wordpress is a CMS for the masses and also caters for the non-tech population, you're sure to find a plugin that can help you with this. I know it's built-in backup solution just backups posts etc. to XML, but even this does a pretty decent job of restoring over a clean wordpress installation and working fine.
But I found this plugin (which works for Wordpress and Joomla) by asking Google, which most probably is the answer to your question: XCloner
Also in terms of workflow, specifically for Wordpress, don't give the user Admin privileges, but editor or contributor or something, so they can still edit content, etc. but not make changes that could mess up the CMS itself. And maybe this XCloner plugin can do some kind of recurring backup or something. Otherwise, I suggest you move to a LAMP stack hosting environment where you can at least have cron jobs setup to backup your databse and files regularly. Most hosing companies do this in any case at no cost.
Wordpress also keeps revisions of all posts and pages, so if a user doesn't like an update they've made, the full revision history is available. Be sure to check screen options at the top to see that Revisions is checked, if you aren't seeing this option. Kind of a nice built-in.
Can also (depending on host) have scheduled database/file backups through cPanel, in addition to scheduled database backup plugins through WordPress. Some will save remotely or even email the database out.

new wordpress design over an existing complicated one?

Hey folks, I got a project from a firm program out a Wordpress design. 80% into it I learn that the client already have an existing one, a robust one, with subsrciptions, blogs, forums, newsletter mailers and so on. Turns out there is a discrepancy bettweent design and old wp structure which I will work on resolving.
I have been developing in on my own server for the time being.
At this point I am not clear on what the strategy should be.
1.) Export out the current wp site out to a different server, duplicate it and then reskin/rework the frame work.
2.) The firms hope was that I would be able to go in and add a new theme, but am not convinced that doing this live will be a good idea since I am using a different theme so all the hooks will be different then the current one.
3.) There is already a large amount of users etc that have signed up to the existing newletter, forum etc. Not sure how to carry this forward?
Any insights are greatly appreciated.
Definitely make a copy of the existing environment. Check it into a version control system (if it's not already the case) and work on that.
Try to put all your work into a new theme: That will make installing the changes on the production server super-easy.
Be careful about any notifications and pings that your development copy may send to the outside world. Be especially careful about the newsletter.

Etherpad and Wordpress, possible?

I recently stumbled upon Etherpad, it's a collaborative writing tool
http://code.google.com/p/etherpad/ - main project page
online Examples:
http://piratepad.net/
http://ietherpad.com/
http://typewith.me/
I want to add this engine somehow to my wordpress and let people collaborate their posts,
I'm wondering if it has been done before and/or does it take more than
shared hosting (that is what I have) to do it [server capabilities or what-not] ?
In general, I think this is a complicated way to go about it. Also, Etherpad allows some very basic font formatting but no images and such things you might want to include in a blog. Instead I suggest looking for some Wordpress plugin for collaborative writing, and you might find something less "real-timey" but perhaps good enough.
Or if you really want to try with Etherpad:
Etherpad needs lots of memory (RAM) to run. A typical configuration is 1 GB, but it might be possible to get by on 128MB dedicated to Etherpad. This means you'll need at least 256MB in total for a first attempt. Your shared host also needs to have a Java server installed (typically Jetty) and some proxying server (typically nginx). All in all, you have some work ahead of you in just getting Etherpad up and running. After that, integrating into the Wordpress blog editor. If/how this can be done, I don't know. I'd probably do a client-side javascript-hack to get the Wordpress textarea or richtext editarea to update from the Etherpad readonly view, which is the only place where you can get the contents of a pad as more-or-less raw source text.
A simpler solution would be to just add an Etherpad page through an iFrame. See this post for example - http://www.knowledgepolicy.com/2010/02/embed-etherpad-into-blogpost-or-on-any.html
In theory it's possible to replace Wordpress' editor with an Etherpad Lite iFrame. Etherpad now allows image/font editing and table support as plugins.
Java is no longer required for Etherpad, NodeJS however is.
Here is a plugin that is in development that does what you want - however development seemed to stop in early 2012.
http://participad.org/ seems to be the best solution in this space to date. I haven't tested it on my own site, but they have an at least partially-working demo online.
Yes! It is possible. WordPress now has a plugin. The plugin has three modules which enables an Editor in dashboard and let you edit via front-end.
You can find more details on their FAQ page.

Drupal: xmlsitemap file is not generated

I have chosen XMLSiteMap module from the most popular usage statistics on Drupal site,
so I assume the module is not too buggy. But the map file is absent.
I've installed this module on my Windows machine into drupal/sites/default/modules.
I've activated all the submodules of XMLSiteMap in admin menu.
Per docs, I've also run cron.php manually to create sitemap.xml in drupal/sites/default/files - but it's just not present there even when second re-install.
How can I force to create sitemap.xml?
(also tried with and w/o clean URLs - still no help).
Also, if there any good reliable alternative for this module?
Are you sure you've installed it properly? Please check the Status report (admin/logs/status in Drupal 5, admin/reports/status in Drupal 6) to ensure that you've got everything right.
It's possible that you haven't set the permissions of sites/default/files properly yet for example.
I'm not sure if this will help you, but if you are looking for an actual created sitemap.xml file rather than navigating to it in the browser I don't believe one is created by the module. I think the module creates a menu callback to create the sitemap file, so a request for sitemap.xml is handled by Drupal's menu system, rather than creating an actual file. There will however be a cached version in sites/default/files/xmlsitemap.
Apologies if this is an oversimplification of the question asked.
I have not had any problems with the reliability of the module myself.
Also make sure you have the latest version installed, it just came out yesterday:
http://drupal.org/project/xmlsitemap
Also, see this issue, seems related to your problem:
http://drupal.org/node/458546
I'd probably recommend trying the 6.x-2.x branch which I've been rewriting to kind of solve all the annoying bugs and architectural problems of the 6.x-1.x branch. It's currently incomplete, but it works for nodes and menu items currently. Taxonomy terms and user profiles will be added soon.
You can find the link to it on the project page. Sorry I can't link since I'm a new user. :)
Running the CRON worked for me:
/admin/reports/status/run-cron

Resources