# Landingspagina's Blog 🛩

**URL:** https://meta.discourse.org/t/landing-pages-blog/190390
**Category:** Extras
**Tags:** pavilion
**Created:** [14 mei 2021 om 09:07 UTC](https://meta.discourse.org/t/landing-pages-blog/190390 "2021-05-14T09:07:15Z")
**Posts on this page:** 20
**Page:** 2

<div class="post-metadata">

### Author: ![amusew](https://avatars.discourse-cdn.com/v4/letter/a/7ab992/32.png) [@amusew](https://meta.discourse.org/u/amusew)
#### Post date: [27 juli 2022 om 12:28 UTC](https://meta.discourse.org/t/landing-pages-blog/190390/21 "2022-07-27T12:28:04Z")

</div>

14 days are over, still no update or progress.

Please mark this plugin broken and not under active maintenance.

---

<div class="post-metadata">

### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)
#### Post date: [27 juli 2022 om 14:21 UTC](https://meta.discourse.org/t/landing-pages-blog/190390/23 "2022-07-27T14:21:56Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![amusew](https://avatars.discourse-cdn.com/v4/letter/a/7ab992/32.png) [@amusew](https://meta.discourse.org/u/amusew)
#### Post date: [27 juli 2022 om 14:37 UTC](https://meta.discourse.org/t/landing-pages-blog/190390/24 "2022-07-27T14:37:08Z")

</div>

2.9.0 beta 4 or higher is the discourse version when it occur.

My app.yml is default except the plugins

```plaintext
          - 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

```

---

<div class="post-metadata">

### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)
#### Post date: [27 juli 2022 om 14:40 UTC](https://meta.discourse.org/t/landing-pages-blog/190390/25 "2022-07-27T14:40:45Z")

</div>

I didn’t flag your post, but I’d just wait for the moderator to review it and it may well be restored.

> [@amusew](#):
>
> suddenly you come up with Covid

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.

> [@amusew](#):
>
> 2.9.0 beta 4 or higher is the discourse version when it occur.

Ok, then set your Discourse to a version lower than `2.9.0 beta 4`.

---

<div class="post-metadata">

### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)
#### Post date: [28 juli 2022 om 20:46 UTC](https://meta.discourse.org/t/landing-pages-blog/190390/27 "2022-07-28T20:46:57Z")

</div>

Please note that this will work with the latest on `tests-passed` again now.

> [@Landing Pages Plugin small\_airplane](https://meta.discourse.org/t/landing-pages-plugin/180967/45):
>
> This plugin is working with the latest version of Discourse again tada

---

<div class="post-metadata">

### Author: ![amusew](https://avatars.discourse-cdn.com/v4/letter/a/7ab992/32.png) [@amusew](https://meta.discourse.org/u/amusew)
#### Post date: [29 juli 2022 om 07:30 UTC](https://meta.discourse.org/t/landing-pages-blog/190390/28 "2022-07-29T07:30:46Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![Jagster](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagster/32/192154_2.png) [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [29 juli 2022 om 08:00 UTC](https://meta.discourse.org/t/landing-pages-blog/190390/29 "2022-07-29T08:00:16Z")

</div>

Just FYI: domain `try.thepavillion.io` is broken — Safari can’t create secured connect.

---

<div class="post-metadata">

### Author: ![Jagster](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagster/32/192154_2.png) [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [29 juli 2022 om 09:36 UTC](https://meta.discourse.org/t/landing-pages-blog/190390/30 "2022-07-29T09:36:26Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)
#### Post date: [29 juli 2022 om 10:35 UTC](https://meta.discourse.org/t/landing-pages-blog/190390/31 "2022-07-29T10:35:24Z")

</div>

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

[https://demo.pavilion.tech/blog](https://demo.pavilion.tech/blog)

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](https://thepavilion.io/welcome) from this plugin to Hugo. We may pick this up again in the future if someone is interested in continuing the project.

---

<div class="post-metadata">

### Author: ![Jagster](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagster/32/192154_2.png) [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [29 juli 2022 om 10:43 UTC](https://meta.discourse.org/t/landing-pages-blog/190390/32 "2022-07-29T10:43:10Z")

</div>

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?

---

<div class="post-metadata">

### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)
#### Post date: [29 juli 2022 om 10:53 UTC](https://meta.discourse.org/t/landing-pages-blog/190390/33 "2022-07-29T10:53:04Z")

</div>

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.

> [@Jagster](#):
>
> But if you don’t continue with this should it tell in the beginning

I’m sorry, I made the decision this morning. I’ve added a note at the top of the topic.

> [@Jagster](#):
>
> Should you close this topic then?

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.

---

<div class="post-metadata">

### Author: ![Jagster](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagster/32/192154_2.png) [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [29 juli 2022 om 11:02 UTC](https://meta.discourse.org/t/landing-pages-blog/190390/34 "2022-07-29T11:02:02Z")

</div>

> [@angus](#):
>
> I’ve pushed more commits since then

You were fast, I’ll give you that.

> [@angus](#):
>
> I’m sorry, I made the decision this morning. I’ve added a note at the top of the topic.

Yeah, decisions will happend fast. And should too.

> [@angus](#):
>
> I don’t want to leave people in the lurch while they move off it.

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.

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [29 juli 2022 om 11:37 UTC](https://meta.discourse.org/t/landing-pages-blog/190390/35 "2022-07-29T11:37:17Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [29 juli 2022 om 12:00 UTC](https://meta.discourse.org/t/landing-pages-blog/190390/36 "2022-07-29T12:00:43Z")

</div>

~~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.

---

<div class="post-metadata">

### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)
#### Post date: [29 juli 2022 om 12:07 UTC](https://meta.discourse.org/t/landing-pages-blog/190390/37 "2022-07-29T12:07:17Z")

</div>

> [@JammyDodger](#):
>
> I have tagged it with the new #unmaintained tag, if that is acceptable to you @angus?

Perfect, thank you 👍

---

<div class="post-metadata">

### Author: ![manuel](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/manuel/32/468169_2.png) [@manuel](https://meta.discourse.org/u/manuel)
#### Post date: [29 juli 2022 om 17:26 UTC](https://meta.discourse.org/t/landing-pages-blog/190390/38 "2022-07-29T17:26:16Z")

</div>

> [@Jagster](#):
>
> Your plugins seems to be quite… damn, I don’t remember word I’m looking for…

sophisticated 🥸 ?

---

<div class="post-metadata">

### Author: ![Jagster](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagster/32/192154_2.png) [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [29 juli 2022 om 17:28 UTC](https://meta.discourse.org/t/landing-pages-blog/190390/39 "2022-07-29T17:28:25Z")

</div>

You nailed it. Precisely.

---

<div class="post-metadata">

### Author: ![hyphalos](https://avatars.discourse-cdn.com/v4/letter/h/3ab097/32.png) [@hyphalos](https://meta.discourse.org/u/hyphalos)
#### Post date: [8 september 2022 om 23:03 UTC](https://meta.discourse.org/t/landing-pages-blog/190390/40 "2022-09-08T23:03:53Z")

</div>

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:

```plaintext
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?

---

<div class="post-metadata">

### Author: ![afa7789](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/afa7789/32/289744_2.png) [@afa7789](https://meta.discourse.org/u/afa7789)
#### Post date: [18 januari 2023 om 20:08 UTC](https://meta.discourse.org/t/landing-pages-blog/190390/41 "2023-01-18T20:08:28Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![45thj5ej](https://avatars.discourse-cdn.com/v4/letter/4/34f0e0/32.png) [@45thj5ej](https://meta.discourse.org/u/45thj5ej)
#### Post date: [31 maart 2024 om 12:57 UTC](https://meta.discourse.org/t/landing-pages-blog/190390/42 "2024-03-31T12:57:28Z")

</div>

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.

 ![forums.mysite.me_b_bloggy-testingggg](https://global.discourse-cdn.com/meta/original/4X/0/5/a/05a7c185039f9d96bee4578e221bb4a6cede9979.jpeg)

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:

 ![hhhh](https://global.discourse-cdn.com/meta/original/4X/f/4/5/f453fe9037d8d21935d6e49e7c057daf6bd03ae6.jpeg)  
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):  
 ![cccc](https://global.discourse-cdn.com/meta/original/4X/9/a/7/9a713e7f9c7f13ba565c07af90a1d04023c81dea.png)

[Vorige pagina](https://meta.discourse.org/t/landing-pages-blog/190390.md?page=1)

[Volgende pagina](https://meta.discourse.org/t/landing-pages-blog/190390.md?page=3)
