Presenting a fresh batch of updates to kick off the month! No jokes. Just the straight up truth.
The following updates were just deployed and are now live on your site:
You can now delete your Latest posts. The 'delete' button lives in the bottom right-hand corner of the Latest posts' editing screen.
Please note: This feature is only to be used in the event of a duplicate or otherwise unintended post. Your Latest feeds should tell the story of your city, so you should not delete any posts concerning past giveaways, show previews or on sale announcements - you'll just want to let your new posts push those farther down the feed.
Please note: This feature is only to be used in the event of a duplicate or otherwise unintended post. Your Latest feeds should tell the story of your city, so you should not delete any posts concerning past giveaways, show previews or on sale announcements - you'll just want to let your new posts push those farther down the feed.
We also made sure to automatically bust the Latest cache and refresh your feed whenever a post is deleted - so you'll always see an updated list after deleting.
You can sort the pending queue by title. This was requested by Jamie from 416 so she could check her pending queue for a possible duplicate event.
Images that are uploaded to /p pages will automatically center by default. They were previously left aligned by default. Now, you don't have to dig through a mess of code to center some images.
We built a tool to auto-populate the 'Add Event' form when adding events from Facebook. If you're adding a large quantity of events from Facebook, we highly recommend using this tool. Here's how to do so:
1. Log in with Facebook on any metro.
2. Click the 'Add Event' button under MYXYZ.
3. Scroll down to the bottom of the page to see a link for the FB Bookmarklet.
4. Click on that link and drag it to your bookmarks bar.
5. Navigate to the Facebook Event that you want to add (you do not need to leave the 'Add Event' form open).
6. Click the bookmarklet link in your bookmarks bar. The event form will automatically populate with all of the Facebook event's primary information.
A couple things to note:
- You will still want to do some light editing to make sure all of the information is expressed correctly on the event form.
- You will still need to assign the event a category (since Facebook doesn't express that information).
- You will still need to add bands (when applicable).
- You will still need to answer the spam question.
- You will need to change the venue IF the venue on the Facebook event is not an exact match to a venue in Radmin. This form is not able to recognize keywords.
- The event's cover photo will populate to the Poster URL (since Facebook events usually contain text-rich poster images).
- You will still need to add an event description.
- You will still need to add an event description.
Users who delete their accounts will now be removed from all event activity. This should put an end to the angry emails by users who still see their display names in event activity long after their accounts have been deleted. (They were never removed before.)
Please note that event activity is still cached for a maximum of one hour - so if a user contacts you wondering why their name is still is appearing in the event activity shortly after (s)he deleted it, you'll want to edit any part of the event's key details (title, name, date, topline, etc) and then tell the user to refresh event the screen. The contentious name will be gone.
Latest posts and /p pages will no longer display on ECPs. This was a request by Jay Cox - and makes great sense since our partner calendars generally live on music websites that have their own editorial initiatives and only want to out-source the event listings portion of their content.
We fixed up ongoing and repeating event widgets to display more characters and changed the font size of the 'Free' and 'Every _Day' top bars to prevent text from overlapping with the title.
We fixed a bug that was caused by adding capitalized test to event, artist, venue, user or /p pages. Capitalizing URL text such as "/P", "/EVENTS," and "/USERS" had been leading users to a page not found.
And we fixed a bug that was preventing the 'Ask Birthdate?' field on RSVP forms from correctly validating a user's birthdate. You can rest assured that the 'Ask Birthdate?' field will prevent underage users from RSVPing to any event with 'Require minimum age?' checked.
That's all for us. Thanks so much for reading this Product Update! We hope you all have a super smooth week!
No comments:
Post a Comment
Thoughts to share? DO!