github: shadowy octopus with the head of a robot, emblazoned with the Dreamwidth swirl (Default)
Branch: refs/heads/develop
Home: https://github.com/dreamwidth/dw-free
Commit: 9c68d12c92e8943576c39a6dc831c83dfa9f901d
https://github.com/dreamwidth/dw-free/commit/9c68d12c92e8943576c39a6dc831c83dfa9f901d
Author: Kareila <kareila@dreamwidth.org>
Date: 2017-04-26 (Wed, 26 Apr 2017)

Changed paths:
M cgi-bin/DW/Proxy.pm
M t/https-url.t

Log Message:
-----------
convert URL space to %20 in get_proxy_url subroutine

This will change the link returned by the proxy to use %20 if the
original URL included a space, which is what most browsers will
expect. Without this transformation, requests that changed
spaces to %20 would fail because the checksums wouldn't match.

Fixes #2134.


Commit: 90162620fee3f26d61eba669a8d6e4a9395ea649
https://github.com/dreamwidth/dw-free/commit/90162620fee3f26d61eba669a8d6e4a9395ea649
Author: alierak <alierak@gmail.com>
Date: 2017-04-26 (Wed, 26 Apr 2017)

Changed paths:
M cgi-bin/DW/Proxy.pm
M t/https-url.t

Log Message:
-----------
Merge pull request #2143 from kareila/2134-urlspaces

convert URL space to %20 in get_proxy_url subroutine


Compare: https://github.com/dreamwidth/dw-free/compare/891e920ab716...90162620fee3
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
Our content importer has mostly caught up with its backlog; almost everything that's still listed as being "in the queue" are jobs that were tried, failed once or more with a temporary failure, and are waiting to try again. (The importer tries a few times, at successively longer intervals, when it gets a failure it thinks might be temporary/might correct itself later on.) This means that new imports scheduled now should complete in hours (or even minutes), not the "several days" it's been taking.

If you tried to schedule a second import while the first one was still running, at any time in the past 10 days or so, you may have confused the poor thing. If you think your import should be finished by now and it isn't, and you're seeing "Aborted" on the Importer Status part of the Importer page, feel free to open a support request in the Importer category and we'll look into it for you. (It may take a little bit before you get a response; those of us who have the access to look into importer problems have been really busy for the past two weeks or so, and I at least need a few days to catch my breath a bit before diving back into the fray! But we'll do what we can.)

I hope all y'all are continuing to settle in well to your new home!
github: shadowy octopus with the head of a robot, emblazoned with the Dreamwidth swirl (Default)
Branch: refs/heads/develop
Home: https://github.com/dreamwidth/dw-nonfree
Commit: 09dc19e0f33e6acbb587e7781958a5bfb9406ed1
https://github.com/dreamwidth/dw-nonfree/commit/09dc19e0f33e6acbb587e7781958a5bfb9406ed1
Author: NightFlyer <nightflyer.dw@nocturnalaviation.com>
Date: 2017-04-19 (Wed, 19 Apr 2017)

Changed paths:
M views/legal/diversity.tt

Log Message:
-----------
Fix typo in diversity statement

Fixes #2124


Commit: d6c357df553bdf6201bb7574f0d5710cb57f99d7
https://github.com/dreamwidth/dw-nonfree/commit/d6c357df553bdf6201bb7574f0d5710cb57f99d7
Author: Denise Paolucci <denise@dreamwidth.org>
Date: 2017-04-19 (Wed, 19 Apr 2017)

Changed paths:
M views/legal/diversity.tt

Log Message:
-----------
Merge pull request #120 from NightFlyer/DiversityStatementTypo-bug-2124

Fixes dw-free/2124. (And welcome to new contributor NightFlyer!)

Fix typo in diversity statement


Compare: https://github.com/dreamwidth/dw-nonfree/compare/5a6f87c509fd...d6c357df553b

[done] Dreamhack maintenance reminder

Apr. 19th, 2017 09:31 am[personal profile] sophie posting in [site community profile] dw_dev
sophie: A cartoon-like representation of a girl standing on a hill, with brown hair, blue eyes, a flowery top, and blue skirt. ☀ (Default)
As mentioned in my last post, I will be taking the Dreamhack server down for maintenance in 30 minutes! I'll edit this post once it starts and again when it's back up.

10:04am BST: I have restricted logins to admins and am beginning the maintenance now. This will involve a reboot and some diagnostics before opening it back up.

10:58am BST: The maintenance is done, and logins are unrestricted again!
sophie: A cartoon-like representation of a girl standing on a hill, with brown hair, blue eyes, a flowery top, and blue skirt. ☀ (Default)
Hi all,

I'm going to need to schedule some maintenance for the Dreamhack server as I've just discovered that the quota settings haven't taken effect. I'm therefore going to schedule maintenance for Wednesday 2017-04-19, 10am BST (5am EDT, 2am PDT) (about 36 hours from now) for up to 2 hours. (It shouldn't actually take that long, but I'm reserving it just in case.)

This maintenance will involve a reboot of the Dreamhack server. I will also be restricting logins until the maintenance is done, as the nature of the maintenance means that it will need as little data modification done as possible.

I'll post again once the maintenance starts, and edit that post when it ends.
github: shadowy octopus with the head of a robot, emblazoned with the Dreamwidth swirl (Default)
Branch: refs/heads/develop
Home: https://github.com/dreamwidth/dw-free
Commit: 891e920ab716a284d629463b4ad0d0a40cd1ad79
https://github.com/dreamwidth/dw-free/commit/891e920ab716a284d629463b4ad0d0a40cd1ad79
Author: Mark Smith <mark@dreamwidth.org>
Date: 2017-04-17 (Mon, 17 Apr 2017)

Changed paths:
M cgi-bin/Apache/LiveJournal.pm
M cgi-bin/LJ/Web.pm

Log Message:
-----------
Fix redirect for query strings

Certain codepaths use querystrings that do not contain arguments and
instead are just plaintext. This codepath was only passing through valid
looking arguments. This updates it to always use the raw query string.

Fixes #2121.
github: shadowy octopus with the head of a robot, emblazoned with the Dreamwidth swirl (Default)
Branch: refs/heads/release-1.32
Home: https://github.com/dreamwidth/dw-free
Commit: c1e47cd76e6cd881045b53744d68655ff74e0bbb
https://github.com/dreamwidth/dw-free/commit/c1e47cd76e6cd881045b53744d68655ff74e0bbb
Author: Mark Smith <mark@dreamwidth.org>
Date: 2017-04-17 (Mon, 17 Apr 2017)

Changed paths:
M cgi-bin/Apache/LiveJournal.pm
M cgi-bin/LJ/Web.pm

Log Message:
-----------
Fix redirect for query strings

Certain codepaths use querystrings that do not contain arguments and
instead are just plaintext. This codepath was only passing through valid
looking arguments. This updates it to always use the raw query string.


Commit: b94c7efbf8101a501207a577e1b4bec2d0138154
https://github.com/dreamwidth/dw-free/commit/b94c7efbf8101a501207a577e1b4bec2d0138154
Author: Jen <kareila@dreamwidth.org>
Date: 2017-04-17 (Mon, 17 Apr 2017)

Changed paths:
M cgi-bin/Apache/LiveJournal.pm
M cgi-bin/LJ/Web.pm

Log Message:
-----------
Merge pull request #2122 from zorkian/fix-redir

Fix redirect for query strings - fixes #2121.


Compare: https://github.com/dreamwidth/dw-free/compare/1d34018a37d8...b94c7efbf810

[dreamwidth/dw-free]

Apr. 16th, 2017 10:39 pm[personal profile] github posting in [site community profile] changelog
github: shadowy octopus with the head of a robot, emblazoned with the Dreamwidth swirl (Default)
Branch: refs/heads/fix-redir
Home: https://github.com/dreamwidth/dw-free
github: shadowy octopus with the head of a robot, emblazoned with the Dreamwidth swirl (Default)
Branch: refs/heads/fix-redir
Home: https://github.com/dreamwidth/dw-free
Commit: c1e47cd76e6cd881045b53744d68655ff74e0bbb
https://github.com/dreamwidth/dw-free/commit/c1e47cd76e6cd881045b53744d68655ff74e0bbb
Author: Mark Smith <mark@dreamwidth.org>
Date: 2017-04-17 (Mon, 17 Apr 2017)

Changed paths:
M cgi-bin/Apache/LiveJournal.pm
M cgi-bin/LJ/Web.pm

Log Message:
-----------
Fix redirect for query strings

Certain codepaths use querystrings that do not contain arguments and
instead are just plaintext. This codepath was only passing through valid
looking arguments. This updates it to always use the raw query string.

Dreamhack applications are now open!

Apr. 16th, 2017 10:19 am[personal profile] sophie posting in [site community profile] dw_dev
sophie: A cartoon-like representation of a girl standing on a hill, with brown hair, blue eyes, a flowery top, and blue skirt. ☀ (Default)
Apologies again for the delay on this - Dreamhack applications are now officially open again!

As I explained in my previous post (which you should read if you haven't already - there's a lot of info in there), anybody who wants a Dreamhack should apply through this form, even if you already had one before. I will, as a one-time thing, email everybody who had an account before to let them know that the service is back up and that they'll need to re-apply.

My apologies once again for the delay! If you find any issues with the service, please feel free to let me know.
siderea: (Default)

Title:
Page Statistics 2: Electric Boogaloo

Area:
entries

Summary:
Native journal stats, like LJ used to do, only not horribly invasive like LJ. How many, not whom. Also integrated into the DW user interface.

Description:
Way back when, somebody else suggested, in a suggestion titled Page stats (http://dw-suggestions.dreamwidth.org/570175.html), "something like LiveJournal's My Guests feature", and the commenters here promptly set the suggestion on fire and then drowned it. The My Guests feature of the LJ Stats page makes *reading* journals less private, and gave many DW Suggestion commenters the heebee-geebees.

Unfortunately, that was the end of the proposal to implement any of the LJ Stats Page here. Unfortunately, because the LJ Stats Page also had lots of other useful analytics information, that was in aggregate and didn't violate anybody's privacy. For instance, from my LJ Stats page I just discovered that my LJ typically gets about 35 daily hits to my journal's RSS feed – information that would otherwise be utterly invisible to me. Since in the past I've wondered if anybody cares about RSS, that is usefully informative to me. For another instance, I am able to see how many visitors – not, mind you, LJ users, just unique visitors – came to a given post. If I had the same stats here on DW, I would be able to see how my efforts to move my readers from LJ to here were working.

When last this was proposed, one of the questions a commenter reasonably asked was "How is it different from the Google stats feature available for paid DW accounts?"

1) It doesn't involve Google for one thing. I have two big problems with Google Analytics:

1a) It is, to me, a much bigger privacy violation than My Guests ever was. My Guests was optional: if you ever wanted not to be counted, you turned it off and you never appeared in anybody's My Guest report. I, as a reader, have no way to opt out of GA – except to use a script blocker to clobber GA, which I in fact do, because....

1b) Google Analytics' degrades site performance. I have to block the GA scripts at my browser, because otherwise, from time to time, page loads start hanging on trying to communicate with google-analytics.com. I don't want GA on my journal both because I don't want to inflict on my readers a privacy compromise I don't want inflicted on myself, and I don't want to inflict on either me or my readers the page load times GA periodically (or is it always? as I said, I block it) causes.

2) As per 1b above, GA is client-side and third party. I don't want this sort of functionality coming through *any* third-party javascript. It will always tax the user's browser and internet connection, and expose information to a third-party. I have no interest in trusting any third-party with, for example, statistics *about my locked posts* the existence of which should be a private.

3) Not having a GA account I can't say what it includes in its reports, but knowing what I do about its implementation, I'm guessing it has no way to tell you *the number of times your post appeared on other parts of the site*. AFAIK, GA only knows – only *can* know – about the concept of "webpages". LJ's Stats would give you *two* numbers: the number of unique visitors to a post's page *and* the numbers of unique viewers of your post _in all the other places it appears on LJ_, such as on friends pages, your own Recent Entires pages, your Calendar pages, etc. LJ Stats leverages LJ's knowledge of its own info-architecture to come up with stats that GA can't.

Finally, it would be great if the interface for such a thing were integrated into the general DW journal interface, such that journal owners would have a contextual stats icon/link (visible only to them) wherever appropriate, that takes them to the corresponding stats page. For instance, such a link would appear on posts, and would take one to the stats page for that specific post. One's Calendar would have it on the day, month, and year views, and take one to one's corresponding day, month, and year stats pages. And that's not something that GA or any third-party javascript-based analytics implementation could manage.

More Details

When last this came around, it became clear most commenters didn't know what LJ did provide. Here's an overview:

There are four top level categories to the Stats page that I propose are of interest to DW: Journal, Comments, Entries, and RSS Readers.

The Journal page shows stats for your whole journal, breaking it out by number of total visits, total unique vistors, and how many of those unique visitors were logged-in LJ users. It allows you to view this information by either your journal itself, or your journal plus all friends pages on which your posts appear, and it allows you to drill down in either of these views to any year (shows bar chart by month), month (shows bar chart by day), or day (shows bar chart by hour). This last allows one to get a sense of on what days and at what times of the day one's readers are seeing one's journal.

The Comments page shows the stats on numbers of comments and numbers of commenters. Like the Journal page, you can drill down by time span.

The Entries page shows the stats for a given entry (post). It defaults to the most recent entry in your journal, has a list at the bottom of your ten most recent posts with links to their stat pages, for user convenience, and a text box in which you can put the URL to any of your entries to get the stats for it (not the most convenient of user interfaces). For a given entry, it shows Visits, viewers ("Who Viewed"), and Comments. Visits breaks out by Entry Views, All Visitors and Livejournal Visitors. "Entry Views" is the other sense of "entry": when that page is the page-of-entry of a reader to LJ – what happens when somebody follows a link somewhere else, like Twitter or Tumblr or FB or an RSS reader or an email, to a post of yours. That gives one a sense of how much traffic is being driven to a post by virality elsewhere. Visits also allows drill down by year/month/day, same as above. "Who Viewed" gives a break down between the number of all viewers of the post vs. the number of the subset that are Friends of you - it shows you whether it's just Friends reading your posts or other people. Also allows drill down by year/month/day. "Comments" shows comments vs number of unique commenters for the post, with year/month/day drill down.

The RSS Readers page shows a chart of number of requests to one's RSS feed, with drill down by year/month/day.

Poll #18206 Page Statistics 2: Electric Boogaloo
Open to: Registered Users, detailed results viewable to: All, participants: 32


This suggestion:

View Answers

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

Should be implemented with changes. (please comment)
4 (12.5%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
9 (28.1%)

(Other: please comment)
0 (0.0%)

solarbird: (Default)

Title:
"Activity"-like view of 1st page of Inbox, in a dropdown, from Navigation Strip

Area:
navigation strip, messaging

Summary:
It is currently very easy to configure your Inbox to serve as an activity notification hub. It would be very useful to have a shorted version of the first page of that Inbox be accessible via a dropdown on the Navigation Strip, and allow some manipulation of your Inbox via that dropdown.

Description:
Each line of the proposed dropdown would contain a one line description of the activity. (N replied to [your post|comment], N messaged you, subject "", N posted to group X, and so on). Each entry would contain an "x" dismissal button which would delete the notification from both the Inbox and the dropdown. Clicking on an individual entry outside of the dismissal button would take you to the item about which you are being notified - the message, the comment made, etc - and mark it as read. A "see all" entry at the bottom of the dropdown could take you to the current Inbox view. Currently, using the Inbox as a notification centre results in large numbers of page swaps and reloads, as you go from Inbox to post to Inbox to reply form to Inbox etc., etc., etc., with mark-as-read and delete-item as separate actions across separate pages. Further, it is difficult to maintain (de-clutter, etc) without engaging in that maintenance as a separate task. As a result, those of us who have this issue end up with over-full Inboxes that we tend to bulk-delete. This suggested feature would allow us both to use our Inbox more easily and maintain it more effectively, resulting in improved usability of the service and - hopefully - fewer notifications being stored on the servers.

Poll #18205 "Activity"-like view of 1st page of Inbox, in a dropdown, from Navigation Strip
Open to: Registered Users, detailed results viewable to: All, participants: 30


This suggestion:

View Answers

Should be implemented as-is.
5 (16.7%)

Should be implemented with changes. (please comment)
5 (16.7%)

Shouldn't be implemented.
5 (16.7%)

(I have no opinion)
15 (50.0%)

(Other: please comment)
0 (0.0%)

melannen: Commander Valentine of Alpha Squad Seven, a red-haired female Nick Fury in space, smoking contemplatively (Default)

Title:
When uploading images, display most recent upload at top

Area:
Upload Images page

Summary:
On the wonderful, amazing new image upload page, it would be nice to be able to immediately tell if the correct image uploaded. Changing the display so the most recent image is on top would fix this.

Description:
Most of the time when I use the image upload page, it's from my phone camera, on a tiny mobile screen. Currently, when I'm uploading multiple images, the only way to tell if an image was correctly uploaded is to scroll down to the bottom of the page to see it, and then scroll back to the top to upload the next image. This quickly gets tedious with more than a couple images. If the new image preview appeared directly below the upload box, it would be immediately visible and make workflow much smoother on mobile. I can't think how it would make it harder for anyone. (If that's not technically doable for some reason, any kind of upload confirmation that is visible near the upload box on mobile would be nice.)

Poll #18204 When uploading images, display most recent upload at top
Open to: Registered Users, detailed results viewable to: All, participants: 38


This suggestion:

View Answers

Should be implemented as-is.
32 (84.2%)

Should be implemented with changes. (please comment)
1 (2.6%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
5 (13.2%)

(Other: please comment)
0 (0.0%)

ninetydegrees: Drawing: a girl's face, with a yellow and green stripe over one eye (Default)

Title:
Support Board: add exclude filter

Area:
support, site interface

Summary:
The Support Board has a filter to show you all requests from category Z. I'd like the opposite of that: show me all requests but the ones from category Z.

Description:
The board could certainly do with more complex filter options such as letting you filter and exclude multiple categories but that's a discussion for when the board will get a full redesign. I think the exclude Z filter would be a simple yet still practical option for now.

Poll #18203 Support Board: add exclude filter
Open to: Registered Users, detailed results viewable to: All, participants: 31


This suggestion:

View Answers

Should be implemented as-is.
20 (64.5%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
11 (35.5%)

(Other: please comment)
0 (0.0%)

marahmarie: Sheep go to heaven, goats go to hell (Default)

Title:
Unscreen your comments from Post Comment Success page

Area:
entry comments

Summary:
Dreamwidth screened comment settings currently entail screening our own comments when we choose to screen all comments on our journals (I'm not sure if this behavior is the same for communities). I'd like to suggest we save time for journal owners, specifically, by allowing them to unscreen their own comments from the Post Comment Success page.

Description:
Dreamwidth screened comment settings currently entail screening our own comments when we choose to screen all comments on our journals (I'm not sure if this behavior is the same for communities). I'd like to suggest we save time for journal owners, specifically, by allowing them to unscreen their own comments from the Post Comment Success page (https://www.dreamwidth.org/talkpost_do). This saves time - no more going back to the entry or your DW Inbox or off-site email to find and unscreen the comment you just replied made in reply to someone.

Poll #18202 Unscreen your comments from Post Comment Success page
Open to: Registered Users, detailed results viewable to: All, participants: 29


This suggestion:

View Answers

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

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
15 (51.7%)

(Other: please comment)
0 (0.0%)

Quick jump to next/previous entry

Mar. 27th, 2017 11:11 pm[personal profile] allen posting in [site community profile] dw_suggestions
allen: (Default)

Title:
Quick jump to next/previous entry


Area:
reading page


Summary:
Add a javascript function to skip to the next or previous entry in your reading page. The function would be available either through a sticky element for desktop, or through a swipe gesture for mobile.


Description:
This is kind of like the Jump Links suggestion (which it looks like was accepted but lost in the bugzilla crash), but with a few differences.


The problem that it's supposed to solve is for when you end up with some long, uncut entries on your reading page (like from changelog or an RSS feed). And then you want to go to the next entry, but end up hitting page down a whole lot. Or worse, you're in mobile and you have to scroll down and keep scrolling and scrolling...


So the idea is to have a javascript function available to scroll to the next (or previous) entry in your page. This could be made available with a sticky module which would be available either in one of the sidebars or (if you don't have a sidebar) at the top of the main entry area. It would have just a 'Next' and 'Previous' button, which would take you to the next or previous entry in your reading list.


We could also include a jquery touch plugin that would add the same functionality with, say, a two-finger swipe up or down.



Edit 2017-04-24 I don't see much love for the sticky idea, but having a way to configure an optional shortcut has at least some support. So now I'm thinking a new tab in My Account Settings for Shortcuts, which would have options for

Enable keyboard shortcuts (checkbox, default unchecked)
Next (text field, default j)
Previous (text field, default k)
Enable touch shorcuts (checkbox, default unchecked)
Next (options for swipe/disabled, 1,2,or 3 fingers, and up/down/left/right)
Previous (options for swipe/disabled, 1,2,or 3 fingers, and up/down/left/right)

I could also add a way to make a link call the JS function so that anyone who wanted to use links instead of key bindings or touch gestures could just include those in their styles.

Poll #18201 Quick jump to next/previous entry
Open to: Registered Users, detailed results viewable to: All, participants: 26


This suggestion:

View Answers

Should be implemented as-is.
5 (19.2%)

Should be implemented with changes. (please comment)
4 (15.4%)

Shouldn't be implemented.
10 (38.5%)

(I have no opinion)
5 (19.2%)

(Other: please comment)
2 (7.7%)

github: shadowy octopus with the head of a robot, emblazoned with the Dreamwidth swirl (Default)
Branch: refs/heads/develop
Home: https://github.com/dreamwidth/dw-free
Commit: 03abdb33eea316ee1657f5bae44198f1b3b67db9
https://github.com/dreamwidth/dw-free/commit/03abdb33eea316ee1657f5bae44198f1b3b67db9
Author: Kareila <kareila@dreamwidth.org>
Date: 2017-04-15 (Sat, 15 Apr 2017)

Changed paths:
M cgi-bin/lj-bml-blocks.pl

Log Message:
-----------
syntax error - missing semicolon

Was masked by conditional braces which were removed in #2116.
github: shadowy octopus with the head of a robot, emblazoned with the Dreamwidth swirl (Default)
Branch: refs/heads/develop
Home: https://github.com/dreamwidth/dw-free
Commit: 54e5f2f8020a75a864b1408904849daf6ab7f415
https://github.com/dreamwidth/dw-free/commit/54e5f2f8020a75a864b1408904849daf6ab7f415
Author: Kareila <kareila@dreamwidth.org>
Date: 2017-04-15 (Sat, 15 Apr 2017)

Changed paths:
M cgi-bin/LJ/Console/Command/Finduser.pm

Log Message:
-----------
[#2078] add OpenID search to finduser console command

Syntax: finduser openid

Fixes #2078.


Commit: 6d6864f431975ac2f69c05dfbe559666d8ecdd2a
https://github.com/dreamwidth/dw-free/commit/6d6864f431975ac2f69c05dfbe559666d8ecdd2a
Author: Mark Smith <mark@qq.is>
Date: 2017-04-14 (Fri, 14 Apr 2017)

Changed paths:
M cgi-bin/LJ/Console/Command/Finduser.pm

Log Message:
-----------
Merge pull request #2117 from kareila/2078-finduser

[#2078] add OpenID search to finduser console command


Compare: https://github.com/dreamwidth/dw-free/compare/abd4f10f016e...6d6864f43197
github: shadowy octopus with the head of a robot, emblazoned with the Dreamwidth swirl (Default)
Branch: refs/heads/develop
Home: https://github.com/dreamwidth/dw-free
Commit: fad527f2a1fef89343351820434b899c728689ea
https://github.com/dreamwidth/dw-free/commit/fad527f2a1fef89343351820434b899c728689ea
Author: Kareila <kareila@dreamwidth.org>
Date: 2017-04-07 (Fri, 07 Apr 2017)

Changed paths:
M cgi-bin/LJ/Global/Img.pm
A htdocs/img/btn_trash.gif
R htdocs/img/portal/btn_del.gif

Log Message:
-----------
rename portal/btn_del.gif to btn_trash.gif

Portal is no longer a thing, so let's move this up with the
other buttons and give it a more accurate name.


Commit: 4df5920eb177be25a3ac3e08006becbb3334dbb6
https://github.com/dreamwidth/dw-free/commit/4df5920eb177be25a3ac3e08006becbb3334dbb6
Author: Kareila <kareila@dreamwidth.org>
Date: 2017-04-08 (Sat, 08 Apr 2017)

Changed paths:
M cgi-bin/DW/Controller/Community.pm

Log Message:
-----------
undefined variable warning in DW/Controller/Community.pm

Use of uninitialized value in pattern match (m//) ..
cgi-bin/DW/Controller/Community.pm line 177.

This happens when creating a new community on a dev server.


Commit: 165b1b1dc8b0b0dd52e2e97d67133512cb5f3064
https://github.com/dreamwidth/dw-free/commit/165b1b1dc8b0b0dd52e2e97d67133512cb5f3064
Author: Kareila <kareila@dreamwidth.org>
Date: 2017-04-09 (Sun, 09 Apr 2017)

Changed paths:
M t/protocol.t

Log Message:
-----------
fix failing test in t/protocol.t

Protocol error 157 was removed in #1739.

The test suite as a whole still suffers from inconsistent
behavior of content filters; I've documented the misbehaving
tests here with FIXME comments.


Commit: 271d992cd47148f36912366a3d42e1eb85743e43
https://github.com/dreamwidth/dw-free/commit/271d992cd47148f36912366a3d42e1eb85743e43
Author: Kareila <kareila@dreamwidth.org>
Date: 2017-04-12 (Wed, 12 Apr 2017)

Changed paths:
M cgi-bin/LJ/Event/JournalNewComment/Reply.pm

Log Message:
-----------
undefined variable warnings in LJ/Event/JournalNewComment/Reply.pm

Use of uninitialized value in string ne .. cgi-bin/LJ/Event/JournalNewComment/Reply.pm line 100.

Use of uninitialized value in string eq .. cgi-bin/LJ/Event/JournalNewComment/Reply.pm line 101.


Commit: 1cbe8d4b987f13e8b732ec93a9ab42dc6af3e090
https://github.com/dreamwidth/dw-free/commit/1cbe8d4b987f13e8b732ec93a9ab42dc6af3e090
Author: Kareila <kareila@dreamwidth.org>
Date: 2017-04-13 (Thu, 13 Apr 2017)

Changed paths:
M htdocs/admin/vgifts/index.bml
M htdocs/admin/vgifts/index.bml.text

Log Message:
-----------
fix translation string on /admin/vgifts


Commit: 331352368fad618d3d006fa3af2e5b6ad5556340
https://github.com/dreamwidth/dw-free/commit/331352368fad618d3d006fa3af2e5b6ad5556340
Author: Kareila <kareila@dreamwidth.org>
Date: 2017-04-13 (Thu, 13 Apr 2017)

Changed paths:
M htdocs/openid/index.bml.text
M htdocs/openid/login.bml.text
M htdocs/site/opensource.bml.text

Log Message:
-----------
remove .bml from site links in translation strings

I'm assuming these were already fixed on the live site.


Commit: addb167ae259c081317db45383d02b34d8668946
https://github.com/dreamwidth/dw-free/commit/addb167ae259c081317db45383d02b34d8668946
Author: Kareila <kareila@dreamwidth.org>
Date: 2017-04-13 (Thu, 13 Apr 2017)

Changed paths:
M cgi-bin/LJ/CleanHTML.pm

Log Message:
-----------
remove AOL http -> ftp link rewrite code

The 1990s called, they want their ridiculous workaround back.


Commit: ad73e60ed3ef492227fdd797d5c150c3a67c1f9d
https://github.com/dreamwidth/dw-free/commit/ad73e60ed3ef492227fdd797d5c150c3a67c1f9d
Author: Kareila <kareila@dreamwidth.org>
Date: 2017-04-14 (Fri, 14 Apr 2017)

Changed paths:
M bin/upgrading/deadphrases.dat
M htdocs/modify_do.bml.text

Log Message:
-----------
remove unused strings from modify_do.bml.text


Commit: 514048d97506cd156120fdb3a5c802664e73a0af
https://github.com/dreamwidth/dw-free/commit/514048d97506cd156120fdb3a5c802664e73a0af
Author: Kareila <kareila@dreamwidth.org>
Date: 2017-04-14 (Fri, 14 Apr 2017)

Changed paths:
M bin/upgrading/deadphrases.dat
M bin/upgrading/en.dat
M cgi-bin/LJ/Customize.pm
R htdocs/modify_do.bml.text

Log Message:
-----------
move .moodicons.personal string into en.dat

This was the only string remaining in modify_do.bml.text.


Commit: 8aff15c4641ef26c7ec6d1673dcbbb6456ebc8cb
https://github.com/dreamwidth/dw-free/commit/8aff15c4641ef26c7ec6d1673dcbbb6456ebc8cb
Author: Kareila <kareila@dreamwidth.org>
Date: 2017-04-14 (Fri, 14 Apr 2017)

Changed paths:
A cgi-bin/DW/Controller/Admin/EventOutput.pm
R cgi-bin/DW/Controller/EventOutput.pm

Log Message:
-----------
DW::Controller::EventOutput is an admin page

Should be DW::Controller::Admin::EventOutput.


Commit: abd4f10f016eeefd4e568c80e3cdb85273cdf303
https://github.com/dreamwidth/dw-free/commit/abd4f10f016eeefd4e568c80e3cdb85273cdf303
Author: Mark Smith <mark@qq.is>
Date: 2017-04-14 (Fri, 14 Apr 2017)

Changed paths:
M bin/upgrading/deadphrases.dat
M bin/upgrading/en.dat
A cgi-bin/DW/Controller/Admin/EventOutput.pm
M cgi-bin/DW/Controller/Community.pm
R cgi-bin/DW/Controller/EventOutput.pm
M cgi-bin/LJ/CleanHTML.pm
M cgi-bin/LJ/Customize.pm
M cgi-bin/LJ/Event/JournalNewComment/Reply.pm
M cgi-bin/LJ/Global/Img.pm
M htdocs/admin/vgifts/index.bml
M htdocs/admin/vgifts/index.bml.text
A htdocs/img/btn_trash.gif
R htdocs/img/portal/btn_del.gif
R htdocs/modify_do.bml.text
M htdocs/openid/index.bml.text
M htdocs/openid/login.bml.text
M htdocs/site/opensource.bml.text
M t/protocol.t

Log Message:
-----------
Merge pull request #2118 from kareila/cleanup-2017q2

Cleanup 2017q2


Compare: https://github.com/dreamwidth/dw-free/compare/b6b7a595a838...abd4f10f016e
github: shadowy octopus with the head of a robot, emblazoned with the Dreamwidth swirl (Default)
Branch: refs/heads/develop
Home: https://github.com/dreamwidth/dw-free
Commit: a75dd3c0bce4d912385a63aa29a1c16ccbcbafe8
https://github.com/dreamwidth/dw-free/commit/a75dd3c0bce4d912385a63aa29a1c16ccbcbafe8
Author: Kareila <kareila@dreamwidth.org>
Date: 2017-04-14 (Fri, 14 Apr 2017)

Changed paths:
M styles/goldleaf/layout.s2
M styles/venture/layout.s2

Log Message:
-----------
STRIP TRAILING WHITESPACE


Commit: 1e186d3403d30ea5693fccbd8e0ac3a93d8ca827
https://github.com/dreamwidth/dw-free/commit/1e186d3403d30ea5693fccbd8e0ac3a93d8ca827
Author: Kareila <kareila@dreamwidth.org>
Date: 2017-04-14 (Fri, 14 Apr 2017)

Changed paths:
M styles/goldleaf/layout.s2
M styles/venture/layout.s2

Log Message:
-----------
fix insecure font_sources


Commit: cef6c97829a31b670bd3c63e3019d33d6662591b
https://github.com/dreamwidth/dw-free/commit/cef6c97829a31b670bd3c63e3019d33d6662591b
Author: Kareila <kareila@dreamwidth.org>
Date: 2017-04-14 (Fri, 14 Apr 2017)

Changed paths:
M cgi-bin/LJ/EmbedModule.pm

Log Message:
-----------
vimeo has https support


Commit: d71321c6676508780bf4f8f003cb91c1edf4e6e5
https://github.com/dreamwidth/dw-free/commit/d71321c6676508780bf4f8f003cb91c1edf4e6e5
Author: Kareila <kareila@dreamwidth.org>
Date: 2017-04-14 (Fri, 14 Apr 2017)

Changed paths:
M bin/worker/incoming-email

Log Message:
-----------
future-proof incoming-email worker to look for https in requests

Also removes the .bml part of the regexp, which was likely a bug.


Commit: 405ce6642b34daea17e4052e693b0a8357924f88
https://github.com/dreamwidth/dw-free/commit/405ce6642b34daea17e4052e693b0a8357924f88
Author: Kareila <kareila@dreamwidth.org>
Date: 2017-04-14 (Fri, 14 Apr 2017)

Changed paths:
M htdocs/login.bml

Log Message:
-----------
[#2072] remove siteroot? from form action link on /login

Was showing up as http: regardless of requested protocol.

Just use /pagename - that's what we do most other places.


Commit: b6b7a595a8388559beab8627c4c3336b3bfd7e7a
https://github.com/dreamwidth/dw-free/commit/b6b7a595a8388559beab8627c4c3336b3bfd7e7a
Author: Mark Smith <mark@qq.is>
Date: 2017-04-14 (Fri, 14 Apr 2017)

Changed paths:
M bin/worker/incoming-email
M cgi-bin/LJ/EmbedModule.pm
M htdocs/login.bml
M styles/goldleaf/layout.s2
M styles/venture/layout.s2

Log Message:
-----------
Merge pull request #2113 from kareila/2072-http

various http: to https: fixes


Compare: https://github.com/dreamwidth/dw-free/compare/f4cd51ec8c5f...b6b7a595a838

July 2015

S M T W T F S
   1234
56 7891011
12131415161718
19202122232425
262728293031 

Page Summary

Style Credit

Expand Cut Tags

No cut tags
Page generated Apr. 27th, 2017 03:23 am
Powered by Dreamwidth Studios