Code update

[mark]

Just did a code push. The big thing in this push is the new icons you'll see on the site. Some tweaks and fixes to S2 layouts. And a lot of work on the payment system, which still is disabled, so you can't see that yet.

The issues with the crossposter are still outstanding, so if it's broken for you, it's still broken. We'll be working on it a lot this weekend.

Also, the issues with the importer are mostly resolved. There are only two outstanding issues -- the use of the mass privacy tool causing problems with some imports and importing from multiple accounts on one service -- but otherwise, the importer should be stable. If you've been holding off on importing your journal, I'd highly recommend you get it done before the Open Beta rush hits and the wait time becomes days!

As always, please let me know if you run into problems!

Edited: For more information on the S2 change I referred to in comments, please see this informational post in dw_styles. Thanks!

Comments

[mark]

Someone else was reporting this on IRC. It's because the style you're using depends on the reading page being called "friends" still, and we just changed that. It's pretty easy to fix, but you have to go into the code for your layout and change "friends" to "read".

If you want more detailed instructions, let me know, and I'll poke someone to come help. :)

[logovo]

Ah, having this same issue. Will try and see if I can fix it by doing what you suggest.

[quiara]

I tried fixing it, but I just attempted a simple find-and-replace (of all instances of "friends" with "read") and .... it didn't work. It registered errors when it compiled and, um, I have no idea what they mean. ^_^

I think I'll just switch to another layout for now till the regular Core 2 stuff comes in or until mark has time to poke at the process and put it in layman's terms. ^_^

[logovo]

Ah, thank you, I was just about to do the same thing! Will have to go back to the default styles for now.

[rydra_wong]

Ditto -- find and replace gave me error messages.

ETA: okay, some fumbling around indicates that you can't just find-and-replace "friends" to "read", or it borks things; it's $p.view == "friends" (and $p.view != "friends") that needs to change to $p.view == "read", etc..

ETA2: http://dw-styles.dreamwidth.org/5062.html

So okay, I could have saved myself the flailing around if I'd just waited five minutes, but I'm smug that I managed to find the right answer by means of a cunning strategy of randomly changing shit to see what happens.

[montanaharper]

I applaud your cunning strategy, though, and not just because it's the same one I employ. *g*

[rydra_wong]

This is the first time I've ventured into actually trying to edit the code myself! I feel very brave *g*.

[montanaharper]

First, I always recommend copying your existing layout to a text document and saving it, in case something goes horribly wrong. *g*

After the search and replace, once you get errors in the compiling process, you can scroll down to the bottom of the list of errors (in the lower frame) and find out which line it didn't like. The bad line of code will be in italics. Then you can search for that text in the upper frame, manually replace read with friends for that instance, and compile it again.

Rinse and repeat as many times as is necessary, until you get a clean compile.

I just did it for a friend's journal (I keep her styles up-to-date) and it took a few minutes but wasn't too bad in Mixit.

[quiara]

Yeah, I'm kind of a n00b for anything more complicated, style-wise, than simple CSS, but I do know to back my stuff up before I monkey with it. ^_^ Despite my not knowing my way around the layouts very well, I do habitually build/take apart computers and keep excellent backup. I just didn't see a reason to restore without first figuring out the fix for certain, rather than proceeding to re-try the thing-that-made-sense-to-me if it didn't, in fact, make sense. ^_^

[montanaharper]

I didn't mean for that to sound like a dig or anything. O.O I was just trying to go through steps in order, and that's the one thing I always forget when I'm tinkering with my layout, and then end up kicking myself about later.

Everything I know about layouts (which isn't a lot, honestly), I've learned by poking at existing code, changing things and watching how it breaks, and trying to brute-force it into doing what I want; I'm sorry if I came across sounding like I thought I was some kind of layout guru. *g*

[quiara]

I'm sorry. Long day. I just read things wrong and snarked when there was no reason.

Urgh. My normal rule is "step away from the computer till you've had a nap or some coffee."

Let's start over, 'kay? ^_^

[montanaharper]

Let's start over, 'kay? ^_^

Sure, we're cool. *g* (For the record, I wasn't upset by your comment, just concerned that I'd offended.)

[ashtoreth]

Detailed instructions for the wary [like me] would be lovely, thank you.

[trobadora]

I'd appreciate detailed instructions as well.