[00:21:57] | * eddieironsmith[m has quit (*.net *.split) |
[00:21:58] | * botlfarm[m] has quit (*.net *.split) |
[00:21:58] | * skipper_is[m] has quit (*.net *.split) |
[00:23:30] | * eddieironsmith[m has joined #farmos |
[00:27:00] | * runfastthinkslow has quit (*.net *.split) |
[00:27:00] | * EvanKelley[m] has quit (*.net *.split) |
[00:29:05] | * skipper_is[m] has joined #farmos |
[00:30:08] | * symbioquine[m] has quit (*.net *.split) |
[00:33:47] | * botlfarm[m] has joined #farmos |
[00:37:20] | * runfastthinkslow has joined #farmos |
[00:39:52] | * EvanKelley[m] has joined #farmos |
[00:45:18] | * symbioquine[m] has joined #farmos |
[06:34:17] | * farmBOT has joined #farmos |
[07:35:00] | * better_sleeping[ has joined #farmos |
[07:38:16] | * better_sleeping[ has left #farmos () |
[11:28:21] | <mstenta[m]> | Just made a `2.x-9.4.0` branch to update Drupal core to 9.4.0. |
[11:28:30] | <mstenta[m]> | Tests are passing: https://github.com/mstenta/farmOS/actions/runs/2529867880 |
[11:28:32] | <mstenta[m]> | Haven't tested manually yet. |
[11:28:43] | <mstenta[m]> | Reviewing change records now: https://www.drupal.org/list-changes/drupal/published?to_branch=9.4.x |
[11:29:50] | <mstenta[m]> | Some notable changes that might be useful to us in the future: |
[11:31:17] | <mstenta[m]> | - https://www.drupal.org/node/3262453 |
[11:31:17] | <mstenta[m]> | - https://www.drupal.org/node/3259199 |
[11:31:17] | <mstenta[m]> | - https://www.drupal.org/node/3261680 |
[11:31:17] | <mstenta[m]> | - https://www.drupal.org/node/3261358 |
[11:32:54] | <mstenta[m]> | Opened a pull request: https://github.com/farmOS/farmOS/pull/545 |
[11:33:09] | <mstenta[m]> | Might not have a chance to test manually this week, but it's there in case anyone else wants to. |
[12:46:04] | <paul121[m]> | Mo asked about farmOS & 9.4 last week! Mo I think you said you already updated some Drupal sites to 9.4, anything to note there? Were there any particular features you updated for or just maintenance? |
[12:50:47] | <Mo[m]> | I had this issue Fatal error: Class `Symfony\Component\DependencyInjection\Exception\ExceptionInterface cannot implement previously implemented interface Throwable in /code/vendor/symfony/dependency-injection/Exception/ExceptionInterface.php on line 22` it's mainly because of your PHP version being < 7.4. Once you update your PHP version to 7.4+ it should work. |
[12:51:11] | <Mo[m]> | more info https://github.com/php-fig/container/issues/30 |
[12:54:57] | <Mo[m]> | I can test it on my local to see if i get any issues |
[14:52:39] | * TheSlurpee[m] has joined #farmos |
[14:52:40] | <TheSlurpee[m]> | Thoughts on using a Documentation system in farmOS? As a Drupal person, I'd assume using the core Book module and it's related features would work nicely? |
[15:05:39] | <mstenta[m]> | Hi TheSlurpee! There has been some previous discussion related to this... |
[15:05:42] | <mstenta[m]> | https://farmos.discourse.group/t/inline-user-guides/680 |
[15:06:01] | <mstenta[m]> | And specifically paul121's recent comment: https://farmos.discourse.group/t/inline-user-guides/680/10 |
[15:06:14] | <mstenta[m]> | Which links to this d.o issue: https://www.drupal.org/project/farm/issues/3243901 |
[15:12:46] | <TheSlurpee[m]> | I believe that solution is in context to "help using the farmos system" which will for sure help. However, I'm looking for more of an internal organization/farm documentation system. Example, "How to do task X" on the farm. Maybe, "How to take a transplant"? "How to take a lab sample"? Plus allowing users access to create and edit (and moderation) Docs on their own. I've accomplished this easily with the core Book module countless times |
[15:12:46] | <TheSlurpee[m]> | over the years. Things such as tags and adding fields for Images or Files/PDF works great. Then Views to list/organize/search the docs. |
[15:13:16] | <mstenta[m]> | Oooh I see! |
[15:13:31] | <mstenta[m]> | You might be interested in this: https://farmos.discourse.group/t/documenting-conventions/1263 |
[15:14:24] | <mstenta[m]> | I was thinking a bit outside of the context that you're talking about (visible within farmOS) - but very much overlap in the overall idea I think! Perhaps the "conventions" markdown files could somehow be sucked into farmOS and displayed somewhere. |
[15:14:39] | <mstenta[m]> | Although they may be too technical too. Maybe something different is needed for normal users. |
[15:15:25] | <TheSlurpee[m]> | Think more along the lines of "employee handbook" for staff members on a farm. |
[15:15:49] | <mstenta[m]> | Yea, I'd love to think through how that could be generated from "conventions" perhaps. |
[15:15:55] | <mstenta[m]> | But that's probably longer term... |
[15:16:41] | <mstenta[m]> | FWIW I know a farm that just creates logs FAR in the future (so it always shows on the dashboard in "Upcoming tasks" with "standard operating procedures" for their data entry - so everyone has something easy to refer to. |
[15:16:48] | <mstenta[m]> | Definitely a workaround :-) |
[15:16:58] | <mstenta[m]> | * "Upcoming tasks") with |
[15:17:27] | <mstenta[m]> | Actually this reminds me of an older issue too: https://www.drupal.org/project/farm/issues/2965987 |
[15:18:05] | <mstenta[m]> | https://www.drupal.org/project/farm/issues/2994159 |
[15:18:17] | <TheSlurpee[m]> | Documenting SOPs is one of the things I'm attempting to accomplish. Plus I want the localization stuff too. Example, I want all my documentation in Spanish and English. We have lots of migrant workers who only speak Spanish, but do data entry on pen/paper. |
[15:18:47] | <mstenta[m]> | Ah good point re: localization. One thing to note is that farmOS does not currently make use of "content translation" at all... only "interface translation". |
[15:19:04] | <mstenta[m]> | If you were to use entities (eg: book module) then you would need to use content translation I believe. |
[15:19:31] | <TheSlurpee[m]> | Good timing because I was just struggling with that lol |
[15:19:50] | <mstenta[m]> | In general this feels like something that I would like to see experimented in contrib before we make any official decisions in core |
[15:19:57] | <mstenta[m]> | Lots of ways to slice it |
[15:20:12] | <TheSlurpee[m]> | I've been building a list of words/terms in Spanish that are essentially "slang", but are the words our workers use everyday and should be in our system. |
[15:20:13] | <mstenta[m]> | But having some lessons from the wild would help a lot! |
[15:20:28] | <mstenta[m]> | Cool! |
[15:21:24] | <TheSlurpee[m]> | I'll play around with it a bit and see if I can get people to actually use it. Then I'll try to contrib back with a proper roadmap proposal. |
[15:22:39] | <TheSlurpee[m]> | We're basically in "farmos beta test mode" this summer/season. Attempting to mold it into our farm's organization. The entire system is very impressive :) |
[15:23:21] | <mstenta[m]> | Cool! |
[15:24:00] | <mstenta[m]> | Well if you're a Drupal developer you have a lot more power to build custom quick forms too... making data entry easy is always the hardest part :-) |
[15:24:13] | <mstenta[m]> | https://farmos.org/development/module/quick/ |
[15:24:56] | <mstenta[m]> | (Basically just a thin wrapper around Drupal Form API, with automatic route/menu integration and some helper methods for creating assets/logs/etc) |
[15:25:44] | <mstenta[m]> | So consider making some quick forms for common tasks that you need specifically! |
[15:26:03] | <mstenta[m]> | You may find that avoids the need for a lot of documentation in the first place! |
[15:26:17] | <mstenta[m]> | or it just becomes: "Fill out this quick form" |
[15:27:13] | <mstenta[m]> | And if you need to use maps in you forms, you're in luck because we just merged https://www.drupal.org/project/farm/issues/3290929 ;-) |
[15:27:33] | <mstenta[m]> | https://farmos.org/development/module/maps/ |
[15:27:37] | <mstenta[m]> | Gotta run - good luck! |
[15:47:30] | * farmBOT has quit (Ping timeout: 264 seconds) |
[15:50:15] | * farmBOT has joined #farmos |