Changelog
1.12.5
Improved
- Behind-the-scenes maintenance and stability improvements.
1.12.4
Fixed
- When a save, delete, import or build can't reach Daymarked, for example on a dropped connection, the screen now says so and lets you try again instead of staying on Sending…, Creating… or Saving….
- If creating a wedding fails that way, Daymarked asks you to check your weddings before you try again, since the wedding may already have been created.
- Deleting a block that fails now shows why. Before, the message was hidden behind the delete window.
- The Build Timeline window now says when it couldn't load your studio's block settings, instead of listing the default block names.
1.12.3
Fixed
- Sections on the timeline your couple and guests see when they sign in now appear where you placed them, as they do on the share link and the PDF. Before, they all appeared at the end. Your preview of their view shows the same order.
1.12.2
Fixed
- The "Updated" date on your share link no longer changes when you edit a block your couple can't see.
- Questionnaire reminders now need at least one person you emailed the questionnaire to, since reminders go by email. If you've only shared the link, the reminders switch stays off and tells you why. If reminders were already on with nobody emailed, the panel now says none will go.
- If your account can't be loaded while you invite a guest, send them a new link, or revoke their access, you now see an error and can try again. Before, you were taken to the dashboard and the action was lost.
1.12.1
Improved
- When a page in the app fails to load, the sidebar and header stay on screen, with a button to try again and a link to your weddings.
Fixed
- Running Build timeline or Build backwards twice at the same time, on two devices or with a double tap, no longer adds a second set of blocks. The second device shows the blocks the first one built without a reload.
- If your weddings can't be loaded, the Weddings page now says so and offers Try again. Before, it showed the empty "Create a wedding" screen, as if you had no weddings.
- Try again on an error page now loads the page again. Before, it often showed the same error until you reloaded the browser.
1.12.0
Improved
- The dashboard and wedding pages download less code, so on a slow connection they are ready to use about a second sooner.
Fixed
- A wedding whose venue is near a time zone border, such as El Paso or Tijuana, now opens its timeline and couple portal. Before, those pages could fail to load.
- Importing a questionnaire no longer waits indefinitely when the service that reads the file stalls. The import stops and asks you to try again.
- When a questionnaire import can't be processed, the message now asks you to try again in a few minutes, instead of saying the file has no questions or answers.
- You can now choose a file to import with the keyboard. In the three questionnaire import windows, the file area can take keyboard focus, shows a focus outline, and opens the file picker with Space or Enter. If the file can't be imported, screen readers now announce the message.
1.11.0
Fixed
- If saving Wedding Details failed because your connection dropped, the Save button stayed on "Saving…" and later changes to your vendor team were not saved. It now says it couldn't connect, keeps your changes, and saves them when you try again.
- On the desktop timeline, accepting a travel time suggestion after moving one of its blocks added the travel stop with the old times. It now uses the blocks' current times, and a suggestion whose block was deleted or changed location goes away without adding anything.
- On the desktop timeline, if adding a block failed, nothing happened and the hover line for adding blocks could stop working until you reloaded. It now shows why the block wasn't added.
- After you remove a wedding's last guest, the timeline no longer keeps showing comment counts on its blocks.
- Replacing a timeline with Build Timeline could leave the wedding with no timeline if the save failed partway. The old timeline now stays until the new one is saved.
- Starting a timeline from the ceremony on two devices at once could add the blocks twice. Now only the first start builds the timeline.
- Building a timeline now uses the block names you set in your block library. Before, a block type you renamed, such as Ceremony to "Vows", was added under its standard name.
- If importing your couple's questionnaire answers ran into a brief server problem, the import could add a second copy of custom fields the wedding already had. It now stops and shows an error instead.
- If building a timeline ran into a brief server problem, it could add a second copy of blocks the timeline already had. The build now stops and shows an error instead.
- If adding a block or building a timeline ran into a brief server problem, a block type you hide from your couple could be added visible to them, with the default color and length. It now stops and shows an error instead.
- If saving a block ran into a brief server problem, the wedding's First Look setting could be switched off. It now stays as it was.
- Editing a wedding from your weddings list could overwrite names or a venue your couple entered in their questionnaire after you opened the list. Now only the fields you changed are saved.
- If saving a change to a section failed, the change disappeared from the section. It now stays, the timeline shows that the save failed, and the change is saved again the next time you close the section.
- On the desktop timeline, changes to a section were not saved when you clicked outside it, and a single change, such as hiding a section from your couple, was sometimes not saved. Both now save.
- Saving Wedding Details could overwrite or clear ceremony, reception or other details your couple entered in their questionnaire after you opened the wedding. Now only the fields you changed are saved.
- Editing a block or section on the desktop timeline could undo a change made to it on another device, such as your phone. Now only the fields you changed are saved.
- If saving a new studio logo failed, your logo could disappear from shared timelines and PDFs. This no longer happens.