Currently, the development of version 2 is very, very active . New features and fixes are implemented on a daily basis. The version 2 update will essentially be a full rewrite of the entire application , including the backend, frontend, standard theme and blocks. The goal is to also include as many open feature requests and resolve as many open issues as possible until the day of the release. Existing websites using version 1 as well as existing extensions, except for some minor execptions, will continue to work just fine and will be compatible with version 2. Minor breaking changes will be communicated with the relase notes. The new dashboard will be entirely written in TypeScript and will no longer have jQuery and UIkit as dependencies . The new backend will require at least PHP 8.0 or newer. Please note that this is an open-source project that is free to use and the maintainer spends a substatial portion of his free time, weekends and nights in order to finish the release as soon as possible. That said, there is no fix release date yet. It is done whenever it is done. In the meantime you can safely start a new website using version 1 and migrate to version 2 afterwards.

Can't wait see the new version 🙂

I was previously using Kirby CMS and I found Automad today. I will be following this CMS closely, it looks very promising!

I also agree that Automad looks promising - fingers crossed! 🤞🏻

The hype is real about v2 on my side. Can't wait to seen the brand new version. I probably will test it right away because I'm thinking about rebuilding my Automad theme on my website for quite a while now. Great job on that CMS so far. I love it and already use it on two websites.

@mad will there be some sort of an easier i18n feature such as a pipe function?

I downloaded the v2 code from github, unzip and fire it up in MAMP and I get an error message: No main theme defined! Please define a theme!

consumer This post clearly states that v2 is work in progress. In other words, v2 is not finished and simply can’t be used yet. It is also written in the README of the repository that new projects still have to use version 1 and must migrate later to version 2. Please follow the official docs for installation instructions.

Ah, I see: I had misinterpreted, "you can safely start new website using version 1 and migrate to version 2 afterwards." to mean, "it is possible to..." when in reality it seems like it means you must start a new website in version 1 and then upgrade to version 2. Sorry! I'm just really excited to see what v2 looks like. Thank you for all your hard work, MAD!!

Version 2

phil2202

mad Thank you for your answer.
The custom css file is reachable and loadable.
The file is located in dist/blocks/custom.css I tried to find in the docs where to place custom files, but i didn't found hints.
I will move the file to package instead.
Is the folder "package" a good place to store font awesome (or similar) files and folders, or what place should local content from external sources to be located in?

mad

phil2202 You can take a look at the developer guide. Or simply upload it to the shared settings.

mh321

mad "Existing websites using version 1 as well as existing extensions, except for some minor execptions, will continue to work just fine and will be compatible with version 2. [snip] In the meantime you can safely start a new website using version 1 and migrate to version 2 afterwards."

I'm stunned that you posted that and have now released v2 without a simple means of migrating content. Textbook bait and switch. I won't read whatever your response is.

mad

mh321 I am also stunned that you obviously can't understand what an alpha version is. It is not a final release. Migration will be there when there is a stable version. This is for testing only.

And you won't read a response, yet you post in a forum. Seriously? Interesting attitude. What is your contribution to the community exactly?

Please stop wasting people's time with this nonsense!

mad

mh321 You won't read it as you said, but the funny thing is, that before you have been here on that forum and spreading complaints, there was already a migration tool in the works. It has just been released.

It also would not have been so hard to write one yourself. An average junior developer could make that happen in 20min.

But complaining about people who spend all there spare time to create something useful and free is obviously the way to go for you. You can be proud of you. Sad ...

People like you are the reason why open-source maintainers abandon projects. Demanding without giving.

Lz127

Hello. I'm very glad that the second version has seen the light, congratulations. I really like Automad CMS.

One question. Will there be a headless mode in the second version or not?

phil2202

Lz127 Yes v2 do have headless mode

Lz127

phil2202 I installed Automad v2 and couldn't find the headless mode there, where it used to be.

mad

Lz127 The current alpha of Automad 2 has no headless mode (see changelog). I was not aware that it was used at all and resources were limited. However, I‘m curios what your use cases are. It is always possible to bring it back.

Lz127

mad
I have previously used Automad for two projects without utilizing headless mode. Currently, I am working on a small React project and needed a CMS. I attempted to use Strapi for free, but I couldn't deploy it on my hosting. That's when I thought about Automad. For my needs in this project, its capabilities are sufficient. Each page has its own JSON file, and I retrieve page data with a fetch request, utilizing it accordingly. The only thing I would add to the headless mode is different templates for various types of entries, and pages. Because in different types of entries, there are different fields that appear in the admin panel, and in certain entry types where they are not needed, they just remain empty. This is not very convenient for the end user. Automad is well-suited for a small project.

mad

Lz127 Hi, that is indeed a good use case. I think it would be very easy to just write a template that returns json instead of html. That was basically what the previous headless mode did.

Username

kann mir bitte jemand helfen ?

ich versuche seit Tagen automad zu installieren und bekomme immer wieder diesen Fehler:

session_start(): open(/var/www/vhosts/xxx-xxx.de/tmp/sess_vkhhjp12knd404slpbh5m9jvrk, O_RDWR) failed: No such file or directory (2)
In file /automad/src/server/App.php
on line 143

ich habe eine subdomain angelegt, mein Hoster ist domainunion.de. Serversoftware ist Apache
Ich habe alle php Versionen getestet und es auch in verschiedenen Unterverzeichnissen versucht.
Ich habe zudem mit der htaccess Datei experimentiert und sie auch schon ganz weggelassen..

i have no clue

mad

Username First of all, please only ask in English here as stated in the forum rules.

As the error says, the session directory in the tmp directory is missing on the server. That has nothing to do with the CMS itself. This is a basic requirement for having user sessions in PHP. The best would be to forward this error to the support team of your hoster. Did you try v1 as well?

Lz127

mad I have been given such advice here before, but I don't quite understand how to do it. Could you please suggest the steps to take in order to return JSON?

madzpf

Lz127 It's just a template that returns json as content instead of html and sets the correct headers. The json content can be rendered like any other html content using the template language. All variables you use, show up automatically in the dashboard then.

Lz127

madzpf
I downloaded the Skeleton theme and I'm trying to edit the page.php template file, but I'm having trouble returning valid JSON. If you understand, please provide some sample code.

« Previous Page