You can redesign a WordPress website without interrupting visitors by treating the live site as production, building an isolated staging clone, testing the redesign there, reconciling content changes, and deploying with a tested rollback plan. The critical rule is that staging is a workbench, not a backup: keep an independently restorable production backup before every deployment.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
What a safe WordPress redesign looks like
A safe redesign separates creative work from production traffic. Visitors, search engines, forms, orders, memberships, and scheduled jobs continue using the live site while you change the theme, templates, CSS, plugins, and settings on a private copy. You publish only after the copy passes a defined test list and you have a way to restore the previous release.
As an Amazon Associate I earn from qualifying purchases.
The workflow has four control points:
- Inventory: document what the live site contains and what can be affected.
- Recovery: create and verify a complete files-and-database backup that can actually be restored.
- Isolation and testing: clone the site to a protected URL and prevent test actions from reaching real services.
- Controlled release: reconcile new production content, deploy during a low-traffic window, run smoke tests, and monitor until the release is accepted.
WordPress Developer Resources states: “Before making any modifications to your website, verify that you have either utilized a staging environment or taken an appropriate backup of your site.” For a redesign, use both.
1. Inventory the live site before creating a clone
Do not begin by changing the theme. First make a written inventory of the production system. This becomes your scope document and your post-launch test plan.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
Domains, URLs, and redirects
- Record the primary domain,
wwwand non-wwwbehavior, HTTP-to-HTTPS redirects, alternate domains, and language or regional domains. - Export the current redirect rules and note redirects handled by the server, a plugin, or a reverse proxy.
- List important landing pages, campaign URLs, feeds, XML sitemaps, attachment URLs, and any hard-coded links in templates.
WordPress components and custom code
- Record the WordPress version, active theme, child theme, parent theme, and every active and inactive plugin.
- Note each component’s version, license status, update history, and whether it is essential to forms, SEO, caching, security, membership, or commerce.
- Locate custom code in the child theme, must-use plugins, snippets, server configuration, scheduled tasks, and deployment scripts.
Data and integrations
- List forms and their delivery destinations, SMTP settings, CRM connections, newsletter lists, and webhook endpoints.
- Document payment gateways, tax and shipping services, subscriptions, memberships, customer accounts, and order workflows.
- Record analytics, tag managers, advertising pixels, search-console verification, heat-map tools, uptime monitors, and error reporting.
- List scheduled jobs such as backups, imports, product feeds, email digests, publishing queues, and cron tasks.
Users, permissions, and search settings
- Record administrator, editor, author, shop-manager, and custom roles. Note which accounts require access during the redesign.
- Capture permalink settings, reading settings, robots controls, sitemap behavior, canonical rules, structured-data settings, and no-index exceptions.
- Identify pages that must remain private, membership-protected, password-protected, or excluded from search.
Save the inventory with a date and the current release identifier. If a regression appears later, you will know what changed.
2. Create a backup you can restore, not merely an export
Before cloning or updating anything, create a complete production backup. WordPress migration guidance calls for the WordPress directory, images, plugins, other files, and database to be backed up. A database-only export cannot restore uploaded media, theme files, or custom code.
What to include
- The complete WordPress directory, including
wp-content/uploads, themes, plugins, must-use plugins, and configuration files. - A full database export containing posts, pages, revisions, settings, users, memberships, products, orders, and metadata.
- Server-level configuration that affects redirects, PHP settings, cron, caching, and security headers.
- Encryption keys, salts, and deployment notes stored securely rather than inside a public web directory.
Verify the recovery path
- Store the backup outside the production server and retain the timestamp, WordPress version, PHP version, and database engine.
- Check that the archive opens and that the database dump contains expected tables and recent records.
- Restore a copy to an isolated environment or use your host’s documented restore procedure. Confirm that the site loads, users can authenticate, media appears, and representative forms work.
- Write the rollback steps, credentials required, estimated restoration sequence, and person authorized to make the decision.
Never call the staging clone your backup. A staging database can be deleted, overwritten, or accidentally connected to live services. Keep the independent production backup until the redesign is accepted and the retention period has elapsed.
3. Build an isolated staging environment
Staging should have its own URL, database, credentials, and operational controls. It may be a host-provided staging environment, a separate server, or a manually cloned installation. The implementation can vary; the isolation requirements do not.
Clone files and database
- Create a new staging URL and an empty database with credentials different from production.
- Copy the production files and import the database into staging using the host’s documented cloning process or a migration tool.
- Update the staging configuration so it points only to the staging database and file paths.
- Confirm that the login URL, media paths, and administrative email addresses are correct for staging.
Tools such as WP STAGING document cloning, login protection, no-index handling, and migration features. If you use a managed host, confirm exactly whether its “push” operation replaces files, the database, or both.
Block search indexing and public access
- Require authentication at the web-server or staging-tool level, not only a WordPress password-protected page.
- Enable the staging system’s no-index control and verify that the generated robots behavior and page-level directives prevent indexing.
- Do not rely on robots rules alone for confidential data; authentication is the actual access barrier.
- Use a staging administrator account with a unique password and remove unnecessary production administrators.
Disconnect real-world side effects
A clone contains production credentials unless you deliberately replace them. Before anyone tests it:
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
- Redirect forms to a test mailbox or disable sending.
- Use payment-provider sandbox credentials, or disable checkout and subscription actions entirely.
- Point webhooks, CRM callbacks, shipping, tax, and inventory services to test endpoints.
- Disable analytics and advertising tags, or send them to a separate test property.
- Disable publishing emails, password-reset emails, scheduled imports, and background jobs that could contact customers.
- Disable or reroute cron so a staging import cannot alter production data.
Place a visible “STAGING” marker in the admin bar and, where appropriate, in the page header. This simple control prevents a tester from confusing the two environments.
4. Redesign incrementally on staging
Make changes in small, documented batches. Record the date, person, component version, and purpose in a change log. Updating everything at once makes it difficult to identify the cause of a failure.
Theme and template work
- Use a child theme or a version-controlled custom theme so updates do not erase changes.
- Build reusable templates for the homepage, posts, pages, archives, search results, 404 pages, and any commerce or membership views.
- Keep content separate from presentation. Avoid placing essential copy or links only in CSS backgrounds or theme files.
- Check typography, color contrast, focus states, keyboard navigation, image alternatives, and readable error messages as you build.
Plugin and platform updates
- Update one related group at a time, beginning with a staging backup.
- After each update, test login, editing, media uploads, forms, search, and any feature owned by that plugin.
- Record version numbers and configuration changes. A version record is essential when you need to roll back one component rather than the entire release.
Content and layout changes
Use representative content, not only a polished demo page. Include long headlines, short titles, galleries, embedded video, captions, tables, quotations, code blocks, missing images, and posts with unusual metadata. Test the templates that generate those pages rather than manually checking only the homepage.
5. Test the redesign as a release candidate
Use a written test matrix and mark each result. WordPress maintenance guidance specifically calls for checking links, search visibility, pages, and CSS; a redesign also needs functional, responsive, data, and integration tests.
Free tools Windows power users keep installed
One-click scans. No signup required.
| Area | What to test | Pass condition |
|---|---|---|
| Navigation | Header, footer, menus, breadcrumbs, mobile menu, skip links, pagination | Every intended destination opens without a loop, 404, or blocked focus state |
| Templates | Homepage, posts, pages, archives, search, 404, author, category, tag, custom post types | Correct content, metadata, images, and calls to action appear at each breakpoint |
| Responsive layout | Phone, tablet, laptop, wide desktop; portrait and landscape | No overflow, clipped controls, unreadable text, or accidental horizontal scrolling |
| Forms | Required fields, validation, spam controls, success and failure states, notifications | Test submissions reach the designated test destination and do not email real users |
| Authentication | Login, logout, password reset, role permissions, protected content | Each role can do only what it should, and session behavior is correct |
| Media | Uploads, thumbnails, captions, galleries, lazy loading, missing-file behavior | Images and videos load with appropriate dimensions and accessible alternatives |
| Search and SEO | Index controls, canonicals, titles, descriptions, structured data, XML sitemap | Staging remains no-indexed while metadata and markup are valid for launch |
| Performance and cache | Page cache, object cache, minification, lazy loading, cache invalidation | New assets appear after changes and no stale layout remains |
| Integrations | Analytics, webhooks, CRM, payment sandbox, shipping, imports | Only test endpoints receive events; payloads and retries behave as expected |
| Redirects | Changed slugs, old campaign URLs, HTTP/HTTPS, host variants | Important old URLs resolve once to the correct destination without chains |
Test real journeys
- New visitor: arrive on a landing page, navigate to an article, use search, and submit a form.
- Returning user: log in, view protected content, update a profile, and log out.
- Editor: create a draft, upload media, preview it, schedule it, and verify the resulting layout.
- Commerce or membership user: use only sandbox or disabled transactions, test entitlement changes, and confirm that no live order or customer record is created.
Check browser console errors, server logs, PHP warnings, broken links, missing fonts, and mixed-content warnings. Test in more than one browser and on an actual phone; a desktop-width emulator will not reveal every touch and viewport problem.
6. Change URLs without corrupting WordPress data
Moving from a staging URL to the live domain requires more than changing the two site-URL fields. URLs can appear in post content, options, metadata, widgets, serialized PHP values, and plugin tables.
Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
WordPress warns that blanket database replacement can damage serialized values. Do not run a blind SQL string replacement across every column. Use a serialization-aware migration tool. WP-CLI’s wp search-replace handles PHP serialized data and supports dry runs, table selection, exports, and multisite operations.
A cautious WP-CLI sequence
- Take a fresh production backup immediately before the URL change.
- Run a dry run against the staging database to see the number of replacements without writing changes:
wp search-replace 'https://staging.example.test' 'https://www.example.com' --all-tables --dry-run - Review the tables and counts. Exclude tables that belong to an intentionally separate system, and use the multisite options when operating a multisite network.
- Run the replacement only after confirming the old and new schemes, hostnames, and trailing-slash conventions.
- Flush rewrite rules, clear application and object caches, regenerate critical assets, and test media, forms, feeds, canonical links, and redirects.
The domains in the example are placeholders for the actual staging and production addresses. Substitute your real values; do not paste a production URL into a command until you have verified the target database.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
7. Reconcile content before deployment
The most dangerous “push to live” mistake is replacing the entire production database with an older staging database. While the redesign was being built, production may have received new posts, comments, users, orders, products, memberships, form entries, or settings.
Choose a data strategy
| Situation | Safer approach | Risk to control |
|---|---|---|
| Mostly static site with a short content freeze | Announce a freeze, stop publishing, take a final backup, and deploy the approved database and files | Anything created after the freeze can be lost if it is not recorded |
| Active editorial site | Deploy theme, plugin, and media changes while keeping the live database; migrate only required options or content | New templates must work with production content and settings |
| Commerce or membership site | Keep live users, orders, products, subscriptions, and transactions in production; deploy code and selectively migrate configuration | A full database replacement can erase or overwrite customer and transaction records |
| High-volume or regulated data | Use a documented, selective migration with a tested maintenance window and approval from the data owner | Partial migrations can create duplicate, missing, or inconsistent records |
WordPress.com warns that staging database synchronization can replace the destination site’s user list and commerce data and recommends a backup before synchronization. Treat any tool’s “sync” or “push” button as a database operation until its scope is explicitly confirmed.
Prepare the delta
- Compare staging and production content created or changed after the clone date.
- Export or record new production posts, users, orders, products, form entries, and settings.
- Decide which environment is authoritative for each data type and document that decision.
- Freeze publishing and administrative changes for the agreed window, or use a selective migration that preserves live records.
- Take the final production backup only after the freeze is in effect.
8. Deploy during a controlled maintenance window
Choose a low-traffic period based on your audience, transaction pattern, and support coverage. Tell editors, customer-service staff, and stakeholders when publishing and checkout will be paused and how they will be notified when the site is available.
- Confirm the release identifier, approved change log, tested backup, rollback procedure, and person authorized to abort.
- Put the live site in a short maintenance mode only if the deployment requires writes to be paused. Keep the period as brief as possible.
- Disable or pause production cron and external jobs that could write during a database or file migration.
- Deploy the approved theme, child-theme, plugin, media, and configuration changes using the same method tested in staging.
- Apply only the planned database or content migration. Do not use a full staging database overwrite unless the content freeze and data review explicitly support it.
- Update URLs with a serialization-aware tool, flush rewrite rules, and purge page, object, CDN, and browser caches as appropriate.
- Restore production credentials and integrations; keep staging credentials, test endpoints, analytics, and no-index controls isolated.
- Run smoke tests on the live domain before removing maintenance mode: homepage, one representative page per template, navigation, search, login, a form, media, redirects, and any critical transaction path.
- Remove maintenance mode, notify stakeholders, and record the exact release time and actions taken.
9. Monitor the live release and keep rollback ready
Deployment is not complete when the homepage opens. Monitor the site closely through the first traffic cycle and the next scheduled jobs.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
- Review web-server, PHP, WordPress, security, and integration logs for new errors.
- Check uptime and response times from outside the server.
- Submit forms and verify delivery without creating duplicate notifications.
- Confirm that analytics receives the intended production events and that staging traffic is not mixed into reports.
- Watch transactions, subscriptions, customer accounts, inventory, and fulfillment for failures or duplicates.
- Inspect redirects, canonical URLs, robots behavior, sitemap generation, and search-console alerts.
- Verify cache purges and test a changed asset from a fresh browser session.
When to roll back
Roll back when a critical journey is broken, data integrity is uncertain, transactions are failing, users cannot authenticate, or error rates rise beyond the agreed threshold. Do not keep patching a release while unknown writes continue.
- Enable maintenance mode and stop scheduled jobs or integrations that could add more inconsistent data.
- Preserve logs and record what happened, when it began, and which data was written.
- Restore the independently verified production backup or redeploy the previous release using the written procedure.
- Recheck login, forms, transactions, redirects, and the most important templates.
- Notify stakeholders that the previous release is active, then investigate on staging rather than directly on production.
Retain the old backup and rollback notes until the new release has passed the agreed acceptance period and all critical jobs have run successfully.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to choose a staging approach
Compare approaches by control rather than by a feature checklist. The right choice depends on how much live data changes and who will operate the deployment.
| Approach | Strengths | Questions to answer before use |
|---|---|---|
| Managed hosting staging | Usually provides cloning, access protection, backups, and a guided push process | Does push replace files, database, or both? Can you exclude users, orders, and other live tables? How are cron and email isolated? |
| Staging plugin such as WP STAGING | Convenient cloning, login protection, no-index handling, restore, and migration features | Where are backups stored? Is the migration selective? What happens to serialized data, multisite tables, and external credentials? |
| Developer-managed environment with WP-CLI | Fine-grained control over table selection, dry runs, exports, URL replacement, and scripted releases | Who owns access, backups, secrets, monitoring, and the tested restore procedure? |
| Manual server clone | Maximum infrastructure control and repeatability for experienced teams | Are web-server rules, PHP extensions, permissions, cron, cache, mail, and database versions equivalent to production? |
Regardless of approach, require separate credentials, no-index defaults, integration isolation, a verified backup, a documented data strategy, and a rollback path.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Common failure modes and fixes
Staging appears in search results
Remove public access, enable no-index controls, inspect page directives and robots behavior, and request removal if a staging URL has already been indexed. Authentication is more reliable than a robots rule for preventing access.
Test emails reach real customers
Replace SMTP and notification settings with a test mailbox, disable outbound mail, and test a form after the change. Check scheduled jobs as well as manual submissions.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
A push erases new orders or users
Stop the deployment, restore the last safe backup if data was overwritten, and compare the clone date with production activity. Use a selective migration or a controlled content freeze instead of replacing the live database.
Images or widgets break after the domain change
Run a dry-run, serialization-aware URL replacement; inspect attachment metadata, widget settings, CSS, and page-builder fields; then clear caches and regenerate derived assets.
Recommended Free Tools
Only some pages have the new design
Check template hierarchy, child-theme overrides, custom post-type templates, cached HTML, and CDN invalidation. Test representative content rather than assuming the homepage represents every template.
Forms work in staging but not production
Verify production credentials, allowed callback URLs, webhook secrets, DNS, CAPTCHA keys, and mail delivery. Submit a controlled live test and confirm receipt without sending duplicate notifications.
Redirect chains or loops appear
Compare server rules, WordPress home and site URLs, plugin redirects, and proxy rules. Keep one canonical redirect path from each old URL to its final destination.
Quick Recap
Reusable launch checklist
- Live domains, redirects, themes, plugins, custom code, integrations, analytics, cron, roles, and data are inventoried.
- A complete files-and-database backup is stored separately and its restore path has been verified.
- Staging has a separate URL, database, credentials, authentication, and no-index controls.
- Email, payments, webhooks, analytics, imports, cron, and other side effects are disabled or redirected to test systems.
- Changes are recorded with versions and tested incrementally.
- Navigation, templates, responsive breakpoints, forms, login, permissions, media, links, search controls, structured data, redirects, caching, and integrations pass.
- URL migration uses a serialization-aware tool with a dry run and reviewed table scope.
- Production content, users, orders, products, and memberships created after cloning are reconciled.
- A final production backup exists immediately before deployment.
- The maintenance window, release owner, smoke tests, monitoring, and rollback trigger are written down.
- Post-launch logs, uptime, forms, transactions, analytics, indexing, redirects, and error rates are monitored.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
