New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Released Datenstrom Yellow 0.7.2 #296

Closed
markseu opened this Issue Nov 22, 2017 · 8 comments

Comments

3 participants
@markseu
Copy link
Member

markseu commented Nov 22, 2017

Datenstrom Yellow 0.7.2 was released today.

What's new:

  • better configuration, all plugin settings are discoverable
  • added text settings, can be used to overwrite language files
  • added error page for failed login attempts, HTTP status code 430
  • updated installation, shows if web server is not configured properly
  • updated JavaScript, removed support for old web browsers
  • added Instagram and Twitter plugin (thanks Steffen)
  • added support for GIF images

Update your website. Do you have questions? Something not working? 😄

@markseu markseu added the news label Nov 22, 2017

@schulle4u

This comment has been minimized.

Copy link

schulle4u commented Nov 22, 2017

In my blog content folder I also have some static pages which should not be displayed as blog pages, for example a list of tags and a list of monthly archives. After updating to Yellow 0.7.2, these pages are treated as blog pages too. A template setting has been added to the configuration header and the pages show up in the blog pages view. The updater didn't touch these pages before, so I'm wondering why this happens now.
I simply will remove the template setting to restore the pages.

Steffen

@BsNoSi

This comment has been minimized.

Copy link

BsNoSi commented Nov 23, 2017

HTTP stauts code 430 → 403 ?

Updated two sites this morning, seems as if they are somhow faster – even faster – than before. Thank you.

I was a little bit unsettled by the .well-known folder at first. If someone else is concerned about this: I think that this is a side effect of the login changes? Besides that, everything runs smooth.

@markseu

This comment has been minimized.

Copy link
Member

markseu commented Nov 24, 2017

About template setting, I think the automatic update did some wrong guesses. When pages don't have a template setting, they get the best guess depending on the parent page. It was meant to help users updating to Datenstrom Yellow 0.7.1. We usually keep this kind of code for a few months, so everyone has a chance to get the latest version. Should we remove the code responsible before next release?

About HTTP status code for failed login attempts, I was surprised that web developers still haven't settled for one and that's why I invented 430 Login failed. I think 401 Unauthorized comes close, but the specification says the response must include a WWW-Authenticate header. I think 403 Forbidden is used by the web server for other things, so it's not unique enough to be used for this purpose.

About well-known folder, it's not from us. Perhaps check with your web hosting provider.

@schulle4u

This comment has been minimized.

Copy link

schulle4u commented Nov 24, 2017

@markseu Regarding template setting: The updater is doing a great job, old installations should still be considered. My idea is, assuming this is actually possible, the updater should check if a page file name contains a date string such as 2017-11-24-some-article, otherwise ignore the file. This should prevent souch accidental page modifications at least for blog pages. Wiki pages are a different kettle of fish.

The .wellknown folder is for the letsencrypt bot.

Steffen

@BsNoSi

This comment has been minimized.

Copy link

BsNoSi commented Nov 24, 2017

@mark: 430 – I understand – good idea!

@steffen: .wellknows – thank you, useful informatin.

@BsNoSi

This comment has been minimized.

Copy link

BsNoSi commented Nov 24, 2017

I'm getting braver and have updated another domain without explicitly backing it up. Absolutely smooth - whereby my heart fell into my pants, because the page remained white afterwards and required a page refresh for display.

@markseu

This comment has been minimized.

Copy link
Member

markseu commented Nov 25, 2017

Thanks for your feedback, this is much appreciated. I think updating websites should be as painless as possible. So I took Steffen's idea and improved the updater. Any page in the blog folder without template setting and without publication date will be ignored. This should be working now. Can you test that it's working?

@schulle4u

This comment has been minimized.

Copy link

schulle4u commented Nov 25, 2017

Tested successfully on two sites, one was still at Yellow 0.7.1. Thank you! :)

@markseu markseu closed this Apr 22, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment