LiveJournal Test Community
 
[Most Recent Entries] [Calendar View] [Friends]

Below are the 20 most recent journal entries recorded in LiveJournal Test Community's LiveJournal:

    [ << Previous 20 ]
    Monday, January 3rd, 2005
    2:46 pm
    [whitaker]
    Login bugfix
    As mentioned here in [info]changelog, there's been a recent minor bugfix with login sessions expiring when the browser closes.

    More simply put: I've made a small change to how logins are handled on LiveJournal and would like everyone to spend a few minutes playing around on the Test Server. If you find any problems with your login, please report them here by leaving a comment.

    The following are a couple of examples of things you might look for:
    • you get randomly logged out
    • you notice your cookie-length is incorrect (because you're a techie)
    • you've selected the "when browser closes" expiration type and you don't get logged on on browser close
    • you've selected the "never" expiration type and you DO get logged out on browser close
    • etc
    As always, thank you for your help!
    Tuesday, July 27th, 2004
    11:15 am
    [whitaker]
    Variable Flow S2 Style
    A call to testing by [info]mart:

    There's a new layout live on the Test Server called Variable Flow. It'd be cool if people could have a play with it and see if there are any obvious bugs or problems with it. To enable Variable Flow, go to the Customize Page and be sure you're using S2, then select Variable Flow as your layout.

    The main kind of testing wanted here is whether any of the available customization features don't work quite right, or cause unexpected things to happen. The customize interface provides quite a lot of customizability, but people who write their own user layers can override some extra things and have more control over the options, so both kinds of testing would be great. The functions that advanced users are intended to override should all be documented as such, although you'll have to poke through the source code to see the docstrings.

    For now I'd like to stick to bug reports only. Once I'm satisfied that the layout works properly as it is now I'll start to deal with adding more features. Please note that the layout doesn't currently support customized comment pages, and they're disabled by default — so don't report this as a bug! Customized comment pages will probably come later as an option.

    [info]mart should be following this thread and answering any questions/concerns anyone has.
    Wednesday, July 14th, 2004
    12:01 pm
    [jproulx]
    New Update + Edit Entry Pages
    I've been working on a new layout for the "Update your Journal" and "Edit Journal Entry" pages, using the same style where appropriate and trying to make things easier to use and understand. It's mostly done from a code perspective, but I want to make sure it's tested heavily before putting this up on livejournal.

    If you have some time today to test, that would be cool. Be sure to leave me a comment here if you have any problems or bug reports.
    Monday, June 7th, 2004
    7:47 pm
    [marksmith]
    Testing Dversion 5 Support Code
    This is step one of two. This test will run for the next few days. Basically, what I want to test is memories and friend groups. I have written new code that completely changes the way memories are handled, and it also does some futzing with how friend groups are handled, and it needs to be tested.

    If you are interested in helping test this out, head on over to the test server:

        http://test.livejournal.org/

    On it, please test everything that relates to memories--communities, security, deleting, deleting the entry they point to, et cetera.

    The same with friend groups. Specifically, we want to make sure that friend groups are working with regard to security. That's the big part--don't want to have that mess up when this code goes live!

    Please let me know if you find any bugs or problems or inconsistencies. Thank you!

    Here in a few days (Wednesday?), we'll start Round Two of testing--by upgrading the users and then having everybody retest things to see how dversion 6 holds up. But first, we need everybody to get some memories and friend groups created so that we can upgrade them!
    Thursday, May 13th, 2004
    5:05 pm
    [whitaker]
    User MemCache testing
    I recently committed a patch that alters the way user objects are stored in MemCache. I think I got all of the update cases covered but I'd still like to have everyones' help testing since we'll be putting the code live soon.

    What to do: Go to the Test Server and load all kinds of pages: Recent entries, friends pages, userinfo, etc. Then go modify account settings, particularly at the Edit Info page and make sure that all the changes take effect immediately and show up everywhere on the site.

    As always, please report any bugs you find by commenting on this post. Thanks for your help!
    Tuesday, February 3rd, 2004
    3:32 am
    [whitaker]
    Interests Changes
    Just a quick update. [info]bradfitz has done some interest memcaching which needs to be tested. So, please use the test server to test everything having to do with interests and please report any problems here.

    For the nerds, here is the commit log for this change:
    http://www.livejournal.com/community/changelog/1201675.html
    Thursday, January 15th, 2004
    8:09 pm
    [whitaker]
    Secure Commenting
    Testing request from [info]mahlon:

    The challenge/response mechanism that was previously added to login.bml is now site wide, including the commenting areas. Please help us test the commenting system from S1 and S2 styles, previewing, commenting with anonymous, cookie, and username/password credentials, as well as from different browsers... and with Javascript on/off. This also includes the /portal, and update.bml. Report any problems found here. Thanks!
    Thursday, January 8th, 2004
    4:18 pm
    [xevinx]
    New style - Opal
    A new style, based off another OSWD (Libra), has been added to the test server and is available to those with accounts there. Let me know how it looks and works for you. Also, it was build to be pretty customizable through advanced customizations, so if you're into that, could use some testing there too. A note that the source is public, but it is not GPL'd.

    Thanks!
    Wednesday, December 31st, 2003
    5:27 pm
    [whitaker]
    SSL Logins
    [info]mahlon has implemented secure challenge-response logins for the main login page on the Test Server. (Logins via comment pages are not done yet.) This secuirty method will be used when an SSL connection is not available.

    This security requires javascript, so non javascript browsers will fall back to insecure mode if not connected via SSL. As such, we could use a hand testing logins under various browsers and environments to make sure no one is suddenly left out in the cold when they want to login.

    To help us test, just go to the login page and try to login. If you have problems, please comment on this post with your browser version and operating system so that we can fix the problem.
    Thursday, October 2nd, 2003
    12:17 pm
    [avva]
    testing sought
    We're finishing our work on some very important code that should dramatically improve the site's performance once it's put live. It shifts to memcache and from the database servers most of the load of our most intensive DB query (the one used for building friend views).

    However, this code is also complicated, and it's crucial that we get it right. We need your help testing it now. Please go to the test server and do some of the stuff described below.

    Basically, what needs to be tested is the whole business of displaying friend views, and also pages with individual entries. Create some users (if you haven't yet), post some entries, have them friend one another, look at their friend views. Here's some of the stuff that's especially important to check:

    • That security is right. That you can't see any non-public entry on a friends view if you're not logged in. If you're logged in, you must not be able to see your friends' private entries, friends-only entries of your friends who didn't friend you, or specific-friend-group entries for groups you don't belong to.

      All of this stuff also needs checking in the case where you're logged in as one user and reading the friend view of another.

    • That the order and the number of entries are right. The entries must appear on the friend view in the correct reverse chronological order. If entry A was posted later than entry B but appears after B on the friend view, it's a bug. If entry A is supposed to be on the friends view but isn't there - also a bug. If the page's says it's showing 20 entries, but actually there's more or less than that - a bug. If it shows less than the default number, claiming that it can't find enough, but there actually are enough entries posted to make it 20 or whatever the default is - a bug.

      Also, friend views should never display entries posted more than 2 weeks ago (nevermind the time specified on them, the important thing is when they were physically posted). If they do, it's a bug.

    • That the text of the entries, logprops (mood, music) and comments (on comment pages) are correctly displayed. Also extremely important: that the time of the entry corresponds to the time specified when posting it (you can play with posting time on update.bml and change it to something else rather than today or change the hour etc. - then check that it displays exactly that time, not shifted anywhere, on friends views or comment views).

    • Obviously if some pages refuse to load, give weird errors etc. - it's a bug.

    • Note: replycounts aren't working currently. This means that the number of comments to entries isn't reported correctly on friend views and such (even if there're comments, it behaves as if there weren't any). No need to report that, we're still working on this last step. The comments themselves, on the other hand, should display fine on individual entry pages.

    • If you find anything suspicious or buggy, please report in comments here. Many thanks in advance!

      Update: One serious problem has already been fixed thanks to your reports: some friends-only entries were visible on the relevant journal pages, but didn't show up on friend views. This shouldn't happen anymore (if it does, it's a separate bug, please report). Thanks!
    Tuesday, September 30th, 2003
    3:45 pm
    [whitaker]
    MemCache (a quick request)
    We've been working on misc performance / stability / bugfixes for a while now so there haven't been many earth-shattering changes to report in test-server-land, as I'm sure you've noticed.

    We've just finished work on optimizing and debugging the MemCache client code, so please pound on the test server for a bit and try to break it. Report any problems you find here.
    Thursday, September 4th, 2003
    7:33 pm
    [whitaker]
    Style System Changes

    There have been quite a few style changes in the past week or so. All changes are available for testing on the Test Server. Some of these changes are pretty major so we need to be sure to test extra-thoroughly before this stuff goes live.

    S1 Style Clustering/MemCaching
    The benefits of this are mostly technical and only really helpful to LiveJournal.com, but the patch was massive and the backend of all S1 functionality was overhauled. This means that everything that uses S1 or modifies S1 styles needs to be tested.
    S2 Layout Settings
    A style is now kept for each S2 layout you use. So if you modify your settings for Component at the customize page, then those changes will be kept if you switch to Boxer for a while and switch back. As a neat trick, you can see your wizard styles for each layout at the advanced style editor page.
    Style=Mine
    There is a new option in editinfo.bml that will allow you to view comments pages linked from your friends page in your journal style, rather than the style of the user who posted it. This has been a frequently requested feature for S2 since some people dislike some of the comment page styles. This change affected all aspects of the S1 and S2 comment systems.

    As always, post any bug reports here and we will investigate them and file Zilla bugs as appropriate.

    Tuesday, August 26th, 2003
    2:05 pm
    [evan]
    we like simple
    Better?

    Thanks for your input.
    Monday, August 25th, 2003
    4:17 pm
    [whitaker]
    New front page
    We've just written some new content for the main page. We're going to keep it on the test server for about 30 minutes before moving to the live site.

    During that time, let us know what you think so we can make any necessary changes before it goes live. So that everyone doesn't jump at once: We know that the text is really long. It will eventually find a new home, but for now we think it's better/more informative than what's there.

    Road map:
    • Put up new, long text front page
    • Make Xcolibur default scheme and switch change front page text again


    Update: It's live now. [info]brad had to leave the office, so we put it live just before he left.
    Tuesday, August 19th, 2003
    5:33 pm
    [whitaker]
    New Style: The Boxer
    This is just a quick update. If you've been following [info]changelog, you already know about a slew of minor/unexciting changes that have been taking place lately on the test server. Since my last post, code from the test server has not been migrated over to the live site. It will soon, but please be patient.

    In other news, [info]xevinx has made a new S2 style called "The Boxer." Since it is new, it will likely be changing over the next few days as we work out problems and add features. To test, go to the S2 customize page and select "The Boxer" as your layout. There are about a dozen themes to choose from and you're welcome to try and make derivative user layers if you're feeling brave. [info]xevinx will be replying to your comments on this post and fixing any issues that you find.
    Wednesday, July 30th, 2003
    6:50 pm
    [whitaker]
    Lots of Test Server Updates
    If you've been following [info]changelog, you'll see that there are a ton of changes on the Test Server.
    Extra Userpics
    Changes have been made to the payment system to allow users to buy extra userpics. The changes came in 2 parts: the cart front end and the payment back end. Sufficiently testing the backend code requires being able to modify the database directly to set up test cases and make sure they work out, so this can only be done on local development machines (if you'd like to do so, it's appreciated). To test the cart frontend, go to the payment page and look for any problems with buying extra userpics or coupons. The key is to make sure that there is no way to buy extra userpics for a user who does not have a paid account. Userpic add-on packages can expire after a paid account expires, but you should never be able to purchase a userpic package which starts at a time when the user will not have a paid account. Note that SSL is not set up on the test server so you won't be able to check out using any method other than cash/check.
    Browse Options
    The previous setscheme and setlang pages have been replaced with a new Browse Options page. To test, just make sure that you are able to switch your language and site scheme.
    S2 Link List
    Our newest S2 style, Component, came with a feature that let users add a list of links to the side of their page. We decided to make this into a feature supported globally rather than on a per-style basis. As a result, there is a new link management page for creating and modifying S2 link lists. Free users are currently restricted to 5 links, while paid users are allowed 30... though those numbers are subject to change. The link list persists even if you change your style, but only works with S2 styles which currently support the feature: A Sturdy Gesture, Clean & Simple, Punquin Elegant, and Component. All of these styles should be tested to make sure that they work properly with and without link lists. Additionally, Component has received a few bugfixes from [info]xevinx and all existing Component link lists have been converted to the new format (as they will be on the live site), so you shouldn't have to retype your links.
    Atom Feeds
    We have support for Atom Feeds (example). Also, all rss feed urls of username/rss now redirect to username/data/rss. Look for Atom support to evolve as the specification is still being worked out.
    Wednesday, July 23rd, 2003
    5:32 pm
    [whitaker]
    A quick update
    We've been making a lot of minor code changes lately, so they've been going live pretty quickly. There are a few things that need to be tested now, but nothing major.
    Community Interest Search
    This was recently disabled but database changes have been made so it can be re-enabled. All pages that deal with interests were modified, so please make sure that adding/deleting/viewing/searching interests works. This includes editinfo.bml and userinfo.bml.
    CSS Cleaner
    In response to user requests, the CSS cleaner should be more lenient now and let more harmless CSS through.
    Component S2 Style
    [info]xevinx has been working to fix the final bugs with the Component S2 style. It should be bug-free now, but still needs a bit of testing. Please report any problems you come across here.
    Misc Changes
    There have also been a bunch of very minor changes that I won't mention here. You can review [info]changelog if you'd like to keep up with what is new.
    Tuesday, July 15th, 2003
    4:00 pm
    [evan]
    syndication
    Thanks for the bug reports regarding syndicated accounts. It turns out that they were never set up right on the test server, so now they’re sorta broken in the database. [info]whitaker manually fixed some of the existing accounts enough so their userinfo works, at least: sample userinfo.
    (There’s no need to report further syndication bugs, as it looks like it’s still a bit broken; the syndication cost on the userinfo there is the only recent change.)
    2:21 pm
    [evan]
    New protection against duplicate comments and some changes in user pictures went live. To test the former, try posting a comment multiple times, or try posting comments with the same text or different settings; to test the latter, maybe look at different journals’ userpics or upload your own.
    Monday, July 14th, 2003
    2:29 pm
    [evan]
    testing needed
    Ugh. Relatively major bug that didn’t show up on my server. Lemme get back to you.

    It seems that everyone* got so excited about the new style that few people noticed the bit about the new comments code. It took two days for anyone to notice that comment previews were totally broken. :)

    In theory, this code will go live soonish, so any problems will appear on the main site.

    So, again, I’d appreciate it if you check for problems with:
    • emails, both HTML and plain, including whether all the links work
    • banned users, screened comments
    • anonymous comments, logging in as one user then posting as another
    • both S1 and S2
    • translation, whether strings are disappearing
    • replying to top-level posts as well as replying to other comments
    • entering meta-data on comments
    • and of course, anything else you can think of...

    For example, can anyone reproduce this?

    * Though [info]ursamajor and [info]kamoranakrre were notable exceptions.
[ << Previous 20 ]
LiveJournal Test Server   About LiveJournal.com