Description: This security plugin detects and backup wordpress database and WP CONTENT folder
automatically in function to frequency time that is adjusted in admin panel, without need to
back up them manually every time, these backed up automatically when visitor access to your
web site pages or when you get access to your WordPress administrator interface, so this plugin
useful in case you have loosed or modified your databases either deleted accidentally or
hacked, so you have a chance 100% to recover them safely!
A few notes about the sections above:
Stable tag should indicate the Subversion “tag” of the latest stable version, or “trunk,” if you use /trunk/
for
stable.
Note that the readme.txt
of the stable tag is the one that is considered the defining one for the plugin, so
if the /trunk/readme.txt
file says that the stable tag is 4.3
, then it is /tags/4.3/readme.txt
that’ll be used
for displaying information about the plugin. In this situation, the only thing considered from the trunk readme.txt
is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk readme.txt
to reflect changes in
your in-development version, without having that information incorrectly disclosed about the current stable version
that lacks those changes — as long as the trunk’s readme.txt
points to the correct stable tag.
If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where
you put the stable version, in order to eliminate any doubt.
You may provide arbitrary sections, in the same format as the ones above. This may be of use for extremely complicated
plugins where more information needs to be conveyed that doesn’t fit into the categories of “description” or
“installation.” Arbitrary sections will be shown below the built-in sections outlined above.
Ordered list:
Unordered list:
Here’s a link to WordPress and one to Markdown’s Syntax Documentation.
Titles are optional, naturally.
Markdown uses email style notation for blockquotes and I’ve been told:
Asterisks for emphasis. Double it up for strong.
<?php code(); // goes in backticks ?>