Feature #284
closed
Adjust the language for a blog's privacy settings
Added by Sarah Morgano almost 14 years ago.
Updated almost 14 years ago.
Category name:
WordPress (misc)
Description
The current content for the blog's privacy settings reads:
I would like my blog to be visible to everyone, including search engines (like Google, Bing, Technorati) and archivers
I would like to block search engines, but allow normal visitors
I would like my blog to be visible only to registered users from the blog community*
I would like my blog to be visible only to registered members of this blog
I would like my blog to be visible only to administrators*
Perhaps we could adjust the two selected options to read something like:
I would like my blog to be visible only to registered members of the CUNY Academic Commons
I would like my blog to be visible only to administrators of this blog
Best,
Sarah
- Assignee set to Chris Stein
- Target version set to 1.1
Good idea, Sarah. Chris, you're the language file master :)
- Status changed from New to Reporter Feedback
I updated the en_CAC.mo file to make this change. A couple of notes on that. To make it work across all of the blogs we need to write a script to change their language (see http://redmine.gc.cuny.edu/issues/show/309)
The text in question here come from two places. The first two lines are in the options-privacy.php file from core WP but the next three lines come from a plugin that hooks into the blog_privacy_selector action. The plugin file is named 1208464393_ds_private_blog.php So that is something to keep track of.
Finally, Boone, I committed it to the master branch (https://github.com/castiron/cac/commit/71e400aa74355f13331bd2c0f6e9b4bdd34f7c8d). This speaks to what we briefly talked about before in terms of making git branches to match the targets on these bug tickets. I didn't want to be the one to create a new branch though until we settle that so I did it on the master. Also maybe bump this to 1.0.1 target release.
- Status changed from Reporter Feedback to Resolved
- Target version changed from 1.1 to 1.0.1
I was just telling a member about these privacy levels tonight; this new language makes them much more clear. Thanks, Chris!
oops -- and thanks to Sarah, as well!
Yes, it was Sarah's suggestion and wording. The setup now makes it a bit easier to change these things so if you see more like this then fire away.
Also, to keep in the back of our brains, the way the language thing works is that it searches for a given string of text and replaces it with another. So it's great because we don't have to touch the code, but... sometimes they change the wording when the version is upgraded. This has the effect of removing the changes because the string it's looking for has changed. It's a simple fix, just have it look for the new string, So especially when we upgrade to WP3.0 we will have to check and see if we lose any of these updated wordings.
Also available in: Atom
PDF