WordPress Backup • WordPress Help

 Secure Data "title =" Secure Data "width =" 425 "height =" 282 "class =" aligncenter size-full wp-image -6605 "/> </a></p>
<p> Well, we already know that you have to backup regularly, do not you? What happens is that sometimes we forget it, but imagine that you are carrying something and you do not have a recent backup What does it hurt? </p>
<p> Mainly, as we have said several times, we must <a href= make backup – preferably – of two things:

  • the database, which is where the configurations and content
  • the folder wp-content where are the plugins, the themes and the files that you have uploaded.

If you have access to phpMyAdmin on your server you can make backups very easily PhpMyAdmin has an Export function that makes a copy of the entire database, a table, whatever you want.

Yes, if your base data is very large then you should use another backup tool, usually available on the server side, if you have access to systems like CPanel or Plesk.

On the other hand, for the more advanced, you can use SSH, which is already I have spoken, and once you control it greatly facilitates backups, and other actions.

To backup with SSH you just have to access with your data (usually FTP data), move in command line to the folder where you want to make backup and, once there, execute this command:

mysqldump -opt -u dbuser -p dbname> dbname.sql

This replaces the dbuser and dbname with yours. Now all that remains is to compress the backup:

gzip -c dbname.sql> dbname.sql.gz

Once this is done, there is less, but you can also do the previous two steps in just one:

mysqldump -opt -u dbuser -p dbname> dbname.sql | gzip> ficheroresultante.sql.gz

Now you have done the backup of the database. If you did the previous steps well you will have it in a zip and in SQL

The next thing is to compress the folder wp-content :

zip -r wp-content-backup-Dec-3.zip wp-content /

This puts everything in wp-content inside a zip. The modifier '- r' is precisely the one we use to "collect" all the subfolders.

Then we can upload the zip to the backup folder, for example:

mv wp-content -backup-Dec-3.zip ../backups

If we do this from time to time, and do not worry about the commands, you can copy them and paste them in the command window, you will have backup of your site safely.

NOTICE : This publication is from two years ago or more. If it's a code or a plugin it might not work in the latest versions of WordPress, and if it's a news story it might be obsolete. Then do not say we have not warned you.

Loading …

That may also help you:

Features that WordPress 3.0 should include

 wordpress_futuro "width =" 599 "height =" 441 "class =" aligncenter size-full wp-image-6364 "srcset =" https: //ayudawp.com/wp-content/uploads/2009/10/wordpress_futuro.png 599w, https://ayudawp.com/wp-content/uploads/2009/10/wordpress_futuro-500x368.png 500w "sizes =" ( max-width: 599px) 100vw, 599px "/> </p>
<p> Although WordPress 2.9 is soon to be released, we all know that version 3.0 will be a real revolution for the semantic publishing system. integration with WordPress MU that we will see in this version (because, realistically, version 2.9 will not be able to implement it). </p>
<p> I have thought about some features that WordPress 3.0 should include, some of which have been available for a long time in others CMS Here they go: </p>
<p> <strong> Define password and username </strong><br /> By default, WordPress creates the user <code> admin [19] 459013] with a very robust random password, but very difficult to remember. Since version 2.8 a message appears (post-installation) that reminds us to change this password to a friendlier one, but it is an unnecessary step, since we should be able to choose both our password and our username during the installation process. On the other hand, it is almost impossible to change the username <code> admin </code> although there are always some tricks. <br /><span id=
Define friendly URLs
Those of us who have installed WordPress at some time, know that the URLs are of type p? = ID very ugly and unfriendly to users. This is to avoid problems of compatibility with your hosting in case of not having activated mod_rew in Apache or in those extreme cases where your hosting does not allow the creation of a .htaccess . What would be great, is to include the option to change these ugly URLs for a custom ones during the installation process or that we get a message (as in the case of passwords, in version 2.8) reminding us to change them.

Remove compatibility with previous versions
This is a feature that will be added in version 3.0, but I will also mention it. If we eliminate backward compatibility, we will get a much lighter WordPress but just as powerful. More than bad, few use themes of version 1.5, and those who do are missing many wonders that the WordPress 2.7 themes offer us.

Activate / Deactivate post review
For blogs with many users , this feature is great, but when we talk about blogs managed by a single user, the thing is not the same anymore. The post review makes use of our database to save post reviews (worth the redundancy), but if we are a single user, this feature will only occupy a valuable space in our database. There are plugins to erase that character, but there should be an option that allows us to deactivate it if we do not need it. And I think many would be very useful.

Revive option "Activate Gzip compression"
In WordPress 2.5 this option was removed and many users expressed their dissatisfaction. GZip, in simple words, compresses the files on our server, sends them to the user (understand, who wants to view the page) and the browser is responsible for decompressing them: this saves a significant percentage of bandwidth. Now, that option falls on the hosting that we host, and there is no way to activate it from our WordPress unless we use a plugin.

Submenu for "Comments"
Have you noticed that the menu " Comments "has submenus, but has no link to them? This "All", "Pending", "Approved" and "Spam". If you click on "Comments" it will take you to "Everyone" and from there you have to move to the submenu you want. From "All" you see all the comments of your blog, are pending moderation, classified as spam or those that you have already approved, so the idea of ​​a submenu will seem illogical for some, but I'm sure it would be very useful to directly access " Spam "or" Pending "without necessarily having to go through the Desktop or" Everyone ". It would save us click and it would not be a very difficult feature to implement.

Do you have more features that you would like to see in future versions? Comment! Who knows, one of those Matt meets this blog and makes a revision, but we promise nothing 😉

NOTICE : this publication is two years ago or more. If it's a code or a plugin it might not work in the latest versions of WordPress, and if it's a news story it might be obsolete. Then do not say we have not warned you.

Loading ...

That may also help you:

Important news in WordPress 2.8 • WordPress Help

in the that " true " means that it is queued in the footer (" false " is the default option).

When you queue a script in the footer all the dependencies will be added (if they are not already active) and will be launched before the script. Some will be in the header, and others also in the footer. By default only jQuery is thrown in the header but when a script is queued in the header all the dependencais are also thrown in the header. Almost all external scripts will be executed after loading the page so there is no real need to queue the header.

Scripts queued for the cover footer depend on wp_footer () ; is present in the active theme. Unfortunately, this is not the case in all cases, so we will have to publish this novelty so that the developers of the themes as well as the plugins know and can include it.

To make it easier to queue the scripts, you can add two new actions :: "wp_enqueue_scripts" that runs in the header of the cover where the functions is_page (), is_home (), etc., and "admin_enqueue_scripts" are available that runs in the header of the administration layer and can be queued for specific pages.

Another important feature is that all management core scripts are concatenated and compressed before being sent to the browser. This functionality can be easily extended to include scripts added by plugins and use the server cache, although this would require some changes to the server configuration (.htaccess in Apache).

Although compression through PHP can be problematic in some hosts there are several "switches" (constants) that can manage it: define ('CONCATENATE_SCRIPTS', false); disables both concatenation and compression in all scripts. You can also use define ('COMPRESS_SCRIPTS', false); to disable JavaScript compression and define ('COMPRESS_CSS', false); for CSS files. The compression is configured by default to "deflate" since it is faster and uses less server resources. You can also force the gzip with the settings define ('ENFORCE_GZIP', true);

Also, all the main scripts are reduced. All custom scripts are included in two versions: .dev.js is the unreduced scripts, and .js is the reduced version. The constant defines ('SCRIPT_DEBUG', true); will load the .dev.js versions of the scripts making debugging easier.

There are some possible changes: removing the switch COMPRESS_CSS ] and using only COMPRESS_SCRIPTS use compression in "deflate" mode but adding the file header of gzip and use it as "encoded content gzip" since it seems to be more compatible with web servers and proxys (all current browsers have "deflate" support).

In short, a series of internal changes that will surely continue to make WordPress the most advanced CMS and, surely, the most effective.

NOTICE ]: This publication is from two years ago or more. If it's a code or a plugin it might not work in the latest versions of WordPress, and if it's a news story it might be obsolete. Then do not say we have not warned you.

Loading …

That may also help you: