Warning for Bad Markup

[melannen]

Title:
Warning for Bad Markup

Area:
entries

Summary:
When you have bad markup in an entry, DW fails with an error message in the displayed post. Instead, it should warn you about the bad markup before posting, and give you a chance to go back and edit.

Description:
DW clearly has a way to check the markup in a post for basic problems, since it displays some really ugly error text when it happens, and I remember a time on LJ before the error text was there.

The current behavior is to interrup the post at the point where the error occurs, with the message [Error: Irreparable invalid markup ('<foo [...] bar>') in entry. Owner must fix manually. Raw contents below.] followed by the complete raw text of the entry.

I see this message, um, pretty much every time I attempt to make a post with more than a couple bits of mark-up in it. It's ugly, it breaks cut-tags, and with a long and complicated post, it's easy to miss it on preview. We hates it, precious.

It would be really nice if, instead of posting the entry complete with error text and raw code, DW instead gave you some kind of really noticeable warning that there was bad markup (a pop-up, or a big screaming message, or something difficult to miss) and offer to send you back to the entry to fix before posting. (Give the user the option to post anyway, but let them know there will be errors.)

I have no idea how this would work with clients, but even if it only worked from the web form, it would be an amazingly helpful improvement for me.

(And aside from that, some sort of polish to the current behavior would be great. I suggest post the entire entry in raw HTML but behind a cut, with the error message as the cut text. That way at least it wouldn't take over everyone's flists.)

Poll #872

Open to: Registered Users, detailed results viewable to: All, participants: 48

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
39 (81.2%)

Should be implemented with changes.
7 (14.6%)

Shouldn't be implemented.
1 (2.1%)

(Other: please comment)
1 (2.1%)

Index for /security/

[cesy]

Title:
Index for /security/

Area:
entries

Summary:
Add an index page for /security/

Description:
You can go to http://exampleusername.dreamwidth.org/security/friends to view just the access-only entries that person has made, or http://exampleusername.dreamwidth.org/security/group:ExampleCustomGroup similarly, or http://exampleusername.dreamwidth.org/security/public. Could a page be added to http://exampleusername.dreamwidth.org/security/ with a list of these, rather than the current 404 error?

Poll #875

Open to: Registered Users, detailed results viewable to: All, participants: 35

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
14 (40.0%)

Should be implemented with changes.
21 (60.0%)

Shouldn't be implemented.
0 (0.0%)

(Other: please comment)
0 (0.0%)

Comment screening in another user's entry

[elizabeth_rice]

Title:
Comment screening in another user's entry

Area:
entries, comments

Summary:
Ability to screen my own comment(s) in another user's entry in a personal journal and/or community.

Description:
Each user has the ability to delete his/her own comment in another user's entry. Only the entry poster can delete, screen and freeze comments made to their entry(ies).

If I wish to share personal information that I do not want others to view, what I can currently do is to delete the comment after posting it to ensure that only the entry poster can view it. Even if I were to ask the entry poster to screen my comment, s/he will only do so when s/he reads my comment.

My suggestion is to allow each user the ability to screen his/her own comment in another user's entry(ies) made in a personal journal/community, whether the entry/journal/community is public or restricted to that user's access list or community members. This way a user can share personal information with the entry poster that s/he does not wish for others to view.

Regarding communities, perhaps some users might feel hesitant to implement this in case it creates additional problems for maintainers/moderators in case of conflict between the entry poster and other members/users. However, I know that members/users with posting access already have the ability to delete, screen and freeze all comments made to their entries in a community. So I don't believe that it would cause additional problems if users have the ability to screen their own comments.

Poll #873

Open to: Registered Users, detailed results viewable to: All, participants: 38

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
9 (23.7%)

Should be implemented with changes.
7 (18.4%)

Shouldn't be implemented.
22 (57.9%)

(Other: please comment)
0 (0.0%)

Visibility of information and who can view information on profile page

[elizabeth_rice]

Title:
Visibility of information and who can view information on profile page

Area:
profile page

Summary:
If profile information (eg. birthday, contact information, etc.) has been set to 'registered accounts' or 'access list only', alert those users who are in the respective groups.

Description:
On my profile page, I can choose to make my information visible in the following ways: everybody, registered accounts, access list only, or nobody.

The problem with this is that people who view my profile don't know what setting I have chosen. Example, if I chose 'registered accounts' or 'access list only', logged-in users, who visited my profile, would ony assume that my information is publicly viewable. They can share my information with other users not realising that they're not supposed to do so.

My suggestion is to have a way of alerting only those users who belong to either group if the information on the profile page has been set to either 'registered accounts' or 'access list only'.

For instance, if I chose 'registered accounts' - then logged-in users, who visit my profile page, would see text informing them that my information is visible to registered accounts only.

If I chose 'access list only' - then the users to whom I have given access, who visit my profile page, would see text informing them that my information is visible to my access list only.

Poll #874

Open to: Registered Users, detailed results viewable to: All, participants: 35

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
19 (54.3%)

Should be implemented with changes.
10 (28.6%)

Shouldn't be implemented.
6 (17.1%)

(Other: please comment)
0 (0.0%)