Skip to content
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

FreshRSS 1.11.1 #1921

Merged
merged 14 commits into from
Jun 16, 2018
Merged

FreshRSS 1.11.1 #1921

merged 14 commits into from
Jun 16, 2018

Conversation

Alkarex
Copy link
Member

@Alkarex Alkarex commented Jun 6, 2018

FreshRSS 1.11.1 is a quick fix for a regression introduced in version 1.11.0 and affecting the fetching of full article contents. This version also contains a few more improvements.

Changelog:

  • Features
    • Better support of media: tags such as thumbnails and descriptions (e.g. for YouTube) #944
  • Extensions
    • New extension mechanism allowing changing HTTP headers and other SimplePie parameters #1924
    • Built-in extension to fix Tumblr feeds from European Union due to GDPR #1894
  • Bug fixing
    • Fix bug in case of bad i18n in extensions #1797
    • Fix extension callback for updated articles and PubSubHubbub #1926
    • Fix regression in fetching full articles content #1917
    • Fix several bugs in the new Fever API #1930
    • Updated sharing to Mastodon #1904

Alkarex and others added 6 commits June 3, 2018 13:42
* Fix type exception in loadCompleteContent

#1917
With some refactoring

* Changelog 1917

#1917
#1918
* Support for media: tags

#944
E.g.  YouTube

* Fix for medium attribute

* Changelog 944

#944
#1920

* enclosure styling

* Compatibility old enclosure content
@Alkarex Alkarex added this to the 1.11.1 milestone Jun 6, 2018
Julkikod and others added 4 commits June 8, 2018 16:12
* Update 06_Mobile_access.md

Mise à jour de l'aide sur l'accès via mobile

* Update 06_Mobile_access.md

* Minor text

* Minor edits
* New extension event + Tumblr GDPR

#1894
simplepie_before_init event

* Refactor extension enabling + Tumblr GDPR enabled by default

Add possibility for extensions to be enabled by default, and disabled
back by users.

* Minor whitespace
@Alkarex
Copy link
Member Author

Alkarex commented Jun 10, 2018

@Frenzie If you can, could you please test the /dev branch with one of your extensions?

@Frenzie
Copy link
Member

Frenzie commented Jun 10, 2018

@Alkarex I might be able to squeeze it in somewhere today; not sure, no time for sure from Mon-Wed. :-/

gllmhyt
gllmhyt previously approved these changes Jun 11, 2018
Copy link
Contributor

@gllmhyt gllmhyt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixes the automatic feed update that was broken with 1.11.0 and make FreshRSS an amazing software once again.

Getting this warning when running actualize_script.php:

PHP Warning:  Invalid argument supplied for foreach() in /var/www/freshrss/app/Models/Feed.php on line 388

* Fever fixes

Was hardcoded for MySQL. Bug in "before" parameter. Bug in mark all as
read.

* Fix construct

* Changelog 1930

#193
#1931
* Fix extension hook for updated articles

#1926

* Enable extensions during PubSubHubbub

* A little array protection

* Changelog 1926

#1926
#1932

* Add null check
@GLLM
Copy link

GLLM commented Jun 14, 2018

I really need this patch as all my feeds update are now broken.
Some feeds dont react well when I attempt to force update (actualize) them individually. Other do.

Cant wait for the release :)

@Alkarex
Copy link
Member Author

Alkarex commented Jun 14, 2018

@GLLM Probably Saturday. I am only waiting for a little bit more feedback from people testing/using the /dev branch. Otherwise it is ready. You are very welcome to use the /dev branch, by the way. You can think of the /dev branch as a rolling release, while the tags on the master branch are a versioned release.

@GLLM
Copy link

GLLM commented Jun 14, 2018

Hey @Alkarex
thanks for your reply .... I admit I prefer being on the dev version, to avoid potentiel bugs which could potentially break the DB (and this is something i'd hate).

Moreover, I use the web updater and I'm not sure if I can switch the update channel. Can I ?
If so, can I revert to the stable version (provided it has a higher CL than the dev) afterwards ?
Thanks

@Alkarex
Copy link
Member Author

Alkarex commented Jun 14, 2018

@GLLM If you back-up your DB before the operation, that should be safe enough. You can also install the /dev version in parallel. From master to dev should always be fine, as well as from dev to the next master version (which is what I suggest here). However, going back to older versions can sometime be more hazardous. The Web updater has a number of issues / limitations, and needs to be improved. Git, Docker, manual ZIP methods should all be fine.

@Alkarex Alkarex merged commit 3306a16 into master Jun 16, 2018
@GLLM
Copy link

GLLM commented Jun 17, 2018

@Alkarex : issue solved with v1.11.1 Thanks

javerous pushed a commit to javerous/FreshRSS that referenced this pull request Jan 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants