narcisgarcia

If the plugin gets the images from CreativeCommons website, then the plugin will depend forever of that remote location to download media, and will not work when CC changes website URLs.

Image locations can be relative and ever be in the same directory and with expected names (at least can be called “cc-license.png” or cclicense[1][2][3].png) and files could be conveniently renamed by the plugin when setting preferences.

Thanks for taking it into account.

An easier way could be to include those images with the plugin package; not to necessarily make a tool to manage new files.
And the URLs simply point to statically placed images in the plugin directory.

Great.
Few options but works.

Is there any <noparse> as <nowiki> tag for WordPress not touches HTML code in posts or pages?

I’ve found this one:
https://www.ads-software.com/extend/plugins/xcloner-backup-and-restore/

but doesn’t seem to distinct sub-sites.

As a multisite administrator, I already have the way to backup all data (DB & filesystem). But I was looking for a solution for my friends who have a weblog inside, easy as the first response I got.

I suspect I need to choose between: wait for a more complete export/import tool in next WP versions, or develop a new plugin.

If 1 site has more that one administrator, it’s normal that any of those administrators can make a backup of the entire site or blog.

This is necessary both in simple-site installation and in multi-site blogs. The only restrictions needed is that the administrators in 1 multisite blog cannot backup data from other blogs in the same multisite installation, and may not also backup the users accounts that have access to multiple blogs.

But the current situation is: no files, no preferences, no plugin options,..

Is necessary to talk about sites (blogs) not users.

A site can have multiple users, and viceversa.

With this last information and exploring filesystem content, I deduce that all attached/accessory files for blog nr.3 are stored together in this directory:
/wp-content/blogs.dir/3/

I’ve discovered with this SQL command:
SELECT * FROM wp_blogs;
That the field “blog_id” can be used to distinct all the tables related to a sub-site.

For example:

SELECT blog_id, path FROM wp_blogs;
+---------+----------------------+
| blog_id | path                 |
+---------+----------------------+
|       1 | /                    |
|       3 | /myfriend/           |
+---------+----------------------+

Then I can list site’s tables:

SELECT TABLE_NAME FROM information_schema.TABLES WHERE TABLE_SCHEMA = "multisitedatabase" AND TABLE_NAME LIKE "wp_3_%";
+-------------------------+
| TABLE_NAME              |
+-------------------------+
| wp_3_commentmeta        |
| wp_3_comments           |
| wp_3_ec3_schedule       |
| wp_3_links              |
| wp_3_options            |
| wp_3_postmeta           |
| wp_3_posts              |
| wp_3_socialslider       |
| wp_3_term_relationships |
| wp_3_term_taxonomy      |
| wp_3_terms              |
+-------------------------+

I suppose these are all the tables to be exported for a complete backup (database part).

I manage a multisite installation (subdirectory based), and need to give a way for each user (1 user owns 1 sub-site, another user owns another sub-site) to backup own contents.

Of course I can backup the entire multisite directory and database, but cannot deliver this backup to “user 1” when also contains data from user 2, 3, 4, etc.

I see that the multisite uploaded files are in /wp-content/blogs.dir/ and I don’t see clear separation between each site correspondence.

Then, is there any way to export easily attached files for published contents?

I understand as user’s data:
– Published texts (Posts, Pages, Comments)
– Attached files (media)
– Site preferences (menus, selected theme, title, etc.)
– Plugin preferences and their custom accessory files

Conclusion: all information and files that single-site administrator could set, write and upload.

Sure, I don’t want to give blog users access to the entire network data; only to their own data to make it restorable on another WordPress installation.

Thanks, very useful.
But I don’t find an export way for site preferences and files.