Digital Pacific or WP Hosting for a seasonal WordPress festival?

The season ends, the posters remain

An Australian community festival prepares its programme in WordPress, opens registration, then publishes a report. The team plans four paid months: preparation, the event and a margin for checking closure. Posters and partners already link to the programme page. Visitors will find them after the last session. Hosting must therefore run WordPress during the season and keep the correct addresses readable once the subscription stops.

In this case, information that remains useful includes the dated programme, organiser contact details and a public report. Forms, accounts and registrations must no longer accept new data after closing. A small static archive of prebuilt pages is sufficient if it responds on the same domain and promised paths. It requires its own publication destination and HTTPS certificate. Its cost, setup and domain renewal must be planned separately from the WordPress plan.

Digital Pacific WordPress Hosting Basic and WP Hosting WordPress Startup each cover one site in their pricing tables. Archived commercial materials allow comparison of monthly and annual cycles in Australian dollars. The best calculation for this festival depends on paid periods, the margin needed to switch to the archive and when the account holder can actually cancel. Ticketing features and simultaneous traffic were not evaluated here.

Four months, ten months or a prepaid year

Digital Pacific's billing catalogue lists AUD 22.55 for one monthly Basic period. The sales page separately presents a prepaid year at AUD 227.27. Four monthly periods at the same rate give AUD 90.20. Ten give AUD 225.50, still below the displayed annual price. Eleven give AUD 248.05. The AUD 18.94 monthly equivalent on the annual card is rounded: it is neither an available monthly payment at that price nor the correct figure for recalculating the annual total.

WP Hosting lists Startup at AUD 19 per month, including Australian GST. The public annual rule is to pay for ten months and receive twelve, giving a calculated AUD 190. At a constant price, four periods cost AUD 76, ten AUD 190 and eleven AUD 209. The annual amount comes from a calculation, not a cart. The archived pricing policy advertises a recurring annual-cycle discount; it does not present a first-year-only reduction. The applicable rate may nevertheless change.

Public amounts were rechecked on November 10, 2026. Digital Pacific does not clearly state whether GST is included in both compared amounts. Ask each provider for the chosen cycle's total price, including tax and any fees, before comparing invoices. Thresholds are calculated references based on each host's displayed amounts. If the invoice does not use the same basis across cycles, recalculate with duly confirmed totals. Also retain one line for the domain and one for the archive.

The schedule counts billed periods. If the team must keep WordPress active for a fifth period to verify the archive, the simulation rises from AUD 90.20 to AUD 112.75 on Digital Pacific's displayed basis, and from AUD 76 to AUD 95 including GST at WP Hosting. This calculation assumes five monthly payments at the same price; it allows for neither prorating nor refunds.

Make exit decisions before printing links

Put the domain and WordPress subscription on two budget lines. Identify the domain holder, registrar, renewal date and person controlling DNS settings. If the domain, DNS or certificate depends on the hosting contract, check how to maintain these services after stopping the plan. For an Australian domain name, registration terms are separate from the WordPress contract. Hosting priced in AUD does not prove eligibility for the intended domain extension.

Next choose a stable address, such as /programme/, that the team can maintain across seasons or retain as an archive for the past edition. Print the domain and path on important materials alongside the QR code. Test the code actually printed, including capitalisation, trailing slash and any parameters. If a QR provider uses its own domain, document what it controls and what must be retained for posters to keep working.

Before going live, schedule the last registration date, end of the paid period, post-switch link checks and cancellation deadline. If the team may exceed the planned margin, budget another monthly period and compare again. Neither a general refund promise nor cutting off payment yourself replaces closure confirmation. The effective closure date determines how long the original WordPress remains available for rollback.

Sort addresses before building the archive

Gather addresses from posters, public emails, the town council website and partner pages. For each, note where it appears, who can change it and what visitors expect after the event. Start with addresses impossible to correct remotely, such as those on a printed poster. Add essential image paths if an old page must remain readable, and check that the archive also serves the files it requests.

Assign an explicit destination to each important address. The programme page can remain at the same path with a 200 response and a note that the edition has ended. An old session page can redirect with 301 directly to the corresponding report section if its content has permanently moved. A removed action, such as registration not printed on posters, may return 410 with a short explanation. If the registration link remains a public reference address, instead keep a readable closure page returning 200. Do not automatically send every address to the homepage.

Build static pages with the programme, a report and authorised media. Check that they no longer load resources from the old WordPress, a registration widget or a service scheduled to stop. Keep exports needed for next season and any registration data retained under internal rules separate. The public archive does not need raw database contents or administration files. Review pages in a visitor session and follow every link before preparing the switch.

Test five addresses on a local archive

The “Exercise: test the festival's printed links” ZIP contains three fictional HTML pages, expected results, an acceptance-test sheet to complete and a small server running only on the computer. It checks the programme at its original address, then the same address with a parameter printed on a poster. It also checks an old session moved to the report. The response must indicate a single redirect; the target must respond and the session anchor must exist. A final 200 status is insufficient if the link lands in the wrong place.

The old registration page displays a closure message without a form. In the mock-up, a submission attempt is rejected and an unknown address remains a genuine 404. The five addresses and submission rejection were checked locally. This shows that the example archive preserves expected links and a removed action does not reappear. It verifies neither the real domain's certificate, destination configuration nor either host's behaviour.

Repeat the protocol with festival paths on a private copy. For a redirect, compare the starting address, destination header and visible result. If a partner uses a domain variant or a code with parameters, add it to the list. Another person must be able to follow the link from a phone, recognise the archived edition and understand that registration has ended. A photo of the printed material and its check result avoid reconstructing later what was distributed.

• Download and extract the ZIP from “Further reading”. With Node.js 20 or later, run node exercice-archive.mjs in the resulting folder and compare results with resultat-attendu.json.
• Repeat the real links on the private copy, including image paths and printed variants.
• Delay WordPress closure if a printed link does not yet respond as expected.

Digital Pacific Basic: retain a margin before the notice deadline

The table advertises one site, 10 GB and two databases for WordPress Hosting Basic, with Plesk. If you plan WordPress checks on a copy, verify what the plan actually allows; the outgoing static copy is a separate destination independent of the database quota. To retain next season's project, Plesk documentation describes exporting through Databases, then Export Dump. Also save the site's files. You must be able to reopen the set on a copy before losing service access.

The archived terms require a cancellation request through the Members Portal at least two working days before the due date. Record the deadline as it applies to the contract and service calendar, allowing margin around non-working days. Payment is recurring and in advance. Already-paid periods do not automatically qualify for refunds. Do not choose the annual cycle expecting to recover unused months after the last session.

For four periods, monthly billing limits the upfront amount if the festival controls its exit day. If archives must be validated near renewal, plan an overlap period or bring validation forward. Confirm tax, billed amount and effective date. Keep the request number and written confirmation with evidence that the domain name will continue working.

WP Hosting Startup: distinguish the annual cycle from refunds

WP Hosting is the brand found in the offering's address; the commercial journey is now presented under Network Dynamics. Startup lists one site and 5 GB of NVMe storage. Check that event photos, the database and site files fit with a margin. The Startup table advertises a test environment. Documentation for cPanel WordPress Management cloning reserves that particular tool for Business plans or higher. If you must clone or republish from Startup, clarify the included workflow. The proposed protocol here uses local HTML files and does not depend on that tool.

Before closing, cPanel documentation describes downloading files and databases through JetBackup 5. Identify the components needed to reopen WordPress next season, then check files outside the account. The billing policy distinguishes notices issued thirty days before annual renewal and seven days before monthly renewal. These issuance periods are not cancellation deadlines. The listing indicates per-service cancellation in the customer area before the next cycle; confirm the effective date and time for your account.

The annual rule of ten months paid for twelve remains attractive for a festival needing WordPress almost all year. Outside the eligible refund window, the policy provides no prorated refund for unused time. It also excludes services that used free migration. For four planned working months, base the choice on required periods and a controlled exit. Leaving an invoice unpaid may suspend service and then terminate it; this is not a way to extend archive checks.

Switch only after validating the domain and links

Prepare the archive at its test destination, then verify that this destination can respond for the public domain and provide the correct certificate. The holder must retain control of the name and DNS settings. Document records to change and their original values. If mailboxes or another service remain active, separate their records from website records. Switching the web destination must not remove services the organisation decided to keep.

When closing registration, remove or close forms on the original WordPress before repeating the final export. Keep the site and contract available while checking the archive. After the authorised switch, check HTTPS, domain variants actually published, the programme, redirect and media from a logged-out browser. Also check the exact addresses printed on posters. If results differ across connections, record the observation: DNS and caches may delay consistency.

If a critical address is broken, first correct the archive or return to the previous web configuration while the service still exists. A DNS rollback is not instant and does not guarantee that all visitors switch simultaneously. Check the result before announcing restored service. Close the old subscription only after confirming links, certificate and independent export. If the cancellation deadline precedes confirmation, retain the necessary paid margin and update the budget.

Choose the plan according to the actual schedule

If the festival stops after four paid periods and the archive is ready to take over, monthly billing ties up less money than annual billing in both recorded schedules. At Digital Pacific, ten monthly payments remain below the annual reference; at WP Hosting, they equal it under the public rule. At eleven periods, monthly totals exceed the annual reference at both. Recalculate with confirmed taxes, any fees and actual duration before paying.

To choose between plans, first compare the active site's space needs and the team's ability to export files and the database. Basic advertises 10 GB and uses Plesk. Startup advertises 5 GB and documents a cPanel workflow, with GST explicitly included in storefront pricing. The archived materials establish neither a guaranteed future price nor ticketing performance. If the festival exceeds storage or needs a particular service, have that requirement priced before comparing the two displayed amounts.

The right outcome is observable after the season: registration is closed, the programme remains readable at the printed address and the team holds files needed for the next edition. Compare full-year costs if WordPress must remain open between seasons. If an independent archive suffices, budget mainly for the domain, destination and testing time. Cancellation must follow evidence of continuity, with a date and responsible person.

Further reading

• Read the Digital Pacific profile
• Read the WP Hosting and Network Dynamics profile
• Check that the HTTPS certificate covers the archive’s domain
• Exercise: test the festival’s printed links (ZIP)