farmOS 3.5.1 has been released

[mstenta]

farmOS 3.5.1 has been released.

For the full release notes, see CHANGELOG.md.

[mstenta]

Note: farmOS 3.5.0 was released yesterday, but the packaged tarball upload to the GitHub release failed due to a GitHub release immutability setting that I enabled recently. It is impossible to fix that release (due to the immutability), so I created a 3.5.1 release simply for folks who are using the packaged release tarballs. 3.5.1 and 3.5.0 are otherwise identical.

[altix]

hi, @mstenta

in this update the admin/reports/status page not work

thanks for the help

[mstenta]

@altix What do you see? Are there any errors in your logs?

[altix]

500 internal server error at admin/status/report and in the password reset form . This error are not in the 3.4.6 version

[mstenta]

A 500 error is usually accompanied by a more detailed error in the Apache/PHP server logs. Are you able to see that in your logs?

Just to confirm: did you follow the mandatory upgrade steps described in Updating farmOS | farmOS

If you did not run database updates and rebuild cache, that could explain the error.

[altix]

I don’t see anything abnormal in the log, and updated correctly following all the steps.

This is a bug because in the previous version everything works correctly.

[mstenta]

@altix

This is a bug because in the previous version everything works correctly.

I am not experiencing this issue in the instances that I host. I’ll need more details about your environment to help debug the issue.

Please visit your admin/reports/status page in your browser and then copy and paste all relevant Apache/PHP logs, showing the 500 error code and any related messages.

[mstenta]

@mstenta

copy and paste all relevant Apache/PHP logs

To be specific, I mean the server logs. Not the logs in “Administration > Reports > Recent log messages” in the farmOS UI. Those may not show anything if a 500 error occurs.

[altix]

Sorry for not replying, but I haven’t seen any problems in the Apache log. The 500 error was a permissions issue that was resolved with beta 1 of version 4. In version 4, there’s a bug when I update the database; some files aren’t updated because I have the table prefix. If you don’t have the prefix in the database, the update works fine and is successful.

thanks for you job and love farmos !!
PS farmos fieldkit is blocked?

[mstenta]

@altix Sorry but I’m going to need specific errors in order to help track down your issues. It sounds like you figured out the 500 error, though, so that’s good.

@altix

In version 4, there’s a bug when I update the database; some files aren’t updated because I have the table prefix. If you don’t have the prefix in the database, the update works fine and is successful.

Did this happen while you were running drush updb? Please copy and paste the output from your terminal that shows the exact error.

It’s possible that there is an update hook that is not handling table prefixes correctly, and I would like to fix that. But the only way to know is to see your terminal/log output.

@altix

PS farmos fieldkit is blocked?

What do you mean by “blocked”? Field Kit has not been maintained in the past few years, and is not compatible with farmOS v3 or v4. We recently moved the companion farm_fieldkit module out of farmOS core to a separate Git repository for anyone who wants to continue experimenting with it. See Move Field Kit module to contrib by mstenta · Pull Request #1037 · farmOS/farmOS · GitHub

[altix]

@mstenta

Cosa si intende per “bloccato”? Field Kit non è stato mantenuto negli ultimi anni e non è compatibile con farmOS v3 o v4. Recentemente abbiamo spostato il compagno farm_fieldkitmodulo fuori dal nucleo farmOS a un repository Git separato per chiunque voglia continuare a sperimentarlo. Vedi il modulo Move Field Kit per contribuire con mstenta · Pull Request #1037 · farmOS/farmOS · GitHub

Sorry for my English, I wanted to ask if the project was continuing.

@mstenta

È possibile che ci sia un gancio di aggiornamento che non gestisca correttamente i prefissi della tabella, e vorrei risolverlo. Ma l’unico modo per sapere è vedere l’uscita del terminale / log.

Unfortunately I have already updated by adding the prefix in the asset.post_update.php file and relaunching the update.

There was also another file that needed to have the table prefix inserted but I can’t remember which one it was I should try installing another instance and check again

[mstenta]

@altix

Unfortunately I have already updated by adding the prefix in the asset.post_update.php file and relaunching the update.

Ah thank you so much for pointing this out @altix! This is indeed a bug!

I have opened a pull request to fix it: Fix asset and plan update hooks for prefixed database tables by mstenta · Pull Request #1051 · farmOS/farmOS · GitHub

I will merge that and include in in the 4.0.0-beta3 release. I’m working on a few other small fixes, so I hope to release that soon.

Thanks again!

[mstenta]

@altix

There was also another file that needed to have the table prefix inserted but I can’t remember which one it was I should try installing another instance and check again

I think it was the plan module. My PR fixes both asset and plan update hooks.

I searched all other update hooks for SQL queries to see if there are any others, but those are the only two I found.

PS: We should probably start a new forum topic, since this is no longer relevant to the 3.5.1 release.

[altix]

@mstenta

think it was the plan module. My PR fixes both asset and plan update hooks.

Exactly the other file that I modified is a php in plan module