Landing Pages Plugin 🛩

[Lightwaves (Lucas)]

How to get such result? I would like to understand how this is coded through the landing page plugin. Dynamic page can come later.

[merefield (Robert)]

That’s covered in this section: https://coop.pavilion.tech/t/experimental-the-home-pages-add-on-integrate-static-content-from-landing-pages-and-add-dynamic-pages-too/3554?u=merefield#editing-simple-pages-5

(but you will first need to create your first page with the Create button).

If you need more dedicated help you can hire me or one of the team.

We can also help you with Dynamic pages.

[jenmck (jen)]

I’ve been wrapping my head around this plugin and I’m finally starting to get the hang of it.

However - we have a private Discourse instance. I hadn’t realized that by not putting a group restriction that the page would be open to anyone whether logged in or not. So, I restricted the page to only trust level 0, figuring it would be anyone logged in.

But, when visiting the page when logged out, it returns an error; what I would like instead is to go to the login page. Is that possible?

[Lightwaves (Lucas)]

I finally got the result I wanted with the sidebar and header by simply changing the settings related to enable and redirect homepage (see below screenshot).

However, when loading the same code, it didnt work as before, the category content wasn’t fetched. Not sure how to go about it.

Also tried to use the code in the example with the “simple html boxes” (see below) and got an error msg that “body is missing”.

[merefield (Robert)]

@Lightwaves

the category content wasn’t fetched.

Not sure what you mean by this?

Home pages doesn’t support any Category paths (yet, no funding/sponsor).

You are meant to either link the pages in the side bar or in a header component.

It only supports standalone pages.

the settings have to be very simple:

Note all the “blanks”.

That’s stated in the guide:

@merefield

Only the first two and page editing field are currently used:

I’ll change that to “supported”

[kOS (KilianS)]

Hi there. Is there a Idiot proof guidance for a noob like me to enable the Landingpage established via this plugin, as the Forums Homepage?

My landingpage is pointing to: “https://mydomain.com/home” I can access this fine via the url bar. Now what I miss is that when users click inside discourse on the logo at the top left, or when they just enter “https://mydomain.com” to their url bar. Them to be moved to https://mydomain.com/home instead.

[cabidop (Pablo Cabido)]

Hi, KilianS, sorry to be this late to your question but at the moment it is not possible to configure a landing page to be your homepage. If the capability gets added it will be notified here.

[merefield (Robert)]

Wait, wait, if you use the Home Pages extension you can direct the home URL to one of your landing pages within Discourse.

[Nikola_Mitrovic]

Hi Team,

We are running a self-hosted version of Discourse at my company and we’ve set up several Landing pages and display them through the Home Pages plugin, and everything works as intended as long as the pages are not restricted to a particular group.

As soon as we try to restrict a landing page to a group we just get the navigation and an empty page body. I’ve inspected the developers console and discourse logs and found the following:

• The request for a restricted landing page returns a 403 response
  

• Further processing of this requests throws a “not valid JSON” response
  

• After this, Discourse JS complains about the lack of data passed to safeHtmlContent method
  

• The last error that I am seeing is related to a VM Bug on the page
  

This completely disables SPA navigation until the user performs a hard refresh of the page (Shift + F5).

Looking at the logs, the only related entries that I could see are these two:

Do you have any ideas on how to troubleshoot this? We have make sure that our Discourse instance is updated to the latest version 3.5.0.beta2-dev .
Let me know if there is any additional info that I can provide from my end in order to get to the bottom of this issue faster.

[merefield (Robert)]

@Nikola_Mitrovic

works as intended as long as the pages are not restricted to a particular group.

Hey Nikola,

This is because this is not explicitly supported, that’s essentially a feature request.

The client this extension was originally built for didn’t require this specific functionality.

The Home Pages add-on only works with a fairly simple setup in Landing Pages.

I’d review a PR to add this feature if you have someone who can submit one?

Or you are welcome to PM me to discuss contracting me to work on it.

[Nikola_Mitrovic]

Hey Robert,

Thank you for the prompt reply. I’ll consult with my team and get back to you if we decide to fund this enhancement request.

[Steve_John]

We are getting this error after Rebuild All of the discourse. Not sure, what was changed all the pages were working fine before rebuild. Not sure, if any one else faced issue which recent rebuild

----------------Below error message on the page

Oops

The software powering this discussion forum encountered an unexpected problem. We apologize for the inconvenience.

Detailed information about the error was logged, and an automatic notification generated. We’ll take a look at it.

No further action is necessary. However, if the error condition persists, you can provide additional detail, including steps to reproduce the error, by posting a discussion topic in the site’s feedback category.

---

Checking the console, we see 505 error:

Failed to load resource: the server responded with a status of 500 (Internal Server Error)

[tobiaseigen]

Hi Steve! If I were in your place, I’d try to rebuild again from the command line. That usually works. And if it does not, you can at least scroll back up to see if an error has occurred that is preventing your site from rebuilding correctly.

Then I’d try ./discourse-doctor which can help you identify issues with your installation. Often the problem is you are running out of disk space and need to create space by deleting old docker instances (./launcher cleanup) or deleting backups.

If you have an unofficial plugin installed, that might cause a problem with updates if the plugin doesn’t play well with the latest version of discourse. You can remove or comment out the relevant lines in your app.yml and try rebuilding.

And finally, there’s the question we always have to ask.. did you install using the official install instructions? If not, then it’s going to be hard for us to support you.

[PCPal (Jelle van der Pal)]

I have the same error.
I have tried a full manual rebuild of the Discourse - it did not fix the issue.

Submitted an Issue on it’s GitHub:
Please provide Additional info here or there, whatever makes sense to the Devs:

After rebuild - Landing Pages result in error 500

[tobiaseigen]

Oh, sorry, I missed that this was specific to the landing pages plugin. I’ve moved these replies here so our friends at Pavilion who developed this plugin can look at it when they get a chance.

It’s not unusual for plugins to need a fix to remain compatible with the latest version of Discourse.

@PCPal thanks for being proactive and posting an issue on github. I think it’s fine to talk here, or you can report a bug to pavilion using their form (see first post for the link).

[Steve_John]

Awaiting fix for this regression bug from Pavilion’s team. Any ETA would be appreciated.

[PCPal (Jelle van der Pal)]

Does your Chat work?
Mine stopped.
(This Appearantly was changed in my profile settings - I need to talk to some other Admins I suppose - but seems not related to this error…)

Seems the build process when at the “precompile for desktop…” step, spits out a lot of HTML.
I’m disabling Landing Pages now and rebuilding again to see if chat works again.

Update: Tested it, again, without Landing Pages plugin - the error of HTML being dropped to the Build Terminal with the Desktop step, is gone.

[angus (Angus McLeod)]

I’ve updated the plugin to support the latest version of Discourse.

[PCPal (Jelle van der Pal)]

Thank you very much!
I run a forum for a MH-community, as a volunteer - and we, the whole team running that forum, appreciate your timely effort a lot!

[angus (Angus McLeod)]

Please let me know if you’re still experiencing any issues and I’ll address them. @mention me.