| 01:55 |
* |
BingoBoingo on standyby awaiting news jfw has arrived in the oriental republic |
| |
~ 1 hours 52 minutes ~ |
| 03:48 |
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 |
| 03:48 |
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. |
| 03:55 |
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 |
| 03:55 |
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. |
| |
~ 3 hours 28 minutes ~ |
| 07:24 |
* |
jfw and bags arrived safe and sound. |
| |
~ 1 hours 3 minutes ~ |
| 08:28 |
diana_coman |
jfw: glad to hear it and enjoy your time there! |
| 08:29 |
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? |
| |
~ 4 hours 54 minutes ~ |
| 13:24 |
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. |
| 13:24 |
whaack |
s/ that the problem/that the problem it fixes/ |
| 13:27 |
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 |
| 13:28 |
diana_coman |
useful pain on both options there. |
| 13:34 |
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 |
| |
~ 17 minutes ~ |
| 13:52 |
whaack |
(I applied the pingbacks-in-recent-comments fix manually for now) |
| 13:57 |
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. |
| 14:00 |
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) |
| 14:01 |
diana_coman |
whaack: no, it's not a drawback to having a manifest file, ugh. |
| 14:04 |
diana_coman |
dorion_road: you know, by now you can probably append there a whole list of stuff that fell by the wayside. |
| 14:05 |
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. |
| 14:07 |
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. |
| 14:10 |
whaack |
diana_coman: ok. |
| 14:13 |
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 |
| 14:13 |
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? |
| 14:17 |
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. |
| 14:25 |
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 |
| 14:26 |
diana_coman |
myeah, it's a mess for sure. |
| |
~ 9 hours 18 minutes ~ |
| 23:44 |
dorion_road |
http://logs.ossasepia.com/log/ossasepia/2019-12-07#1012211 << glad to hear you made it and met BingoBoingo. |
| 23:44 |
ossabot |
Logged on 2019-12-07 03:31:59 jfw: and bags arrived safe and sound. |
| 23:46 |
dorion_road |
http://logs.ossasepia.com/log/ossasepia/2019-12-07#1012223 << ok, I will append the wayside tasks. |
| 23:46 |
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. |