Datenstrom Yellow 0.9 has been released

[annaesvensson]

What’s new:

• Improved website, more information about available extensions
• Updated API, added method pages->group()
• Updated API, added method lookup->getHtmlAttributes()
• Updated API, added method lookup->normaliseAddress()
• Updated API, added method toolbox->getDirectoryInformation()
• Updated API, added coreAssetLocation for virtually mapped system files
• Updated API, replaced coreThemeLocation with coreAssetLocation
• Updated API, replaced coreExtensionLocation with coreAssetLocation
• Updated API, changed onParseContentShortcut() to onParseContentElement()
• Updated API, changed parseContentShortcut() to parseContentElement()
• Updated API, backwards compatibility with the old API will be removed soon
• Updated core extension, virtual location for layouts/themes/workers has changed
• Updated core extension, support for sourcemap files was added
• Updated feed extension, support for more filters was added
• Updated Markdown extension, better event handling
• Updated publish extension, new way of publishing extensions

Let us know what you think. Any comments are welcome.

[glow12121]

$ php yellow.php update all
ERROR updating files: Can't connect to the update server!
Yellow update: Website not updated, 0 extensions updated
$ php yellow.php update all
Yellow update: Website updated, 16 extensions updated
$ php yellow.php build
Yellow flux capacitor has reached 1.21 gigawatts. Please run command again.
$ php yellow.php build
Yellow build: Command not found

In the process of updating, there were these errors. After several attempts, they disappeared.

The Berlin theme and layout were likely overwritten by the update. I used my old berlin.css. Now, the website looks fine in serve mode but it has default barebone formatting when I build it.

[annaesvensson]

You can use the generate command to generate a static website, for more information see #858.

[glow12121]

FYI, build still works, but in a way different from generate:

$ php yellow.php generate
Generating static website 100%... done
Yellow generate: 230 files, 0 errors
$ php yellow.php build
Building static website 100%... done
Yellow build: 199 files, 0 errors

[glow12121]

yellow-system.ini now contains these duplicate lines:

CommandStaticUrl: http://www.website.org
CommandStaticDirectory: public/
CommandStaticDefaultFile: index.html
CommandStaticErrorFile: 404.html

GenerateStaticUrl: https://www.website.org
GenerateStaticDirectory: public/
GenerateStaticDefaultFile: index.html
GenerateStaticErrorFile: 404.html

[annaesvensson]

It's done. The command extension and its settings are deleted when updating from an old release. The updater makes sure that the command extension is deleted, even if you skip a release or two. If you wonder why generating a static website doesn't work, at least not like it used to, the build command has been replaced by the generate command.

Here's what you do if you want to generate a static website in 2024:

1. Install the generate extension, for example php yellow.php install generate
2. Use the new command, for example php yellow.php generate

Hope this helps.

[v-bulynkin]

I have updated without any problem, but 3rd-party plugins like https://github.com/GiovanniSalmeri/yellow-sound and https://github.com/GiovanniSalmeri/yellow-typography stopped working.

[GiovanniSalmeri]

I will update my extensions to the new API as soon as possible (perhaps before midnight 🥲 ). Sorry for the delay!

[v-bulynkin]

Great, thank you very much!
Is it possible to make your extensions to update by yellow.php update all?

[GiovanniSalmeri]

I have answered in GiovanniSalmeri/yellow-sound#1 (comment)

[PetersOtto]

Hello
Have I perhaps found a small error in the documentation?

public function onParseContentElement($page, $name, $text, $type)
to
public function onParseContentElement($page, $name, $text, $attributes, $type) .

[annaesvensson]

Yes, you are right. If you have time send a pull request to yellow-help?

[annaesvensson]

When you update an old website, from 2022 and earlier, you may see the following error message:

Can't download file 'https://github.com/datenstrom/yellow-extensions/raw/main/update-latest.ini'!

Here's what you can do:

1. Download the missing file from this address
2. Save the file as system/extensions/update-latest.ini
3. Update your website in the usual way, for example php yellow.php update all
4. Update your website one more time, for example php yellow.php update all

Hope this helps.

[schulle4u]

For the above instructions you will need a terminal program, and your web host must offer shell/SSH access. A normal browser update is also possible after step 2, just run twice to get all updates. Alternatively you can download all website files to your computer and use a local php installation to run the update.

[tikita]

Thank you for your quick reply!

> For the above instructions you will need a terminal program, and your web host must offer shell/SSH access.

Unfortunately no.

> A normal browser update is also possible after step 2, just run twice to get all updates.

I did that and the log (../yellow/system/extensions/yellow-website.log) shows that it actually took two runs.

2024-04-30 11:20:26 info Update extension 'Contact 0.9.1'
2024-04-30 11:20:26 info Update extension 'Core 0.9.8'
2024-04-30 11:20:26 info Update extension 'Edit 0.9.5'
2024-04-30 11:20:26 info Update extension 'English 0.9.1'
2024-04-30 11:20:26 info Update extension 'German 0.9.1'
2024-04-30 11:20:26 info Update extension 'Image 0.9.3'
2024-04-30 11:20:26 info Update extension 'Markdown 0.9.1'
2024-04-30 11:20:26 info Update extension 'Meta 0.9.3'
2024-04-30 11:20:26 info Update extension 'Serve 0.9.1'
2024-04-30 11:20:26 info Update extension 'Swedish 0.9.1'
2024-04-30 11:20:26 info Update extension 'Update 0.9.4'
2024-04-30 11:20:26 info Apply patches for Datenstrom Yellow 0.8.22
2024-04-30 11:20:26 info Apply patches for Datenstrom Yellow 0.9
2024-04-30 11:20:26 info Update Datenstrom Yellow 0.9, PHP 8.3.6, Apache x.x.x, Linux
2024-04-30 11:20:26 error Can't parse file 'system/layouts/header.html'!
2024-04-30 11:20:33 error Can't parse file 'system/layouts/header.html'!
2024-04-30 11:20:33 error Can't parse file 'system/layouts/header.html'!
2024-04-30 11:20:39 error Can't parse file 'system/layouts/header.html'!
2024-04-30 11:20:39 error Can't parse file 'system/layouts/header.html'!
2024-04-30 11:20:42 info Update extension 'Berlin 0.9.2'
2024-04-30 11:20:42 info Update extension 'Stockholm 0.9.2'
2024-04-30 11:20:42 error Can't parse file 'system/layouts/header.html'!
2024-04-30 11:20:42 error Can't parse file 'system/layouts/header.html'!
2024-04-30 11:20:49 error Can't parse file 'system/layouts/header.html'!
2024-04-30 11:20:49 error Can't parse file 'system/layouts/header.html'!
2024-04-30 11:20:54 error Can't parse file 'system/layouts/header.html'!
2024-04-30 11:20:54 error Can't parse file 'system/layouts/header.html'!
2024-04-30 11:20:57 error Can't parse file 'system/layouts/header.html'!
2024-04-30 11:20:58 error Can't parse file 'system/layouts/header.html'!

And so on, but unfortunately the website display remains empty ...

2024-04-30 11:20:42 error Can't parse file 'system/layouts/header.html'!
2024-04-30 11:20:42 error Can't parse file 'system/layouts/header.html'!
2024-04-30 11:20:49 error Can't parse file 'system/layouts/header.html'!
2024-04-30 11:20:49 error Can't parse file 'system/layouts/header.html'!
2024-04-30 11:20:54 error Can't parse file 'system/layouts/header.html'!
2024-04-30 11:20:54 error Can't parse file 'system/layouts/header.html'!
2024-04-30 11:20:57 error Can't parse file 'system/layouts/header.html'!
2024-04-30 11:20:58 error Can't parse file 'system/layouts/header.html'!

... even after a few hours ...

2024-04-30 16:43:03 error Can't parse file 'system/layouts/header.html'!
2024-04-30 16:43:04 error Can't parse file 'system/layouts/header.html'!

... and the view-source says:

"Datenstrom Yellow stopped with fatal error. Activate the debug mode for more information."

[schulle4u]

Depending how old your installation is, your layout files may contain deprecated API calls. My guess here is something like page->getContent instead of page->getContentHtml. I was assuming the patch also changed this, but apparently it did not in your case. The simplest solution is to grab a fresh copy of the installation files and replace your system/layouts directory.

[tikita]

Thank you already!

Now I have just added the following to the file

system/extensions/yellow-system.ini

changed to CoreDebugMode: 1 and the result is:

Fatal error: Uncaught Error: Call to undefined method YellowPage::getContent() in /var/www/vhosts/hosting123456.a1e27.netcup.net/httpdocs/yellow/system/layouts/header.html:17
Stack trace:
#0 /var/www/vhosts/hosting123456.a1e27.netcup.net/httpdocs/yellow/system/workers/core.php(3244): require()
#1 /var/www/vhosts/hosting123456.a1e27.netcup.net/httpdocs/yellow/system/workers/core.php(320): YellowPage->includeLayout('header')
#2 /var/www/vhosts/hosting123456.a1e27.netcup.net/httpdocs/yellow/system/layouts/berlin-default.html(1): YellowCore->layout('header')
#3 /var/www/vhosts/hosting123456.a1e27.netcup.net/httpdocs/yellow/system/workers/core.php(3238): require('/var/www/vhosts...')
#4 /var/www/vhosts/hosting123456.a1e27.netcup.net/httpdocs/yellow/system/workers/core.php(3222): YellowPage->includeLayout('default')
#5 /var/www/vhosts/hosting123456.a1e27.netcup.net/httpdocs/yellow/system/workers/core.php(3177): YellowPage->parsePageLayout('default')
datenstrom/community#7 /var/www/vhosts/hosting123456.a1e27.netcup.net/httpdocs/yellow/system/workers/core.php(196): YellowPage->parsePage()
datenstrom/community#8 /var/www/vhosts/hosting123456.a1e27.netcup.net/httpdocs/yellow/system/workers/core.php(142): YellowCore->sendPage('https', 'my-domain-with-yellow...', '/edit', '/', 'content/1-home/...', false, true)
#8 /var/www/vhosts/hosting123456.a1e27.netcup.net/httpdocs/yellow/system/workers/edit.php(297): YellowCore->processRequest('https', 'my-domain-with-yellow...', '/edit', '/', 'content/1-home/...', false)
datenstrom/community#9 /var/www/vhosts/hosting123456.a1e27.netcup.net/httpdocs/yellow/system/workers/edit.php(259): YellowEdit->processRequestShow('https', 'my-domain-with-yellow...', '/edit', '/', 'content/1-home/...')
#10 /var/www/vhosts/hosting123456.a1e27.netcup.net/httpdocs/yellow/system/workers/edit.php(68): YellowEdit->processRequest('https', 'my-domain-with-yellow...', '/edit', '/', 'content/1-home/...')
datenstrom/community#1 /var/www/vhosts/hosting123456.a1e27.netcup.net/httpdocs/yellow/system/workers/core.php(107): YellowEdit->onRequest('https', 'my-domain-with-yellow...', '/edit', '/', 'content/1-home/...')
datenstrom/community#12 /var/www/vhosts/hosting123456.a1e27.netcup.net/httpdocs/yellow/yellow.php(9): YellowCore->request()
datenstrom/community#13 {main} thrown in /var/www/vhosts/hosting123456.a1e27.netcup.net/httpdocs/yellow/system/layouts/header.html on line 17

For the sake of completeness.

[tikita]

The simplest solution is to grab a fresh copy of the installation files and replace your system/layouts directory.

I did it and everything works.

Thank you for your quick and detailed help!

[schulle4u]

I helped a friend update her website over the weekend, which she has forgotten to do since at least 2019. Does anyone remember the old Flatsite theme? 😄 Normally even old Yellow installations run quite long without problems, but in this case there were PHP error messages due to outdated code. Fortunately it was an installation without much customization (some static pages with stories and poems), so it was basically just a matter of reinstalling Yellow and restoring the files from the content folder. Some customizations were moved and even made easier, such as the global header and footer for additional content, which previously had to be customized in the snippet files. All the extensions we had installed back then were still available, so there were no problems here either. Only the user had to be recreated because the yellow-user.ini was still in the old tabular format and I didn't know if it was possible to convert it without errors. A new theme was also needed, and since my girlfriend really wanted one with dark mode, my Wittstock theme was used first. We still need to tweak the contrast a bit as she is visually impaired and needs a lighter text color for better readability. Apart from that updating even a very old installation will still work, since the page settings have not changed significantly.
Yellow rocks! 👍🙂

[annaesvensson]

Yes, I remember the old Flatsite theme. I'm happy that the update worked. 👍

[markseuffert]

I updated the help extension and removed the section about commercial support. In recent years there has been more or less no interest in commercial support, at least not from private individuals. At the same time I saw an increasing number of emails, from the contact page, with questions that would be appropriate for an open source support community. I like the idea of ​​having a place for people to help each other. Of having a place to ask and answer questions. This could allow developers to spend more time on making better products and... more time for working towards Datenstrom Yellow 1.0.

Datenstrom community discussions can now be found at https://github.com/datenstrom/community/discussions