Landing Pages Blog 🛩

If you want the blog category to be visible to anonymous people as well as account-holders then you’d want the Everyone group as at least ‘See’.

And then set the other categories to be at least trust_level_0 so people would need to have an account to view and interact with the topics in those.

1 Like

Thanks that worked. Appreciate the help

2 Likes

I need a bit help in understanding this plugin. On the one hand you tell that you can

Set a category to be your blog, and the first post of every topic in that category will have its own blog page, and appear on a blog post list page.

and on the other hand

  1. Set up the Blog Landing Pages as your landing pages repository.

Im confused. Can I run a blog off my Discourse posts without a git repository and any *html.erb files?

1 Like

The content of the blog is pulled from discourse posts. The layout of the blog is handled by the html files, which could be in the Blog Landing Pages repository.

This plugin is not like Hugo where you make blog posts in markup. Although integrating this with Hugo would be cool, we could attempt that at some point (cc @jumagura)

3 Likes

I’ve been running a forum with Discourse for a couple of months so I’m still pretty new to it. I’ve installed a plugin before but when I tried installing the Landing Pages Plugin tonight I got an error when the app is rebuilt and it wouldn’t boot. Perhaps there’s a compatibility or version issue with something but I’m not sure where to start. Can anyone give me a pointer? I’ve looked back through the log but I can’t tell what the problem might be.

This is the last part of the results from running the rebuild:

Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 364 exit 1>
Location of failure: /usr/local/lib/ruby/gems/2.7.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"db_migrate", "cmd"=>["su discourse -c 'bundle exec rake db:migrate'"]}
bootstrap failed with exit code 1
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one.
./discourse-doctor may help diagnose the problem.
fb680c9c3b46dcd068abe877ed4187c730351c10139cc3eda2a8b7202822bf07
saul@discourseonubuntu2004-s-1vcpu-2gb-intel-lon1-01:/var/discourse$ 
saul@discourseonubuntu2004-s-1vcpu-2gb-intel-lon1-01:/var/discourse$ 

Thanks for any help.

1 Like

Can someone please check this plugin. I have the same issue like the guy above me. I get some errors while trying to build it, apparently it is broken since 2.9.0 beta 4 and higher.

I could provide some logs but it would be better if the creator checks a fresh discourse installation and then try to build it, because I tested this on an existing discourse installation as well as a fresh one, it always fails to build.

I followed exactly the provided steps in the initial post.

  1. Install the Landing Pages Plugin (how to install a plugin in Discourse) .
  2. Install the Blog Landing Theme , (how to install a theme in Discourse) .
  3. Set up the Blog Landing Pages as your landing pages repository .
  4. In the Landing Pages Administration UI change the category of the “Blog” page to whatever category you want to use to run your blog.
1 Like

I’ll update this plugin to be compatible with the latest Discourse in the coming week

4 Likes

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 :wink: 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 :wink:

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.

1 Like

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