BingoBoingo on standyby awaiting news jfw has arrived in the oriental republic
whaack: diana_coman: EOD Report: I spent just about the entire day finishing the rough draft of my meeting with Adam. I know this is quite a problem. There may have been more spinning, although I can't say I was too hung up on what to include/not to include today. Part of the issue may have been I made the article too long, right now it is at 1,600 words. I moved my rough draft of my article on rereading to Sunday, and my Odyssey reading b
whaack: lock to tomorrow. I am going to leave the revision of the article as the last task i do tomorrow. I am worried it will drag on and _again_ eat up my other tasks.
whaack: Another side task that I have not forgotten is fixing the pingbacks appearing in my recent comments. I was tempted today to apply your fix without going through the V overhead, but I figured that was the wrong way to go about it. The problem I have is I have made a few edits to my mpwp without changing up my V tree. So if my understanding is correct there will be a problem with my manifest file when I try to apply the new patch. Wh
whaack: at's more, I built my mp-wp folder with V locally and then scp'd it over to my server. If I update mp-wp locally and try to scp it over again, i'm going to lose the few edits I've made + my photos. There is a work around for these problems, but it will require an a bit of an investigation and that is why I have not yet applied the fix.
jfw and bags arrived safe and sound.
diana_coman: jfw: glad to hear it and enjoy your time there!
diana_coman: whaack: applying code manually would not be a problem in itself (it's code and you are supposed to read & get it therefore be able to deploy it yourself!); the problem there though is from your changes: if they are useful fixes, why didn't you v-pack and publish them?
whaack: diana_coman: The change is a snippet of code that prevents the selection tool from mangling html tags. I wasn't sure if I should v-pack it because MP commented that the problem came from user error, not from anything wrong with the tool. I kept it running on my personal blog because I still believe it has some utility and I had already made the change anyways.
whaack: s/ that the problem/that the problem it fixes/
diana_coman: well, you are then quite stuck on either porting all vpatches to some local vtree branch or otherwise making all further changes manually
diana_coman: useful pain on both options there.
whaack: diana_coman: i think the right way to go about addressing the problem is to create a vpatch, even if i only use it personally
whaack: (I applied the pingbacks-in-recent-comments fix manually for now)
diana_coman: whaack: note that if you go the route of own local v-branch, you'll need to keep regrinding all future vpatches; if that's worth it, sure.
whaack: diana_coman: Ah right, I forgot there is this (drawback?) to having a manifest file. (Without the manifest file I would only have to regrind for patches that made changes to files affected by my private vpatch)
diana_coman: whaack: no, it's not a drawback to having a manifest file, ugh.
diana_coman: dorion_road: you know, by now you can probably append there a whole list of stuff that fell by the wayside.
diana_coman: it's unclear to me how do you pick out of the list and/or whether you have any defined way to pick really.
diana_coman: whaack: what that is, is the pain that signals to you that either you are doing something stupid or otherwise the rest of people around are doing something stupid.
whaack: diana_coman: ok.
BingoBoingo: http://logs.ossasepia.com/log/ossasepia/2019-12-07#1012213 << The balance I've hit is mp-wp patches touching the theme still need read and applied manually so I don't nuke the changes I made to the theme. Just have to make sure the theme folder has a name other than one included in the v-tree
ossabot: Logged on 2019-12-07 04:37:12 diana_coman: whaack: applying code manually would not be a problem in itself (it's code and you are supposed to read & get it therefore be able to deploy it yourself!); the problem there though is from your changes: if they are useful fixes, why didn't you v-pack and publish them?
diana_coman: in truth, themes should rather be branches on the mp-wp common trunk, the way I see it but this is again not entirely possible without friction atm and so the tension there + getting them mixed in, ugh.
BingoBoingo: Right. Just the way mp-wp and its predecessor is organized, the themes contain moving parts that aren't entirely restricted to a theme's functions.php file
diana_coman: myeah, it's a mess for sure.
dorion_road: http://logs.ossasepia.com/log/ossasepia/2019-12-07#1012211 << glad to hear you made it and met BingoBoingo.
ossabot: Logged on 2019-12-07 03:31:59 jfw: and bags arrived safe and sound.
dorion_road: http://logs.ossasepia.com/log/ossasepia/2019-12-07#1012223 << ok, I will append the wayside tasks.
ossabot: Logged on 2019-12-07 10:12:00 diana_coman: dorion_road: you know, by now you can probably append there a whole list of stuff that fell by the wayside.