14 days are over, still no update or progress.
Please mark this plugin broken and not under active maintenance.
1 Like
Apologies for the slowness here. Iāve been recovering from a bout of covid.
In the meantime, you can pin your instance to a commit you were using prior to the compatibility issue. Just set version in your app.yml file to a specific commit.
3 Likes
2.9.0 beta 4 or higher is the discourse version when it occur.
My app.yml is default except the plugins
- git clone https://github.com/discourse/docker_manager.git
- git clone https://github.com/discourse/discourse-cakeday.git
- git clone https://github.com/discourse/discourse-spoiler-alert.git
- git clone https://github.com/discourse/discourse-user-card-badges.git
- git clone https://github.com/discourse/discourse-yearly-review.git
- git clone https://github.com/discourse/discourse-solved.git
- git clone https://github.com/discourse/discourse-encrypt.git
- git clone https://github.com/discourse/discourse-reactions.git
- git clone https://github.com/paviliondev/discourse-news.git
- git clone https://github.com/discourse/discourse-chat-integration.git
- git clone https://github.com/discourse/discourse-rss-polling.git
- git clone https://github.com/discourse/discourse-follow.git
- git clone https://github.com/discourse/discourse-push-notifications.git
- git clone https://github.com/communiteq/discourse-delete-unreplied-topics.git
- git clone https://github.com/discourse/discourse-footnote.git
- git clone https://github.com/discourse/discourse-math.git
- git clone https://github.com/communiteq/discourse-geo-blocking.git
- git clone https://github.com/discourse/discourse-category-experts.git
# - https://github.com/paviliondev/discourse-landing-pages.git
# - https://github.com/paviliondev/blog-landing-theme.git
# - https://github.com/discourse/discourse-templates.git
1 Like
I didnāt flag your post, but Iād just wait for the moderator to review it and it may well be restored.
Ah, if only. Unfortunately it wasnāt sudden 
Yes I didnāt tell you I had it last week, but coming on meta to update this topic wasnāt top of mind. Iāll have to ask for your forgiveness on that one.
Ok, then set your Discourse to a version lower than 2.9.0 beta 4.
5 Likes
Please note that this will work with the latest on tests-passed again now.
4 Likes
Still does not work, when I build the app I get errors and failures that the database already exists with the same name among some other errors.
Need to give up, I hope Discourse one day get an Blog feature integrated.
1 Like
Just FYI: domain try.thepavillion.io is broken ā Safari canāt create secured connect.
1 Like
Sorry, it doesnāt work. All I got was infinitive splash screen. When I tried safe-mode with unofficial plugins excluded the forum came back to online again. I couldnāt even get a chanse to disable the plugin at admin side. And because of that I couldnāt check any collisions with a couple another unofficial plugins.
Sorry, I didnāt have time to check out console errors ā three rebuilds just took too much time.
1 Like
Yes, there were more changes to the Discourse asset pipeline. Iāve moved the plugin off of the main asset pipeline entirely. The plugin and these pages are definitely working with the latest on tests-passed. You can see an example here
However I wonāt be continuing to develop this plugin as the general approach is no longer feasible with the current structure of Discourse. Pavilion itself is moving our own landing pages from this plugin to Hugo. We may pick this up again in the future if someone is interested in continuing the project.
1 Like
Well, Iām on latest and it doesnāt work.
But if you donāt continue with this should it tell in the beginning (Iāve not checked you already did it) because now I wasted over an hour for nothing. Well, I didnāt have anything else to do, so it doesnāt matter
Anyway ā if it would work and I would start building blogāish environment and realize after update or two that there is no futureā¦ well, that would not be the funniest situation.
Should you close this topic then?
2 Likes
It didnāt work at the time you made your previous post. Iāve pushed more commits since then. You can see a working example linked above.
Iām sorry, I made the decision this morning. Iāve added a note at the top of the topic.
There are various people who use the plugin already (not just as an experiment). The reason Iāve fixed it now, even though I decided to not actively develop it further is that I donāt want to leave people in the lurch while they move off it. Closing the topic would be premature.
2 Likes
You were fast, Iāll give you that.
Yeah, decisions will happend fast. And should too.
I totally understand that. But the reality is there is really big chance it will break quite soon anyway. Your plugins seems to be quiteā¦ damn, I donāt remember word Iām looking forā¦ anyway, these are quite complex and do a lot of things. Iām guessing that doesnāt help maintenance.
It is really nice move to give some time to find another solutions. But there is no point what so ever to start using it anymore ā thatās Iām meaning.
2 Likes
All closing the topic would achieve is preventing discussion about the alternatives people are considering.
Iām sad to see the turn this topic has taken though. Angus has done a lot for Discourse and doesnāt deserve the tone of some of the above posts.
6 Likes
I have tagged it with the new unmaintained tag, if that is acceptable to you @angus? This will hide it by default, but will still be searchable by name and displayed in the tag filtered view (this will be the first test of this tag on a recently retired customisation, so if there are quirks we can tweak to better suit and hopefully strengthen the process 
).
Update: To further refine this new process, weāve added an end-of-life tag to the group, which can be used while a customisation still currently works, but will no longer be actively maintained. This will allow visibility for information purposes, and to give people a chance to be made aware that it is indeed at the end of its current lifespan. After a reasonable amount of time, or until a breaking change occurs, it will then be removed from active view using one of the other tags. Please be patient with this, it is a new system and further refinements may need to be made.
I for one appreciate all of Angusā contributions to Discourse, as well as here on Meta, and just want to emphasise that, while I sympathise that itās disappointing that this customisation is no longer going to be maintained, we should not lose sight of how much time and energy has gone into providing it as a free, open-source contribution in the first place, as well as keeping it running for the past year or more. These things take a lot of effort.
Thank you Angus. And thanks for keeping us informed as to its current status, as well as giving people the time and opportunity to make alternative plans. I donāt think anyone can reasonably ask for any more than that.
11 Likes
Perfect, thank you
4 Likes
sophisticated 
?
8 Likes
You nailed it. Precisely.
3 Likes
Hey @angus ,
Thanks for all your work on the Landing Pages!
What are the alternatives available for landing pages that would make it easy to pull Discourse data? You mentioned Hugo, will it be possible to do calls similar to landing pages like this:
topic_list(list_opts: { order: 'created', category:category_id, status:"open"}, opts: {})
Or would we have to custom SQL call these like how the landing page plugin does it?
2 Likes
Do you guys know if this features slugifies the topics name for the blog too ?
Iāll have to use this + blog plugin for a project, thanks for the work.
1 Like
So, I went and just manually updated the code stuff and the blog post page now looks like thisā¦repeats the background image, colors are off, weird button placements, etc. Also, the Subscribe button still does nothing when clicked on any page. And on mobile, the hamburger menu thatās there does nothing still either.
That being said, it looks like that awkward smaller grey box is fine if the blog post has enough text content. So maybe a fix somehow for blogs that are short? Example of longer post layout:
Still does weird tile background thing, though. And I unfortunately had to do a lot of CSS customization so it didnāt look like the above photo, color-wise.
Oh, also just now noticed that the link breaks on mobile but works fine on Desktop when clicking a blog title on the blog landing page.
Desktop properly takes you to:
https://forums.mysite.me/blogpath/topic-title
Mobile takes you to:
https://forums.mysite.me/blogpath/blogpath/topic-title -
adding a second /blogpath/ for some reason.
EDIT3: Another thing I just now found: If I make a new topic to be a blog post, the dates of all the previous blogs get changed to the most recent one. Thatās not good at all. I made a new topic/blog post and they all changed to the date of the new one (yesterdayās date when I made it):
