Uploading pdf to assest getting error: The file could not be uploaded because the destination "private://farm/asset/2022-04" is invalid
|
|
5
|
844
|
August 8, 2022
|
farmOS 2.0.0-beta6 has been released
|
|
4
|
301
|
July 31, 2022
|
VirtualBox Hosting farmOS
|
|
0
|
215
|
July 12, 2022
|
Migrating from FarmOS v1 to FarmOS v2
|
|
5
|
209
|
June 28, 2022
|
farmOs v1 migrate v2 - issue with taxonomy
|
|
10
|
327
|
June 11, 2022
|
farmOS 2.0.0-beta5 has been released
|
|
0
|
159
|
June 2, 2022
|
Backup and restore of FarmOS - need to redo server
|
|
3
|
295
|
May 16, 2022
|
Odd behavior when running update.php
|
|
3
|
194
|
May 11, 2022
|
farmOS 2.0.0-beta4 has been released
|
|
15
|
439
|
April 22, 2022
|
Migrating from dev to prod
|
|
6
|
213
|
April 20, 2022
|
KML Upload unsuccessful
|
|
17
|
265
|
April 14, 2022
|
Troubleshooting JSON:API / JupyterLite
|
|
7
|
251
|
March 26, 2022
|
farmOS 2.0.0-beta3 has been released
|
|
4
|
236
|
March 16, 2022
|
OAuth Connection issue (with WFS Module and QGIS)
|
|
21
|
343
|
March 8, 2022
|
KML import in 2.x
|
|
28
|
764
|
February 19, 2022
|
Node-Red scurity
|
|
1
|
156
|
February 9, 2022
|
Where'd Location go?
|
|
19
|
376
|
February 8, 2022
|
Admin Search Box
|
|
5
|
311
|
February 8, 2022
|
Farmier v2 Upgrades
|
|
0
|
194
|
February 4, 2022
|
Migrate farmos installed from tar
|
|
2
|
193
|
January 25, 2022
|
farmOS 2.0.0-beta2 has been released
|
|
0
|
211
|
January 19, 2022
|
An AJAX HTTP error occurred. farmos2 beta1
|
|
8
|
384
|
January 18, 2022
|
farmOS 2.0.0-beta1 has been released! Happy New Year! 🎉
|
|
4
|
935
|
January 5, 2022
|
Farmos installation error
|
|
3
|
262
|
December 28, 2021
|
farmOS 1.8 has been released
|
|
0
|
308
|
December 22, 2021
|
Can we host the FarmOS on our own server?
|
|
3
|
357
|
October 5, 2021
|
Postgres DB configuration issue
|
|
5
|
564
|
September 20, 2021
|
Apache/2.4.38 (Debian) Server at localhost Port 80
|
|
5
|
3981
|
September 17, 2021
|
Hosting with Docker
|
|
12
|
1404
|
September 17, 2021
|
Docker -> AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.23.0.3. Set the 'ServerName' directive globally to suppress this message
|
|
3
|
230
|
September 15, 2021
|