Jump to content


Backup Buddy & Woocommerce

Woocommerce backup buddy digital downloads

This topic has been archived. This means that you cannot reply to this topic.
3 replies to this topic

#1 Guest_Karen_*

Guest_Karen_*
  • Guests

Posted 09 December 2013 - 09:21 PM

Hello,
I'm developing a woocommerce site for digital downloads on a subdirectory right now. Each digital download has a distinct file path. Will Backupbuddy adjust the download file path for my digital files when I move the site to the root of the domain?
Thanks so much for your time,
Karen


#2 Jeremy Trask

Jeremy Trask

    Moderator

  • Moderators
  • Others: All Plugins, Builder, Members, Toolkit
  • 11,803 posts

Posted 10 December 2013 - 08:05 AM

Hi Karen

Thanks for your interest in BackupBuddy.

Provided the path details are stored in the database in a standard format as file paths are usually stored in the database (no private encoding in plugin specific formats) and the file path is an absolute path (starting from the filesystem root) then a migration would be able to change such paths. This will not be done if paths are not stored as above.

Just to check that when you say file path you mean an actual file path? Alternatively if you mean as a path appended to the site url then these too can be changed but the stored url must be an absolute url.

These kind of things can always be fixed up after a migration if the data storage isn't done in a standard recommended manner.

In general if you are developing a site it's easier to do it as a subdomain rather than as a subdirectory installation because there can be issues with things like relative paths and urls whether these be stored in the database or sometimes within files like css files.

Not to discourage you from using BackupBuddy but if you currently have a site in a subdirectory installation, e.g., the site url is like http://mydomain.com/main/ or whatever then you do also have the option of leaving the installation where it is and following WordPress Codex instructions for making a few tweaks to config to have the site virtual content such as a pages/posts appear to be served out of http://mydomain.com/ whilst "real" content such as css files, media files etc. would still be served out of http://mydomain.com/main/ - generally it doesn't matter what such urls are provided the page/post type urls are the simple domain url with no additional relative path - just an idea to consider.

Regards...jeremy

"Everything will be all right in the end. If it isn't all right yet then it isn't the end."


#3 Guest_Karen_*

Guest_Karen_*
  • Guests

Posted 11 December 2013 - 09:24 AM

Hi Jeremy,

I really appreciate the time you took to answer my question! Just to be clear, when I'm setting the file path for a digital product download, it is currently:

http://mydomain.com/dev-wp/wp-content/uploads/woocommerce_uploads/xxx/xxxxxx3.tif.zip

When I move the site out of the subdirectory-- /dev-wp/ -- I want to make sure that the link will also be updated so that the /dev-wp/ will be gone and it will just be http://mydomain.com/wp-content/uploads/woocommerce_uploads/xxx/xxxxxx3.tif.zip


I'm adding hundreds of images, and I just want to make sure that when i migrate my site from the sub-directory to the root directory that I won't have to go in and change every file download path by hand. Does that make sense?

Thanks again for your time,
Karen



#4 Jeremy Trask

Jeremy Trask

    Moderator

  • Moderators
  • Others: All Plugins, Builder, Members, Toolkit
  • 11,803 posts

Posted 12 December 2013 - 05:08 AM

Hi Karen

Yes, update of absolute urls/links stored as above in the database is part of the migration process. We would normally not call this a file path as that can be confused with meaning an actual file path such as /home/account/public_html/wp-dev/directory/file.txt (which when stored in the database are also handled by migration).

Technically the "relative" part of the url and the actual file path part that is relative to where the site is rooted can be different, e.g., these can refer to the same thing:

http://mydomain.com/products/file.txt
/home/account/public_html/wp-dev/wp-content/uploads/latest_products/file.txt

since the first just refers to a resource and that reference can be mapped by the server (when appropriately configured) to reference a file within the site with any file path.

BTW, the WordPress Codex article about operating a site out of a subdirectory are here: http://codex.wordpress.org/Giving_WordPress_Its_Own_Directory#Using_a_pre-existing_subdirectory_install

Regards...jeremy

"Everything will be all right in the end. If it isn't all right yet then it isn't the end."