Archive or delete a hub, event cards in emails, member tickets and bigger photo uploads

Archive or delete a hub

In hub Settings, under Archive or delete, an owner can archive a hub. The hub, its events, chat and photos are hidden from members and the public, nobody is told, and everything is kept.
Restore hub brings it all back. Until then its owners and admins can still read it, and it sits under Archived at the bottom of their hubs list.
A hub that has never been used for real can be deleted. Hubbaly asks you to confirm it is you and to type the hub’s name, and says what to sort out first if the hub is not ready.

An event card has its own Event list. Pick any of your events and the card fills in its name, date, place, picture and link, and follows the event until the email is sent.
Add several cards to mention several events in one email, each Large or Small.
For something with no event page yet, such as a save the date, choose No event: write your own.
The record of a sent email shows each card as it went out.

On an event open to everyone, the ticket form asks Who can buy it? for each ticket: Anyone or Hub members. One event can sell member tickets beside public ones, and you choose whether people who are not members can see them.
A hub members ticket is one for each member. A buyer keeps one and names a different hub member for each extra one.
When an event sells only multi-day passes, the passes are shown as its tickets, with each day’s times above them and the days each pass covers marked.
On the event page, two or three dates sit in one bar that fits a phone, and for members each date opens its tickets. Ticket names read in full on a phone.
The ticket form asks how people wait for tickets only when the new ticket can be queued for.
Your own tickets are filed by the dates each one is for, so a ticket for a date that has gone moves to Past.

The Ticket movement line on Sold Tickets, Recent Sold Tickets and Order details shows who a ticket came from, who it went to, and when.
If a refund cannot reach the buyer’s card, Order details opens with the warning, lists the failed attempt on its own, and says what to do next.
The refund email to a buyer with no account opens their ticket, which says it was refunded and when.
A purchase invite starts from the buyer limits on the event, the ticket and the date, and keeps what you typed if a send is refused.
Event shop order details fit a phone screen.

An upload of thousands of photos paces itself through to the end. The list says when it is pausing, shows anything that failed with Retry failed, and photos join the album once they are ready to view.
Photos are ready sooner after a big upload. In our tests 600 photos were ready in about four minutes, down from ten.
Albums keep up with a fast scroll in the same way as the Timeline.
A photo report’s notice clears for every owner and admin once the report has been dealt with.

Typing an event’s days in by hand is easier. Each day is an open form named Day 1, Day 2 and so on, Add another day opens the next one, and an empty day offers the next day with the same hours. Review lists the days in date order.
Event questions can ask about dietary needs, allergies and accessibility. If a save is refused, the message names the question and says what to change.
After you add dates to an event that has staff, the page brings the Review staff notice into view.
When a paid ticket needs your hub’s seller details first, the message takes you to Add seller details.

Accepting an invitation to work at an event gives access to that event and its staff tools, without joining the hub.
The contact search on an incident also finds event staff you have invited who have yet to accept.
Giving a member import more time keeps the joining links you have already emailed working.
In the text editor, Move up and Move down on a picture always move it somewhere you can see.
Hub pages need nearly a fifth less to download before they show.