| 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 | [00:02] |
| 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. | [00:02] |
| jfw: | and bags arrived safe and sound. | [03:31] |
| diana_coman: | jfw: glad to hear it and enjoy your time there! | [04:35] |
| 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? | [04:37] |
| 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. | [09:31] |
| whaack: | s/ that the problem/that the problem it fixes/ | [09:32] |
| 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 | [09:35] |
| diana_coman: | useful pain on both options there. | [09:35] |
| 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 | [09:42] |
| whaack: | (I applied the pingbacks-in-recent-comments fix manually for now) | [09:59] |
| 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. | [10:04] |
| 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) | [10:08] |
| diana_coman: | whaack: no, it's not a drawback to having a manifest file, ugh. | [10:08] |
| diana_coman: | dorion_road: you know, by now you can probably append there a whole list of stuff that fell by the wayside. | [10:12] |
| 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. | [10:13] |
| 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. | [10:15] |
| whaack: | diana_coman: ok. | [10:18] |
| BingoBoingo: | http://ossasepia.com/2020/04/21/ossasepia-logs-for-07-Dec-2019#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 | [10:20] |
| 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? | [10:20] |
| 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. | [10:24] |
| 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 | [10:32] |
| diana_coman: | myeah, it's a mess for sure. | [10:33] |
| dorion_road: | http://ossasepia.com/2020/04/21/ossasepia-logs-for-07-Dec-2019#1012211 << glad to hear you made it and met BingoBoingo. | [19:52] |
| ossabot: | Logged on 2019-12-07 03:31:59 jfw: and bags arrived safe and sound. | [19:52] |
| dorion_road: | http://ossasepia.com/2020/04/21/ossasepia-logs-for-07-Dec-2019#1012223 << ok, I will append the wayside tasks. | [19:54] |
| 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. | [19:54] |
| BingoBoingo: | dorion_road: jfw contributed admirably to the day's disk destruction session. | [21:02] |
| dorion_road: | BingoBoingo hah, nice! sounds fun. pics to come ? | [21:10] |
| BingoBoingo: | dorion_road: Pics to come | [21:15] |
| BingoBoingo: | It turns out NAND chips flake, sorta like slate when you break them up | [21:18] |
| BingoBoingo: | Since the two rusty spinners ended up having metallic platters, they are cooking in a mild acid bath after having been sanded. | [21:19] |
| BingoBoingo: | Despite Samsung SSD's using pentalobe screws, a pentalobe screwdriver was found to be unecessary for shucking them to get the good stuff out of the aluminum shells. | [21:21] |
Comments feed: RSS 2.0