পণ্যের অংশে চলে যান
LCPanelলাইসেন্স সেন্টার প্যানেল
BXP BoxPuff টি অধ্যায়

BoxPuff ডকুমেন্টেশন

YetiShare মাইগ্রেশন

YetiShare 5.x / 6.x সাইট BoxPuff-এ নিয়ে আসে - পাসওয়ার্ডসহ ইউজার, প্যাকেজ, সার্ভার, ফোল্ডার, ফাইল, পরিসংখ্যান, শেয়ার - একটি ফাইলও কপি না করে; পুরনো প্রতিটি লিংক চালু থাকে। ফ্রি।

প্লাগইন হালনাগাদ ৬ নভে ২০২৬ ২৮ / ৫০

The YetiShare Migration plugin brings a running YetiShare 5.x or 6.x site into BoxPuff: users (their passwords keep working), account packages and their prices, file servers, folders, files with every stored copy, download statistics, shares, abuse reports, banned addresses and payments. The files themselves are not copied - BoxPuff's local server is pointed at the old files/ folder - so a site with terabytes moves in minutes, and every old link keeps working: short URLs, folder hashes and share hashes are carried over as they are.

Who it is for

Anyone leaving YetiShare for BoxPuff. BoxPuff only reads the old database, so the old site stays untouched until you switch the domain over, and the import can be run again and again while you rehearse.

Switching it on

YetiShare Migration is free and works with every licence; a fresh install switches it on. Otherwise open Admin → Extensions → Plugins (Manage Plugins) and switch it on. Its page appears under Extensions as YetiShare Migration (/admin/plugin/yetishare-migration). Switching it on makes the table bp_ysm_map, which remembers every old id and the new one it became.

Before you start

  1. Install BoxPuff (Installation) on the same server as the old site, or anywhere that can reach its database and its files/ folder. A database on another server must allow BoxPuff's server in (cPanel: Remote MySQL).
  2. Have the old _config.inc.php to hand for the database details.
  3. Make the BoxPuff admin account with the same username as your YetiShare admin if you like: the migration links it to the old row instead of overwriting it.

The settings card: The old YetiShare database

  • Database host, Port, Database name, Database user, Database password (leave empty to keep the saved one), Table prefix (normally empty).
  • Old files/ folder - the full server path of the old site's files/ folder, e.g. /home/user/public_html/files/. BoxPuff reads the files from there; nothing is copied. Leave it empty when BoxPuff is installed in the same folder as the old site.
  • Old site URL - remembered for your records.
  • Rows per step (300, 50 to 2000) - how many rows one request imports. Lower it on a slow host.

Save & test the connection connects read-only, checks that the YetiShare tables users, user_level, file, file_folder and file_server exist, and fills the plan.

The plan

A table of every step with the old table it reads, how many rows it holds, and how many are imported so far:

StepOld table
Site settingssite_config (site name, e-mail settings, password policy and the other settings that have a BoxPuff equivalent)
Account packagesuser_level
Package pricinguser_level_pricing
File serversfile_server
Usersusers
Foldersfile_folder
Filesfile (and each file's stored copies)
Download statisticsstats (the last 400 days)
Sharesfile_share (with their items)
Abuse reportsfile_report
Banned IPsbanned_ips
Paymentspayment_log
Rewards (plugin)every table whose name contains reward (see below)
Recounts- (storage used, file counts, server totals)

Both naming styles of YetiShare (camelCase in v4/v5, snake_case in v6) are understood. A table the old site does not have is marked missing and skipped.

Running it

Start the import runs batch after batch through POST /plugins/yetishare-migration/run (admin and CSRF-protected; each call works for about six seconds and answers the progress). The bar fills, the status line names the step, and the log under it lists what each batch did. Pause stops after the current batch; the button then reads Continue the import. Start over clears the progress (not the imported rows) and begins at the first step. Closing the browser also just pauses it.

Running again updates rows imported before instead of duplicating them, thanks to bp_ysm_map and the legacy_id columns on users, files, folders and servers. So you can rehearse today, let the old site run for another week, and run the import once more on the night of the move to pick up the new users and files.

What comes across, and how

  • Users keep their username, e-mail, package, expiry and their password hash (bcrypt, md5 or sha1); the hash is re-made on their first sign-in. Your installing admin is linked, not replaced.
  • Packages map onto BoxPuff's package types (free, paid, moderator, admin, non-user); free and trial packages get a 10 second countdown.
  • File servers: the old local server becomes (or maps onto) BoxPuff's local server with its storage path set to the old files/ folder; Flysystem-style bucket servers become Amazon S3 servers with the keys from the old server config. Artifact paths like 9c/9cfc… are kept, so no byte moves.
  • Files and folders keep their short URL, folder hash, privacy, keywords and minimum level to download (mapped onto the package). Site Settings → File Manager → Support legacy folder urls keeps the old numeric folder addresses answering too. The ~i and ~s suffixes on file links are handled by BoxPuff's file page already.
  • Shares keep their hash; reports, bans and payments come across for your records.

The Rewards step

YetiShare's rewards plugin names its tables differently from one version to the next, so this step does not look for fixed names. It takes every table of the old database whose name contains reward, reads each by its columns and imports into the tables of BoxPuff's Rewards Program plugin:

  • a row with a user, an amount and a payment method or payment details (or a table with "payout" or "request" in its name) becomes a payment request, marked paid, cancelled or pending from its status and noted Imported from YetiShare;
  • a row with a user, a file and an amount becomes a download earning, already cleared;
  • a row with a user and a balance becomes (or adds to) the member's totals, with what was paid.

Rows whose user was not imported are skipped, and a row imported once is not imported twice when you run the migration again. The step needs the Rewards Program plugin switched on in BoxPuff (it provides the tables) - premium, so it needs the rewards addon; without it the step does nothing. The plan shows the step as present when such tables exist and lists their names and row count.

After the move

  1. Point the domain at BoxPuff (or swap the folders) and check a few old links.
  2. Open Infrastructure → File Servers and press Test on the local server; its statistics refresh with the cron.
  3. Switch on the plugins you need - File Previewer will make thumbnails for the imported pictures over time.
  4. Leave the plugin on until you are sure you will not run it again; then switch it off. The mapping table stays.

Known limits

  • Rewards come across in the shape described under The Rewards step, recognised from the column names, so look over the totals on the Rewards overview after the run. The old plugin's rates and settings are not imported: set them again in Rewards Program.
  • File, folder and share access passwords are plain md5 in YetiShare; they are carried over in a form BoxPuff can check and re-hashes on the first correct entry.
  • Download statistics older than 400 days are left behind to keep the move short.
এটি কি কাজে লেগেছে?
এই অধ্যায়টি শেয়ার করুন