Code push next weekend

[denise]

We will be doing a code push next weekend: 9PM PDT Sunday 13 Jul/midnight EDT/5AM GMT Monday 14 Jul/noon PHT. (See in your time zone.) This one is mostly bugfixes and small tweaks and shouldn't be much risk for things going kerblooey, and I really hope saying that didn't just jinx us.

(Getting one more code push in before I'm out who knows how long for surgical recovery!)

Comments

[eos_joy]

Sounds good. :)

(Good luck with your surgery and recovery! ^^)

[denise]

Thanks!

[tameiki]

Thanks for the notice, Denise. I hope your surgery is successful and your recovery swift and easy. I'll be rooting for you. ^__^

[denise]

Thanks!

[fonetiks]

I hope your surgery is fast, done perfectly, and your recovery is as easy as possible. ♥

[denise]

Thanks! (My surgeon is awesome and incredibly talented, so I'm hoping it will all be over quickly.)

[juliet316]

Good luck with the surgery.

[kaleidodope]

Get well soon!

[veritas_poet]

All the best to you with the surgery!

[dickgrayson]

Good luck with surgery!

[jordannamorgan]

So nice to be on a site that not only gives advance notice of a code push, the occasion is also not a cause for dread. ;Þ

Good luck with the surgery, and a full, swift recovery!

[lot]

/crosses fingers to avoid jinx/

Good luck with your surgery! ♥

[sarajayechan]

Good luck with your recovery!

[laurose8]

Thank you. Good wishes for your health!

[bluewolf458]

Good luck with the surgery!

[susanreads]

Here's hoping code push and surgery both go smoothly!

[blaisedec]

Any chance of enabling HTTPS for more than just the login screen? It would make it safer for folks who want to use it through public Internet access.

[denise]

It's something we've talked about before, yes, and it's on our list of things we'd like to do, but it's not as easy as flipping a config switch and we're not certain whether we could support the additional load.

[jazzyjj]

Hope the surgery goes perfectly for you if you haven't already had it, because perfectly is how this site goes for me thus far. If you already had the surgery, hope it went smoothly! I recently took up reading again, thus the lateness of my comment. I mean reading as in audio books and magazines. Also known as listening.

[wessidestory]

Just out of curiosity, is one of the bug fixes possibly going to be icon keywords? Because they're a bit borked at the moment, it's almost impossible to change them.

[denise]

The only known issue with icon keywords is that if you had a "pic###" keyword (the sort that's automatically generated if you don't give an icon a keyword when you upload it), renaming that icon's keywords will cause issues. It's a known bug and we've been trying to fix it, but it's proven more complex than we'd hoped and we haven't been able to fix it yet. The only workaround is to be sure to assign keywords to your icons when you upload them; the "pic###" auto-assigned keywords really are a fallback and you shouldn't rely on them.

If you mean something else, then that's something that hasn't been reported to us. Best thing to do is open a support request.

[wessidestory]

That is what I meant- and I appreciate the quick answer! Thank you very much. I'll be sure to not rely on them like I have been. It's mostly a laziness issue, haha.

[denise]

Yes, I have the feeling that the ultimate fix is going to include making it impossible for people to upload icons without keywording them, because those fallback keywords are treated very weirdly in the code, and it's probably going to be easier to require people to set keywords than it would be to make sure fallback keywords are handled properly...

[azurelunatic]

I wonder if a workaround might be "accept automatically assigned keyword 'pic#####' or set your own" where the same autogenerated keyword is used, but saved as though it were a user-entered one?