¿ªÔÆÌåÓý

Groups.io site updates #changelog


 

Hi all,

The last two week's change logs:



Feel free to reply to this topic if you'd like to comment on the
changes. Or better yet, if you expect a lot of discussion start a new
topic (or rejoin an existing one) about a specific change.


* Changes to /leave link behavior:
If you click on a leave link and are logged in as someone else,
you are logged out.
This behavior was subsequently changed:
* When visiting a /leave link for someone else, display an error
message and an option to log out.
I believe the latter behavior is superior, as most people in this circumstance will be logged in to their own (and only) account - logging them out unexpectedly would be a rude surprise.

If you are logged out, you are not then logged in as the person
the /leave link belongs to.
One thing I haven't tested yet is what you can do at this point. I'm presuming (hoping) that you can unsubscribe even though not logged in. The details on this one are important for email-only subscribers. There's a rather long thread on this in beta@, if you want the details.



* Gathering SPF responses on inbound messages for testing/possible
future use.
Yay! Hopefully this is a prelude to eliminating the need to confirm email commands, in many (most) cases.



* Search results have the topics actions dropdown when viewing
collapsed topics.
Yay! Another step toward consistency in messages list presentation & controls.


Comments about these others are also welcome:

CHANGE: Clarification in the help on hashtag behavior.
CHANGE: Changes to /leave link behavior:
If you are logged in as the person the /leave link belongs to, you are still logged in.
I re-ordered the buttons for leaving, putting the 'Leave Group' button last.
The email address of the account is now displayed on the page.
BUGFIX: The Vote link in poll messages didn't work for some people without permission to add a new poll.
CHANGE: Much more accurate count of total search results when using the 'collapse topics' option.
BUGFIX: When trying to view a deleted event, now show a banner explaining it's been deleted.
BUGFIX: Couldn't approve a pending message from someone who has already unsubscribed and when the group is set to moderate new users.
CHANGE: Column hiding when viewing a table is remembered as you page through the table. Also the buttons look nicer.
BUGFIX: The /updategroup and /deletegroup API end points returned invalid_permissions when they should not.
BUGFIX: We were not processing some bounce emails that were marked as being autoresponder messages.
CHANGE: Changed format of ICS files to try to fix erroneous timezone problem with a couple of calendar programs.
CHANGE: When creating the #guidelines hashtag when sending the group guidelines, set Mods Only Post and Mods Only Reply to true, and if the guidelines should be sent special, set the tag to Special as well.
CHANGE: Wording changes to help and group notices.
INTERNAL: Using the search cluster for viewing messages by month/year to take load off main db.
BUGFIX: Search results were displayed incorrectly when summaries had HTML unsafe characters.
BUGFIX: Fixed email subscription process for some Enterprise sub groups.
SYSADMIN: Changed the messages and activities tables autovaccuum scale factor to 0.00.
NEW: Added 'Member Page' option to 'More' menu and dropdown when viewing messages.
BUGFIX: Fixed subjects for new member notices to match new terminology.
BUGFIX: For member notices with HTML links that have text that is the same as the link itself, don't display it double when converting it to plain text.
NEW: Generate name tags for people who have RSVPed Yes to an event.


Please call out any you find significant.

Shal


 

On Sat, Nov 18, 2017 at 10:40 pm, Shal Farley wrote:


CHANGE: Clarification in the help on hashtag behavior.
This still doesn't work quite right. According to the help page, any hashtags in the middle should be duplicated at the end of the subject line. Instead they are moved to the end. In the example shown, "Seeking #advice for a #rosebush with blackened leaves", it becomes "Seeking for a with blackened leaves #advice #rosebush", instead of "Seeking #advice for a #rosebush with blackened leaves #advice #rosebush" as shown. I've notified Support and Mark said the moving action is what is intended. Unless the behavior is changed, you'll need to be careful of hashtag placement.

Duane


J_Catlady
 

The clarification was about the fact that there needs to be a space before a hashtag if it is not at the beginning of the subject line (there were some people in another group who didn't realize that and were having trouble with using hashtags in general). What you're reporting seems to be a separate bug or change.?
--
J