Merge in from Deploy #768
Merged
Merge in from Deploy #768
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Totally normal way to develop software.
IDK why they're now appearing in lowercase, but the solution is to uppercase them.
This is actually a deploy problem. These RewriteRules are in photosynthesis/.htaccess, but something is going wrong on deploy, with the file not being included.
This is less efficient, but it's easier than figuring out why the Photosynthesis .htaccess file is going missing during the deploy process.
I'm not sure how PHP does the math in the functional absence of parentheses, but let's go for certainty here.
Leave this blank to be completed on deployment, so that the variable can be replaced on instances other than the prod server.
I could have sworn that I already made this change, but here we are.
Yes, I am making changes this often.
That's now part of the value of the impact statement ID.
Just what it says on the tin.
In the years since I wrote this, three things have changed. The first is that the racial identities of many legislators have become a lot more representative of Virginia. The second is that there are increasing numbers of legislators whose racial identities cannot be reduced to a label. The third is that the racial descriptors used by the house (the senate doesn't provide any) have become free-form—which is good. Anyway, this old approach doesn't work, and I need to rethink how I gather and present that data. At the moment, the data isn't accurate, in that it's too reductive and doesn't reflect people's identities. So best to remove it from here, the only place on the site where it's shown.
They were overlapping until zoomed in really, really close. Now there are weird rings around population centers, but at least the markers can be seen.
This will encourage zooming.
I prefer the DL! It's semantically right! But the layout can never be correct, because flexbox is impossible. So DIV soup it is.
There's been a frustrating problem where users are randomly are unable to register. I think I've _finally_ identified the source of the problem.
Here we both use the system's temporary directory and also respect the constant that defines the cache directory.
This is something the site had maybe a decade ago, but I accidentally broke it at some point.
I can't see any benefit here.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I do so much in Docker that I rarely use the staging site, leading to this bad practice. 🤷♂️