AmauryPi Ah I disabled it after it wasn't working, that's why you got 404. Can't really see how I can install it wrongly, since it's installed via composer.
Enabled it again.
AmauryPi Ah I disabled it after it wasn't working, that's why you got 404. Can't really see how I can install it wrongly, since it's installed via composer.
Enabled it again.
I can see your RSS feed.
That being said, the validation could (and should) be improved.
This extension is really nice and useful, thanks for developed it! However and sadly, I can't use it as I would like because with the /atom
feed:
- The GUID (id) are not unique, they match the discussion URL. So RSS readers don't see replies in a same discussion thread as they seem to be updates of existing entries and not full new entries. A solution would be to use a hash from the publication date + author for example.
- Only the last reply of a discussion is in the feed. So if two or more replies occur between two feed fetching, only the last one is available. Is it possible to store every replies in the feed, or at least those from the week or the day?
Also, I'm wondering if, by any chance, it would be possible to have primary tags somewhere in the entries?
Thank you!
how to change this ? --> Derniers messages dans cette discussion
Broke on installation, producing the following error....
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for amaurycarrade/flarum-ext-syndication 0.1.5 -> satisfiable by amaurycarrade/flarum-ext-syndication[v0.1.5].
- amaurycarrade/flarum-ext-syndication v0.1.5 requires flarum/core 0.1.0-beta.6 -> satisfiable by flarum/core[0.1.x-dev, v0.1.0-beta.6, v0.1.0-beta.7, v0.1.0-beta.7.1] but these conflict with your requirements or minimum-stability.
Installation failed, deleting ./composer.json.
Blodeuwedd make sure you're running composer commands in the Flarum root folder.
jordanjay29 whoops, thanks for pointing that out
Opened a pull request adding 0.1.0.beta.8 support: https://github.com/AmauryCarrade/flarum-ext-syndication/pull/5
jtojnar You might want to consider forking this extension and releasing it yourself.
@jordanjay29 At the moment, my flarum website is only in maintenance mode so I so not expect to actively develop any of the extensions I updated. I feel that amount of inactive forks of forks of forks is already too high in Flarum community and publishing my forks would only make this issue worse.
Having a community GitHub group for important extensions with larger pool of developers would be nice. I imagine something like Friends of Flarum but with open membership policy. That would at least solve the problem of having to replace the extension repository every few months. Unfortunately, since the Flarum community is so small, some extensions might not have a maintainer for a while. The repositories would probably need to carry a disclaimer like “This extension is occasionally maintained, if it seems like it is abandoned and you want to contribute, please request a membership of our group by pinging @OurFlarumGroup/admins in your pull requests.” The group would need to be reasonably big so there were always someone available to add new members and it would be also nice if there were volunteers who could help review the pull requests. Not sure the Flarum community has enough resources for something like this.
jtojnar the thing we worry about most before even considering adding any new members (especially in ReFlar) is if people can live up to the standards of not only updating, but creating quality extensions altogether. A problem that I notice the most with new or currently active/returning 3rd party extension developers is that everyone seems to follow a different coding style and have different opinions of how they want an extension to function. Being part of a team is not only about being a team player, but the very idea of our minds, opinions, goals, and philosophies being in sync. Although it may sound easy to do, it actually isn't as I've experienced this first-hand through my time in this community and being the co-owner of ReFlar. We would rather form a group of well-known developers that get along well enough to bring you constantly updated (to match the breaking changes in Flarum core development) and bring you the best quality and support we can possibly provide
If we let any willy-nilly person join, there is guaranteed to be conflicts and things would get messy really quick, Plus, you wouldn't trust a stranger in the street to look after your car and home while you were working, would ya? Who knows what traps and intentions that person may have, let alone the fact that you never met them before. It's not always about numbers, just the amazing minds and people that can get the job done and ultimately work in harmony
All-in-all, being part of a team is not just being another number within the group, it's a privilege and ongoing trust to where you don't have to wake up one day and one of your new members you just added completely cleaned house and deleted all of your repositories
500 errors after ssl is installed
jtojnar Friends of Flarum but with open membership policy
Friends of flarum doesn't even have a membership policy yet. This means anyone can join. Joining something like that means pushing code.
Fatal error: Interface 'Flarum\Http\Controller\ControllerInterface' not found in /vendor/amaurycarrade/flarum-ext-syndication/src/Controller/AbstractFeedController.php on line 57
Alkir I see an open pull request but no updates to the repository itself. This will remain tagged Incompatible unless that changes.
Alkir This manual contains errors for the whole forum. https://github.com/AmauryCarrade/flarum-ext-syndication/pull/5/commits/e1604b9be0ad9db3413d046fc331f6199902b4f1