It looks like you don't have any Field Modules installed

Field Kit
1

Hi all,

I just installed field kit to local and connect it to local farmOS server.

I have successfully logged in but i get this message

Screenshot 2023-02-20 at 12.42.57
Screenshot 2023-02-20 at 12.42.571922Ă—1004 73.3 KB

I enabled all the modules on farmOS and tried to create some seed and harvest records

Screenshot 2023-02-20 at 12.48.53
Screenshot 2023-02-20 at 12.48.531020Ă—1746 110 KB

Please help me, what should I do?

Thank you!

1 Like
2

Hi @henry, typically for module development I don’t install the module on the local farmOS server. Instead, I use a separate development environment, provided by field-scripts develop-module, that mocks the process of loading the module’s script file itself, but still connects to the local farmOS server to authenticate (and on that note, just leave the “Host” field blank at login) and to fetch and send data over the API. That way I get the benefits of module reloading (HMR) and all that good stuff. One of these days it’d be great to work out a way to do HMR w/ modules actually live on the local farmOS server, but that’s some extra finesse I haven’t had time to figure out.

So for the Tasks field module, I include these npm scripts in its package.json:

{
  "name": "field-module-tasks",
  // ...
  "scripts": {
    "start": "npm run dev",
    "dev": "field-scripts develop-module",
    "build": "field-scripts build-module --config module.config.js",
    "preview": "vite preview",
    "test": "echo \"Error: no test specified\" && exit 1"
  },
// ...
}

To just test that field module scripts can load properly from the local farmOS server, you can install the test script (although I don’t have it installed regularly, as you can see below):

image
image942Ă—1095 59.1 KB

The process would be the same for loading a test build of the module you’re developing, which can be created with the field-scripts build-module, as you can see in the Tasks module’s package.json above. Then you would just need to upzip the build artifact into your local farmOS file directory and install it from http://127.0.0.1/admin/modules (oh, and I also tend to use 127.0.0.1 for viewing my local farmOS server in the browser just so it doesn’t mess w/ the authentication process for my Field Kit dev environment, which I view at localhost:8080; again, some extra finesse w/ my hosts files or whatever could eliminate the need for all that, but it’s just easier right now to view them from different addresses).

If you’d like to walk through the process together I’d be happy to schedule a chat, probably separate from the weekly dev call b/c it can be tricky for me to make those, but we could use the dev call Jitsit room and leave it open for others to join, possibly record it too.

2 Likes
3

Thank you so much @jgaehring. I’m trying to install it as you instructed.

2 Likes
4

Hi I’m having the exact same problem on production.

Fresh new install with farmOS version 3, docker install and reverse proxy with nginx for ssl.

I even installed the test module as suggested above and I get this on console
“If you can see this, then the field module was successfully loaded.”
after login

But still getting the nomod card. I can also see the network tab loading all the schemas from API and all that seem to be working.

Is there any other thing I could be missing for the Field Kit to properly load?

5

nevermind. I figured out now that I actually need the field kit tasks module (or other modules). I got it downloaded and uncompressed in my sites/default/modules folder and can now see it in the /admin/modules

Although it seems I can’t still install the latest version of field kit tasks module on farmos 3 because it it’s on Drupal 9, whereas I’m on Drupal 10

1 Like