farmOS 3.0.0 has been released

farmOS 3.0.0 has been released.

This is the first “stable” release of farmOS v3. See the release notes for
3.0.0-beta1 (link below) for more information about major changes in the 3.x branch,
including breaking changes to be aware of.


I have a map display problem, and some page display problems after updating to the 3 stable version. I have google map module and map custom layer ( with 3 beta3 it is work fine)

1 Like

@altix Weird that it works on 3.0.0-beta3 but not on 3.0.0. There were no changes that would affect the map between them (that I’m aware of).

Usually when map issues occur there are error messages in the browser console. Can you take a screenshot and/or copy and paste them?

@mstenta it is the https protocol that causes the problem? in the beta 3 no error on the http2 protocol

the menu works badly because when you hover the mouse the submenu doesn’t open… anyway by removing the https protocol and opening the site in http farmos works normally.
PS the version I installed is the package
PS2 doing a new installation the stable version 3 has this http2 protocol bug. the site with http without https works normally

@mstenta any idea for correct this bug ?

If you uninstall the Google Map module, does the map work correctly? This will help to isolate whether or not that module is the cause.

Installing version 3 without any community module the map does not work

Can you screenshot your browser console without Google Maps module installed?

FYI: The Google Map module ( does not work with farmOS 3 because it only supports Drupal 9. farmOS 3+ is Drupal 10. So I’m not sure how it was installed in the first place.

without installing any module the map doesn’t work, in beta 3 I installed the google map module

I have never encountered the net::ERR_HTTP2_PROTOCOL_ERROR error before myself, but it may have to do with your server environment. Can you provide more information about how you are hosting farmOS?

1 Like

Technically this should be impossible. farmOS 3.0.0-beta3 is Drupal 10, and the farm_map_google module declares core_version_requirement: ^9 in its file. Drupal will not allow a module to be installed if its core_version_requirement does not match the Drupal version.

Reference: · 2.x · project / farm_map_google · GitLab

it is possible to go back to beta3 after updating to the stable version?

If you took a backup of your database before you upgraded to 3.0.0 then all you need to do is go back to 3.0.0-beta3 and restore that database backup.

Hope that helps!

I’m skeptical that it will though. The differences between 3.0.0 and 3.0.0-beta3 wouldn’t explain the issues you’re seeing, I don’t think. And I’m still confused how you were able to install the Google Maps module. I suspect there is more going on specifically with your hosting environment.

Please let us know if you figure out what the problem was! Try to keep the number of variables limited between your tests! And always take backups before upgrades!

I added the ^10 version in the file and I didn’t take a backup of the database before update.
We hope that the next update will solve this problem with the https protocol. the beta 3 didn’t have this problem

Ah! OK that explains it. Important detail - please include information like that next time you report that farmOS is not working for you. :slight_smile:

Simply adding ^10 to the info file does not guarantee that a module will work with Drupal 10 or farmOS 3. That is just how the module maintainer declares that everything works, after it has been tested and upgraded. If you would like to help test that module and contribute changes to make it ready for farmOS 3+ / Drupal 10+ you can do so in that module’s issue queue (, or by opening a dedicated forum topic. Thanks!

1 Like

Sorry to hear that! Please read Updating farmOS | farmOS before attempting your next update! It says very clearly in bold at the top of that page:


We hope that the next update will solve this problem with the https protocol. the beta 3 didn’t have this problem

If this is a bug with farmOS we should get it fixed, I agree! However I haven’t seen any evidence that it is a bug with farmOS. Perhaps we should open up a separate forum topic to help you debug. I suspect it is a hosting environment issue, but let’s do some more investigation to find out, in a separate thread. :slight_smile:

Thanks for you help, the google map module and map custom layer work into farmos 3 by changing the version in the info.yml file

1 Like

Good to know! Thanks for testing!

1 Like